With regard to I18N-ISSUE-161: > > > >> 161: Notifications have no way to identify the language of their > >> user-visible text (title and body). Knowledge about the language is > >> often necessary for the user agent to select the right font or to > >> pronounce the text correctly - see > >> http://www.w3.org/International/questions/qa-lang-why > > > > The Working Group would like you to add the language attribute to the > > title and body elements as requested. > > This is now added, but only at a global level (same for direction). > Adding more granularity at this point before getting more deployment > experience seems unwise. > > http://dvcs.w3.org/hg/notifications/raw-file/tip/Overview.html > The Internationalization Core WG discussed your changes [1] and is satisfied by this change regarding the addition of a 'language' attribute. (Under separate cover I will respond regarding 'direction'). Thanks, Addison [1] http://www.w3.org/2012/07/25-i18n-minutes.html#item07 Addison Phillips Globalization Architect (Lab126) Chair (W3C I18N WG) Internationalization is not a feature. It is an architecture.Received on Tuesday, 31 July 2012 23:06:53 UTC
This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:33 UTC