i18n fr_ch and it_ch locales uses wrong decimal separator

[alexandrevoilab]

Hi,
Thoses two locales uses ',' as a decimal separator instead of '.' which is standard in Switzerland.
The locale de_ch uses the correct decimal separator.

Following the guidelines I've checked Closure's i18n scripts, and they are correct.
See fr_ch and it_ch

Thus, I'm submiting it here.

[caitp]

Currently, only the "common locales" number formats are being processed. See https://github.com/angular/angular.js/tree/master/i18n/closure.

Working on generating locale info directly from CLDR, without closure, so this may change soon (but it takes much longer when processing the full range of locales rather than just the common ones!). In the mean time, you're free to send a pull request to get us using the "extra" locales for number formats, too.

[alexandrevoilab]

I've made the changes. But can't push since my CLA is not accepted yet. At least I think this is why my push are rejected.

I will create a pull request ASAP.

[caitp]

@alexandrevoilab you can send a pull request whether you've signed the CLA or not =)

[alexandrevoilab]

My bad, I was trying to push on the master repo...

[alexandrevoilab]

Up?

[srl295]

@caitp hi, saw that you did a regenerate (sounds like from closure data) - please note CLDR 26 (edit: has just finished) final beta please check latest CLDR data as well and provide feedback. http://unicode.org/pipermail/unicode/2014-September/000935.html

[caitp]

@srl295 we don't generate locale data directly from CLDR currently, we piggyback on the CLDR processing done by https://github.com/google/closure-library/ --- I would suggest bringing it up there

[srl295]

@caitp OK. I saw your note earlier about wanting to generate directly from CLDR, which is why I mentioned something. update Closure says it's on CLDR 25, so latest GA data.