Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/ngstack/translate

Translation library for Angular and Ionic applications.
https://github.com/ngstack/translate

angular angular-component i18n internationalization translation translation-library typescript

Last synced: about 1 month ago
JSON representation

Translation library for Angular and Ionic applications.

Awesome Lists containing this project

README 

        
# translate



Lightweight (±3KB) translation library for Angular applications.



[Live Demo](https://stackblitz.com/edit/ngstack-translate)





  Buy Me A Coffee




# Table of Contents



- [Installing](#installing)

- [Using with the application](#using-with-the-application)

- [Features](#features)

  - [Translate Pipe](#translate-pipe)

  - [Title Service](#title-service)

    - [Translating application title](#translating-application-title)

  - [Translate Service](#translate-service)

    - [Using from code](#using-from-code)

    - [Custom language without external files](#custom-language-without-external-files)

  - [Formatted translations](#formatted-translations)

- [Advanced topics](#advanced-topics)

  - [Testing components](#testing-components)

  - [Watching for language change](#watching-for-language-change)

  - [Custom translation path](#custom-translation-path)

  - [Loading from multiple locations](#loading-from-multiple-locations)

  - [Cache busting](#cache-busting)

  - [Define active language](#define-active-language)

  - [Restricting supported languages](#restricting-supported-languages)

  - [Using with your own pipes](#using-with-your-own-pipes)

  - [Lazy Loading](#lazy-loading)

- [See also](#see-also)



## Installing



```sh

npm install @ngstack/translate

```



### Compatibility with Angular



| @ngstack/translate | Angular |

|--------------------|---------|

| 8.0.0              | 15      |

| 9.0.0              | 16      |

| 10.0.0             | 17      |



## Using with the application



Create `en.json` file in the `src/app/assets/i18n` folder of your application.



```json

{

  "TITLE": "Hello from NgStack/translate!"

}

```



Import `TranslateModule` into you main application module,

configure `TranslateService` to load during application startup.



You will also need `HttpClientModule` module dependency.



```ts

import { NgModule, APP_INITIALIZER } from '@angular/core';

import { HttpClientModule } from '@angular/common/http';

import { TranslateModule } from '@ngstack/translate';



// needed to load translation before application starts

export function setupTranslateService(service: TranslateService) {

  return () => service.load();

}



@NgModule({

  imports: [

    BrowserModule,

    HttpClientModule,

    TranslateModule.forRoot({

      // options

    })

  ],

  providers: [

    // needed to load translation before application starts

    {

      provide: APP_INITIALIZER,

      useFactory: setupTranslateService,

      deps: [TranslateService],

      multi: true

    }

  ],

  declarations: [AppComponent],

  bootstrap: [AppComponent]

})

export class AppModule {}

```



In the main application template, use the following snippet:



```html



  {{ 'TITLE' | translate }}



```



## Features



### Translate Pipe



- `{{ 'KEY' | translate }}`

- ``

- ``

- ``

- `{{ 'PROPERTY.PATH' | translate }}`

- `{{ 'FORMAT' | translate:params }}`

- (2.3.0) ``

- (2.3.0) ``

- (2.3.0) ``



### Title Service



- Sets page title value with automatic translation

- Watches for language changes and updates the title accordingly



#### Translating application title



Update the localization files for your application and add `APP.TITLE` resource key:



```json

{

  "APP": {

    "TITLE": "My Application"

  }

}

```



Update the title from the code, the main application component is a perfect place for that:



```ts

import { TitleService } from '@ngstack/translate';



@Component({...})

export class AppComponent implements OnInit {

  constructor(private titleService: TitleService) {}



  ngOnInit() {

    this.titleService.setTitle('APP.TITLE');

  }

}

```



Now every time the language is changed, the page title is going to get changed automatically.



### Translate Service



- Load translations on language change

- Translation from code

- Defining translation data from code

- Merging multiple translations

- Loading translations from multiple locations

- Automatic fallback for missing translations

- Defining supported languages

- Configurable cache busting

- Lazy loading support

- Visual debugging mode to simplify development and testing



#### Using from code



You can import and use translate service in the code:



```ts

@Component({...})

export class MyComponent {



  text: string;



  constructor(translate: TranslateService) {



    this.text = translate.get('SOME.PROPERTY.PATH');



  }



}

```



#### Custom language without external files



An example for providing translation data from within the application,

without loading external files.



```ts

@NgModule({...})

export class AppModule {

  constructor(translate: TranslateService) {

    translate.use('en', {

      'TITLE': 'Hello from @ngstack/translate!'

    });

  }

}

```



### Formatted translations



You can use runtime string substitution when translating text



```json

{

  "FORMATTED": {

    "HELLO_MESSAGE": "Hello, {username}!"

  }

}

```



Then in the HTML:



```html

{{ 'FORMATTED.HELLO_MESSAGE' | translate:{ 'username': 'world' } }}


```



Or in the Code:



```ts

@Component({...})

export class MyComponent {



  text: string;



  constructor(translate: TranslateService) {



    this.text = translate.get(

      'FORMATTED.HELLO_MESSAGE',

      { username: 'world' }

    );



  }



}

```



Should produce the following result at runtime:



```text

Hello, world!

```



You can use multiple values in the format string.

Note, however, that TranslateService checks only the top-level properties of the parameter object.



## Advanced topics



You can provide custom parameters for the `forRoot` method of the `TranslateModule`



```ts

interface TranslateSettings {

  debugMode?: boolean;

  disableCache?: boolean;

  supportedLangs?: string[];

  translationRoot?: string;

  translatePaths?: string[];

  activeLang?: string;

}

```



For example:



```ts

TranslateModule.forRoot({

  debugMode: true,

  activeLang: 'fr'

});

```



### Testing components



When testing localisation with a single translation file it is sometimes hard to tell

if a component text switches to a different language.

You can simplify testing of the end-applications and components by enabling the debug mode.



While in the debug mode, the service automatically prepends active language id to very translated result.

That allows to verify that your components support i18n correctly and do not contain hard-coded text.



```ts

TranslateModule.forRoot({

  debugMode: true

});

```



Now, if using `en` as the active language, all strings should start with the `[en]` prefix.



### Watching for language change



You can watch for language change event utilising the `activeLangChanged` event:



```ts

@Component({...})

export class MyComponent {



  constructor(translate: TranslateService) {



    translate.activeLangChanged.subscribe(

      (event: { previousValue: string; currentValue: string }) => {

        console.log(event.previousValue);

        console.log(event.currentValue);

      }

    );



  }

}

```



### Custom translation path



By default TranslateService loads files stored at `assets/i18n` folder.

You can change the `TranslateService.translationRoot` property to point to a custom location if needed.



```ts

TranslateModule.forRoot({

  translationRoot: '/some/path'

});

```



### Loading from multiple locations



To provide multiple locations use the `TranslateService.translatePaths` collection property.



```ts

TranslateModule.forRoot({

  translatePaths: ['assets/lib1/i18n', 'assets/lib2/i18n']

});

```



The files are getting fetched and merged in the order of declarations,

and applied on the top of the default data loaded from `TranslateService.translationRoot` path.



### Cache busting



You can disable browser caching and force application always load translation files by using `TranslateService.disableCache` property.



```ts

TranslateModule.forRoot({

  disableCache: true

});

```



### Define active language



The service takes browser language as an active language at startup.

You can use `activeLang` property to define a custom value and override browser settings.



```ts

TranslateModule.forRoot({

  activeLang: 'fr'

});

```



### Restricting supported languages



It is possible to restrict supported languages to a certain set of values.

You can avoid unnecessary HTTP calls by providing `TranslateService.supportedLangs` values.



```ts

TranslateModule.forRoot({

  supportedLangs: ['fr', 'de']

});

```



The service will try to load resource files only for given set of languages,

and will use fallback language for all unspecified values.



By default this property is empty and service will probe all language files.

The service always takes into account the Active and Fallback languages, even if you do not specify them in the list.



### Using with your own pipes



It is possible to use `TranslateService` with your own implementations.



You can see the basic pipe implementation below:



```ts

import { Pipe, PipeTransform } from '@angular/core';

import { TranslateService, TranslateParams } from '@ngstack/translate';



@Pipe({

  name: 'myTranslate',

  pure: false

})

export class CustomTranslatePipe implements PipeTransform {

  constructor(private translate: TranslateService) {}



  transform(key: string, params?: TranslateParams): string {

    return this.translate.get(key, params);

  }

}

```



Then in the HTML templates you can use your pipe like following:



```html



  Custom Pipe: {{ 'TITLE' | myTranslate }}



```



### Lazy Loading



To enable Lazy Loading

use `TranslateModule.forRoot()` in the main application,

and `TranslateModule.forChild()` in all lazy-loaded feature modules.



For more details please refer to [Lazy Loading Feature Modules](https://angular.io/guide/lazy-loading-ngmodules)



## See also



List of alternative libraries you can check out:



- [ngneat/transloco](https://github.com/ngneat/transloco)

- [ngx-translate/core](https://github.com/ngx-translate/core)