Consider using CLDR data

[sanxiyn]

CLDR(Common Locale Data Repository) is where everybody is collecting locale data. Looking at locales directory, I think you should take data from https://github.com/unicode-cldr/cldr-dates-full. For example, here is data for fr.

[Alex-PK]

This is a great idea. I didn't know about CLDR.

I (quickly) went through the project's pages and it shouldn't be too hard to write a script to import the data from the json repo before publishing a new version.

There are a couple of things that will need to be kept in mind. I'll add them here as a recap:

• some locales have multiple sub-locales (zh-*)
• some locales have 3-letter codes (asa, bem, bas, ...). What are they? :)
• LatAm is encoded as 419 (ISO code) but should be accessible as XL (used by MS, Apple, Android, etc.)
• adding that many locales would make the default build huge. Maybe build flags to select what to build?

[sanxiyn]

I think just replacing current data with CLDR data would be useful. Handling other locales can be done later.

If you do so, consider documenting CLDR version used (currently 34). unicode-cldr repositories provide Git tags for CLDR versions to do so.