In Section 4.1, numbered item 4 discusses entries in 639-2 that require special care. The text then goes on to discuss the various cases individually in numbered paragraphs. A few comments: 1. Wrt formatting, the second-level numbering uses the same format as the top level numbering. It’s not clear to me why the second-level items need to be numbered, but if they are then formatting should be consistent with formatting practice elsewhere in the doc. E.g. compare 3.4 which uses numbers, then letters. 2. The first itemized paragraph discusses collections: ---------------- Use specific language subtags or subtag sequences in preference to subtags for language collections. A "language collection" is a subtag derived from one of the [ISO639‑5] codes that represents multiple related languages. These codes are included as primary language subtags in the registry. For example... ---------------- I find the wording creates a feel of discontinuity from the intro paragraph as it's not obvious how this relates to 639-2, particularly given the reference to 639-5. Suggested revision: ---------------- ISO 639-2 includes codes for language collections, as does [ISO 639-5]. A "language collection" code represents multiple related languages. These codes are included as primary language subtags in the registry. However, specific language subtags or subtag sequences SHOULD be used in preference to subtags for language collections. For example... ---------------- 3. The second itemized paragraph has the following: ---------------- The 'mul' (Multiple) primary language subtag identifies content in multiple languages. This subtag SHOULD NOT be used when a list of languages (such as Content-Language)... ---------------- Please give a context and reference when introducing external concepts such as Content-Language. In this case, you might say "such as MIME Content-Language headers [RFC3282]...", "such as [Content-Language] headers", or something similar. 4. Finally, the last itemized paragraph in this section discusses "i-default", which has not connection to ISO 639-2. This should not be a sub-item under item 4 on ISO 639-2, but should be a top-level item, numbered 5. Peter _______________________________________________ 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.