W3C home > Mailing lists > Public > public-publ-wg@w3.org > June 2017

Bidir text and Unicode

From: Laurent Le Meur <laurent.lemeur@edrlab.org>
Date: Tue, 27 Jun 2017 17:27:03 +0200
Message-Id: <D4F54EAD-B42B-4755-A834-6F84BABF6D0E@edrlab.org>
To: W3C Publishing Working Group <public-publ-wg@w3.org>
A question was raised during the F2F meeting in NYC, about the proper internationalization of UTF-8 metadata values (eg. the book title). 

I quote Ivan from the minutes: "On the i18n side, we will need to be careful about ids, uris, iris, etc. w/respect to i18n char-sets. Another area we need to be careful about is metadata, which also have issues with the char-sets for the actual text content. One example is mixing bidi text in the metadata content.",  

Reading http://www.iamcal.com/understanding-bidirectional-text/ <http://www.iamcal.com/understanding-bidirectional-text/>, I see here a use of the HTML dir attribute, which will not be available natively in a JSON manifest; so we may have to create a JSON dir attribute representing document order. I also see the "implicit marker characters" (Left-to-Right Mark and Right-to-Left Mark) which help tailoring the direction of "neutral" characters. And the existence of "explicit markers" which describe a local text direction. 

Therefore it appears that the only item we need to add to a JSON manifest to assure proper rendering of international text is a "document order" (a dir attribute that can be injected in the HTML rendering of the metadata values).

Any thought on this before I create a Github issue on the subject? 

Laurent Le Meur
Received on Tuesday, 27 June 2017 15:38:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:52:11 UTC