ng2-translate
An implementation of angular translate for Angular 2.
Simple example using ng2-translate: http://plnkr.co/edit/btpW3l0jr5beJVjohy1Q?p=preview
Get the complete changelog here: https://github.com/ocombe/ng2-translate/releases
Installation
First you need to install the npm module:
npm install ng2-translate --save
If you use SystemJS to load your files, you can check the plunkr example for a working setup that uses the cdn https://unpkg.com/.
If you're importing directly from node_modules
, you should edit your systemjs config file and add 'ng2-translate': 'node_modules/ng2-translate/bundles'
in the map and 'ng2-translate' : { defaultExtension: 'js' }
in packages.
Usage
TranslateModule
:
1. Import the Finally, you can use ng2-translate in your Angular 2 project.It is recommended to import TranslateModule.forRoot()
in the NgModule of your application.
The forRoot
static method is a convention that provides and configures services at the same time. Make sure you only call this method at the root module of your application, most of the time called AppModule
. This method allows you to configure the TranslateModule
loader. By default it will use the TranslateStaticLoader
, but you can provide another loader instead as a parameter of this method (see below Write & use your own loader).
For now ng2-translate requires HttpModule from @angular/http
(this will change soon).
;;;;
SharedModule
If you use a SharedModule
that you import in multiple other feature modules, you can easily export the TranslateModule
to make sure you don't have to import it in every module.
Note: Never call a
forRoot
static method in theSharedModule
. You will end up with multiple different instances of a service in your injector tree.
Configuration
By default, only the TranslateStaticLoader
is available. It will search for files in i18n/*.json
, if you want you can customize this behavior by changing the default prefix/suffix:
AoT
If you want to configure a custom TranslateLoader
while using AoT compilation or Ionic 2, you must use an exported function instead of an inline function.
TranslateService
for your application:
2. Init the ;;
3. Define the translations:
Once you've imported the TranslateModule
, you can put your translations in a json file that will be imported with the TranslateStaticLoader
. The following translations should be stored in en.json
.
You can also define your translations manually with setTranslation
.
translate.setTranslation'en', ;
The TranslateParser
understands nested JSON objects. This means that you can have a translation that looks like this:
You can then access the value by using the dot notation, in this case HOME.HELLO
.
4. Use the service, the pipe or the directive:
You can either use the TranslateService
, the TranslatePipe
or the TranslateDirective
to get your translation values.
With the service, it looks like this:
translate.get'HELLO', .subscribe;
This is how you do it with the pipe:
{{ 'HELLO' | translate:param }}
And in your component define param
like this:
param =;
This is how you use the directive:
Or even simpler using the content of your element as a key:
HELLO
5. Use HTML tags:
You can easily use raw HTML tags within your translations.
To render them, simply use the innerHTML
attribute with the pipe on any element.
API
TranslateService
Properties:
-
currentLang
: The lang currently used -
currentLoader
: An instance of the loader currently used (static loader by default) -
onLangChange
: An EventEmitter to listen to lang change events. ALangChangeEvent
is an object with the propertieslang: string
&translations: any
(an object containing your translations).example:
onLangChange.subscribe; -
onTranslationChange
: An EventEmitter to listen to translation change events. ATranslationChangeEvent
is an object with the propertieslang: string
&translations: any
(an object containing your translations).example:
onTranslationChange.subscribe; -
onDefaultLangChange
: An EventEmitter to listen to default lang change events. ADefaultLangChangeEvent
is an object with the propertieslang: string
&translations: any
(an object containing your translations).example:
onDefaultLangChange.subscribe;
Methods:
setDefaultLang(lang: string)
: Sets the default language to use as a fallbackgetDefaultLang(): string
: Gets the default languageuse(lang: string): Observable<any>
: Changes the lang currently usedgetTranslation(lang: string): Observable<any>
: Gets an object of translations for a given language with the current loadersetTranslation(lang: string, translations: Object, shouldMerge: boolean = false)
: Manually sets an object of translations for a given language, setshouldMerge
to true if you want to append the translations instead of replacing themaddLangs(langs: Array<string>)
: Add new langs to the listgetLangs()
: Returns an array of currently available langsget(key: string|Array<string>, interpolateParams?: Object): Observable<string|Object>
: Gets the translated value of a key (or an array of keys) or the key if the value was not foundinstant(key: string|Array<string>, interpolateParams?: Object): string|Object
: Gets the instant translated value of a key (or an array of keys). /!\ This method is synchronous and the default file loader is asynchronous. You are responsible for knowing when your translations have been loaded and it is safe to use this method. If you are not sure then you should use theget
method instead.set(key: string, value: string, lang?: string)
: Sets the translated value of a keyreloadLang(lang: string): Observable<string|Object>
: Calls resetLang and retrieves the translations object for the current loaderresetLang(lang: string)
: Removes the current translations for this lang. /!\ You will have to calluse
,reloadLang
orgetTranslation
again to be able to get translationsgetBrowserLang(): string | undefined
: Returns the current browser lang if available, or undefined otherwisegetBrowserCultureLang(): string | undefined
: Returns the current browser culture language name (e.g. "de-DE" if available, or undefined otherwise
Write & use your own loader
If you want to write your own loader, you need to create a class that implements TranslateLoader
. The only required method is getTranslation
that must return an Observable
. If your loader is synchronous, just use Observable.of
to create an observable from your static value.
Example
Once you've defined your loader, you can provide it in your configuration by adding it to its providers
property.
How to handle missing translations
You can setup a provider for the MissingTranslationHandler
in the bootstrap of your application (recommended), or in the providers
property of a component. It will be called when the requested translation is not available. The only required method is handle
where you can do whatever you want. If this method returns a value or an observable (that should return a string), then this will be used. Just don't forget that it will be called synchronously from the instant
method.
Example:
Create a Missing Translation Handler
;
Setup the Missing Translation Handler in your module by adding it to the providers
list.
Parser
If you need it for some reason, you can use the TranslateParser
service.
Methods:
-
interpolate(expr: string, params?: any): string
: Interpolates a string to replace parameters.This is a {{ key }}
==>This is a value
withparams = { key: "value" }
-
getValue(target: any, key: stirng): any
: Gets a value from an object by composed keyparser.getValue({ key1: { keyA: 'valueI' }}, 'key1.keyA') ==> 'valueI'
FAQ
No provider for Http!
I'm getting an error Because of the TranslateStaticLoader you have to load the HttpModule from @angular/http
, even if you don't use this Loader
I'm still using RC4, but I cannot use ng2-translate because I get errors?!
If you're still using RC4, you should fix the version of ng2-translate to 2.2.2.
npm ERR! peerinvalid Peer [...]
I'm getting an error If you're using npm 2.x, upgrade to npm 3.x, because npm 2 doesn't handle peer dependencies well. With npm 2 you could only use fixed versions, but with npm 3 you can use ^
to use a newer version if available.
If you're already on npm 3, check if it's an error (npm ERR!
) or a warning (npm WARN!
), warning are just informative and if everything works then don't worry !
If you're using an old version of angular 2 and ng2-translate wants a newer version then you should consider upgrading your application to use the newer angular 2 version. I cannot support old versions because the framework keeps doing breaking changes... If it's not an option for you, then check the changelog to know which version is the last compatible version.
I'm using Ionic 2 and ng2-translate doesn't work
Ionic 2 is still using angular 2 RC4, but ng2-translate uses RC5. You should fix the version of ng2-translate to 2.2.2 until Ionic 2 upgrades to RC5.
Plugins
- Localize Router by @meeroslav: An implementation of routes localization for Angular 2. If you need localized urls (for example /fr/page and /en/page).
- .po files Loader by @biesbjerg: Use .po translation files with ng2-translate
- ng2-translate-extract by @biesbjerg: Extract translatable strings from your projects