Home » Reactjs » React / Redux and Multilingual (Internationalization) Apps – Architecture

React / Redux and Multilingual (Internationalization) Apps – Architecture

Posted by: admin November 29, 2017 Leave a comment


I’m building an app that will need to be available in multiple languages and locales.

My question is not purely technical, but rather about the architecture, and the patterns that people are actually using in production to solve this problem.
I couldn’t find anywhere any “cookbook” for that, so I’m turning to my favourite Q/A website 🙂

Here are my requirements (they are really “standard”):

  • The user can choose the language (trivial)
  • Upon changing the language, the interface should translate automatically to the new selected language
  • I’m not too worried about formatting numbers, dates etc. at the moment, I want a simple solution to just translate strings

Here are the possible solutions I could think off:

Each component deal with translation in isolation

This means that each component have for example a set of en.json, fr.json etc. files alongside it with the translated strings. And a helper function to help reading the values from those depending on the selected language.

  • Pro: more respectful of the React philosophy, each component is “standalone”
  • Cons: you can’t centralize all the translations in a file (to have someone else add a new language for example)
  • Cons: you still need to pass the current language as a prop, in every bloody component and their children

Each component receives the translations via the props

So they are not aware of the current language, they just take a list of strings as props which happen to match the current language

  • Pro: since those strings are coming “from the top”, they can be centralized somewhere
  • Cons: Each component is now tied into the translation system, you can’t just re-use one, you need to specify the correct strings every time

You bypass the props a bit and possibly use the context thingy to pass down the current language

  • Pro: it’s mostly transparent, don’t have to pass the current language and/or translations via props all the time
  • Cons: it looks cumbersome to use

If you have any other idea, please do say!

How do you do it?


After trying quite a few solutions, I think I found one that works well and should be an idiomatic solution for React 0.14 (i.e. it doesn’t use mixins, but Higher Order Components) (edit: also perfectly fine with React 15 of course!).

So here the solution, starting by the bottom (the individual components):

The Component

The only thing your component would need (by convention), is a strings props.
It should be an object containing the various strings your Component needs, but really the shape of it is up to you.

It does contain the default translations, so you can use the component somewhere else without the need to provide any translation (it would work out of the box with the default language, english in this example)

import { default as React, PropTypes } from 'react';
import translate from './translate';

class MyComponent extends React.Component {
    render() {

        return (
                { this.props.strings.someTranslatedText }

MyComponent.propTypes = {
    strings: PropTypes.object

MyComponent.defaultProps = {
     strings: {
         someTranslatedText: 'Hello World'

export default translate('MyComponent')(MyComponent);

The Higher Order Component

On the previous snippet, you might have noticed this on the last line:

translate in this case is a Higher Order Component that wraps your component, and provide some extra functionality (this construction replaces the mixins of previous versions of React).

The first argument is a key that will be used to lookup the translations in the translation file (I used the name of the component here, but it could be anything). The second one (notice that the function is curryed, to allow ES7 decorators) is the Component itself to wrap.

Here is the code for the translate component:

import { default as React } from 'react';
import en from '../i18n/en';
import fr from '../i18n/fr';

const languages = {

export default function translate(key) {
    return Component => {
        class TranslationComponent extends React.Component {
            render() {
                console.log('current language: ', this.context.currentLanguage);
                var strings = languages[this.context.currentLanguage][key];
                return <Component {...this.props} {...this.state} strings={strings} />;

        TranslationComponent.contextTypes = {
            currentLanguage: React.PropTypes.string

        return TranslationComponent;

It’s not magic: it will just read the current language from the context (and that context doesn’t bleed all over the code base, just used here in this wrapper), and then get the relevant strings object from loaded files. This piece of logic is quite naïve in this example, could be done the way you want really.

The important piece is that it takes the current language from the context and convert that into strings, given the key provided.

At the very top of the hierarchy

On the root component, you just need to set the current language from your current state. The following example is using Redux as the Flux-like implementation, but it can easily be converted using any other framework/pattern/library.

import { default as React, PropTypes } from 'react';
import Menu from '../components/Menu';
import { connect } from 'react-redux';
import { changeLanguage } from '../state/lang';

class App extends React.Component {
    render() {
        return (
                <Menu onLanguageChange={this.props.changeLanguage}/>
                <div className="">



    getChildContext() {
        return {
            currentLanguage: this.props.currentLanguage

App.propTypes = {
    children: PropTypes.object.isRequired,

App.childContextTypes = {
    currentLanguage: PropTypes.string.isRequired

function select(state){
    return {user: state.auth.user, currentLanguage: state.lang.current};

function mapDispatchToProps(dispatch){
    return {
        changeLanguage: (lang) => dispatch(changeLanguage(lang))

export default connect(select, mapDispatchToProps)(App);

And to finish, the translation files:

Translation Files

// en.js
export default {
    MyComponent: {
        someTranslatedText: 'Hello World'
    SomeOtherComponent: {
        foo: 'bar'

// fr.js
export default {
    MyComponent: {
        someTranslatedText: 'Salut le monde'
    SomeOtherComponent: {
        foo: 'bar mais en français'

What do you guys think?

I think is solves all the problem I was trying to avoid in my question: the translation logic doesn’t bleed all over the source code, it is quite isolated and allows reusing the components without it.

For example, MyComponent doesn’t need to be wrapped by translate() and could be separate, allowing it’s reuse by anyone else wishing to provide the strings by their own mean.

[Edit: 31/03/2016]: I recently worked on a Retrospective Board (for Agile Retrospectives), built with React & Redux, and is multilingual.
Since quite a lot of people asked for a real-life example in the comments, here it is:

You can find the code here: https://github.com/antoinejaussoin/retro-board/tree/master


From my experience the best approach is to create an i18n redux state and use it, for many reasons:

1- This will allow you to pass the initial value from the database, local file or even from a template engine such as ejs or jade

2- When the user change the language you can change the whole application language without even refreshing the UI.

3- When the user change the language this will also allow you to retrieve the new language from api, local file or even from constants

4- You can also save other important things with the strings such as timezone, currency, direction (RTL/LTR) and list of available languages

5- You can define the change language as a normal redux action

6- You can have your backend and front end strings in one place, for example in my case i use i18n-node for localization and when the user change the ui language i just do a normal api call and in the backend i just return i18n.getCatalog(req) this will return all the user strings only for the current language

My suggestion for the i18n initial state is:

    {"code":"en","name": "English"},
     "Thank You":"شكراً",
     "You have {count} new messages":"لديك {count} رسائل جديدة"

Extra useful modules for i18n:

1- string-template this will allow you to inject values in between your catalog strings for example:

import template from "string-template";
const count = 7;
template(i18n.catalog["You have {count} new messages"],{count}) // لديك ٧ رسائل جديدة

2- human-format this module will allow you to converts a number to/from a human readable string, for example:

import humanFormat from "human-format";
humanFormat(1337); // => '1.34 k'
// you can pass your own translated scale, e.g: humanFormat(1337,MyScale)

3- momentjs the most famous dates and times npm library, you can translate moment but its already has a built-in translation just you need to pass the current state language for example:

import moment from "moment";

const umoment = moment().locale(i18n.language);
umoment.format('MMMM Do YYYY, h:mm:ss a'); // أيار مايو ٢ ٢٠١٧، ٥:١٩:٥٥ م


Antoine’s solution works fine, but have some caveats :

  • It uses the React context directly, which I tend to avoid when already using Redux
  • It imports directly phrases from a file, which can be problematic if you want to fetch needed language at runtime, client-side
  • It does not use any i18n library, which is lightweight, but doesn’t give you access to handy translation functionalities like pluralization and interpolation

That’s why we built redux-polyglot on top of both Redux and AirBNB’s Polyglot.
(I’m one of the authors)

It provides :

  • a reducer to store language and corresponding messages in your Redux store. You can supply both by either :
    • a middleware that you can configure to catch specific action, deduct current language and get/fetch associated messages.
    • direct dispatch of setLanguage(lang, messages)
  • a getP(state) selector that retrieves a P object that exposes 4 methods :
    • t(key): original polyglot T function
    • tc(key): capitalized translation
    • tu(key): upper-cased translation
    • tm(morphism)(key): custom morphed translation
  • a getLocale(state)selector to get current language
  • a translate higher order component to enhance your React components by injecting the p object in props

Simple usage example :

dispatch new language :

import setLanguage from 'redux-polyglot/setLanguage';

store.dispatch(setLanguage('en', {
    common: { hello_world: 'Hello world' } } }

in component :

import React, { PropTypes } from 'react';
import translate from 'redux-polyglot/translate';

const MyComponent = props => (
  <div className='someId'>
MyComponent.propTypes = {
  p: PropTypes.shape({t: PropTypes.func.isRequired}).isRequired,
export default translate(MyComponent);

Please tell me if you have any question/suggestion !


From my research into this there appears to be two main approaches being used to i18n in JavaScript, ICU and gettext.

I’ve only ever used gettext, so I’m biased.

What amazes me is how poor the support is. I come from the PHP world, either CakePHP or WordPress. In both of those situations, it’s a basic standard that all strings are simply surrounded by __(''), then further down the line you get translations using PO files very easily.


You get the familiarity of sprintf for formatting strings and PO files will be translated easily by thousands of different agencies.

There’s two popular options:

  1. i18next, with usage described by this arkency.com blog post
  2. Jed, with usage described by the sentry.io post and this React+Redux post,

Both have gettext style support, sprintf style formatting of strings and import / export to PO files.

i18next has a React extension developed by themselves. Jed doesn’t. Sentry.io appear to use a custom integration of Jed with React. The React+Redux post, suggests using

Tools: jed + po2json + jsxgettext

However Jed seems like a more gettext focussed implementation – that is it’s expressed intention, where as i18next just has it as an option.


This has more support for the edge cases around translations, e.g. for dealing with gender. I think you will see the benefits from this if you have more complex languages to translate into.

A popular option for this is messageformat.js. Discussed briefly in this sentry.io blog tutorial. messageformat.js is actually developed by the same person that wrote Jed. He makes quite stong claims for using ICU:

Jed is feature complete in my opinion. I am happy to fix bugs, but generally am not interested in adding more to the library.

I also maintain messageformat.js. If you don’t specifically need a gettext implementation, I might suggest using MessageFormat instead, as it has better support for plurals/gender and has built-in locale data.

Rough comparison

gettext with sprintf:

i18next.t('Hello world!');
    'The first 4 letters of the english alphabet are: %s, %s, %s and %s', 
    { postProcess: 'sprintf', sprintf: ['a', 'b', 'c', 'd'] }

messageformat.js (my best guess from reading the guide):

mf.compile('Hello world!')();
    'The first 4 letters of the english alphabet are: {s1}, {s2}, {s3} and {s4}'
)({ s1: 'a', s2: 'b', s3: 'c', s4: 'd' });


If not yet done having a look at https://react.i18next.com/ might be a good advice. It is based on i18next: learn once – translate everywhere.

Your code will look something like:

<Trans i18nKey="userMessagesUnread" count={count}>
  Hello <strong title={t('nameTitle')}>{{name}}</strong>, you have {{count}} unread message. <Link to="/msgs">Go to messages</Link>.

Comes with samples for:

  • webpack
  • cra
  • expo.js
  • next.js
  • storybook integration
  • razzle
  • dat


Beside that you should also consider workflow during development and later for your translators -> https://www.youtube.com/watch?v=9NOzJhgmyQE