Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change the guidelines about establishing base direction and mention ALM #136

Merged
merged 9 commits into from
Oct 17, 2024

Conversation

aphillips
Copy link
Contributor

@aphillips aphillips commented Sep 24, 2024

Fixes #8. Fixes #18.

This addresses both @stevenatkin's comment and @lkimmel's comment.

Note that I added "isolated" to the guideline about providing attributes in markup languages. I am tempted to want to add text to make isolating preferred to embedding. This section may need further review.

I also change the title of the section about strong marks, adding some text ("Strong directional marks:").


Preview | Diff

Fixes w3c#8.

This addresses both @stevenatkin's comment and @lkimmel's comment.

Note that I added "isolated" to the guideline about providing attributes
in markup languages. I am tempted to want to add text to make isolating
preferred to embedding. This section may need further review.
@aphillips aphillips requested review from xfq and r12a September 24, 2024 15:54
Copy link

netlify bot commented Sep 24, 2024

Deploy Preview for bp-i18n-specdev ready!

Name Link
🔨 Latest commit e16baf4
🔍 Latest deploy log https://app.netlify.com/sites/bp-i18n-specdev/deploys/67112e08676f4000087126a2
😎 Deploy Preview https://deploy-preview-136--bp-i18n-specdev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@aphillips aphillips changed the title Change the guidelines about establishing base direction. Change the guidelines about establishing base direction and mention ALM Sep 24, 2024
index.html Outdated Show resolved Hide resolved
@xfq
Copy link
Member

xfq commented Oct 10, 2024

Overall LGTM, but we should probably link to some background information of these characters. We don't seem to have them our website (see w3c/i18n-drafts#602). Maybe somewhere at unicode.org for now?

Co-authored-by: Fuqiao Xue <[email protected]>
index.html Outdated Show resolved Hide resolved
- Fix text to refer to third example
- Make appearance of the text go under the HTML markup to avoid wrapping
  issues
- Use `spilloverExample` style for the rendered text so it is pretty
@aphillips aphillips requested a review from xfq October 17, 2024 15:02
@aphillips aphillips merged commit 702d5e8 into w3c:gh-pages Oct 17, 2024
4 checks passed
@aphillips aphillips deleted the issue-8 branch October 17, 2024 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should also mention ALM beside LRM and RLM Change the rule for establishing base direction
3 participants