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
• Usage
• API
• FAQ
• Plugins
• Additional Framework Support

First you need to install the npm module:

npm install ng2-translate --save

If you use SystemJS to load your files, check the plunkr example for a working setup.

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).

import {BrowserModule} from '@angular/platform-browser';
import {NgModule} from '@angular/core';
import {HttpModule} from '@angular/http';
import {TranslateModule} from 'ng2-translate';

@NgModule({
    imports: [
        BrowserModule,
        HttpModule,
        TranslateModule.forRoot()
    ],
    bootstrap: [AppComponent]
})
export class AppModule { }

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.

@NgModule({
    exports: [
        CommonModule,
        TranslateModule
    ]
})
export class SharedModule { }

Note: Never call a forRoot static method in the SharedModule. You will end up with multiple different instances of a service in your injector tree.

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:

@NgModule({
    imports: [
        BrowserModule,
        HttpModule,
        TranslateModule.forRoot({
            provide: TranslateLoader,
            useFactory: (http: Http) => new TranslateStaticLoader(http, '/assets/i18n', '.json'),
            deps: [Http] 
        })
    ],
    bootstrap: [AppComponent]
})
export class AppModule { }

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.

export function createTranslateLoader(http: Http) {
    return new TranslateStaticLoader(http, './assets/i18n', '.json');
}

@NgModule({
    imports: [
        BrowserModule,
        HttpModule,
        TranslateModule.forRoot({
            provide: TranslateLoader,
            useFactory: (createTranslateLoader),
            deps: [Http] 
        })
    ],
    bootstrap: [AppComponent]
})
export class AppModule { }

import {Component} from '@angular/core';
import {TranslateService} from 'ng2-translate';

@Component({
    selector: 'app',
    template: `
        <div>{{ 'HELLO' | translate:{value: param} }}</div>
    `
})
export class AppComponent {
    param: string = 'world';

    constructor(translate: TranslateService) {
        // this language will be used as a fallback when a translation isn't found in the current language
        translate.setDefaultLang('en');

         // the lang to use, if the lang isn't available, it will use the current loader to get them
        translate.use('en');
    }
}

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.

{
    "HELLO": "hello {{value}}"
}

You can also define your translations manually with setTranslation.

translate.setTranslation('en', {
    HELLO: 'hello {{value}}'
});

The TranslateParser understands nested JSON objects. This means that you can have a translation that looks like this:

{
    "HOME": {
        "HELLO": "hello {{value}}"
    }
}

You can then access the value by using the dot notation, in this case HOME.HELLO.

You can either use the TranslateService or the TranslatePipe to get your translation values.

With the service, it looks like this.

translate.get('HELLO', {value: 'world'}).subscribe((res: string) => {
    console.log(res);
    //=> 'hello world'
});

And this is how you do it with the pipe.

<div>{{ 'HELLO' | translate:{value: param} }}</div>

You can easily use raw HTML tags within your translations.

{
    "HELLO": "Welcome to my Angular application!<br><strong>This is an amazing app which uses the latest technologies!</strong>"
}

To render them, simply use the innerHTML attributeon any element.

<div [innerHTML]="'HELLO' | translate"></div>

• 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. A LangChangeEvent is an object with the properties lang: string & translations: any (an object containing your translations).

  example:

  onLangChange.subscribe((event: LangChangeEvent) => {
    // do something
  });

• onTranslationChange: An EventEmitter to listen to translation change events. A TranslationChangeEvent is an object with the properties lang: string & translations: any (an object containing your translations).

  example:

  onTranslationChange.subscribe((event: TranslationChangeEvent) => {
    // do something
  });

• setDefaultLang(lang: string): Sets the default language to use as a fallback
• getDefaultLang(): string: Gets the default language
• use(lang: string): Observable<any>: Changes the lang currently used
• getTranslation(lang: string): Observable<any>: Gets an object of translations for a given language with the current loader
• setTranslation(lang: string, translations: Object, shouldMerge: boolean = false): Manually sets an object of translations for a given language, set shouldMerge to true if you want to append the translations instead of replacing them
• addLangs(langs: Array<string>): Add new langs to the list
• getLangs(): Returns an array of currently available langs
• get(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 found
• instant(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 the get method instead.
• set(key: string, value: string, lang?: string): Sets the translated value of a key
• reloadLang(lang: string): Observable<string|Object>: Calls resetLang and retrieves the translations object for the current loader
• resetLang(lang: string): Removes the current translations for this lang. /!\ You will have to call use, reloadLang or getTranslation again to be able to get translations
• getBrowserLang(): string | undefined: Returns the current browser lang if available, or undefined otherwise
• getBrowserCultureLang(): string | undefined: Returns the current browser culture language name (e.g. "de-DE" if available, or undefined otherwise

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.

class CustomLoader implements TranslateLoader {
    getTranslation(lang: string): Observable<any> {
        return Observable.of({KEY: 'value'});
    }
}

Once you've defined your loader, you can provide it in your configuration by adding it to its providers property.

@NgModule({
    imports: [
        BrowserModule,
        TranslateModule.forRoot({
            provide: TranslateLoader,
            useClass: CustomLoader
        })
    ],
    bootstrap: [AppComponent]
})
export class AppModule { }

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.

Create a Missing Translation Handler

import {MissingTranslationHandler, MissingTranslationHandlerParams} from 'ng2-translate';

export class MyMissingTranslationHandler implements MissingTranslationHandler {
    handle(params: MissingTranslationHandlerParams) {
        return 'some value';
    }
}

Setup the Missing Translation Handler in your module by adding it to the providers list.

@NgModule({
    imports: [
        BrowserModule,
        TranslateModule.forRoot()
    ],
    providers: [
        { provide: MissingTranslationHandler, useClass: MyMissingTranslationHandler }
    ],
    bootstrap: [AppComponent]
})
export class AppModule { }

If you need it for some reason, you can use the TranslateParser service.

• interpolate(expr: string, params?: any): string: Interpolates a string to replace parameters.

  This is a {{ key }} ==> This is a value with params = { key: "value" }

• getValue(target: any, key: stirng): any: Gets a value from an object by composed key parser.getValue({ key1: { keyA: 'valueI' }}, 'key1.keyA') ==> 'valueI'

Because of the TranslateStaticLoader you have to load the HttpModule from @angular/http, even if you don't use this Loader

If you're still using RC4, you should fix the version of ng2-translate to 2.2.2.

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.

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.

• Localize Router by @meeroslav: An implementation of routes localization for Angular 2. If you need localized urls (for example /fr/page and /en/page).

• Use with NativeScript