-
Notifications
You must be signed in to change notification settings - Fork 215
Conversation
This wasn't configured properly and didn't work
@Turbo87, thanks for putting this together. I tried to update when 27 was out, but there were so many issues, that I decided to deferred it. It seems that 27.0.3 is better. Nevertheless, I ran the same program I created to compute the diff when I was trying to upgrade, and I these is the result:
At the first glance, it seems to be ok. My only concern are those 11 top level locales that we will be eliminated. Ideally, no top level locale should be removed from version to version, maybe we should ask @rxaviers or @srl295 if they know why is that data removed. |
cc @JCEmmons |
@caridy I fixed the second commit and regenerated the |
... and update CLDR to v27.0.3
@Turbo87 everything looks good now. Let's way for @JCEmmons to see if he can give us more details about the following missing locales from CLDR 27.0.3:
|
The removed locales were the result of a review on our part of CLDR locales that had very preliminary data submitted many years ago (like before I came to the project 10 years ago), but have not had any meaningful work done on them since. We have a "seed" repository that we use to keep locale data for locales that are deemed by the committee to be incomplete or perhaps inaccurate, and the locales on this list were moved from "common" to "seed". It is not very often that we do this, and we are in the process of trying to craft a more precise policy as to what goes into "common" vs. "seed". Refer to http://unicode.org/cldr/trac/changeset/11339 I don't expect to be moving any more locales out of "common" at any point in the near future. |
PR #115: Update CLDR data to v27.0.3
@Turbo87 I have merged the PR, but more work needs to be done. I noticed that the new data is missing a bunch of calendars:
In fact, since it only uses |
I ran some validation on the new data, and it seems to be ok, this is a testament of it:
@andyearnshaw I think we are ready to roll out 1.0.0 |
This PR is updating the CLDR data to v27.0.3 and also moves from downloading the data via grunt/CURL to using the appropriate NPM packages instead. The test suite seems to run fine, but this definitely should be checked by another pair of eyes before being merged.