(editor hat)
~Addison
>
> 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.
This is an idiosyncrasy of the XML: I didn't specify a format on the list and the default is "numbers". I changed it to "symbols" (bullets, essentially) to be consistent with the other items in Section 4.1.
>
> 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...
> ----------------
I think the first sentence is somewhat artificial (as is the original para): you can't tell the source from the registry anyway.
Your suggested revision doesn't follow the pattern for other items here, which all start with specific advice. Thus I modified the para to read (note that I quote the whole thing):
<t>Use a specific language subtags or sequences of subtags in preference to subtags for language collections. A "language collection" is a subtag that represents multiple related languages. These codes, which are the subset of <xref target="ISO639-2"></xref> that is also defined in <xref target="ISO639-5"></xref>, are included as primary language subtags in the registry. The 'Description' field of a collection typically includes the word "languages" to indicate that it represents more than one language. For example, these subtags include "Chamic languages" ('cmc'), "Algonquin languages" ('alg'), and "Germanic languages" ('gem'). Each collection is also represented by subtags for the individual languages. In the case of 'cmc', the registry also contains the values for each of the approximately ten individual languages represented by this collective code. The subtag 'gem' helps illustrate this further: since it is interpreted inclusively, content tagged with "en" (English), "de" (German), or "gsw" (Swiss German, Alemannic) could also (but SHOULD NOT) be tagged with "gem" (Germanic languages). Obviously, the languages in a collection are frequently not mutually intelligible, as this example demonstrates. Subtags derived from collection codes MAY be used when more specific language information is not available. Note that matching implementations generally do not understand the relationship between the collection and its encompassed languages, and so users ought not assume a subtag based on a language collection is a useful means for selecting content in its encompassed languages.</t>
>
>
>
> 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.
DONE. New text reads:
<t>The 'mul' (Multiple) primary language subtag identifies content in multiple languages. This subtag SHOULD NOT be used when a list of languages or individual tags for each content element can be used instead. For example, the 'Content-Language' header (<xref target="RFC3282"></xref>) allows a list of languages to be used, not just a single language tag.</t>
>
>
>
> 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.
DONE.
_______________________________________________
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.