docs($locale): update

[dragosrususv]

There are a lot of parameters in $locale files, especially on the number/currency formatting part that are not documented at all. Some of them can be distinguished by their name, but some of them are just not readable at all (e.g. gSize and lgSize - which one refers to the count of numbers allowed between GROUP_SEP?).

Would be nice to update https://docs.angularjs.org/api/ng/service/$locale to reflect all these.
These are really useful in large projects and people are actually using them (I know 2 projects at least) for building their dynamic validation regexes.

I can make an initial PR for this one in the days to come, if considered useful.

[btford]

the $locale files are generated from Google Closure. It might be better to just link to the relevant section of the Closure docs.

[dragosrususv]

Ouh the saga of searching through closure docs...
To be honest I couldn't find any and I'm searching for a few hours now. The only link I could find is the actual source code (http://docs.closure-library.googlecode.com/git/local_closure_goog_i18n_numberformatsymbols.js.source.html) but that is just as good as the AngularJS subset source.

Still, what I could find is that there is a converter and AngularJS has defined only a subset of g closure i18n (mapping: https://github.com/angular/angular.js/blob/master/i18n/src/converter.js#L19 ) - for sure you won't find this mapping documented anywhere. Unless someone updates the $locale documentation inside AngularJS.

@btford : I might be just bad with searching on google for this, maybe you have a link?

[dragosrususv]

ping @btford

btw: quick question - is it ok for developers to copy these i18n files and extend them at will for their apps? In other words, how are developers supposed to have their app specific custom date formats through $locale?

[wesleycho]

I found these docs here for Closure, but I'm not sure if this is what was meant.