unicode-org
CLDR-18144 Tooling for improving formats of locales, especially for menus
CLDR-18144
- [ ] This PR completes the ticket.
Tool for investigating which languages / regions could have core and extension values. Prints lists of possible breakdowns, which then need to be filtered manually.
Resulting recommendations in https://docs.google.com/spreadsheets/d/1bbC5iOFVK0A4Hla-1xIGtgwAAOqtj4PWb0llFc-sgOY/edit?gid=386214050#gid=386214050
ALLOW_MANY_COMMITS=true
Will languages be able to re-order the extension and the core parts? Do we know if there are languages where for certain combinations the extension may appear on different sides of the core word (kinda like in French where most adjectives follow the noun, while a handful precede the noun? https://en.wikipedia.org/wiki/French_grammar#Adjectives
Will languages be able to re-order the extension and the core parts? Do we know if there are languages where for certain combinations the extension may appear on different sides of the core word (kinda like in French where most adjectives follow the noun, while a handful precede the noun? https://en.wikipedia.org/wiki/French_grammar#Adjectives
The extension use the same mechanism as the language and (script, region, variant, keys, etc). That is, someone would see in a menu (where the core/extension mechanism is used — it is optional) as the following (look at the Kurdish lines for the differences)
NEW
...
French
Kurdish (Kurmanji)
Kurdish (Sorani)
Serbian (Cyrillic)
Serbian (Latin)
Swedish (Sweden)
Swedish (Finland)
...
OLD
...
French
Kurdish
Serbian (Cyrillic)
Serbian (Latin)
Sorani Kurdish
Swedish (Sweden)
Swedish (Finland)
...
See also the regions' part of the spreadsheet in the ticket.
The tool is just used to help identify items that might need splitting. Can be cleaned up after submission starts
On Tue, Apr 15, 2025, 00:50 Shane F. Carr @.***> wrote:
@.**** commented on this pull request.
I looked at the spreadsheet and there are some interesting findings that should be discussed.
The tool itself looks like a proof-of-concept; is it your intent to eventually land this as part of a test?
— Reply to this email directly, view it on GitHub https://github.com/unicode-org/cldr/pull/4537#pullrequestreview-2764825391, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJLEMCEYGDBPYFFUYAPKPT2ZPKNBAVCNFSM6AAAAABZ5QUJLGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDONRUHAZDKMZZGE . You are receiving this because you were assigned.Message ID: @.***>
@macchiati do you want to land this code? Have there been any changes to the approach since you posted this?
I'd like to go ahead and land the tool, because I think it could be useful in the future.
This is just tooling, with no effect on the release. There is one unrelated test failure; I strongly suspect that rebasing will fix it, but I don't have time now. So when I get back.