npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@rxweb/translate

v1.0.15

Published

[![Build Status](https://travis-ci.org/rxweb/rxweb.svg?branch=master)](https://travis-ci.org/rxweb/rxweb) [![Gitter](https://badges.gitter.im/rx-web/Lobby.svg)](https://gitter.im/rxweb-project/rxweb?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge

Downloads

3,180

Readme

Build Status Gitter Codacy Badge DeepScan grade GitHub license

The most simplified and elegant library for Internationalization in Angular Application. It's easy to integrate in the application without much learning curve or overhead of implementation. Internationalize your application by following the two simple steps.

Overall objective of developing this library is to integration must simple and faster. Use as much as possible available features of Angular instead of reinventing the wheel.

Install Package

$ npm install @rxweb/translate

Automatic Translation Configuration Through CLI

If you want to configure all the translation configuration automatically, you must install @rxweb/cli

$ npm install @rxweb/cli

Image

@Translate

Translate decorator is used for resolving the translation data by given name of translationName. Here is example code:

@translate({translationName:'user'}) translation:{[key:string]:any}

Another approach, Which I liked most to assign the respective translation model to the translation object property.

@translate({translationName:'user'}) translation:UserTranslation

The UserTranslation will be generated automatically based upon the JSON data.

Binding

Simple Binding

Simple Binding consists of two types ie. property binding and nested object property

global.en.json:

{
   "applicationTitle":"User Registration",
  "text":{   
    "Description":"Full Name"
  }
}

Translation Property Declaration

The first step is to add @translate decorator in the component with the multilingual name

export class AppComponent  {
    @translate() multilingualContent:{[key:string]:any}
}

Property Binding

In the component html it is done using syntax

 <h1>  {{multilingualContent.applicationTitle}} </h1>

Nested Object Property

Binding nested level object

<div>
      <p>{{multilingualContent.text.Description}}</p>
</div>

Scope Parameter Binding

Component Scope

This can be done by interpolating the property name in the content string.

Now we are going to define the content with interpolating the property name of freeText. See the below JSON

user.en.json

{
"enteredText": "You have entered text is: {{freeText}}"
}

In the component, use the @translate decorator and passing the translationName

export class UserComponent {
    
    @translate({ translationName: "user" }) multilingualContent: { [key: string]: any }

    freeText: string = "India";
}

And in The html

<p>{{multilingualContent.text.enteredText}}</p>

On Demand Scope

While defining a JSON content string you have to use { for on-demand object value changes from the TS file. Here is the example text.

{
"selectedRecord": "You have selected record of '{name}'"
}

Now in the component, you have to call the function like as below:

selectUser(user) {
// the user object json would be like : {name:"John" }
let message = RxTranslateModule.tranlate(this.multilingualContent.text.selectedRecord, user);
}

Conditional Scoped Binding

For showing the multilingual content conditionally based upon the keys defined in the JSON.

Let’s consider a case where we want to show some information about the countries according to the input name of the country. If the user enters a value of India then it must show the content in English or French according to the user preferred language. Other than India it must show the information about the World. So, as per the above case, we have to define two properties in the JSON file, which are as below:

{    
"indiaInfo": "India, officially the Republic of India, is a country in South Asia. It is the seventh-largest country by area, the second-most populous country, and the most populous democracy in the world.",
"worldInfo": "The World is Planet Earth and all life on it, including human civilization. In a philosophical context, the world is the whole of the physical Universe, or an ontological world.",
}

We have defined two properties and we need one more property that returns the content based upon the passed condition. So we have to write the code in string format, the code same as we write in the TS file. Here is the example

{
"conditionalText": "this.freeText == 'India' ? this.multilingualContent.indiaInfo : this.multilingualContent.worldInfo",
}

On the HTML side, you have to use conditionalText property for conditionally showing the content. Here is the output:

  <mark>{{multilingualContent.text.conditionalText}}</mark>

Binding By Key Name

This is another approach to get the key value from the object property by key name. Here is the JSON, which we get the userName value by calling the get method.

{
	"text":{
		"userName":"User Name"
	}
}

Here is the HTML.

  {{multilingualContent.get("text.userName")}}

Translation Loading Stratergy

Loading translated content can be done using lazy loading and using shared component.

Loading Page Translation

Lazy loading can be achieved using @rxweb/translate by configuration routes in app routing.
Let’s create a UserComponent and map the route into app routing.

    {
        path: 'user',
        component: UserComponent
    }

In the UserComponent TS:

export class UserComponent {

    @translate({ translationName: "user" })
    multilingualContent: { [key: string]: any }
   
}

Loading Shared Component Translation

Shared component can be achieved using rxTranslate. So let’s create a AddressComponent and map the translate decorator on the component property.

export class AddressComponent {
    @translate({ translationName: "address" }) multilingualContent: { [key: string]: any };
}

Next step is to apply on the component element which is a rxTranslate directive. The rxTranslate directive will resolve the content before initializing the component.

<app-address *rxTranslate=""></app-address>

Preload Translation Stratergy

preload translation strategy can be set to NoPreloading or PreloadAllModules with the RouterModule

 [
   RouterModule.forRoot(routes, { preloadingStrategy: PreloadAllModules  })
 ]

And in RxWebModule define preloadingStrategy true into RxTranslateModule.

  RxTranslateModule.forRoot({
        preloadingStrategy:true
        })

Language Content Translation

Language content translation can be done based upon url, manual language change and fixed language

By URL With Page Title

For loading language content url wise the routing is configured as below:

const routes: Routes = [
    {
        path: '',
        redirectTo: "fr/login",
        pathMatch: "full"
    },
    {
        path: ':languageCode/login',
        component: LoginComponent
    }];

The component TS code:

export class LoginComponent {
    @translate({ translationName: "login" })
    multilingualContent: { [key: string]: any } 

    constructor(private route: Router) {

    } 

    navigate(languageCode: string) {
        this.route.navigate([languageCode, "login"]);
    }
}

For language change in the HTML

 <p class="small text-center text-gray-soft">
               <a class="blue-link" [class.active-language]="multilingualContent.languageCode == 'en'"  (click)="navigate('en')">English</a>
              <a class="blue-link" [class.active-language]="multilingualContent.languageCode == 'fr'" (click)="navigate('fr')">French</a>
  </p>

By Manual

Manual change of language on user selection can be done using changeLanguage of RxTranslateModule as below:

 changeLanguage(languageCode){
   RxTranslateModule.changeLanguage(languageCode)
 }

Fixed Language

In case where the content needs a fixed language to be set. It is done by defining language in @translate decorator.

export class UserComponent {
    @translate({ translationName: "user", language:"en" }) multilingualContent: { [key: string]: any };
}

Cache

Active Language

For setting active language cache true in the application set cacheActiveLanguageObject true.

RxTranslateModule.forRoot({
  cacheActiveLanguageObject:true
      })

Language Wise

For allowing language wise cache in the application we can set cacheLanguageWiseObject true.

          RxTranslateModule.forRoot({
            cacheLanguageWiseObject: true,
          })

Contributing

If you are thinking to make rxweb framework better, that's truly great. You can contribute from a single character to core architectural work or significant documentation – all with the goal of making a robust rxweb framework which helps for everyone in their projects. Even if you are don’t feel up to writing code or documentation yet, there are a variety of other ways that you can contribute like reporting issues to testing patches.

Check out the docs on how you can put your precious efforts on the rxweb framework and contribute in the respective area.

Need Help

We highly recommend for help please ask your questions on our gitter/rxweb-project to get quick response from us. Otherthan our gitter channel you can ask your question on StackOverflow or create a new issue in our Github Repository.

For, issue please refer our issue workflow wiki for better visibility our issue process.

Feature Request

You can request a new feature by submitting an issue to our GitHub Repository. If you would like to implement a new feature, please submit an issue with a proposal for your work first, to be sure that we can use it.

License

MIT