UTF-8, by itself, cannot fully solve this for bidirectional cases: when the same text includes both a ltr and a rtl text the overall direction has to be specified "outside" the full text. [1] describes the issue for the HTML case. We will have to see what will be relevant for our case How to properly code that in JSON for a string is not obvious; in RDF it is even worse (RDF cannot have a string as subject). This is something we will have to look further when the time comes... Ivan [1] https://www.w3.org/International/articles/inline-bidi-markup/ On 10 Jan 2018, 18:39 +0100, Hadrien Gardeur <hadrien.gardeur@feedbooks.com>, wrote: > > > The I18N group will (as they did in that thread for Web Annotations) require the availability of both values. It's why there is both `lang` and `dir` in Web Annotations, Web App Manifest, etc. > > > > > > So. Worth reconsidering. > > > > This is a bigger issue though than any specific format. This is something that should be ideally dealt with at an UTF-8 level. > > > > I know that there's something in JSON-LD/RDF for handling languages, is there anything about direction as well?
Received on Thursday, 11 January 2018 08:00:16 UTC