[Ltru] Review of 4646bis-10, sections 1 to 3.4

[John Cowan <[e-mail]>]

Yet another freakin' de novo review of 4646bis draft 10, sections 1
through 3.4.  More review will follow.  The following two changes are
substantive:

1) I suggest adding this to 2.2.6 (extensions) after the first sentence:

        They are intended to identify information which is commonly used
        in association with language tags but is not part of language
        identification.

2) In 3.1.2, I'd prefer to say that implementations MUST rather than
SHOULD ignore undefined fields in the registry.  There is no reason why
implementations should not be required to be liberal in what they accept.


The remaining changes are all editorial:

In 2.2, the term "code" is defined to refer to a value defined in an
external standard.  We should, pervasively throughout the document,
change this to "code element", which is proper ISO terminology.  (For ISO,
"code" means the whole list.)

The final graf in 2.2 should be bulleted like its predecessors.

In 2.2.x, there are numbered points like "X subtags MUST follow any
... subtags and MUST precede any ... subtags".  The numbers used are #2 in
2.2.3, #1 in 2.2.4, #2 in 2.2.5, #9 in 2.2.6, #3 in 2.2.7.  These should
all be moved to #1 in each list, and minor wording variations removed.

2.2.4(3)(C) uses the phrase "with ambiguous ISO 3166 alpha-2 codes".
This is not very clear to those who don't know the history, and should
be expanded to something like "whose alpha-2 code was formerly (since
<Date B>) associated with a different country".  Someone will have to
look up what the cutoff date was -- I forget.

2.2.5:  s/suitable to form/suitable for forming/

2.2.8: s/current registered/currently registered/

3.1.1: change the definition of folding to "Folding is always done on
Unicode default grapheme boundaries".  That says what the current text
says, and also prohibits folding in the middle of a Hangul syllable
written as separate jamo.

3.1.2:  In the explanation of "Preferred-Value", the first two bullet
points say "Preferred-Value contains" but the third does not.

3.1.3:  "The 'Subtag' field MUST use lowercase letters" says too much;
it implicitly forbids digits.  What is meant is "The 'Subtag' field
MUST NOT use uppercase letters".  Adding "all" before "uppercase" in
the sentence about region subtags will clarify it.

3.1.4: s/For records taken/For subtags taken/.

3.1.4:  s/English localized names/localized English names/.

3.1.7:  s/a prefix a prefix/a prefix/.

3.1.4: it's not about countries changing their official names, as official
names aren't even in the registry.  (Hands up all those who can say the
official name of the U.S.  without looking it up.)  Remove "official".

3.4(16): s/should it be possible/should it become possible/.

-- 
John Cowan <[e-mail]>             http://www.ccil.org/~cowan
Today an interactive brochure website, tomorrow a global content
management system that leverages collective synergy to drive "outside of
the box" thinking and formulate key objectives into a win-win game plan
with a quality-driven approach that focuses on empowering key players
to drive-up their core competencies and increase expectations with an
all-around initiative to drive up the bottom-line. --Alex Papadimoulis


_______________________________________________
Ltru mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/ltru