Language Tags and Locale Identifiers for the World Wide Web
"Language Tags and Locale Identifiers" (LTLI)
- LTLI describes mechanisms for identifying or selecting the language of content or locale preferences used to process information using
Web technologies
- Relies on RFC 3066bis and RFC 3066bis Matching (together: BCP 47)
- About these: hear next talk from Richard
"Language Tags and Locale Identifiers" (LTLI)
- Language Identification:
xml:lang, hreflang (HTML), language property (XSL), ...
- Locale identification: e.g. within the CLDR project
- Application for LTLI: multi-locale operation of Web Services, locale negotiation
- Out of scope: LTLI does *not* define locale formats / locale data. For this: see e.g. CLDR.
Current discusion topics for LTLI
- Relation between language identifiers (BCP 47) and locale identifiers:
- BCP 47 as the core of locale identifiers? or:
- locale and language identificiation completely independent?
- Issues: language unrelated locale information like time zone does not need BCP 47 as a core
Current discusion topics for LTLI
- What other information except language is necessary for a locale ? E.g.: default time zone, currency
- How to cope with the difference between existing locale identifiers and locale identification relying on BCP 47. Example: Java underscore
"_" versus BCP 47 hyphen "-"
