Skip to content

Conversation

robertbastian
Copy link
Member

@robertbastian robertbastian commented Sep 16, 2025

CLDR-18369

  • This PR completes the ticket.

Now that we've aligned all the codes with the correct abbreviations, we should also align the names in root. This finally gets rid of ERA0 and ERA1 for Ethiopic.

The Coptic era was already updated in #4620, that should have probably been a separate PR.

ALLOW_MANY_COMMITS=true

@jira-pull-request-webhook
Copy link

Notice: the branch changed across the force-push!

  • common/main/root.xml is different

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

@jira-pull-request-webhook
Copy link

Notice: the branch changed across the force-push!

  • common/main/root.xml is different

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

@robertbastian robertbastian changed the title CLDR-18369 Update root era names CLDR-18369 Update era names Sep 16, 2025
@jira-pull-request-webhook
Copy link

Notice: the branch changed across the force-push!

  • common/main/root.xml is different
  • common/main/sat.xml is now changed in the branch
  • common/main/ta.xml is now changed in the branch

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

</dayPeriods>
<eras>
<eraNames>
<alias source="locale" path="../eraAbbr"/>
Copy link
Member

Choose a reason for hiding this comment

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

Cannot add or remove aliases without TC approval. Affects all of inheritance.

@jira-pull-request-webhook
Copy link

Notice: the branch changed across the force-push!

  • common/main/en.xml is no longer changed in the branch
  • common/main/es_419.xml is no longer changed in the branch
  • common/main/fi.xml is no longer changed in the branch
  • common/main/fr_CA.xml is no longer changed in the branch
  • common/main/fr.xml is different
  • common/main/is.xml is no longer changed in the branch
  • common/main/ro.xml is no longer changed in the branch
  • common/main/root.xml is different
  • common/main/sat.xml is no longer changed in the branch
  • common/main/ta.xml is no longer changed in the branch

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

sffc
sffc previously approved these changes Sep 16, 2025
Copy link
Member

@sffc sffc left a comment

Choose a reason for hiding this comment

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

LGTM, thanks for making the change more narrow!

@sffc sffc requested a review from macchiati September 16, 2025 20:05
Copy link
Contributor

@AEApple AEApple left a comment

Choose a reason for hiding this comment

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

We are past data freeze. This will need approval from both the CLDR and ICU TCs at this point in the release or you can wait until CLDR 49.

@robertbastian
Copy link
Member Author

So the first CLDR-JSON we could use to test with ICU4X was released after the data freeze, so now I have to go begging to two TCs for any issue we find?

@AEApple
Copy link
Contributor

AEApple commented Sep 16, 2025

So the first CLDR-JSON we could use to test with ICU4X was released after the data freeze, so now I have to go begging to two TCs for any issue we find?

I think this means that we need to refine the schedule to consider ICU4X. Historically ICU4X's release timelines were not aligned with the CLDR or ICU timelines but were independent.

@robertbastian
Copy link
Member Author

Historically ICU4X's release timelines were not aligned with the CLDR or ICU timelines but were independent.

ICU4X has tested every CLDR release since I've been on the project as soon as a CLDR-JSON was available. This has always been way later than ICU could start integration, which I point out every time, but I don't think it has ever been after data freeze.

@AEApple
Copy link
Contributor

AEApple commented Sep 16, 2025

Historically ICU4X's release timelines were not aligned with the CLDR or ICU timelines but were independent.

ICU4X has tested every CLDR release since I've been on the project as soon as a CLDR-JSON was available. This has always been way later than ICU could start integration, which I point out every time, but I don't think it has ever been after data freeze.

It has always been after data freeze at least according to the CLDR BRS. In general we only start generating CLDR JSON data after alpha2 and sometimes after public alpha but always before public beta.

It may have been happening but since it isn't currently reflected that way in the BRS checklist, we should make sure that is updated so that you can test earlier. Otherwise it's likely to get missed if we are running late for any reason.

@macchiati macchiati marked this pull request as draft September 16, 2025 23:27
@macchiati
Copy link
Member

Moved to draft to avoid getting inadvertently merged before we settle remaining issues.

@AEApple
Copy link
Contributor

AEApple commented Sep 17, 2025

Saka change was discussed in https://unicode-org.atlassian.net/browse/CLDR-18487

</eraNames>
<eraAbbr>
<era type="0">ERA0</era>
<alias source="locale" path="../../../calendar[@type='ethiopic']/eras/eraAbbr/era[@type='0']"/>
Copy link
Member

Choose a reason for hiding this comment

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

I looked this over, and I think it is ok if we change to:

Suggested change
<alias source="locale" path="../../../calendar[@type='ethiopic']/eras/eraAbbr/era[@type='0']"/>
<alias source="locale" path="../../../calendar[@type='ethiopic']/eras/eraAbbr"/>

The aliases take the asked-for path, plus the location of the alias itself, in order to construct the new path. You can see that in the other cases. That being said, I haven't tested this out.

Copy link
Member Author

Choose a reason for hiding this comment

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

We don't want to pull in both eras, just the one with type=0

Copy link
Member

Choose a reason for hiding this comment

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

That's not the way that they work: https://unicode.org/reports/tr35/tr35.html#Alias_Elements
That would map any missing item (eg type='1') to the 0 value.

However, I see that you've removed this, so it's moot.

Copy link
Member Author

Choose a reason for hiding this comment

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

I removed it from this PR so it can get merged, but we need to figure out some mechanism to keep these era names in sync.

We might be able to just remove translations for ethipic-amete-alem altogether if patterns also match ethiopic.

Copy link
Member

Choose a reason for hiding this comment

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

Agreed, we do that for the Islamic variants!

@jira-pull-request-webhook
Copy link

Notice: the branch changed across the force-push!

  • common/main/root.xml is different

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

@robertbastian robertbastian marked this pull request as ready for review September 26, 2025 08:51
@jira-pull-request-webhook
Copy link

Notice: the branch changed across the force-push!

  • common/main/bn.xml is now changed in the branch
  • common/main/da.xml is now changed in the branch
  • common/main/ff_Adlm.xml is now changed in the branch
  • common/main/gu.xml is now changed in the branch
  • common/main/he.xml is now changed in the branch
  • common/main/is.xml is now changed in the branch
  • common/main/mk.xml is now changed in the branch
  • common/main/ml.xml is now changed in the branch
  • common/main/mr.xml is now changed in the branch
  • common/main/nl.xml is now changed in the branch
  • common/main/no.xml is now changed in the branch
  • common/main/pa.xml is now changed in the branch
  • common/main/shn.xml is now changed in the branch
  • common/main/ur.xml is now changed in the branch

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

Copy link
Member

@macchiati macchiati left a comment

Choose a reason for hiding this comment

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

You're now removing all the values, even those that change script. I understand that they are probably incorrect in that they include "0", but the Latin abbreviation is probably no better. However, to get this moving I'm approving.

@gclapps0612-cmd

This comment was marked as spam.

@robertbastian
Copy link
Member Author

ping @AEApple

@robertbastian
Copy link
Member Author

autosubmit please

@robertbastian robertbastian merged commit 0d02d32 into unicode-org:main Sep 29, 2025
11 checks passed
@robertbastian robertbastian deleted the eras branch September 29, 2025 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants