Symbols explainer post-workshop#323
Conversation
|
Per the call, we want a hyperlink in the intro that demonstrates that people have been using the Bliss language for some time. |
Per the call, the three intro bullets should introduce the primary sections to come later, as equals. So no need to link to just one.
|
Some other notes from the call:
|
|
I've made the couple of final tweaks we agreed, so I think it's time to mark this as ready for review, and merge it soon. The registry section does need better integration into the rest of the doc, and we have various other parts highlighted for further work, but merging this provides us with a good basis for those more focused additions/changes, which we could do in separate PRs. |
Delete line, no longer applicable.
Delete line
| We're working closely with BCI on this specification, and the W3C AAC Symbol Registry (more details below). | ||
| The W3C AAC Symbol Registry provides the code points used to identify a given concept. | ||
|
|
||
| * **Use of the `<ruby>` element for presentation—with a `lang=zbl` attribute to indicate this is a symbol.** |
There was a problem hiding this comment.
| * **Use of the `<ruby>` element for presentation—with a `lang=zbl` attribute to indicate this is a symbol.** | |
| * **Use of the `<ruby>` element for presentation—with a [`lang=zbl`](https://www.loc.gov/standards/iso639-2/php/code_list.php) attribute to indicate this is a symbol.** |
3 participants
Update the Symbols explainer.
Preview: https://github.com/w3c/adapt/tree/symbols-explainer-post-workshop/explainers/symbols.md
Closes #295