w3c
Change the guidelines about establishing base direction and mention ALM
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:").
// TODO: add the 061C graphic
Deploy Preview for bp-i18n-specdev ready!
| Name | Link |
|---|---|
| Latest commit | e16baf45b0916a9852a0b756d63e362c2dea4d78 |
| 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...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
Overall LGTM, but we should probably link to some background information of these characters. We don't seem to have them our website (see https://github.com/w3c/i18n-drafts/issues/602). Maybe somewhere at unicode.org for now?
