🌐jQuery based internationalization library

Overview

jQuery.i18n

npm

NOTE: For jquery independent version of this library, see https://github.com/wikimedia/banana-i18n

jQuery.i18n is a jQuery based Javascript internationalization library. It helps you to internationalize your web applications easily.

This is a project by Wikimedia foundation's Language Engineering team and used in some of the Wikimedia Foundation projects like Universal Language Selector.

The jquery.i18n library uses a json based localization file format, "banana", which is used as the localization file format for MediaWiki and other projects.

Features

  • Simple file format - JSON. Easily readable for humans and machines.
  • Author and metadata information is not lost anywhere. There are other file formats using comments to store this.
  • Uses MediaWiki convention for placeholders. Easily readable and proven convention. Example: There are $1 cars
  • Supports plural conversion without using extra messages for all plural forms. Plural rule handling is done using CLDR. Covers a wide range of languages
  • Supports gender. By passing the gender value, you get correct sentences according to gender.
  • Supports grammar forms. jquery.i18n has a basic but extensible grammar conversion support
  • Fallback chains for all languages.
  • Data api- the message key. Example: <li data-i18n="message-key"></li>.
  • Dynamic change of interface language without refreshing a webpage.
  • Nestable grammar, plural, gender support. These constructs can be nested to any arbitrary level for supporting sophisticated message localization
  • Message documentation through special language code qqq
  • Extensible message parser to add or customize magic words in the messages. Example: {sitename} or [[link]]

Quick start

git clone https://github.com/wikimedia/jquery.i18n.git
cd jquery.i18n
git submodule update --init

Testing

npm install

To run tests locally, run npm test, and this will run the tests.

Message File Format

The message files are json formatted. As a convention, you can have a folder named i18n inside your source code. For each language or locale, have a file named like languagecode.json.

Example:

App
	|--src
	|--doc
	|--i18n
		|--ar.json
		|--de.json
		|--en.json
		|--he.json
		|--hi.json
		|--fr.json
		|--qqq.json

A simple en.json file example is given below

{
	"@metadata": {
		"authors": [
			"Alice",
			"David",
			"Santhosh"
		],
		"last-updated": "2012-09-21",
		"locale": "en",
		"message-documentation": "qqq",
		"AnotherMetadata": "AnotherMedatadataValue"
	},
	"appname-title": "Example Application",
	"appname-sub-title": "An example application with jquery.i18n",
	"appname-header-introduction": "Introduction",
	"appname-about": "About this application",
	"appname-footer": "Footer text"
}

The json file should be a valid json. The @metadata holds all kind of data that are not messages. You can store author information, copyright, updated date or anything there.

Messages are key-value pairs. It is a good convention to prefix your appname to message keys to make the messages unique. It acts as the namespace for the message keys. It is also a good convention to have the message keys with - separated words, all in lower case.

If you are curious to see some real jquery.i18n message file from other projects:

Single message file for all languages

There are some alternate message file formats supported for different use cases. If your application is not big, and want all the translation in a single file, you can have it as shown in the below example:

{
	"@metadata": {
		"authors": [
			"Alice",
			"David",
			"Santhosh"
		],
		"last-updated": "2012-09-21",
		"locale": "en",
		"message-documentation": "qqq",
		"AnotherMetadata": "AnotherMedatadataValue"
	},
	"en": {
		"appname-title": "Example Application",
		"appname-sub-title": "An example application with jquery.i18n",
		"appname-header-introduction": "Introduction",
		"appname-about": "About this application",
		"appname-footer": "Footer text"
		},
	"ml": {
		"appname-title": "അപ്ലിക്കേഷന്‍ ഉദാഹരണം",
		"appname-sub-title": "jquery.i18n ഉപയോഗിച്ചുള്ള അപ്ലിക്കേഷന്‍ ഉദാഹരണം",
		"appname-header-introduction": "ആമുഖം",
		"appname-about": "ഈ അപ്ലിക്കേഷനെപ്പറ്റി",
		"appname-footer": "അടിക്കുറിപ്പു്"
	}
}

Here the json file contains language code as key-value and messagekey-message pairs as the value for all language pairs. You can choose this format or per-language file formats depending on your use case. Per-language files are more convenient for collaboration, version controlling, scalability, etc.

In this approach, it is also possible to give a file name as the value of language code.

{
	"@metadata": {
		"authors": [
			"Alice",
			"David",
			"Santhosh"
		],
		"last-updated": "2012-09-21",
		"locale": "en",
		"message-documentation": "qqq",
		"AnotherMetadata": "AnotherMedatadataValue"
	},
	"en": {
		"appname-title": "Example Application",
		"appname-sub-title": "An example application with jquery.i18n",
		"appname-header-introduction": "Introduction",
		"appname-about": "About this application",
		"appname-footer": "Footer text"
		},
	"ml": "path/to/ml.json"
}

Translation

To translate the jquery.i18n application, depending on the expertise of the translator, there are multiple ways.

  • Editing the json files directly - Suitable for translators with technical background. Also suitable if your application is small and you want to work with only a small number of languages
  • Providing a translation interface along with your application: Suitable for proprietary or private applications with significant amount of translators
  • Using open source translation platforms like translatewiki.net. The MediaWiki and jquery.uls from previous examples use translatewiki.net for crowdsourced message translation. Translatewiki.net can update your code repo at regular intervals with updated translations. Highly recommended if your application is opensource and want it to be localized to as many as languages possible with maximum number of translators.

Usage

Switching locale

While initializing the jquery.i18n, the locale for the page can be given using the locale option. For example

$.i18n( {
    locale: 'he' // Locale is Hebrew
} );

In case locale option is not given, jquery.i18n plugin will use the language attribute given for the html tag. For example

<html lang="he" dir="rtl">

In this case, the locale will be he(Hebrew). If that lang attribute is also missing, it will try to use the locale specified by the browser.

It is possible to switch to another locale after plugin is initialized. See below example:

$.i18n({
    locale: 'he' // Locale is Hebrew
});
$.i18n( 'message-hello' ); // This will give the Hebrew translation of message key `message-hello`.
$.i18n().locale = 'ml'; // Now onwards locale is 'Malayalam'
$.i18n( 'message-hello' ); // This will give the Malayalam translation of message key `message-hello`.

Message Loading

JSON formatted messages can be loaded to the plugin using multiple ways.

Dynamic loading using load method.

Following example shows loading messages for two locales- localex, and localey. Here localex and localey are just examples. They should be valid IS0 639 language codes(eg: en, ml, hi, fr, ta etc)

$.i18n().load( {
	'localex' : {
		'message-key1' : 'message1' // Message for localex.
	},
	'localey' : {
		'message-key1' : 'message1'
	}
} );

If we want to load the messages for a specific locale, it can be done like this:

$.i18n().load({
    'message-hello': 'Hello World',
    'message-welcome': 'Welcome'
}, 'en');

Note the second argument for the load method. It should be a valid language code.

It is also possible to refer messages from an external URL. See below example

$.i18n().load( {
	en: {
		'message-hello': 'Hello World',
		'message-welcome': 'Welcome'
	},
	hi: 'i18n/messages-hi.json', // Messages for Hindi
	de: 'i18n/messages-de.json'
} );

Messages for a locale can be also loaded in parts. Example

$.i18n().load( {
	en: {
		'message-hello': 'Hello World',
		'message-welcome': 'Welcome'
	}
} );

$.i18n().load( {
    	// This does not remove the previous messages.
	en: {
		'message-header' : 'Header',
		'message-footer' : 'Footer',
		// This will overwrite message-welcome message
		'message-welcome' : 'Welcome back'
	}
} );

Since it is desirable to render interface messages instantly and not after a delay of loading the message files from a server, make sure that the messages are present at client side before using jQuery.i18n.

The library should expose an API to load an object containing key-value pair of messages. Example: $.i18n.load(data). This will return a jQuery.Promise.

jquery.i18n plugin

The jQuery plugin defines $.i18n() and $.fn.i18n()

$.i18n( 'message-key-sample1' );
$.i18n( 'message-key-sample1' );
$.i18n( 'Found $1 {{plural:$1|result|results}}', 10 ); // Message key itself is message text
$.i18n( 'Showing $1 out of $2 {{plural:$2|result|results}}', 5,100 );
$.i18n( 'User X updated {{gender|his|her}} profile', 'male' );

$( '#foo' ).i18n(); // to translate the element matching jquery selector based on data-i18n key

Data API

It is possible to display localized messages without any custom JavaScript. For the HTML tags, add an attribute data-i18n with value as the message key. Example:

<li data-i18n="message-key"></li>.

It is also possible to have the above li node with fallback text already in place.

<li data-i18n="message-key">Fallback text</li>

The framework will place the localized message corresponding to message-key as the text value of the node. Similar to $('selector').i18n( ... ). This will not work for dynamically created elements.

Note that if data-i18n contains html markup, that html will not be used as the element content, instead, the text version will be used. But if the message key is prefixed with [html], the element's html will be changed. For example <li data-i18n="[html]message-key">Fallback html</li>, in this if the message-key has a value containing HTML markup, the <li> tags html will be replaced by that html.

If you want to change the html of the element, you can also use: $(selector).html($.i18n(messagekey))

Examples

See https://thottingal.in/projects/js/jquery.i18n/demo/

Message format

Placeholders

Messages take parameters. They are represented by $1, $2, $3, … in the message texts, and replaced at run time. Typical parameter values are numbers (Example: "Delete 3 versions?"), or user names (Example: "Page last edited by $1"), page names, links, and so on, or sometimes other messages.

var message = "Welcome, $1";
$.i18n(message, 'Alice'); // This gives "Welcome, Alice"

Plurals

To make the syntax of sentence correct, plural forms are required. jquery.i18n support plural forms in the message using the syntax {{PLURAL:$1|pluralform1|pluralform2|...}}

For example:

var message = "Found $1 {{PLURAL:$1|result|results}}";
$.i18n(message, 1); // This gives "Found 1 result"
$.i18n(message, 4); // This gives "Found 4 results"

Note that {{PLURAL:...}} is not case sensitive. It can be {{plural:...}} too.

In case of English, there are only 2 plural forms, but many languages use more than 2 plural forms. All the plural forms can be given in the above syntax, separated by pipe(|). The number of plural forms for each language is defined in CLDR. You need to provide all those plural forms for a language. Please note that many languages will require the inclusion of CLDRPluralRuleParser.js (from here) as well as this project's own files to work properly.

For example, English has 2 plural forms and the message format will look like {{PLURAL:$1|one|other}}. for Arabic there are 6 plural forms and format will look like {{PLURAL:$1|zero|one|two|few|many|other}}.

You cannot skip a plural form from the middle or beginning. However, you can skip from end. For example, in Arabic, if the message is like {{PLURAL:$1|A|B}}, for 0, A will be used, for numbers that fall under one, two, few, many, other categories B will be used.

If there is an explicit plural form to be given for a specific number, it is possible with the following syntax

var message = 'Box has {{PLURAL:$1|one egg|$1 eggs|12=a dozen eggs}}.';
$.i18n(message, 4 ); // Gives "Box has 4 eggs."
$.i18n(message, 12 ); // Gives "Box has a dozen eggs."

Gender

Similar to plural, depending on gender of placeholders, mostly user names, the syntax changes dynamically. An example in English is "Alice changed her profile picture" and "Bob changed his profile picture". To support this {{GENDER...}} syntax can be used as shown in example

var message = "$1 changed {{GENDER:$2|his|her}} profile picture";
$.i18n(message, 'Alice', 'female' ); // This gives "Alice changed her profile picture"
$.i18n(message, 'Bob', 'male' ); // This gives "Bob changed his profile picture"

Note that {{GENDER:...}} is not case sensitive. It can be {{gender:...}} too.

Grammar

$.i18n( { locale: 'fi' } );

var message = "{{grammar:genitive|$1}}";

$.i18n(message, 'talo' ); // This gives "talon"

$.i18n().locale = 'hy'; // Switch to locale Armenian
$.i18n(message, 'Մաունա'); // This gives "Մաունայի"

Directionality-safe isolation

To avoid BIDI corruption that looks like "(Foo_(Bar", which happens when a string is inserted into a context with the reverse directionality, you can use {{bidi:…}}. Directionality-neutral characters at the edge of the string can get wrongly interpreted by the BIDI algorithm. This would let you embed your substituted string into a new BIDI context, //e.g.//:

"Shalom, {{bidi:$1}}, hi!"

The embedded context's directionality is determined by looking at the argument for $1, and then explicitly inserted into the Unicode text, ensuring correct rendering (because then the bidi algorithm "knows" the argument text is a separate context).

Fallback

The plugin takes an option 'fallback' with the default value 'en'. The library reuses the fallback data available in MediaWiki for calculating the language fallbacks. Fallbacks are used when a message key is not found in a locale. Example fallbacks: sa->hi->en or tt->tt-cyrl->ru.

See jquery.i18n.fallbacks.js in the source.

Magic word support

  • For plural, gender and grammar support, MediaWiki template-like syntax - {{...}} will be used.
  • There will be a default implementation for all these in $.i18n.language['default']
  • The plural, gender and grammar methods in $.i18n.language[ 'default' ] can be overridden or extended in $.i18n.language['languageCode'].
  • Language-specific rules about Gender and Grammar can be written in languages/langXYZ.js files
  • Plural forms will be dynamically calculated using the CLDR plural parser.

Extending the parser

Following example illustrates extending the parser to support more magic words

$.extend( $.i18n.parser.emitter, {
	// Handle SITENAME keywords
	sitename: function () {
		return 'Wikipedia';
	},
	// Handle LINK keywords
	link: function ( nodes ) {
		return '<a href="' + nodes[1] + '">' + nodes[0] + '</a>';
	}
} );

This will parse the message

$.i18n( '{{link:{{SITENAME}}|https://en.wikipedia.org}}' );

to

<a href="https://en.wikipedia.org">Wikipedia</a>

Message documentation

The message keys and messages won't give a enough context about the message being translated to the translator. Whenever a developer adds a new message, it is a usual practice to document the message to a file named qqq.json with same message key.

Example qqq.json:

{
	"@metadata": {
		"authors": [
			"Developer Name"
		]
	},
	"appname-title": "Application name. Transliteration is recommended",
	"appname-sub-title": "Brief explanation of the application",
	"appname-header-introduction": "Text for the introduction header",
	"appname-about": "About this application text",
	"appname-footer": "Footer text"
}

In MediaWiki and its hundreds of extensions, message documentation is a strictly followed practice. There is a grunt task to check whether all messages are documented or not. See https://www.npmjs.org/package/grunt-banana-checker

Comments
  • 'jquery.i18n' is not in the npm registry.

    'jquery.i18n' is not in the npm registry.

    When I try to install with NPM I get the following error:

    Not Found

    'jquery.i18n' is not in the npm registry. You should bug the author to publish it

    This issue exists to "bug the author to publish it"

    opened by davidbarratt 13
  • PLURAL not working for some languages

    PLURAL not working for some languages

    Apparently there are pluralization issues for language codes bs, hr and sr.

    Bosnian for instance:

    Message: "num-languages": "$1 {{PLURAL:$1|jezik|jezika}}" In the JavaScript console:

    $.i18n('num-languages', 115);
    => "115 jezik"
    

    When it should be 115 jezika.

    If you need a go-to for Bosnian, @srdjanm has offered to help. They said the plural rules look correct, so maybe it's something else.

    Thanks!

    opened by MusikAnimal 7
  • Can I use i18n for DOM attrs like title or placeholder?

    Can I use i18n for DOM attrs like title or placeholder?

    Can I use i18n for DOM attrs like title or placeholder without using JS to change it's attribute? for example:

    <div class="content">
     <input type="text" placeholder="translate me" title="translate me">
    </div>
    

    How can I use:

    $('div.content').i18n();
    

    To update the translated messages for placeholder or title?

    opened by hustcer 6
  • Adding support to multiple attribute replacements on the same element

    Adding support to multiple attribute replacements on the same element

    Just adding support to multiple attribute replacements on the same element.

    For instance:

    <div id="divChkEnable" data-on="enabled products" data-off="disabled products" data-i18n="[data-on]data-on-messagekey;[data-off]data-off-messagekey">

    Best,

    opened by InsomniumBR 4
  • build(deps-dev): bump jquery from 3.3.1 to 3.4.0

    build(deps-dev): bump jquery from 3.3.1 to 3.4.0

    Bumps jquery from 3.3.1 to 3.4.0.

    Commits
    • b7fc909 3.4.0
    • 59ea765 Release: update AUTHORS.txt
    • 7c1ef15 Release: update version to 3.4.0-pre
    • d940bc0 Build: Update Sizzle from 2.3.3 to 2.3.4
    • 9b9fca4 Update README.md
    • a2a73db Tests: Make Android Browser 4.0-4.3 dimensions tests green
    • 4455f8d Tests: Make Android Browser 4.0-4.3 AJAX tests green
    • 0050403 Core: Preserve CSP nonce on scripts with src attribute in DOM manipulation
    • fe5f04d Event: Prevent leverageNative from double-firing focusin
    • 753d591 Core: Prevent Object.prototype pollution for $.extend( true, ... )
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    opened by dependabot[bot] 4
  • '$10' not translating (/$(\d+)/g)

    '$10' not translating (/$(\d+)/g)

    They not working togather.

    span id="someId" data-bind="attr: {'data-i18n': variable}, text: variable"

    Text setted, attribute setted, but translation not present. I used this: $(#someId).i18n();

    get next error image

    opened by ivanromakh 4
  • Add capability to set attributes and raw HTML

    Add capability to set attributes and raw HTML

    This patch adds special syntax (borrowed from jquery.i18next) that allows to use unencoded HTML and set localized attributes to tags using data-i18n.

    The usage is as follows:

    • Key [html]key - use unencoded HTML for this key
    • Key [attr]key - set attribute attr instead of text content
    opened by smalyshev 4
  • HTML Tags in Translations

    HTML Tags in Translations

    I've got some translations with html markup (specifically ). Due to varying word order, I would like to somehow keep the ability to add these tags in the translation files. Something like this:

    http://stackoverflow.com/questions/16038458/html-tags-in-i18next-translation

    I have tried both directly inputing the HTML directly into the JSON data and creating my own magic word to no avail. In both cases the raw html shows up. Is it possible to use HTML tags in the translations?

    opened by dhpollack 4
  • What is wrong with my JSON content ?

    What is wrong with my JSON content ?

    I followed documentation about file format. So I've supplied i18n/fr.json as follow :

    {
       "@metadata": {
          "authors": [
             "Mathieu BODIN"
          ],
          "last-updated": "2014-07-23",
          "locale": "fr",
          "message-documentation": "qqq"
       },
       "fr": {
          "something": "qqchose"
       }
    }
    

    I've loaded that file somewhere like that :

    $.i18n().load("i18n/fr.json","fr")
    

    Then I tried to use it, like that :

    var label = $.i18n("something");
    

    It just NEVER happened to work until, after reading the code of the example, I tried the following content for i18n/fr.json file:

    {
       "something": "qqchose"
    } 
    

    So my question is : why didn't it work at first with message source formatted as documented ?

    By the way, what's the point of:

    • Having to supply the path to the file when it could be guessed ? I mean, when people follow your recommendations as documented, having the lang attribute supplied on html tag should be enough to deduce a default path to data.
    • Perform initialization asynchronously ? I want to use this jQuery plugin to perform i18n translation in my whole application, so loading the file is kind of a mandatory feature. I still don't get the use case you're supporting... Show me the light !
    opened by mathieubodin 4
  • specified locale wasn't loading when dir was used in load()

    specified locale wasn't loading when dir was used in load()

    I was trying to load a directory of translation messages, but the specified locale would not load, because the program only loads the fallbacks. Here is an example of the code that I was using:

     i18n.load('/i18n', i18n.locale).done(
          function() {
               $('[data-i18n]').each(function(index) {
                    $(this).i18n();
                    $(this).html($.i18n($(this).attr('data-i18n')));
               } );
          } );
    

    If the locale was set to "fr" and the "fr.json" existed, the program would not load this file and instead simply default back to "en.json".

    opened by dhpollack 3
  • Using $.i18n().load() to load from a URL or object destroys other messages

    Using $.i18n().load() to load from a URL or object destroys other messages

    I'm loading messages from two different sources, and it looks like only the messages from the source that is last to arrive actually get picked up.

    $.i18n().load( 'a.json', 'en' );
    $.i18n().load( 'b.json', 'en' );
    

    Ends up with one of the two messages sets being loaded into the message store, but not the other, and which one makes it is not always consistent (but it's usually b).

    The following confirmed my suspicions:

    >>> $.i18n().load({'foo':'bar'}, 'en');
    Object {resolve: function, resolveWith: function, ...}
    >>> $.i18n().messageStore.messages.en
    Object {foo: "bar"}
    >>> $.i18n().load({'bar':'bar'}, 'en');
    Object {resolve: function, resolveWith: function, ...}
    >>> $.i18n().messageStore.messages.en
    Object {bar: "bar"}
    

    This clearing effect does not happen across languages, only within the same language (so loading messages for 'nl' does not clear messages loaded for 'en', but loading additional messages for 'en' does).

    opened by catrope 3
  • How to load multiple json files in a .html file?

    How to load multiple json files in a .html file?

    So i thought making separate translation files for each .js file that i have cause they are very big. So in my html page my code looks like this:

    Obviously this array import method does not work, so how can i do this?

    Also while im here, is there a more effective way of getting the html tags translate tan the method in the .done block?

    Thanks

    opened by Bojan996 1
  • Merge multiple keys

    Merge multiple keys

    I have a long document with a lot of "A", "Select A" "B", "Select B", ...

    Is it possible to specify something like data-i18n="SELECT+A" instead of creating all these duplicate key for every selection? Thank you

    opened by francescofact 0
  • Number formatting

    Number formatting

    I would find it nice if there was a way to format numbers according to the locale. For instance, the number 1234.56 (as written in Javascript) should be rendered as 1,234.56 in English and 1 234,56 in French.

    So it would be amazing if $.i18n('number-of-results', 1234.56) could render as There are 1,234.56 results in English and Il y a 1 234,56 résultats in French.

    Apologies if this is already supported somehow, I couldn't figure it out looking at the readme.

    The standard function Number.prototype.toLocaleString can of course be used but this has two downsides:

    • this will format the number according to the browser's locale, which might not be the same as the one used by this library
    • this means supplying this number as a string to jquery.i18n, so we probably break plural support by doing that (I haven't actually tried)
    opened by wetneb 2
Releases(v1.0.7)
  • v1.0.7(Jan 2, 2020)

  • v1.0.6(Jan 2, 2020)

  • v1.0.5(Jul 23, 2018)

    Major changes:

    • Removed String.prototype overrides(ab0bc2b)
    • Uses CLDR 31 plural rules(df07bcd) with CLDRPluralRuleParser v1.2.0(4d5bc5a). Plural rule documentation expanded(33b4ba0). Arabic plural rule test fixed(0f8f766)
    • Multiple code clean up using eslint, documentation updates, grunt build updates
    • Code of conduct added(c597fca)
    • Updated dependent libraries, bump devDependencies
    • Allow to use "?" symbols in lang file URLs(9fc37f4)
    • Fix the fallback locale looping error(45350ec)

    Thanks to all contributors

    Source code(tar.gz)
    Source code(zip)
  • v1.0.4(Nov 16, 2015)

Owner
Wikimedia
Wikimedia is a global movement whose mission is to bring free educational content to the world.
Wikimedia
A general purpose internationalization library in 292 bytes

A general purpose internationalization library in 298 bytes! Features Simple and Familiar API Unobstrusive and Unopinionated Less than 300 bytes – inc

Luke Edwards 713 Dec 21, 2022
The alternative internationalization (i18n) library for Angular

NGX Locutus The alternative Angular Translation Library used for large scale microfrontend translations. No more worrying about shared translation ass

Stefan Haas 9 May 31, 2022
Internationalization for react done right. Using the i18next i18n ecosystem.

react-i18next IMPORTANT: Master Branch is the new v10 using hooks. $ v10.0.0 npm i react-i18next react-native: To use hooks within react-native, you m

i18next 7.9k Dec 30, 2022
:globe_with_meridians: Internationalization plugin for Vue.js

vue-i18n Internationalization plugin for Vue.js ?? Gold Sponsors ?? Silver Sponsors ?? Bronze Sponsors ⚠️ NOTICE This repository is for Vue I18n v8.x.

kazuya kawaguchi 6.9k Dec 29, 2022
A JavaScript Internationalization Framework

FBT is an internationalization framework for JavaScript designed to be not just powerful and flexible, but also simple and intuitive. It helps with th

Facebook 3.8k Jan 8, 2023
🌍📖 A readable, automated, and optimized (5 kb) internationalization for JavaScript

Linguijs ?? ?? A readable, automated, and optimized (5 kb) internationalization for JavaScript Documentation · Documentation 2.x · Quickstart · Exampl

Lingui 3.5k Jan 2, 2023
Type-safe internationalization (i18n) for Next.js

Type-safe internationalization (i18n) for Next.js Features Usage Examples Scoped translations Change current locale Use JSON files instead of TS for l

Tom Lienard 251 Dec 22, 2022
a jQuery plugin that makes it easy to internationalize your web site.

jquery.localize.js A jQuery plugin that makes it easy to i18n your static web site. Synopsis Lazily loads JSON translation files based on a simple nam

Jim Garvin 469 Dec 17, 2022
A simple library used to handle our multi-language needs.

Vespucci Multiplayer - i18n Integration A simple library used to handle our multi-language needs. ⚠️ Important! This is a very simple implementation o

Vespucci - România 2 Feb 7, 2022
lightweight jQuery plugin for providing internationalization to javascript from ‘.properties’ files

jQuery.i18n.properties About jQuery.i18n.properties is a lightweight jQuery plugin for providing internationalization to javascript from ‘.properties’

null 408 Dec 25, 2022
Internationalisation - A jQuery-Plugin to replace alternate version of text for client side internationalization.

Project status Use case A jQuery plugin to replace alternate version of text for client side internationalisation. Content [TOC] Installation Classica

Torben Sickert 10 Nov 30, 2022
Internationalization for svelte framework. Based on i18next ecosystem

svelte-i18next Svelte wrapper for i18next npm i svelte-i18next i18next Implementation This library wraps an i18next instance in a Svelte Store to obs

Nishu Goel 20 Dec 9, 2022
A general purpose internationalization library in 292 bytes

A general purpose internationalization library in 298 bytes! Features Simple and Familiar API Unobstrusive and Unopinionated Less than 300 bytes – inc

Luke Edwards 713 Dec 21, 2022
The alternative internationalization (i18n) library for Angular

NGX Locutus The alternative Angular Translation Library used for large scale microfrontend translations. No more worrying about shared translation ass

Stefan Haas 9 May 31, 2022
A fully type-safe and lightweight internationalization library for all your TypeScript and JavaScript projects.

?? typesafe-i18n A fully type-safe and lightweight internationalization library for all your TypeScript and JavaScript projects. Advantages ?? lightwe

Hofer Ivan 1.3k Jan 4, 2023
Internationalization for react done right. Using the i18next i18n ecosystem.

react-i18next IMPORTANT: Master Branch is the new v10 using hooks. $ v10.0.0 npm i react-i18next react-native: To use hooks within react-native, you m

i18next 7.9k Jan 9, 2023
:globe_with_meridians: Internationalization plugin for Vue.js

vue-i18n Internationalization plugin for Vue.js ?? Gold Sponsors ?? Silver Sponsors ?? Bronze Sponsors ⚠️ NOTICE This repository is for Vue I18n v8.x.

kazuya kawaguchi 6.9k Jan 8, 2023
Internationalization for react done right. Using the i18next i18n ecosystem.

react-i18next IMPORTANT: Master Branch is the new v10 using hooks. $ v10.0.0 npm i react-i18next react-native: To use hooks within react-native, you m

i18next 7.9k Dec 30, 2022
:globe_with_meridians: Internationalization plugin for Vue.js

vue-i18n Internationalization plugin for Vue.js ?? Gold Sponsors ?? Silver Sponsors ?? Bronze Sponsors ⚠️ NOTICE This repository is for Vue I18n v8.x.

kazuya kawaguchi 6.9k Dec 29, 2022
A JavaScript Internationalization Framework

FBT is an internationalization framework for JavaScript designed to be not just powerful and flexible, but also simple and intuitive. It helps with th

Facebook 3.8k Jan 8, 2023