The progressive guide to jQuery internationalization (i18n) using i18next

jQuery localization

Every web developer may have met the perennial Methuselah jQuery. Created back in January 2006 at BarCamp NYC by John Resig and currently maintained by a team of developers led by Timmy Willison.

You may think:

Why a blog post about the venerable but aged JavaScript library, that made things like HTML document traversal and manipulation, etc. easier?

Because with a combination of versatility and extensibility, jQuery has changed the way that millions of people write JavaScript!

And you can see this by the huge usage of jQuery:

Based on w3Techs web technology surveys, jQuery is used by 95.4% of all the websites whose JavaScript library they know. And 78.3% of all websites.

Checking the npm download trends of the jquery module it is approaching the 5 million downloads per week.

So you see, jQuery is not only still relevant, it takes up the majority of all websites.

Therefore, in this article, we will be using the i18next framework to internationalize a jQuery website.

TOC

So first of all: "Why i18next?"

When it comes to jQuery localization. One of the most popular is i18next with it's jQuery extension jquery-i18next, and for good reasons:

i18next was created in late 2011. It's older than most of the libraries you will use nowadays, including your main frontend technology (react, vue, ...). Only jQuery is older πŸ˜‰

➑️ sustainable

Based on how long i18next already is available open source, there is no real i18n case that could not be solved with i18next.

➑️ mature

i18next can be used in any javascript (and a few non-javascript - .net, elm, iOS, android, ruby, ...) environment, with any UI framework, with any i18n format, ... the possibilities are endless.

➑️ extensible

There is a plenty of features and possibilities you'll get with i18next compared to other regular 18n frameworks.

➑️ rich

Here you can find more information about why i18next is special and how it works.

Let's get into it...

Prerequisites

Make sure you have a jQuery based website or web app. It's best, if you have some experience with simple HTML, JavaScript and basic jQuery, before jumping to jquery-i18next. This jQuery i18n example is not intended to be a jQuery beginner tutorial.

Getting started

Take your own jQuery project or create a new one.

I have here an awesome landing page πŸ˜‰

We are going to adapt the website to detect the language according to the user’s preference. And we will create a language switcher to make the content change between different languages.

Let's install some i18next dependencies:

1
2
3
<script src="https://cdn.jsdelivr.net/npm/[email protected]/i18next.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/[email protected]/jquery-i18next.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/[email protected]/i18nextBrowserLanguageDetector.min.js"></script>

Let's prepare an i18n.js file:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
$(function () {
// use plugins and options as needed, for options, detail see
// https://www.i18next.com
i18next
// detect user language
// learn more: https://github.com/i18next/i18next-browser-languageDetector
.use(i18nextBrowserLanguageDetector)
// init i18next
// for all options read: https://www.i18next.com/overview/configuration-options
.init({
debug: true,
fallbackLng: 'en',
resources: {
en: {
translation: {
// here we will place our translations...
}
}
}
}, (err, t) => {
if (err) return console.error(err);

// for options see
// https://github.com/i18next/jquery-i18next#initialize-the-plugin
jqueryI18next.init(i18next, $, { useOptionsAttr: true });

// start localizing, details:
// https://github.com/i18next/jquery-i18next#usage-of-selector-function
$('body').localize();
});
});

Let's load that file:

1
2
3
4
5
<script src="https://cdn.jsdelivr.net/npm/[email protected]/i18next.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/[email protected]/jquery-i18next.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/[email protected]/i18nextBrowserLanguageDetector.min.js"></script>

<script src="js/i18n.js"></script>

Now let's try to move some hard coded text out to the translations.

1
2
3
4
<!-- ... -->
<h1 data-i18n="intro.title">Landing Page</h1>
<h3 data-i18n="intro.subTitle">Some subtitle</h3>
<!-- ... -->

Since the texts will be part of our translation resources, they could also be removed:

1
2
3
4
<!-- ... -->
<h1 data-i18n="intro.title"></h1>
<h3 data-i18n="intro.subTitle"></h3>
<!-- ... -->

The texts are now part of the translation resources:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
$(function () {
// use plugins and options as needed, for options, detail see
// https://www.i18next.com
i18next
// detect user language
// learn more: https://github.com/i18next/i18next-browser-languageDetector
.use(i18nextBrowserLanguageDetector)
// init i18next
// for all options read: https://www.i18next.com/overview/configuration-options
.init({
debug: true,
fallbackLng: 'en',
resources: {
en: {
translation: {
intro: {
title: 'Landing Page',
subTitle: 'Some subtitle'
}
}
}
}
}, (err, t) => {
if (err) return console.error(err);

// for options see
// https://github.com/i18next/jquery-i18next#initialize-the-plugin
jqueryI18next.init(i18next, $, { useOptionsAttr: true });

// start localizing, details:
// https://github.com/i18next/jquery-i18next#usage-of-selector-function
$('body').localize();
});
});

Language Switcher

Now let's define a language switcher:

1
2
3
<!-- ... -->
<select name="language" id="languageSwitcher"></select>
<!-- ... -->

And also add some translations for the new language:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
const lngs = {
en: { nativeName: 'English' },
de: { nativeName: 'Deutsch' }
};

const rerender = () => {
// start localizing, details:
// https://github.com/i18next/jquery-i18next#usage-of-selector-function
$('body').localize();
}

$(function () {
// use plugins and options as needed, for options, detail see
// https://www.i18next.com
i18next
// detect user language
// learn more: https://github.com/i18next/i18next-browser-languageDetector
.use(i18nextBrowserLanguageDetector)
// init i18next
// for all options read: https://www.i18next.com/overview/configuration-options
.init({
debug: true,
fallbackLng: 'en',
resources: {
en: {
translation: {
intro: {
title: 'Landing Page',
subTitle: 'Some subtitle'
}
}
},
de: {
translation: {
intro: {
title: 'Webseite',
subTitle: 'Ein Untertitel'
}
}
}
}
}, (err, t) => {
if (err) return console.error(err);

// for options see
// https://github.com/i18next/jquery-i18next#initialize-the-plugin
jqueryI18next.init(i18next, $, { useOptionsAttr: true });

// fill language switcher
Object.keys(lngs).map((lng) => {
const opt = new Option(lngs[lng].nativeName, lng);
if (lng === i18next.resolvedLanguage) {
opt.setAttribute("selected", "selected");
}
$('#languageSwitcher').append(opt);
});
$('#languageSwitcher').change((a, b, c) => {
const chosenLng = $(this).find("option:selected").attr('value');
i18next.changeLanguage(chosenLng, () => {
rerender();
});
});

rerender();
});
});

jquery language switcher

πŸ₯³ Awesome, you've just created your first language switcher!

Thanks to i18next-browser-languagedetector now it tries to detect the browser language and automatically use that language if you've provided the translations for it. The manually selected language in the language switcher is persisted in the localStorage, next time you visit the page, that language is used as preferred language.

Translate head information

Let's translate also the title and description of the website. We do this by extending our rerender function, and adding the additional translation resources:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
const rerender = () => {
// start localizing, details:
// https://github.com/i18next/jquery-i18next#usage-of-selector-function
$('body').localize();

$('title').text($.t('head.title'))
$('meta[name=description]').attr('content', $.t('head.description'))
}

// ...

resources: {
en: {
translation: {
head: {
title: 'My Awesome Landing-Page',
description: 'The description of this awesome landing page.'
},
intro: {
title: 'Landing Page',
subTitle: 'Some subtitle'
}
}
},
de: {
translation: {
head: {
title: 'Meine grossartige Webseite',
description: 'Die Beschreibung dieser grossartigen Webseite.'
},
intro: {
title: 'Webseite',
subTitle: 'Ein Untertitel'
}
}
}
}

So you see, this can be also done with the $.t() helper function.

Let's check the DOM:

Nice πŸ‘

Interpolation and Pluralization

i18next goes beyond just providing the standard i18n features. But for sure it's able to handle plurals and interpolation.

Let's count each time the language gets changed:

1
2
3
4
5
6
7
8
<!-- ... -->
<li>
<select name="language" id="languageSwitcher"></select>
</li>
<li id="languageChangedNotification" style="display: none;">
<i data-i18n="footer.counter" data-i18n-options='{ "count": 0 }'></i>
</li>
<!-- ... -->

Let's remember the count in the languageChangedCounter variable and increment it on each language change.
...and extending the translation resources:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
const lngs = {
en: { nativeName: 'English' },
de: { nativeName: 'Deutsch' }
};

const rerender = () => {
// start localizing, details:
// https://github.com/i18next/jquery-i18next#usage-of-selector-function
$('body').localize();

$('title').text($.t('head.title'))
$('meta[name=description]').attr('content', $.t('head.description'))
}

$(function () {
// use plugins and options as needed, for options, detail see
// https://www.i18next.com
i18next
// detect user language
// learn more: https://github.com/i18next/i18next-browser-languageDetector
.use(i18nextBrowserLanguageDetector)
// init i18next
// for all options read: https://www.i18next.com/overview/configuration-options
.init({
debug: true,
fallbackLng: 'en',
resources: {
en: {
translation: {
head: {
title: 'My Awesome Landing-Page',
description: 'The description of this awesome landing page.'
},
intro: {
title: 'Landing Page',
subTitle: 'Some subtitle'
},
footer: {
counter_one: 'Changed language just once',
counter_other: 'Changed language already {{count}} times'
}
}
},
de: {
translation: {
head: {
title: 'Meine grossartige Webseite',
description: 'Die Beschreibung dieser grossartigen Webseite.'
},
intro: {
title: 'Webseite',
subTitle: 'Ein Untertitel'
},
footer: {
counter_one: 'Die Sprache wurde erst ein mal gewechselt',
counter_other: 'Die Sprache wurde {{count}} mal gewechselt'
}
}
}
}
}, (err, t) => {
if (err) return console.error(err);

// for options see
// https://github.com/i18next/jquery-i18next#initialize-the-plugin
jqueryI18next.init(i18next, $, { useOptionsAttr: true });

// fill language switcher
Object.keys(lngs).map((lng) => {
const opt = new Option(lngs[lng].nativeName, lng);
if (lng === i18next.resolvedLanguage) {
opt.setAttribute("selected", "selected");
}
$('#languageSwitcher').append(opt);
});
let languageChangedCounter = 0;
$('#languageSwitcher').change((a, b, c) => {
const chosenLng = $(this).find("option:selected").attr('value');
i18next.changeLanguage(chosenLng, () => {
rerender();

// language changed message
languageChangedCounter++;
$('#languageChangedNotification').localize({ count: languageChangedCounter })
if (languageChangedCounter === 1) {
$('#languageChangedNotification').show();
}
});
});

rerender();
});
});

Based on the count value i18next will choose the correct plural form. Read more about pluralization and interpolation in the official i18next documentation.

jQuery pluralization

πŸ’‘ i18next is also able to handle languages with multiple plural forms, like arabic:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
// translation resources:
{
"key_zero": "zero",
"key_one": "singular",
"key_two": "two",
"key_few": "few",
"key_many": "many",
"key_other": "other"
}

// usage:
t('key', {count: 0}); // -> "zero"
t('key', {count: 1}); // -> "singular"
t('key', {count: 2}); // -> "two"
t('key', {count: 3}); // -> "few"
t('key', {count: 4}); // -> "few"
t('key', {count: 5}); // -> "few"
t('key', {count: 11}); // -> "many"
t('key', {count: 99}); // -> "many"
t('key', {count: 100}); // -> "other"

Formatting

Now, let’s check out how we can use different date formats with the help of i18next and moment.js to handle date and time.

1
2
3
<!-- ... -->
<script src="https://cdn.jsdelivr.net/npm/[email protected]/min/moment-with-locales.min.js"></script>
<!-- ... -->

We like to have the footer displaying the current date:

1
2
3
<!-- ... -->
<p id="footerMessage" class="text-muted small" data-i18n="footer.date"></p>
<!-- ... -->

Define a format function, like documented in the documentation and add the new translation key:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
const lngs = {
en: { nativeName: 'English' },
de: { nativeName: 'Deutsch' }
};

const rerender = () => {
// start localizing, details:
// https://github.com/i18next/jquery-i18next#usage-of-selector-function
$('body').localize();

$('title').text($.t('head.title'))
$('meta[name=description]').attr('content', $.t('head.description'))
}

$(function () {
// use plugins and options as needed, for options, detail see
// https://www.i18next.com
i18next
// detect user language
// learn more: https://github.com/i18next/i18next-browser-languageDetector
.use(i18nextBrowserLanguageDetector)
// init i18next
// for all options read: https://www.i18next.com/overview/configuration-options
.init({
debug: true,
fallbackLng: 'en',
resources: {
en: {
translation: {
head: {
title: 'My Awesome Landing-Page',
description: 'The description of this awesome landing page.'
},
intro: {
title: 'Landing Page',
subTitle: 'Some subtitle'
},
footer: {
counter_one: 'Changed language just once',
counter_other: 'Changed language already {{count}} times',
date: 'It\'s {{date, LLLL}}'
}
}
},
de: {
translation: {
head: {
title: 'Meine grossartige Webseite',
description: 'Die Beschreibung dieser grossartigen Webseite.'
},
intro: {
title: 'Webseite',
subTitle: 'Ein Untertitel'
},
footer: {
counter_one: 'Die Sprache wurde erst ein mal gewechselt',
counter_other: 'Die Sprache wurde {{count}} mal gewechselt',
date: 'Es ist {{date, LLLL}}'
}
}
}
}
}, (err, t) => {
if (err) return console.error(err);

// define the formatter function
i18next.services.formatter.add('LLLL', (value, lng, options) => {
return moment(value).locale(lng).format('LLLL');
});

// for options see
// https://github.com/i18next/jquery-i18next#initialize-the-plugin
jqueryI18next.init(i18next, $, { useOptionsAttr: true });

// fill language switcher
Object.keys(lngs).map((lng) => {
const opt = new Option(lngs[lng].nativeName, lng);
if (lng === i18next.resolvedLanguage) {
opt.setAttribute("selected", "selected");
}
$('#languageSwitcher').append(opt);
});
let languageChangedCounter = 0;
$('#languageSwitcher').change((a, b, c) => {
const chosenLng = $(this).find("option:selected").attr('value');
i18next.changeLanguage(chosenLng, () => {
rerender();

// language changed message
languageChangedCounter++;
$('#languageChangedNotification').localize({ count: languageChangedCounter })
if (languageChangedCounter === 1) {
$('#languageChangedNotification').show();
}
});
});

rerender();
});
});

😎 Cool, now we have a language specific date formatting!

English: jQuery english

German: jQuery german

Context

What about a specific greeting message based on the current day time? i.e. morning, evening, etc. This is possible thanks to the context feature of i18next.

Let's create a getGreetingTime function and use the result as context information for our footer translation.
And add some context specific translations keys:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
// ...

const getGreetingTime = () => {
const split_afternoon = 12; // 24hr time to split the afternoon
const split_evening = 17; // 24hr time to split the evening
const currentHour = moment().hour();

if (currentHour >= split_afternoon && currentHour <= split_evening) {
return 'afternoon';
} else if (currentHour >= split_evening) {
return 'evening';
}
return 'morning';
}

const rerender = () => {
// start localizing, details:
// https://github.com/i18next/jquery-i18next#usage-of-selector-function
$('body').localize();
$('#footerMessage').localize({ context: getGreetingTime() });
$('title').text($.t('head.title'))
$('meta[name=description]').attr('content', $.t('head.description'))
}

// ...

resources: {
en: {
translation: {
// ...
footer: {
counter_one: 'Changed language just once',
counter_other: 'Changed language already {{count}} times',
date: 'It\'s {{date, LLLL}}',
date_afternoon: 'Good afternoon! It\'s {{date, LLLL}}',
date_evening: 'Good evening! Today was the {{date, LLLL}}',
date_morning: 'Good morning! Today is {{date, LLLL}} | Have a nice day!'
}
}
},
de: {
translation: {
// ...
footer: {
counter_one: 'Die Sprache wurde erst ein mal gewechselt',
counter_other: 'Die Sprache wurde {{count}} mal gewechselt',
date: 'Es ist {{date, LLLL}}',
date_afternoon: 'Guten Tag! Es ist {{date, LLLL}}',
date_evening: 'Guten Abend! Heute war {{date, LLLL}}',
date_morning: 'Guten Morgen! Heute ist {{date, LLLL}} | WΓΌnsche einen schΓΆnen Tag!'
}
}
}
}

😁 Yeah, It works!

jQuery translations

Separate translations from code

Having the translations in our i18n.js file works, but is not that suitable to work with, for translators. Let's separate the translations from the code and pleace them in dedicated json files.

Because this is a web application, i18next-http-backend will help us to do so.

1
<script src="https://cdn.jsdelivr.net/npm/[email protected]/i18nextHttpBackend.min.js"></script>

Create a locales folder and move the translations there:

public locales

Adapt the i18n.js file to use the i18next-http-backend:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
// ...

$(function () {
// use plugins and options as needed, for options, detail see
// https://www.i18next.com
i18next
// i18next-http-backend
// loads translations from your server
// https://github.com/i18next/i18next-http-backend
.use(i18nextHttpBackend)
// detect user language
// learn more: https://github.com/i18next/i18next-browser-languageDetector
.use(i18nextBrowserLanguageDetector)
// init i18next
// for all options read: https://www.i18next.com/overview/configuration-options
.init({
debug: true,
fallbackLng: 'en'
}, (err, t) => {
if (err) return console.error(err);

// ...
});
});

Now the translations are loaded asynchronously, so it may be the UI will refresh a bit later, as soon as the translations are loaded. To optimize this behaviour, you can show some sort of loading indicator until the i18next is initialized.

Something like:

1
2
3
4
<div id="loader">Loading...</div>
<div id="content" style="display: none;">
<!-- your real content -->
</div>
1
2
$('#loader').hide();
$('#content').show();

Now your app looks still the same, but your translations are separated.

If you want to support a new language, you just create a new folder and a new translation json file. This gives you the possibility to send the translations to some translators. Or if you're working with a translation management system you can just synchronize the files with a cli.

Better translation management

By sending the translations to some translators or translator agency you have more control and a direct contact with them. But this also means more work for you. This is a traditional way. But be aware sending files around creates always an overhead.

Does a better option exist?

For sure!

i18next helps to get the application translated, and this is great - but there is more to it.

  • How do you integrate any translation services / agency?
  • How do you keep track of new or removed content?
  • How you handle proper versioning?
  • How you deploy translation changes without deploying your complete application?
  • and a lot more...

Looking for something like this❓

transform the localization process

How does this look like?

First you need to signup at locize and login. Then create a new project in locize and add your translations. You can add your translations either by using the cli or by importing the individual json files or via API.

Done so, we're going to replace i18next-http-backend with i18next-locize-backend.

1
2
3
<!-- ... -->
<script src="https://cdn.jsdelivr.net/npm/[email protected]/i18nextLocizeBackend.min.js"></script>
<!-- ... -->

After having imported the translations to locize, delete the locales folder and adapt the i18n.js file to use the i18next-locize-backend and make sure you copy the project-id and api-key from within your locize project:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
// ...

const locizeOptions = {
projectId: '8d751621-323e-4bda-94c8-7d2368102e62',
apiKey: '302aca54-2ea8-4b9f-b5f0-df1369c59427' // YOU should not expose your apps API key to production!!!
};

$(function () {
// use plugins and options as needed, for options, detail see
// https://www.i18next.com
i18next
// i18next-locize-backend
// loads translations from your project, saves new keys to it (saveMissing: true)
// https://github.com/locize/i18next-locize-backend
.use(i18nextLocizeBackend)
// detect user language
// learn more: https://github.com/i18next/i18next-browser-languageDetector
.use(i18nextBrowserLanguageDetector)
// init i18next
// for all options read: https://www.i18next.com/overview/configuration-options
.init({
debug: true,
fallbackLng: 'en',
backend: locizeOptions
}, (err, t) => {
if (err) return console.error(err);

// ...
});
});

i18next-locize-backend offers a functionality to retrieve the available languages directly from locize, let's use it:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
// ...

const locizeOptions = {
projectId: '8d751621-323e-4bda-94c8-7d2368102e62',
apiKey: '302aca54-2ea8-4b9f-b5f0-df1369c59427' // YOU should not expose your apps API key to production!!!
};

$(function () {
const locizeBackend = new i18nextLocizeBackend(locizeOptions, (err, opts, lngs) => {
if (err) return console.error(err);

// use plugins and options as needed, for options, detail see
// https://www.i18next.com
i18next
// i18next-locize-backend
// loads translations from your project, saves new keys to it (saveMissing: true)
// https://github.com/locize/i18next-locize-backend
.use(locizeBackend)
// detect user language
// learn more: https://github.com/i18next/i18next-browser-languageDetector
.use(i18nextBrowserLanguageDetector)
// init i18next
// for all options read: https://www.i18next.com/overview/configuration-options
.init({
debug: true,
fallbackLng: 'en',
backend: locizeOptions
}, (err, t) => {
if (err) return console.error(err);

// new usage
i18next.services.formatter.add('LLLL', (value, lng, options) => {
return moment(value).locale(lng).format('LLLL');
});

// for options see
// https://github.com/i18next/jquery-i18next#initialize-the-plugin
jqueryI18next.init(i18next, $, { useOptionsAttr: true });

// fill language switcher
// with the lngs retrieved directly from locize...
Object.keys(lngs).map((lng) => {
const opt = new Option(lngs[lng].nativeName, lng);
if (lng === i18next.resolvedLanguage) {
opt.setAttribute("selected", "selected");
}
$('#languageSwitcher').append(opt);
});
let languageChangedCounter = 0;
$('#languageSwitcher').change((a, b, c) => {
const chosenLng = $(this).find("option:selected").attr('value');
i18next.changeLanguage(chosenLng, () => {
rerender();

// language changed message
languageChangedCounter++;
$('#languageChangedNotification').localize({ count: languageChangedCounter })
if (languageChangedCounter === 1) {
$('#languageChangedNotification').show();
}
});
});

rerender();

$('#loader').hide();
$('#content').show();
});
});
});

Now the translations are served directly from the locize CDN. The jQuery i18n has now CDN superpower 😁.

save missing translations

Thanks to the use of the saveMissing functionality, new keys gets added to locize automatically, while developing the app.

Just pass saveMissing: true in the i18next options:

1
2
3
4
5
6
7
8
// ...
.init({
debug: true,
fallbackLng: 'en',
backend: locizeOptions,
saveMissing: true // do not enable it on production
}, (err, t) => {
// ...

Each time you'll use a new key, it will be sent to locize, i.e.:

1
<div data-i18n="new.key">this will be added automatically</div>

will result in locize like this:

missing key

πŸ‘€ but there's more...

Thanks to the locize-lastused plugin, you'll be able to find and filter in locize which keys are used or not used anymore.

With the help of the locize plugin, you'll be able to use your app within the locize InContext Editor.

Lastly, with the help of the auto-machinetranslation workflow and the use of the saveMissing functionality, new keys not only gets added to locize automatically, while developing the app, but are also automatically translated into the target languages using machine translation.

Check out this video to see how the automatic machine translation workflow looks like!

1
2
3
4
<!-- ... -->
<script src="https://cdn.jsdelivr.net/npm/[email protected]/locizeLastUsed.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/[email protected]/locize.min.js"></script>
<!-- ... -->

use them in i18n.js:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
const getGreetingTime = () => {
const split_afternoon = 12; // 24hr time to split the afternoon
const split_evening = 17; // 24hr time to split the evening
const currentHour = moment().hour();

if (currentHour >= split_afternoon && currentHour <= split_evening) {
return 'afternoon';
} else if (currentHour >= split_evening) {
return 'evening';
}
return 'morning';
}

const rerender = () => {
// start localizing, details:
// https://github.com/i18next/jquery-i18next#usage-of-selector-function
$('body').localize();
$('#footerMessage').localize({ context: getGreetingTime() });
$('title').text($.t('head.title'))
$('meta[name=description]').attr('content', $.t('head.description'))
}

const locizeOptions = {
projectId: '8d751621-323e-4bda-94c8-7d2368102e62',
apiKey: '302aca54-2ea8-4b9f-b5f0-df1369c59427' // YOU should not expose your apps API key to production!!!
};

i18next.on('editorSaved', rerender); // used for the inContext editor

$(function () {
const locizeBackend = new i18nextLocizeBackend(locizeOptions, (err, opts, lngs) => {
if (err) return console.error(err);

// use plugins and options as needed, for options, detail see
// https://www.i18next.com
i18next
// locize-editor
// InContext Editor of locize
.use(locize.locizePlugin)
// locize-lastused (do not use this in production)
// sets a timestamp of last access on every translation segment on locize
// -> safely remove the ones not being touched for weeks/months
// https://github.com/locize/locize-lastused
.use(locizeLastUsed)
// i18next-locize-backend
// loads translations from your project, saves new keys to it (saveMissing: true)
// https://github.com/locize/i18next-locize-backend
.use(locizeBackend)
// detect user language
// learn more: https://github.com/i18next/i18next-browser-languageDetector
.use(i18nextBrowserLanguageDetector)
// init i18next
// for all options read: https://www.i18next.com/overview/configuration-options
.init({
...opts,
debug: true,
fallbackLng: 'en',
backend: locizeOptions,
locizeLastUsed: locizeOptions,
saveMissing: true
// interpolation: {
// // legacy usage
// format: (value, format, lng) => {
// if (value instanceof Date) {
// return moment(value).locale(lng).format(format);
// }
// return value;
// }
// }
}, (err, t) => {
if (err) return console.error(err);

// new usage
i18next.services.formatter.add('LLLL', (value, lng, options) => {
return moment(value).locale(lng).format('LLLL');
});

// for options see
// https://github.com/i18next/jquery-i18next#initialize-the-plugin
jqueryI18next.init(i18next, $, { useOptionsAttr: true });

// fill language switcher
Object.keys(lngs).map((lng) => {
const opt = new Option(lngs[lng].nativeName, lng);
if (lng === i18next.resolvedLanguage) {
opt.setAttribute("selected", "selected");
}
$('#languageSwitcher').append(opt);
});
let languageChangedCounter = 0;
$('#languageSwitcher').change((a, b, c) => {
const chosenLng = $(this).find("option:selected").attr('value');
i18next.changeLanguage(chosenLng, () => {
rerender();

// language changed message
languageChangedCounter++;
$('#languageChangedNotification').localize({ count: languageChangedCounter })
if (languageChangedCounter === 1) {
$('#languageChangedNotification').show();
}
});
});

rerender();

$('#loader').hide();
$('#content').show();
});
});
});

Automatic machine translation:

missing key auto

Last used translations filter:

i18next last used

InContext Editor:

i18next incontext

Now, during development, you'll continue to save missing keys and to make use of lastused feature.

And in production environment, you should disable or remove the saveMissing and lastused functionality, and also the api-key should not exposed.

Caching:

i18next caching

Merging versions:

overwrite version

πŸ§‘β€πŸ’» The complete code can be found here.

Check also the code integration part in this YouTube video.

πŸŽ‰πŸ₯³ Congratulations 🎊🎁

I hope you’ve learned a few new things about i18next, jQuery localization and modern localization workflows.

So if you want to take your i18n topic to the next level, it's worth to try the localization management platform - locize.

The founders of locize are also the creators of i18next. So with using locize you directly support the future of i18next.

πŸ‘

Share