Ecosyste.ms: Awesome

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

https://github.com/amsul/react-translated

A dead simple way to add complex translations (i18n) in a React (DOM/Native) project 🌎🌍🌏
https://github.com/amsul/react-translated

i18n internationalization localisation localization react react-component react-native react-translate react-translations reactjs translate translation

Last synced: 2 months ago
JSON representation

A dead simple way to add complex translations (i18n) in a React (DOM/Native) project 🌎🌍🌏

Lists

README

        

# react-translated

A dead simple way to add complex translations in a React project 🌎🌍🌏

#### Features

* πŸ’₯ Data interpolation
* β˜„ Component interpolation
* β“‚ Markdown inline-manipulations
* πŸ”€ Custom manipulations, pluralizations, and grammar rules based on input-data
* βš› Component-level translation files (enables loading only required translations)

#### Example

Write this:

```jsx
,
}}
/>
```

To render this:

![](docs/simple_translations_in_react.png)

#### Support

React DOM and React Native πŸ”₯

#### Try

Play around with the library in your browser through the [CodeSandbox](https://codesandbox.io/s/jzq7zwj5k3).


## Table of Contents

* [Installation](#installation)
* [Setup](#setup)
* [Usage](#usage)
* [Contributors](#contributors)
* [TODOs](#todos)
* [License](#license)


## Installation

Whatever floats your boat:

* [Yarn](https://yarnpkg.com): `yarn add react-translated`
* [npm](https://www.npmjs.com): `npm install react-translated`


## Setup

#### Step 1: Create the translations file

Create a file that will contain a mapping of keys to the string in each language you support.

To keep things simple, use the strings of your default language as the key:

```js
// translation.js

export default {
'Hi, World!': {
en: 'Hi, World!',
fr: 'Bonjour le monde!',
},
// ...
}
```

> NOTE: There is no enforcement on the key used for a language. In these examples, [2-digit country codes](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Officially_assigned_code_elements) (`en`, `fr`, etc) are used. Decide on a convention and use that for all translations.

#### Step 2: Connect the `Provider`

Wrap your top-level component with the `` and set the `translation` and `language` props:

```jsx
// index.js

import { Provider } from 'react-translated'
import translation from './translation'
const App = (



)
```

> NOTE: The value of the `language` prop must be one of the keys used for a language defined in Step 1.

#### Step 3: Start translating

That is all!

Continue reading below to see how to handle the various translation scenarios.


## Usage

The library can be imported in whatever way you find suitable:

```js
import ReactTranslated from 'react-translated'
import * as ReactTranslated from 'react-translated'

```

Or:

```js
import { Provider, Translate, Translator } from 'react-translated'

```

#### `Translate` vs `Translator`

The `Translate` component should **always** be used when the translation is rendered as a child component; such as buttons, paragraphs, headings, etc.

The `Translator` component should **only** be used when the translation is needed as a string; such as placeholders, alternate text, etc.

#### Translation scenarios

* [Static text](#static-text)
* [Templated text](#templated-text)
* [Dynamically templated text](#dynamically-templated-text)
* [Styled text](#styled-text)
* [Component within text](#component-within-text)
* [Translated text as string](#translated-text-as-string) (for text input placeholders)


### Static text

This is pretty self-explanatory:

```jsx
// translation.js
export default {
'Hi, World!': {
en: 'Hi, World!',
fr: 'Bonjour le monde!',
},
}

// any component file

```

Renders as:

![](docs/hi_world.png)

### Templated text

To use dynamic text, the text can be templated:

```jsx
// translation.js
export default {
'Hi, {firstName}!': {
en: 'Hi, {firstName}!',
fr: 'Salut {firstName}!',
},
}

// any component file

```

Renders as:

![](docs/hi_sergey.png)

### Dynamically templated text

Sometimes just dynamic text is not enough and the template itself needs to be dynamic (for example pluralization). That can be achieved using a function call:

```jsx
// translation.js
export default {
'There are {catsCount} cats in this room.': {
en({ catsCount }) {
if (catsCount === 1) {
return 'There is {catsCount} cat in this room.'
}
return 'There are {catsCount} cats in this room.'
},
// ...
},
}

// any component file

```

Renders as:

![](docs/cats_in_room.png)

Since these templates are simple function calls, things more complex than pluralization can be done too:

```jsx
// translation.js
export default {
'This is a {fruit}': {
en({ fruit }) {
if (/^[aeiou]/.test(fruit)) {
return 'This is an {fruit}'
}
return 'This is a {fruit}'
},
// ...
},
}

// any component file

```

Renders as:

![](docs/this_is_a_fruit.png)

### Styled text

The translated text can also have some basic styling applied:

```jsx
// translation.js
export default {
'Hi, *World*!': {
en: 'Hi, *World*!',
fr: 'Bonjour *le monde*!',
},
}

// any component file

```

Renders as:

![](docs/styled_hi_world.png)

And of course the same can be done with dynamic templates:

```jsx
// translation.js
export default {
'Hi, *{firstName}*!': {
en: 'Hi, *{firstName}*!',
fr: 'Salut *{firstName}*!',
},
}

// any component file

```

Renders as:

![](docs/styled_hi_sergey.png)

### Component within text

For more advanced uses where Markdown and Emojis don’t suffice, components can be rendered within the text:

```jsx
// translation.js
export default {
'Tap the to add': {
en: 'Tap the to add',
fr: 'Appuyez sur la pour ajouter',
},
}

// any component file

}}
/>
```

Renders as:

![](docs/tap_the_star.png)

Another practical application of this is nested translations - text that requires data that also needs to be translated:

```jsx
// translation.js
export default {
'I was born in ': {
en: 'I was born in ',
fr: 'Je suis nΓ© en ',
},
'August': {
en: 'August',
fr: 'aoΓ»t',
},
}

// any component file
const monthName = 'August'

}}
/>
```

Renders as:

![](docs/born_in_august.png)


### Translated text as string

> _Added v2.2.0_

In scenarios where the translated text is required as a string, such as with text inputs placeholders or accessibility labels, the `Translator` can be used:

```jsx
// translation.js
export default {
'Enter your age {firstName}': {
en: 'Enter your age {firstName}',
fr: 'entrez votre Γ’ge {firstName}',
},
}

// any component file

{({ translate }) => (

)}

```

Renders as:

![](docs/age_sergey.png)


## Contributors

| [
amsul](http://amsul.ca)
[πŸ’»](https://github.com/Amsul/react-translated/commits?author=amsul "Code") [🎨](#design-amsul "Design") [πŸ“–](https://github.com/Amsul/react-translated/commits?author=amsul "Documentation") [πŸ’‘](#example-amsul "Examples") [πŸ”§](#tool-amsul "Tools") | [
Johnson Su](https://johnsonsu.com)
[πŸ›](https://github.com/Amsul/react-translated/issues?q=author%3Ajohnsonsu "Bug reports") [πŸ’»](https://github.com/Amsul/react-translated/commits?author=johnsonsu "Code") |
| :---: | :---: |

πŸ‘‹ Interested becoming a contributor too?

Awesome! This project follows the [all-contributors](https://github.com/kentcdodds/all-contributors)
specification. Contributions of any kind are welcome!

You may also want to take a look at our [TODOs](#todos) below and make sure to give our [Contributing](https://github.com/amsul/react-translated/blob/master/CONTRIBUTING.md) guide a read.


## TODOs

* Add tests using [Jest](https://facebook.github.io/jest/)


## License

Licensed under [MIT](https://github.com/amsul/react-translated/blob/master/LICENSE).

Β© 2019 [Amsul](http://twitter.com/amsul_)