Skip to content
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.

Inconsistent in en_US localization #12134

Closed
tdrozdz opened this issue Jun 16, 2015 · 3 comments
Closed

Inconsistent in en_US localization #12134

tdrozdz opened this issue Jun 16, 2015 · 3 comments
Assignees
Milestone

Comments

@tdrozdz
Copy link

tdrozdz commented Jun 16, 2015

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

posPre: '\u00A4',

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.

@lgalfaso lgalfaso added this to the 1.4.2 milestone Jun 16, 2015
@lgalfaso
Copy link
Contributor

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

@petebacondarwin petebacondarwin modified the milestones: 1.4.2, 1.4.3 Jul 6, 2015
@matsko matsko modified the milestones: 1.4.3, 1.4.4 Jul 14, 2015
@petebacondarwin
Copy link
Member

It seems weird that we have a "sort-of" duplicate of the en-us locale inside the ng module.
If we just copied the ngLocale module for en-us into the angular.js file, we would lose 400 bytes (pre-zip) but we would gain consistency and also get rid of that annoying caught error during bootstrap, where it says that ngLocale is missing.

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
@petebacondarwin petebacondarwin self-assigned this Jul 16, 2015
@petebacondarwin
Copy link
Member

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.
Projects
None yet
Development

No branches or pull requests

4 participants