"Phillips, Addison" <addison at amazon dot com> wrote: > If we need to indicate that a language is a macrolanguage in the > registry, we should use a separate field. Presumably it would be > something like: > > Subtag: zh > Type: language > Encompasses: cmn, yue, wuu, ... etc. No other part of the Registry syntax requires record-jar parsers to subparse a comma-separated field. I opposed this back during the discussions that ultimately led to the Macrolanguage field, and I oppose it now. > Or perhaps: > > Subtag: zh > Type: language > Encompasses: cmn > Encompasses: yue > Encompasses: wuu > ... etc ... Much better syntax, though I maintain that the information is already in the Registry (in the records for 'cmn', 'yue', 'wuu', etc.) and that this "doubly-linked list" approach is unnecessary. > And the encompasses languages would look like: > > Subtag: cmn > Type: language // or extlang > Macrolanguage: zh As they do now. > If we were to restore the use of 'extlang', perhaps the above wouldn't > be necessary, since enclosed languages would not be of the same type > and the 'cmn' record would look more like: > > Subtag: cmn > Type: extlang > Macrolanguage: zh > Prefix: zh > > ... but we would have some enclosed languages grandfathered into the > language slot: > > Subtag: nn > Type: language > Macrolanguage: no This is what we were going to do anyway, before extlangs were removed. The Type and Prefix fields would tell how the subtag was to be used, while the Macrolanguage field would be used to offer suggestions to taggers and matchers about possibly related languages, as it is in the current draft. -- Doug Ewell * Arvada, Colorado, 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.