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

Re: Bidir text and Unicode

From: Ivan Herman <ivan@w3.org>
Date: Tue, 27 Jun 2017 17:45:12 +0200
Cc: W3C Publishing Working Group <public-publ-wg@w3.org>
Message-Id: <D87105C3-2175-4D03-8FCE-5101FF579F07@w3.org>
To: Laurent Le Meur <laurent.lemeur@edrlab.org>

> On 27 Jun 2017, at 17:27, Laurent Le Meur <laurent.lemeur@edrlab.org <mailto:laurent.lemeur@edrlab.org>> wrote:
> 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?

That is indeed the core of the problem as I understand it. B.t.w., another resource is:

https://www.w3.org/International/articles/inline-bidi-markup/ <https://www.w3.org/International/articles/inline-bidi-markup/>

However… although it may be good to have the issue recorded, the exact solution depend on other issues, mainly the kind of serialization that we will use, and we just agreed that this decision will have to be taken later. (Eg, JSON-LD is somewhat different insofar as it reflects RDF and RDF is not really good for this either…). Any solution will have to be seen in a larger context because this is an issue that is not publication specific either; the I18N people may have a preferred general solution for JSON, or they will have one…


> Laurent Le Meur

Ivan Herman, W3C
Publishing@W3C Technical Lead
Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>

Received on Tuesday, 27 June 2017 15:45:30 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:49:04 UTC