Internationalization: Issues with upgrading to UTS 35 version 21
addison at lab126.com
Thu Jul 19 16:11:53 PDT 2012
> > It's a bit late to add any special handling for these new keys and values to
> edition 1 of the Internationalization API Specification. I propose that for edition
> 1 we declare them unsupported:
> > 1) Add "kr" to the list of "not allowed" values in the NOTE in section 10.2.3.
> > 2) For "native", "traditio", and "finance", add a sentence "The array that is the
> value of the 'nu' property of any locale property of [[localeData]] must not
> include the values 'native', 'traditio', or 'finance'." to the description of
> [[localeData]] in section 11.2.3.
> > We can then discuss better solutions for edition 2 of the spec.
> > Comments?
> Sounds like the right answer to me.
Ur... except that we use the 'kr' feature, Rich... :-)
I would prefer a standard that ignores unrecognized values rather than barfs on them ("now allowed"). I'll admit that I didn't go look at section 10.2.3 to see if that's what happens to disallowed values.
More information about the es-discuss