![]() all: IETF BCP 47/RFC 5646 language tags: all language codes reserved for private/local use (`qaa`–`qtz`) are now supported. all: IETF BCP 47/RFC 5646 language tags: reduced the maximum number of extended language subtags that are present in a valid tag from 3 to 1 in compliance with RFC 5646 section 2.2.2. all: IETF BCP 47/RFC 5646 language tags: all in the IANA language subtag registry are now supported, even those marked as deprecated and of type 'grandfathered'. all: IETF BCP 47/RFC 5646 language tags: all lists of valid subtags have been updated from their respective authoritative sources. all: IETF BCP 47/RFC 5646 language tags: all deprecated subtags from theIANA language subtag registry are now supported. all: IETF BCP 47/RFC 5646 language tags: grandfathered language tags are now supported. In this example the IETF language element would be set to `yue` and the corresponding legacy element to `chi`. ![]() ![]() However, there is an extlang subtag `yue` with a valid prefix of `zh` ("Chinese"), and for "Chinese" there is an ISO 639-2 language code: `chi`. For example, "Yue Chinese" = `yue` is not part of ISO 639-2. all: IETF BCP 47/RFC 5646 language tags: when deriving the legacy language element codes to use a language tag's ISO 639 code is also potentially interpreted as an & its prefix is used as the legacy language code. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |