cldr icon indicating copy to clipboard operation
cldr copied to clipboard

CLDR-18620 Add support for regional English in 419

Open AEApple opened this issue 4 months ago • 3 comments

CLDR-18620

Creates support for regional en-419 locales.

Excludes locales which have closer ties to en-GB and prefer direct en-001 inheritance

  • [ ] This PR completes the ticket.

ALLOW_MANY_COMMITS=true

AEApple avatar Aug 12 '25 16:08 AEApple

I wonder if this will confuse people with es_419. To avoid that I may recommend sub-continents rather than regions, so:

en_005 (South America) en_FK en_GY

en_013 (Central America) en_BZ

en_029 (Caribbean) en_AG en_AI en_BB en_BS en_DM en_GD en_JM en_KN en_KY en_MS en_SX en_TC en_TT

FWIW see all territories here: https://translation-commons.github.io/lang-nav/data?objectType=Territory&view=Hierarchy&searchBy=ID&searchString=019&sortBy=Code

conradarcturus avatar Aug 13 '25 15:08 conradarcturus

@conradarcturus - you want to treat en differently than we treat es? We don't have the breakdown in es that you are proposing. Also that goes against what was agreed on in https://unicode-org.atlassian.net/browse/CLDR-18809 where the goal is to group inheritance based on shared locale data instead of based on region. FWIW, es_JP is actually Latin American Spanish (Japan) as well :)

Happy to make a es-029 which is a child of en-419 if you think it would be better? We do have a ticket requesting it, I'm just trying to avoid many levels of data that we have to maintain consistency in. https://unicode-org.atlassian.net/browse/CLDR-15031

AEApple avatar Aug 13 '25 19:08 AEApple

Ah sorry for not following up on my comment & then leaving for vacation. Do you plan to continue this PR (presumably for v49 now?)

To reply to your comment: Your reasoning is sound :) I withdraw my comment. I was overly cautious about people mixing en_419 and es_419 but I don't think that's necessary.

conradarcturus avatar Sep 25 '25 21:09 conradarcturus