New name for the library
See original GitHub issueThis library has been named ng2-translate as an obvious reference to angular-translate (for Angular 1), but it is now growing as an independent project with new features. Also Angular 2 is now called Angular (with Angular 1 being AngularJS), so the name ng2 is gonna be obsolete soon.
Which is why this library needs a new name. I’ve secured the npm username i18n
, and I would like to release future versions on npm under @i18n/...
(for example @i18n/core
), so I’m thinking about renaming this angular-i18n or something like that, but I’m opened to other ideas (preferably with i18n in the name, but not necessary).
Why distribute this under a namespace on npm? Because I’d like to release new optional addons (new loaders, tools, …) and I want everything under the same namespace (so that I can name these new libs the way I want).
Also this is following the @angular
philosophy.
Do you guys have ideas or remarks on the subject ?
Issue Analytics
- State:
- Created 7 years ago
- Comments:26 (2 by maintainers)
Top GitHub Comments
For me personally,
ngx-translate
is the best choice.How about “lingua” ? You’d get to be able to use it as the namespace later then too. (gentle highlight on the ‘ng’)
cref. wikitionary