** >> p1, 3: Need update to later version of specs: Unicode, CLDR.
Especially with requested updates to CLDR.
** >> p2, 4.3: Does not state what the cultural requirements are. Only
knowing the 'people involved' give me any expectation of the output.
** >> Much specification of how the API machinery operates, but not
about the expected output.
** >> p16 11.3.2, The tailoring docs are moving to UTR#35 from UTS#10 as
of last UTC. May be better to refer to UTR#35 for tailoring.
** >> p21-22, p25, p26: again, need more examples to evaluate this.
** >> p30, 14: Should harmonize the base localeCompare, toLocaleString,
etc with default locale behavior.
If a locale isn't specified, shouldn't the behavior be similar to using
the Collator, Formatter, etc with the default locale?
Comments to 1st Edition / Draft 3 May 2012
These are very similar to previous comments.
** >> p1, 3: Need update to later version of specs: Unicode, CLDR.
Especially with requested updates to CLDR.
** >> p2, 4.3: Does not state what the cultural requirements are. Only
knowing the 'people involved' give me any expectation of the output.
** >> Much specification of how the API machinery operates, but not
about the expected output.
** >> p16 11.3.2, The tailoring docs are moving to UTR#35 from UTS#10 as
of last UTC. May be better to refer to UTR#35 for tailoring.
** >> p21-22, p25, p26: again, need more examples to evaluate this.
** >> p30, 14: Should harmonize the base localeCompare, toLocaleString,
etc with default locale behavior.
If a locale isn't specified, shouldn't the behavior be similar to using
the Collator, Formatter, etc with the default locale?
Comments to 1st Edition / Draft 3 May 2012
These are very similar to previous comments.
** >> p1, 3: Need update to later version of specs: Unicode, CLDR.
Especially with requested updates to CLDR.
** >> p2, 4.3: Does not state what the cultural requirements are. Only
knowing the 'people involved' give me any expectation of the output.
** >> Much specification of how the API machinery operates, but not
about the expected output.
** >> p16 11.3.2, The tailoring docs are moving to UTR#35 from UTS#10 as
of last UTC. May be better to refer to UTR#35 for tailoring.
** >> p21-22, p25, p26: again, need more examples to evaluate this.
** >> p30, 14: Should harmonize the base localeCompare, toLocaleString,
etc with default locale behavior. If a locale isn't specified, shouldn't the behavior be similar to using the Collator, Formatter, etc with the default locale?