W3C home > Mailing lists > Public > public-i18n-core@w3.org > April to June 2018

RE: [I18N-ACTION-702] Bidi controls 1-pager

From: Phillips, Addison <addison@lab126.com>
Date: Mon, 25 Jun 2018 18:03:01 +0000
To: "public-i18n-core@w3.org" <public-i18n-core@w3.org>, "public-i18n-arabic@w3.org" <public-i18n-arabic@w3.org>
Message-ID: <29bd8938095f4bafb9bd4213fa1aa320@EX13D08UWB002.ant.amazon.com>
Getting the ALREQ address correct this timeā€¦

From: Phillips, Addison
Sent: Monday, June 25, 2018 10:56 AM
To: public-i18n-core@w3.org; 'public-i18n-alreq@w3.org' <public-i18n-alreq@w3.org>
Subject: [I18N-ACTION-702] Bidi controls 1-pager


At the above link, please find the wiki page I started to address the action item mentioned in the subject line.

Some context for the ALREQ folks: some time ago we were asked about whether the Unicode bidi isolating controls (LRI/RLI/FSI and the corresponding PDI) should automatically and consistently be added to *all* strings in external systems, such as content management systems, resource files, javascript, and so forth. This document is an attempt to set down the pros/cons of doing that versus the more traditional use of external metadata.

I welcome comments/additions/suggestions. Please send email to the public-i18n-core@ list (or to me privately if you prefer).


Addison Phillips
Principal SDE, I18N Architect (Amazon)
Chair (W3C I18N WG)

Internationalization is not a feature.
It is an architecture.

Received on Monday, 25 June 2018 18:03:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:02:23 UTC