John Emmons has provided the following comment on the date and time format component names used in Intl.DateTimeFormat objects:
Since the spec states that CLDR data is the recommended source for
implementation, I would proposed that the allowed values in Table 3, Section
12.1.1.1 be modified to be identical with the names in CLDR, so that there is
no confusion, and that if CLDR were to add additional lengths over time, we
could do so with no confusion for implementers. Also, examples from English
would be helpful here. I would propose changing as follows:
( conforming to the upcoming CLDR 22 release )
Weekday - ( wide (Sunday) - abbreviated (Sun) - Short (Su) - Narrow (S) )
Era - wide - abbreviated - narrow
Month - "2-digit", "numeric", "wide", "abbreviated", "narrow"
John Emmons has provided the following comment on the date and time format component names used in Intl.DateTimeFormat objects:
> Since the spec states that CLDR data is the recommended source for
> implementation, I would proposed that the allowed values in Table 3, Section
> 12.1.1.1 be modified to be identical with the names in CLDR, so that there is
> no confusion, and that if CLDR were to add additional lengths over time, we
> could do so with no confusion for implementers. Also, examples from English
> would be helpful here. I would propose changing as follows:
> ( conforming to the upcoming CLDR 22 release )
>
> Weekday - ( wide (Sunday) - abbreviated (Sun) - Short (Su) - Narrow (S) )
> Era - wide - abbreviated - narrow
> Month - "2-digit", "numeric", "wide", "abbreviated", "narrow"
For a bit of discussion, see
https://bugs.ecmascript.org/show_bug.cgi?id=442
Comments?
Thanks,
Norbert
John Emmons has provided the following comment on the date and time format component names used in Intl.DateTimeFormat objects:
For a bit of discussion, see ecmascript#442
Comments?
Thanks, Norbert