This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.5k
Inconsistent in en_US localization #12134
Comments
This looks like a valid bug. Thanks for reporting this. If someone wants to put together a PR, it would be ideal. If not I will look into this before the next release |
It seems weird that we have a "sort-of" duplicate of the en-us locale inside the |
petebacondarwin
added a commit
to petebacondarwin/angular.js
that referenced
this issue
Jul 16, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes angular#12134 Closes angular#8174
petebacondarwin
added a commit
to petebacondarwin/angular.js
that referenced
this issue
Jul 16, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes angular#12134 Closes angular#8174
Merged
I have a fix for this #12362 |
petebacondarwin
added a commit
to petebacondarwin/angular.js
that referenced
this issue
Jul 16, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes angular#12134 Closes angular#8174
petebacondarwin
added a commit
to petebacondarwin/angular.js
that referenced
this issue
Jul 16, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes angular#12134 Closes angular#8174
lgalfaso
added a commit
to lgalfaso/angular.js
that referenced
this issue
Jul 29, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes angular#12134 Closes angular#8174
lgalfaso
added a commit
to lgalfaso/angular.js
that referenced
this issue
Jul 29, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes angular#12134 Closes angular#8174
lgalfaso
added a commit
to lgalfaso/angular.js
that referenced
this issue
Jul 29, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes angular#12134 Closes angular#8174
lgalfaso
added a commit
to lgalfaso/angular.js
that referenced
this issue
Jul 29, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes angular#12134 Closes angular#8174
lgalfaso
added a commit
to lgalfaso/angular.js
that referenced
this issue
Jul 29, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes angular#12134 Closes angular#8174
lgalfaso
added a commit
to lgalfaso/angular.js
that referenced
this issue
Jul 29, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes angular#12134 Closes angular#8174
lgalfaso
added a commit
to lgalfaso/angular.js
that referenced
this issue
Jul 29, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes angular#12134 Closes angular#8174
lgalfaso
added a commit
to lgalfaso/angular.js
that referenced
this issue
Jul 29, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes angular#12134 Closes angular#8174
lgalfaso
added a commit
that referenced
this issue
Jul 31, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes #12462 Closes #12444 Closes #12134 Closes #8174
netman92
pushed a commit
to netman92/angular.js
that referenced
this issue
Aug 8, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes angular#12134 Closes angular#8174
netman92
pushed a commit
to netman92/angular.js
that referenced
this issue
Aug 8, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes angular#12462 Closes angular#12444 Closes angular#12134 Closes angular#8174
ggershoni
pushed a commit
to ggershoni/angular.js
that referenced
this issue
Sep 29, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes angular#12134 Closes angular#8174
ggershoni
pushed a commit
to ggershoni/angular.js
that referenced
this issue
Sep 29, 2015
Previously there was a custom built en-us locale that was included with angular.js. This made likely that it would get out of sync with the real en-us locale that is generated from the closure library. This change removes that custom one and uses the generated one instead. This also has the benefit of preventing the unwanted caught error on trying to load `ngLocale` during angular bootstrap. Closes angular#12462 Closes angular#12444 Closes angular#12134 Closes angular#8174
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, during development on localizations I've noticed that in core angular code localization for
en_US
looks different than in a file with localizations exposed as bower dep.value in angular core
angular.js/src/ng/locale.js
Line 36 in 291d7c4
value in bower dep
https://github.com/angular/bower-angular-i18n/blob/master/angular-locale_en-us.js#L118
I'm not sure which one is correct so don't want to create PR but would be great if we could have the same value in both cases.
The text was updated successfully, but these errors were encountered: