Mark Davis wrote: >>> Note: I think all the grandfathered tags should be lowercased, for >>> consistency, since their subtags are not formally analyzable.] >> >> True, although they all work correctly. >> >> (retrieves hat, dusts is slightly) >> >> DONE. Therefore, I made an edit so that the casing rules read: >> >> -- >> In this format, all subtags, including all those following singletons >> (that is, in extension or private-use sequences) are in lowercase. >> The >> exceptions to this are: all other non-initial two-letter subtags are >> uppercase and all other non-initial four-letter subtags are >> titlecase. >> -- > > I can live with that. But then also change > > "sgn-BE-fr" / "sgn-BE-nl" / "sgn-CH-de" > =>"sgn-BE-FR" / "sgn-BE-NL" / "sgn-CH-DE" I disagree with systematically normalizing the capitalization of grandfathered tags. They are grandfathered and shouldn't be touched. If we want to say that capitalization of tags doesn't matter, then we should not create this unnecessary diff as though it did matter. In particular, tags like "sgn-BE-fr" are grandfathered because they could not possibly fit the ABNF. Changing the capitalization of such tags in the Registry might give the impression that their syntax has been thereby legitimized in some way, when in fact all it does is make the tags conform to a distillation of the capitalization rules for regular tags. Also, though I haven't checked thoroughly, I'm sure there are some examples somewhere in the draft of private-use tags and subtags and extensions with "non-standard" capitalization, and this is a Good Thing, since the meaning of these subtags is determined outside this BCP, and might be clearer if capitalized in a "non-standard" way. -- Doug Ewell * Fullerton, California, USA * RFC 4645 * UTN #14 http://www.ewellic.org http://www1.ietf.org/html.charters/ltru-charter.html http://www.alvestrand.no/mailman/listinfo/ietf-languages ˆ _______________________________________________ Ltru mailing list Ltru at ietf.org https://www.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.