Skip to content

Conversation

@conradarcturus
Copy link
Contributor

CLDR-18871

  • This PR completes the ticket.

ALLOW_MANY_COMMITS=true

@conradarcturus conradarcturus self-assigned this Nov 25, 2025
@conradarcturus conradarcturus force-pushed the CLDR-18871-new-locale-interslavic-isv branch from 1c789de to b42896d Compare November 25, 2025 19:18
@jira-pull-request-webhook
Copy link

Notice: the branch changed across the force-push!

  • common/main/isv_Cyrl.xml is different

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

@DavidLRowe
Copy link
Contributor

I think the colon after the ticket number (at the beginning of the commit message) is causing problems.

I think it may be too early to include "isv" in en.xml. @srl295: Correct me if I'm wrong!

IIUC the locale needs to have been in CLDR at Basic level already in order to qualify for addition to en.xml, which would then be done at the beginning of the next even-numbered cycle. Thus, assuming isv gets to Basic in v50, at the beginning of v52 "isv" would be added to en.xml and picked up by other locals for localization.

@DavidLRowe
Copy link
Contributor

Other files look okay, though I'm not qualified to comment about GenerateLikelySubtags.java‎. (@srl295 ?)

@conradarcturus conradarcturus changed the title CLDR-18871: Create new locale, Interslavic, isv CLDR-18871 Create new locale, Interslavic, isv Nov 26, 2025
@conradarcturus conradarcturus force-pushed the CLDR-18871-new-locale-interslavic-isv branch from b42896d to cbd3e76 Compare November 26, 2025 02:20
@jira-pull-request-webhook
Copy link

Hooray! The files in the branch are the same across the force-push. 😃

~ Your Friendly Jira-GitHub PR Checker Bot

@conradarcturus
Copy link
Contributor Author

I think the colon after the ticket number (at the beginning of the commit message) is causing problems.

oh! I suspect you are right

I think it may be too early to include "isv" in en.xml. @srl295: Correct me if I'm wrong!

IIUC the locale needs to have been in CLDR at Basic level already in order to qualify for addition to en.xml, which would then be done at the beginning of the next even-numbered cycle. Thus, assuming isv gets to Basic in v50, at the beginning of v52 "isv" would be added to en.xml and picked up by other locals for localization.

I don't think its ever too early to include it. Adding it here means it can be localized but it doesn't require it. It's only required to be translated if we update coverageLevels.xml. I think it's a better practice to add it immediately when we add the locale.

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.

3 participants