All: This email is the first of a series of my comments about the current matching draft. In keeping with Randy's previous requests, I'll be sending each in a separate email. In this paragraph in Section 2.1: -- In particular, the set of language tags that match a specific language-range might not all be mutually intelligible. Matching a language-range (prefix) to various language tags does not mean that it is always true that if a user understands a language identified by a certain tag, then this user will also understand all of the languages for which this tag is a prefix. The use of prefixes (and thus basic language ranges) simply allows the use of a prefix if this is the case. -- ...the final sentence seems particular lame. I think it would be better to say: -- The use of prefixes (and thus basic language ranges) allows languages to be selected as if this were always the case. In most cases, the language range and the set of language tags associated with it are mutually intelligible enough to be useful and this form of matching has historically been to most prevalent. -- Addison Addison P. Phillips Globalization Architect, Quest Software http://www.quest.com Chair, W3C Internationalization Core Working Group http://www.w3.org/International Internationalization is not a feature. It is an architecture.
_______________________________________________ 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.