Polyfill: Allow alternate era codes #2901
Assignees
Labels
no-spec-text
PR can be ignored by implementors
non-prod-polyfill
THIS POLYFILL IS NOT FOR PRODUCTION USE!
Milestone
Comments
ptomato
added
non-prod-polyfill
ptomato
added a commit
to ptomato/test262
that referenced
this issue
Sep 9, 2024
As of the current state of the Intl Era and Month Codes proposal, https://tc39.es/proposal-intl-era-monthcode/#sec-temporal-canonicalizeeraincalendar the canonical name of this era is "japanese". See: tc39/proposal-temporal#2901
ptomato
added a commit
that referenced
this issue
Sep 10, 2024
As of the current state of the Intl Era and Month Codes proposal, the eras table in https://tc39.es/proposal-intl-era-monthcode/#table-eras has a canonical name for each era, and a number of aliases which should also be accepted. Legacy ICU names such as "era0" should not be accepted, although they still need to be handled when using Intl.DateTimeFormat to convert dates. Closes: #2901
ptomato
added a commit
to ptomato/test262
that referenced
this issue
Sep 10, 2024
As of the current state of the Intl Era and Month Codes proposal, https://tc39.es/proposal-intl-era-monthcode/#sec-temporal-canonicalizeeraincalendar the canonical name of this era is "japanese". See: tc39/proposal-temporal#2901
ptomato
added a commit
to ptomato/test262
that referenced
this issue
Sep 10, 2024
As of the current state of the Intl Era and Month Codes proposal, https://tc39.es/proposal-intl-era-monthcode/#sec-temporal-canonicalizeeraincalendar the canonical name of this era is "japanese". See: tc39/proposal-temporal#2901
ptomato
added a commit
to tc39/test262
that referenced
this issue
Sep 10, 2024
As of the current state of the Intl Era and Month Codes proposal, https://tc39.es/proposal-intl-era-monthcode/#sec-temporal-canonicalizeeraincalendar the canonical name of this era is "japanese". See: tc39/proposal-temporal#2901
ptomato
added a commit
that referenced
this issue
Sep 10, 2024
As of the current state of the Intl Era and Month Codes proposal, the eras table in https://tc39.es/proposal-intl-era-monthcode/#table-eras has a canonical name for each era, and a number of aliases which should also be accepted. Legacy ICU names such as "era0" should not be accepted, although they still need to be handled when using Intl.DateTimeFormat to convert dates. Closes: #2901
ptomato
added a commit
that referenced
this issue
Sep 10, 2024
As of the current state of the Intl Era and Month Codes proposal, the eras table in https://tc39.es/proposal-intl-era-monthcode/#table-eras has a canonical name for each era, and a number of aliases which should also be accepted. Legacy ICU names such as "era0" should not be accepted, although they still need to be handled when using Intl.DateTimeFormat to convert dates. Closes: #2901
ptomato
added a commit
that referenced
this issue
Sep 11, 2024
As of the current state of the Intl Era and Month Codes proposal, the eras table in https://tc39.es/proposal-intl-era-monthcode/#table-eras has a canonical name for each era, and a number of aliases which should also be accepted. Legacy ICU names such as "era0" should not be accepted, although they still need to be handled when using Intl.DateTimeFormat to convert dates. Closes: #2901
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'd be nice if the polyfill accepts the era codes from https://tc39.es/proposal-intl-era-monthcode/, so that cross-implementation testing doesn't require manually adjusting era codes.
The text was updated successfully, but these errors were encountered: