A reply to Norbert's reply and a fresh comment. The fresh comment first:
It would be useful to add addLikelySubtags/removeLikelySubtags from UTS #35 C.10 (http://www.unicode.org/reports/tr35/#Likely_Subtags), which is helpful when preparing locale lists for use with legacy language tags (e.g. zh-CN vs. zh-Hans-CN). > > > > Section 6.2.4 DefaultLocale > > o We would like to be able to return a priority list here and not just a > > single > item. While many implementations may have just a single item, those that are > built on top of Windows 8 will have available a list of languages that the > user > has declared to understand instead of just a default user locale that we have > had up until now. Since this is internal, I believe changing the name to > DefaultLocales and returning an array will allow implementations to do either: > > > > The DefaultLocales abstract operation returns an array of string values > representing a priority list of the structurally valid (6.2.2) and > canonicalized > (6.2.3) BCP 47 language tags for the host environment in descending order of > priority. This may return a single item representing the current locale. > > To me the default locale of an implementation and the user's preferred > languages are two different things. The default locale must be supported and a > single locale so that we can fall back to it when none of the requested > locales > are supported. The user's preferred languages can be several, and they may > include languages that an implementation doesn't support. Often the scripter needs to know what the user-agent is requesting in Accept-Language (et al). So I can see providing DefaultLocales as requested, as long as the actual host system default can be identified. Addison Addison Phillips Globalization Architect (Lab126) Chair (W3C I18N WG) Internationalization is not a feature. It is an architecture. _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
