Skip to content

Conversation

@srl295
Copy link
Member

@srl295 srl295 commented Sep 18, 2025

  • add _rbnfRulesFile key under each rule with the name of the text file to load with the rules.

CLDR-18956

  • This PR completes the ticket.

Review Note

output is planned to appear in the forthcoming 48.0.0-ALPHA3 cldr-json release. You can see the new format at:

ALLOW_MANY_COMMITS=true

- add _rbnfRulesFile key under each rule with the name of the text file to load with the rules.
@github-actions
Copy link

@github-actions github-actions bot added the Site Update Updates docs/site label Sep 18, 2025
srl295 added a commit to unicode-org/cldr-json that referenced this pull request Sep 18, 2025
- DATA: unicode-org/cldr-staging:  d763411f6 release-48-alpha3
- TOOL: unicode-org/cldr:  1cf4f283f1 release-48-alpha3-8-g1cf4f283f1 ( unicode-org/cldr#5060 )
- SCRIPT: unicode-org/cldr-json:  d2f155b 48.0.0-ALPHA2D0
@macchiati
Copy link
Member

Question: would it be easier for clients to have the files in a differently named folder, so that all the files in a folder have the same format?

@srl295
Copy link
Member Author

srl295 commented Sep 19, 2025

Question: would it be easier for clients to have the files in a differently named folder, so that all the files in a folder have the same format?

the .txt files are referenced by the .json files, clients don't need to (and should not) "process" the .txt files independently.

I can add a manifest file, though, listing all of them for convenience.

I’m not sure the manifest file is needed— clients should use the available locales list from the cldr-core package.

Also, the transforms are in a similar format, see https://github.com/unicode-org/cldr-json/tree/v48/cldr-json/cldr-transforms/transforms

@github-actions
Copy link

@github-actions
Copy link

@srl295
Copy link
Member Author

srl295 commented Sep 19, 2025

Hm - some of the RBNF rules are identical, so we could hash the output names

        "_rbnfRulesFile": "rbnf-bc4fdbcf2285984.txt"

not as friendly to humans inspecting it, though.

(not for this PR)

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.

Seems about right; didn't do a deep review of the java code

@srl295 srl295 merged commit 95149ea into main Sep 19, 2025
21 checks passed
@srl295 srl295 deleted the srl295/cldr-18956/rbnf-new-format branch September 19, 2025 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Site Update Updates docs/site

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants