-
Notifications
You must be signed in to change notification settings - Fork 4
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
More about directions #75
Comments
(fixed syntax of |
Note that RDF Concepts has a more general discussion of BIDI similar to what you pointed to in the ePub spec, which has been reviewed by the I18N group. But, we can add further explaination of |
Wouldn't it also be useful to have an example where initial direction alone is insufficient? I think that the examples involve a RTL language with embedded LTR strings that are separated by neutral characters. |
Concepts expands more on this, but it could use a langString example which dominates directionality based on the first character. |
@pfps, see w3c/rdf-concepts#109, Specifically https://github.com/w3c/rdf-concepts/blob/0957e914d33cb39326aa6828d84b47fb0056530d/spec/index.html#L860-L864,
|
* Use better BIDI examples. Fixes #75. --------- Co-authored-by: Ted Thibodeau Jr <[email protected]>
* Add a further explanation on `ltr` and `rtl` (based on ePub). Suggested by w3c/rdf-turtle#75. * Add example of displaying right-to-left text in its natural order vs the way it is stored in memory. * Update I18N description of implicit initial text direction * Use I18N-Glossary instead of UAX9 and UAX15 references. --------- Co-authored-by: Andy Seaborne <[email protected]> Co-authored-by: Addison Phillips <[email protected]> Co-authored-by: Ted Thibodeau Jr <[email protected]>
In §2.5.1 Quoted Literals as part of the examples, it may be better to use a "real" example for directions (the ones listed among the examples are really superfluous). E.g.,
show:218 show:blurb "HTML و CSS: تصميم و إنشاء مواقع الويب"@ar--rtl.
or:
show:218 show:blurb "HTML היא שפת סימון."@he--rtl
Maybe it is also important add a note whereby the text the value field in turtle represents the text as it is stored in memory and not as it is supposed to be displayed. (We spent quite some time to get it right in the spec for the publication manifest, feel free to copy and paste.)
(In my experience, getting the spec examples right bidirectional text is a challenge; you should probably ask the i18n guys to check it.)
The text was updated successfully, but these errors were encountered: