We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
(split off from #136, starting at #136 (comment))
The N3 spec boldly cites new ways to specify text-direction of language-tagged literals:
"الرجل العنكبوت"^^i18n:ar-eg_rtl
[ rdf:value "الرجل العنكبوت" ; rdf:language "ar-eg" ; rdf:direction "rtl" ]
As @gkellogg says "There are arguments against i18n and Compound Literals".
The text was updated successfully, but these errors were encountered:
BTW, if I add lang name ttl to the first code block above, the whole line is written RTL:
ttl
Magic? No, just some quirk of Github's syntax highlighter. I pity Arabic semantic web developers :-)
Sorry, something went wrong.
We already have an ongoing issue to track this work: #127
No branches or pull requests
(split off from #136, starting at #136 (comment))
The N3 spec boldly cites new ways to specify text-direction of language-tagged literals:
As @gkellogg says "There are arguments against i18n and Compound Literals".
The text was updated successfully, but these errors were encountered: