search

tc39 / proposal-intl-era-monthcode

To specify necessary details about era, eraYear and monthCode usage with Temporal in internationalization setting (for calendars other than "iso8601").
https://tc39.github.io/proposal-intl-era-monthcode
MIT License
3 stars 3 forks source link

Is CLDR ok for TC39 to define era code? #7

Open FrankYFTang opened 1 year ago

FrankYFTang commented 1 year ago

During 2022-12-01 TC39 meeting, Andrew Paprocki (API) raise the following issues/questions: "Just wondering, if was CLDR like the like the people working on that? I mean, have they been posed? The question, I mean if there are they against creating identifiers for these or if we chose the solution for it, are they okay with it? Do they see in…"

FrankYFTang commented 1 year ago

Issue filed in CLDR https://unicode-org.atlassian.net/browse/CLDR-16185 I will talk to CLDR TC to discuss with them ASAP. @sffc

FrankYFTang commented 1 year ago

@apaprocki

FrankYFTang commented 1 year ago

This issue has been discussed in CLDR TC on Dec 7 2022, and here is the conclusion from that meeting both @ffc and I @FrankYFTang joined

" CLDR TC meeting 2022-10-07

CLDR will create and maintain stable string era identifiers.

Initially keep indices that we have now, but go ahead and define stable string era identifiers, and potentially migrate to use them in the future.

CLDR will establish a small adhoc working group to develop the proposal on how to move forward.

Once the proposal is ready, please change the ticket status to Design Complete for discussion in the CLDR TC. "

Therefore, in this proposal, we will only write spec text to referring to the definition to the resolution of what got defined in that work. But we still need to define this spec in Temporal is referring to that spec/standard, not some other standard or definition.