Doug Ewell scripsit: > > %% > > Type: grandfathered > > Tag: i-default > > Description: Default Language > > Added: 1998-03-10 > > %% > > I oppose messing around with this. It exists because of RFC 2277, which > specified its use for a very limited set of circumstances. Trying to > normalize this one away might be more messy than the results would > justify. I agree. i-default is a very special case that should be left alone; it's a protocol element. > > %% > > Type: grandfathered > > Tag: i-mingo > > Description: Mingo > > Added: 1997-09-19 > > %% > > I really don't understand why this is not in ISO 639-3 to begin with. Because it's almost certainly (we can't be sure, as it's dead) mutually intelligible with Seneca; the Mingo are descended from Seneca that became politically separated from the Seneca Nation two or more centuries ago. If we want to deprecate it, we should replace it with see-mingo. > I see no point in doing anything with this. "zh-min" was apparently > proposed and registered under the faulty assumption that it was > necessary as a basis for "zh-min-nan", which was the tag really wanted. > Any content tagged "zh-min", and I doubt there is any although you never > know, is almost certainly mistagged anyway, and might not even be Min > Nan. I agree. It's garbage, and it's my fault. -- John Cowan cowan at ccil.org http://ccil.org/~cowan Female celebrity stalker, on a hot morning in Cairo: "Imagine, Colonel Lawrence, ninety-two already!" El Auruns's reply: "Many happy returns of the day!" _______________________________________________ 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.