- 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>
Received on Monday, 25 June 2018 18:03:30 UTC
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 https://www.w3.org/International/wiki/BidiControlsAndPlainStrings 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 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:30 UTC