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? Kenneth > -----Original Message----- > From: Phillips, Addison [mailto:addi...@lab126.com] > Sent: Thursday, March 19, 2015 6:32 PM > To: email@example.com > Cc: public-i18n-c...@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.