Frank Ellermann <nobody at xyzzy dot claranet dot de> wrote:
The Preferred-Values for the others are explicitly listed to show how the tags were mapped. The judgment of the WG is involved, although I think in these cases it will be unassailable. In the case of "zh-min" the judgment of the WG is that (a) the tag is deprecated because it doesn't refer to a real language and (b) there is no Preferred-Value because no alternative tagging possibility exists for this non-language.Yes, and that has to be noted for readers of 4645bis, they've no clue how that happened, because it's not obviously triggered by the 639-3 input.
OK, I will add this.
[yi-latn]Case is not significant in RFC { 1766, 3066, 4646, 4646bis } language tags. There happen to be conventions for casing, and the Registry uses those conventions, but they are not normative.In another message I've quoted MUSTard, but admittedly that was about Script records, not directly for all script subtags elsewhere.
I found the passage in RFC 4646 to which you might have been referring, in Section 3.1 (which I swear is longer by itself than some RFCs):
"The 'Subtag' or 'Tag' field MUST use lowercase letters to form the subtag or tag, with two exceptions. Subtags whose 'Type' field is 'script' (in other words, subtags defined by ISO 15924) MUST use titlecase. Subtags whose 'Type' field is 'region' (in other words, subtags defined by ISO 3166) MUST use uppercase. These exceptions mirror the use of case in the underlying standards."
This actually says that all "Tag" fields in the Registry, meaning grandfathered and redundant tags, must be all-lowercase. Since grandfathered and redundant tags are atomic, and not composed of subtags (though redundant tags are equivalent to a sequence of valid subtags), this means "yi-latn" is one of the few redundant tags to be cased correctly!
Seriously, I think this passage is in error with respect to "tags" and needs to be modified to say that redundant tags are either:
(a) cased as they were in the RFC 3066 registry (what I did), or(b) cased as if they were composed of individual subtags, using the casing conventions for those subtags (what you want).
The museum survives it if one yi-latn is fixed to yi-Latn. :-)
s/The museum survives it/The floodgates open/But if the wording in Section 3.1 is changed to option (b) above, I'll be happy to make this change for you.
-- Doug Ewell Fullerton, California, USA http://users.adelphia.net/~dewell/ RFC 4645 * UTN #14 _______________________________________________ Ltru mailing list Ltru at ietf.org https://www1.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.