Official full JSON of CDLR

[ragulka]

CLDR release 25 brings the full CLDR data in JSON format: http://unicode.org/Public/cldr/25/

Any plans to use it? Will it affect this library?

[papandreou]

Ah, that's good news. I haven't taken a thorough look at the JSON format yet, but I sincerely hope it removes the need for node-cldr, since it's mostly an XML-to-JSON converter that knows how to resolve CLDR's weird <alias> nodes. If those aren't present in the JSON, I guess the only value this library is adding is the ability to generate plural and RBNF functions, which should then logically move into separate libraries.

What do you think? Have you tried working with the official JSON yet?

[ragulka]

Yes, I've tried it. It looks good. It's huge though (450MB unzipped). There is some discussion about perhaps creating a library for extracting only the parts you need and perhaps even a CDN on the Globalize project: globalizejs/globalize#224 (comment)

[Nemo64]

I think it is still nice to have a library to ask for data instead of parsing a json file directly. Also it is nice as a dependency! I haven't looked all too deeply into it though.

[jzaefferer]

Since Globalize was already mentioned: The new version based on CLDR uses this project to deal with CLDR: https://github.com/rxaviers/cldrjs

[ericf]

One aspect of where features in this lib would still be needed is generating the plural rule functions, since the plural rules are defined in strings.

[rxaviers]

Perhaps this could help: https://github.com/eemeli/make-plural.js translates Unicode CLDR pluralization rules into executable JavaScript.

[cburatto]

Stopping by to inform that since CLDR 27 (release notes: http://cldr.unicode.org/index/downloads/cldr-27 ) JSON data is available on GITHUB only:

https://github.com/unicode-cldr/cldr-json

[rotsee]

On a related note: https://github.com/rxaviers/cldr-data-npm

Allow i18n libraries to define CLDR data as versioned "peer" dependency