W3C home > Mailing lists > Public > public-i18n-core@w3.org > January to March 2015

RE: [appmanifest] No direction metadata for 'name' (etc.) [I18N-ISSUE-416]

From: Christiansen, Kenneth R <kenneth.r.christiansen@intel.com>
Date: Fri, 20 Mar 2015 08:08:14 +0000
To: "Phillips, Addison" <addison@lab126.com>, "public-webapps@w3.org" <public-webapps@w3.org>
CC: "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Message-ID: <60F18B024F3783428EBEA0B7D7DF31CA288CDB47@IRSMSX108.ger.corp.intel.com>
We are tracking our issues in GitHub. Maybe it makes sense filling them there instead/as well?

We now have a ´lang´ field. I assume that is not enough?


> -----Original Message-----
> From: Phillips, Addison [mailto:addison@lab126.com]
> Sent: Thursday, March 19, 2015 6:32 PM
> To: public-webapps@w3.org
> Cc: public-i18n-core@w3.org
> Subject: [appmanifest] No direction metadata for 'name' (etc.) [I18N-ISSUE-
> 416]
> From Tracker:
> http://www.w3.org/International/track/issues/416

> http://www.w3.org/TR/2015/WD-appmanifest-20150212/#name-member

> The 'name' manifest member does not provide a means of indicating the
> base direction of the name string. This is equivalent to extracting the 'dir'
> attribute appropriate for the HTML <title> element's scope and may be
> necessary for correct rendering of bidirectional content.
> For example, the author might need to set the base direction explicitly, since
> the Unicode paragraph detection algorithm can be fooled by a paragraph that
> starts with a strong LTR character, but is actually a RTL paragraph (or vice
> versa), eg. "نشاط التدويل is how you say 'i18n Activity' in Arabic."
> It would be helpful to the author to be able to set the default base direction
> for a whole manifest file to rtl.
> Addison Phillips
> Globalization Architect (Amazon Lab126)
> Chair (W3C I18N WG)
> Internationalization is not a feature.
> It is an architecture.

Received on Friday, 20 March 2015 08:08:45 UTC

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