Skip to content

Conversation

@sffc
Copy link
Collaborator

@sffc sffc commented Aug 6, 2025

The latest version of unicode-org/cldr#4519 seeks to align with Temporal Intl Era Month Code, but it also removes more of the old era aliases.

I think we should land this PR along with the CLDR one, because we can add the aliases back, but it is hard to remove them. We don't have any evidence that these era aliases are in use.

Ideally we would have removed these before Stage 2.7.

I guess this is Normative, but it is also trying to align with CLDR, but CLDR is trying to align with Intl Era Month Code.

@robertbastian

@sffc sffc requested a review from ptomato August 6, 2025 16:23
Copy link
Collaborator

@ptomato ptomato left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@ptomato
Copy link
Collaborator

ptomato commented Aug 11, 2025

I'm not sure what needs to happen next with this, procedurally. Does it need to be presented to TC39 for consensus?

(FWIW, this is why I preferred that we point to CLDR and not duplicate this info in the spec text)

@Manishearth
Copy link
Contributor

I'll note: CLDR doesn't have nearly as much detail as we want (like the arithmetic year stuff), referencing it wouldn't be great i think.

@sffc
Copy link
Collaborator Author

sffc commented Aug 11, 2025

Let's agree in TG2 this week that we want this, then we include it in the Stage 3 presentation.

@sffc sffc moved this to Priority Issues in ECMA-402 Meeting Topics Oct 8, 2025
@sffc sffc moved this from Priority Issues to Previously Discussed in ECMA-402 Meeting Topics Oct 9, 2025
@sffc
Copy link
Collaborator Author

sffc commented Oct 13, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Previously Discussed

Development

Successfully merging this pull request may close these issues.

3 participants