strong-globalize
Advanced tools
The strong-globalize npm package is designed to help developers internationalize and localize their Node.js applications. It provides tools for message translation, date and time formatting, and number formatting, making it easier to support multiple languages and regions.
Message Translation
This feature allows you to translate messages into different languages. By setting the locale, you can ensure that messages are displayed in the appropriate language for the user.
const g = require('strong-globalize')();
g.setLocale('es');
console.log(g.f('Hello, World!'));
// Output: ¡Hola, Mundo!Date and Time Formatting
This feature helps in formatting dates and times according to the specified locale. It ensures that date and time representations are culturally appropriate.
const g = require('strong-globalize')();
g.setLocale('fr');
const date = new Date();
console.log(g.d(date));
// Output: formatted date in French localeNumber Formatting
This feature allows you to format numbers according to the specified locale. It ensures that numbers are displayed in a way that is familiar to users from different regions.
const g = require('strong-globalize')();
g.setLocale('de');
const number = 1234567.89;
console.log(g.n(number));
// Output: formatted number in German localei18next is a popular internationalization framework for JavaScript. It provides similar functionalities to strong-globalize, such as message translation and formatting. However, i18next is more flexible and can be used with both client-side and server-side applications.
Globalize is a comprehensive internationalization library that provides tools for message translation, date and time formatting, and number formatting. It is similar to strong-globalize but offers more extensive support for various locales and is built on top of the Unicode CLDR data.
react-intl is a library specifically designed for internationalizing React applications. It provides components and APIs for formatting dates, numbers, and messages. While it offers similar functionalities to strong-globalize, it is tailored for use with React.
StrongLoop Globalize CLI and API
strong-globalize is built on top of two foundation layers: Unicode CLDR and jquery/globalize. The Unicode CLDR provides key building blocks for software to support the world's languages, with the largest and most extensive standard repository of locale data available. jquery/globalize is a JavaScript library for internationalization and localization that leverages the Unicode CLDR JSON data. The library works both for the browser and as a Node.js module.
strong-globalize is a JavaScript library for internationalization and localization (globalization in one word) of a Node.js package. strong-globalize provides these features:
As shown in the Demo section, the code written with strong-globalize is simpler, better structured, and easier to read than the original code written as an English-only product; and more importantly, you get all the features at no extra effort.
With strong-globalize, there will be no more 'English product first and worry about localization later'; there will be only one globalized codebase from day one. If you choose, you can still ship it with a few language resources (or English only) initially and incrementally add, remove, or update the resources and ship anytime as you go.
You can customize (add/remove) any languages supported by the Unicode CLDR in your strong-globalize installation.
The line test coverage with and without core part of translation tests are currently 90% and 80% respectively.
With the out-of-box setting, npm test runs all tests but the core translation tests because it requires connection to the machine translation service. To enable the machine translation, please set the environment variables described in this section.
With custom setting such as customized language configuration, some tests may fail. You can edit target messages in the failing test modules to suit your custom setting. To do so, set DEBUG global variable of test/slt-test-helper.js and run the test, identify the actual error messages, then copy and paste the actual error messages to the failing test modules.
All packages are created equal. Autonomous Message Loading is the core concept of strong-globalize designed for globalization of modular and highly distributed Nodejs applications. Two key terminologies are root directory and master root directory:
root directory or simply rootDir: the package's current working directory where intl directory resides.
master root directory: the root directory of the package that called SG.SetRootDir first. Any package in the application can be the master root directory. It's determined solely by the loading order and once the master is chosen, it does not change in the application's life. Usually, the master root directory is the root directory of the package at the root of the application's dependency tree. slt-globalize -d must run under the master root directory so that all the string resources in the application are extracted and stored under the master root directory's intl/en.
Once all the string resource files are deep-extracted and translated at the top level package, the original string resources in the dependencies should not be loaded. To disable loading the string resources in the dependencies, set autonomousMsgLoading to none in the SetRootDir call of the top level package. Since 'none' is the default, simply SG.SetRootDir(rootDir) does it.
In development phase, with regular extraction mode, {autonomousMsgLoading: 'all'} must be set so that string resource included in each dependent package will be used.
Third option is to set specific package names of which the string resources get loaded. One use case of the third option is that you have several dependent packages which you know are properly translated and the translation can be used as-is. For all the other packages, message strings will be deep-extracted and translated.
var SG = require('strong-globalize');
SG.SetRootDir(__dirname, {autonomousMsgLoading: 'none'}); // same as SG.SetRootDir(__dirname);
var g = SG({language: 'en'}); // same as SG();
// use formatters and wrappers API
g.log('Welcome!');
For example, the following does not work as intended because the package sub calls SG.SetRootDir first:
// main/index.js -- my root package
var SG = require('strong-globalize');
var request = require('request');
var sub = require('sub');
SG.SetRootDir(__dirname);
var g = SG();
...
// sub/index.js -- my sub package
var SG = require('strong-globalize');
var request = require('request');
SG.SetRootDir(__dirname);
var g = SG();
...
The 'MUST' coding practice is to call SG.SetRootDir in the very first line of the main module in each package:
// main/index.js -- my root package
var SG = require('strong-globalize');
SG.SetRootDir(__dirname);
var request = require('request');
var sub = require('sub');
var g = SG();
...
// sub/index.js -- my sub package
var SG = require('strong-globalize');
SG.SetRootDir(__dirname);
var request = require('request');
var g = SG();
...
More concise coding is as follows:
// main/index.js -- my root package
var g = require('strong-globalize')(__dirname);
var request = require('request');
var sub = require('sub');
...
// sub/index.js -- my sub package
var g = require('strong-globalize')();
var request = require('request');
...
Out of box, one CLDR file is included in strong-globalize/cldr directory. CLDR stands for Common Locale Data Repository. In the installation of strong-globalize for your production deployment, you can replace the out-of-box CLDR file entirely, or add extra CLDR data to the cldr directory. There are approximately 450 locales (language/culture variations) defined in the Unicode CLDR. Among them, there are 40+ variations of French and 100+ variations of English.
strong-globalize provides a utility tool under util directory. The tool assembles only the languages you need to support in your strong-globalize installation. For example, the out-of-box gz file for the 11 languages is 135KB. See README of the utility under util directory.
In runtime, strong-globalize dynamically loads to memory just the CLDR data required for the specific language by setLanguage(). First, it examines all the gz files under cldr directory in alphabetical order, then searches for the language. If the language is defined in two or more CLDR files, duplicate objects will be overwritten in the examination order.
English string resource files must exist under intl/en directory. Translated string resource files are stored on each language sub-directory under intl If a message is not found in the translated resource files, the corresponding English message is displayed.
CLDR data has no dependencies on string resources. For example, you can load 100 language CLDR data and no translated string resources but the English string resource. However, if there is a translated non-English string resource exists for language xx under intl/xx the CLDR data for xx must be loaded. xx is one of the languages defined in the CLDR file(s).
There are two primary types of Node.js packages strong-globalize is targeting:
slt-globalize itself,Accept-Language header. See `negotiator' on npmjs.com).var SG = require('strong-globalize');
SG.SetRootDir(__dirname);
var g = SG(); // use the default
// the common part comes here.
// then, use formatters and wrappers API always in the same language
g.log('Welcome!');
Setting language to strong-globalize instance is pretty cheap. CLDR data set and translated messages are preloaded at the initial use.
// the common part comes here.
// set language first, then, use formatters and wrappers API
// See 'negotiator' on Npmjs.com for 'getAcceptLanguage()'
g.setLanguage(getAcceptLanguage()); // once per session
g.log('Welcome!');
strong-globalize has a feature similar to traditional pseudo localization.
First, Machine Translation with slt-globalize -t can be used like the traditional pseudo localization. See the CLI - extract, lint, and translate section for details of slt-globalize -t command.
Second, in runtime, set the environment variable STRONG_GLOBALIZE_PSEUDO_LOC_PREAMBLE and strong-globalize adds the string in front of every message processed by the message formatter. If you already have translated message files (by machine or human) and set the language, the string is added to every message in that language.
Third, strong-globalize reserves the language code zz as pseudo-language. slt-globalize -e generates intl/zz/messages.json and intl/zz/messages_inverted.json which show the location of each message extracted from JS files.
Note that strong-globalize does not use intl/zz/*.json in runtime. They are reference only. They are useful to detect globalization bugs usually called hard-coded strings. For example, intl/en/messages.json shows "Shipping cost is {0}." string is properly globalized and extracted to intl/en/messages.json with the auto-generated message key as "77decb50aa6360f0dc9c8ded9086b94e". intl/zz/messages.json shows the string is located at line#31 of index.js as the argument of function call g.log. intl/zz/messages_inverted.json shows that at the line#20 of index.js there is a string "%s Hello %s" as the first argument of util.format which looks like a globalization bug.
Also note that slt-globalize -e extracts the first argument of every function call if it's a literal string or concatenation of literal strings. Literal strings in other arguments of function calls are NOT extracted.
intl/en/messages.json:
{
"77decb50aa6360f0dc9c8ded9086b94e": "Shipping cost is {0}.",
"b5d4af08bf61e58d375923977290d67b": "Listening on {0} by {1}."
}
intl/zz/messages.json:
{
"77decb50aa6360f0dc9c8ded9086b94e": [
"g.log:index.js:31"
],
"b5d4af08bf61e58d375923977290d67b": [
"g.log:index.js:29"
],
"%s Hello %s": [
"util.format:index.js:20"
],
"http://localhost:": [
"request:index.js:35"
]
}
and, intl/zz/messages_inverted.json:
{
"index.js": {
"20": [
"util.format('%s Hello %s', ... )"
],
"29": [
"g.log('b5d4af08bf61e58d375923977290d67b')"
],
"31": [
"g.log('77decb50aa6360f0dc9c8ded9086b94e')"
],
"35": [
"request('http://localhost:')"
]
}
}
strong-globalize CLI supports string resource auto-extraction in two modes: regular extraction mode and deep extraction mode. The regular extraction mode is invoked with slt-globalize -e and typically used in package development phase. The deep extraction mode slt-globalzie -d is designed to be used in globalization of enterprise-scale applications.
Suppose you have a package named gmain which has two JS files: index.js and lib/util.js and the two JS files contain the same g.log('user: %s', userName) call in line# 8 and line# 12 respectively. Running slt-globalize -e under the application root directory, /Users/user/gmain will generate intl/en/messages.json and intl/zz/messages.json as shown in the Pseudo Localization Support section. Note that slt-globalize -e extracts all strong-globalized literal strings as well as non-globalized literal string with positional information in to intl/zz/messages.json. It is useful to pin-point untranslated strings in the source code.
In the regular extraction mode, strong-globalize scans all JS and Html templates owned by the gmain package no matter how deep the directory structure goes -- for example, gmain/lib/usa/california/sanfrancisco/util.js is scanned. However, it does not examine dependent files under node_modules or test directory. All strong-globalized literal strings in JS and Html files of the target package will be extracted and stored in intl/en/messages.json along with the positional information stored in intl/zz/messages.json. All non-strong-globalized literal strings in the first argument of all JS function calls are extracted and stored in intl/zz/messages.json along with the positional information.
In runtime, the string resource JSON files under intl will be loaded on to memory as needed.
Use Case: Self-contained CLI utility package is typically code-globalized and distributed with or without translated messages.json. API library packages are typically code-globalized and distributed without translation. Such library packages are then downloaded and used as part of enterprise-scale applications.
/Users/user
└── gmain
├── index.js
├── intl
│ ├── de
│ ├── en
│ ├── es
│ ├── fr
│ ├── it
│ ├── ja
│ ├── ko
│ ├── pt
│ ├── ru
│ ├── zh-Hans
│ ├── zh-Hant
│ └── zz
├── lib
│ └── usa
│ └── california
│ └── sanfrancisco
│ └── util.js
├── node_modules
│ ├── express
│ ├── request
│ └── strong-globalize -> /usr/local/lib/node_modules/strong-globalize
└── package.json
Enterprise-scale applications may depend on dozens of third party packages directly or indirectly. Such applications typically download dependent packages using npm install and can globalize them using the Deep Extraction mode.
For example, suppose gmain package has one dependent package gsub which is installed under gmain/node_modules as shown in the directory structure diagram below. slt-globalize -d traverses the npm v3 style dependency tree and extracts all the strong-globalized string literals into gmain/intl/en/messages.json. This way, all the literal strings in your package gmain as well as all the dependent modules are extracted and can be translated consistently at gmain/intl level. Note that the package.json dependency traversal is different from simple directory traversal.
Note that string resource extraction from Html templates is supported in the regular extraction mode only.
STRONGLOOP_GLOBALIZE_MAX_DEPTH environment variableAs the size of your application grows, the number of dependent packages can grow exponentially. Since non-globalized literal strings are also recorded on gmain/intl/zz/messages.json, gmain/intl/zz/messages.json may also grow exponentially and cause slt-globalize -d to run out of resource on your computer.
To manage such situations, you can set STRONGLOOP_GLOBALIZE_MAX_DEPTH environment variable. slt-globalize -d stops traversing at the specified directory depth. Note that it works as directory depth although the traversal is controlled by dependencies defined in package.json.
For example, invoking STRONGLOOP_GLOBALIZE_MAX_DEPTH=3 slt-globalize -d under /Users/user/gmain works as follows. gmain/index.js is depth 1; thus examined. gmain/lib/usa/california/sanfrancisco/util.js is depth 5, not examined although it's part of your gmain package. gmain/node_modules/gsub/index.js is level 3, thus examined. Likewise, all the files directly under gmain/node_modules/express and gmain/node_modules/request will also be examined and literal strings are extracted to gmain/intl/zz/messages.json.
npm v3 dependency resolutionnpm v3 tries to install all dependent packages in the root node_modules directory, i.e., gmain/node_modules in the above example, which means that most dependent package directories are at depth level 2. Therefore, STRONGLOOP_GLOBALIZE_MAX_DEPTH does not help in npm v3 installed applications. slt-globalize -d [black list] option can help to reduce the number of packages to scan.
/Users/user
└── gmain
├── index.js
├── intl
│ ├── de
│ ├── en
│ ├── es
│ ├── fr
│ ├── it
│ ├── ja
│ ├── ko
│ ├── pt
│ ├── ru
│ ├── zh-Hans
│ ├── zh-Hant
│ └── zz
├── lib
│ └── usa
│ └── california
│ └── sanfrancisco
│ └── util.js
├── node_modules
│ ├── express
│ ├── gsub
│ │ ├── index.js
│ │ ├── node_modules
│ │ │ └── strong-globalize -> /usr/local/lib/node_modules/strong-globalize
│ │ └── package.json
│ ├── request
│ └── strong-globalize -> /usr/local/lib/node_modules/strong-globalize
└── package.json
Many UI strings are included in HTML templates. slt-globalize -e supports string extraction from the HTML templates as well as JS files. Once extracted, slt-globalize -t can be used to translate the resource JSON.
In the following example, the two strings {{StrongLoop}} History Board and History board shows the access history to the e-commerce web site. are extracted to JSON.
<div class="board-header section-header">
<h2>{{{{StrongLoop}} History Board | globalize}}</h2>
</div>
<div role="help-note">
<p>
{{ History board shows the access history to the e-commerce web site. | globalize }}
</p>
</div>
strong-globalize supports {{ <string to be localized> | globalize }} out of box. In case you need other pattern matching rule for your template engine, you can set custom RegExp by setHtmlRegex API.
The string extraction works for CDATA as well. Text in cdata is extracted in the following example:
<![CDATA[
{{Text in cdata | globalize }}
]]>
You can directly pass the file name of JSON or YAML file and a list of fields to g.t or g.formatMessage. The file name is a path relative to the root directory of the package. The list of the fields is a string notation of two dimensional array being a list of the values to globalize. In the sample code below, data.json is the JSON file and index.js shows how to globalize all fields of data.json. g.t loads the globalized object into memory which is usually done by require(<file name>) or fs.readFile followed by JSON.parse. Note that the file name and the list must be provided as string literals directly in g.t call. YAML file globalization works in exactly the same way.
Note that strong-globalize supports traditional message key approach as well. To take the message key approach in JSON file globalization, manually define a message key like msgKey, store the key and content value pair in intl/en/messages.json, then in run-time, load the JSON file as usual (require or readFile & parse) first and overwrite the value with g.t('msgKey').
Plain text file globalization works in the same way except that 1. the text file name is a path relative to intl/en of the package, and 2. since the entire text file is a message, there are no parameters equivalent to the field list.
In the above paragraphs, g.f can be used instead of g.t if you'd like.
test/fixtures/extract007' is the YAML equivalent. Likewise, test/fixtures/formatyaml001is the parallel oftest/fixtures/formatjson001`.
// test/fixtures/extract006/index.js
var SG = require('strong-globalize');
SG.SetRootDir(__dirname);
var g = SG();
var json = g.t('data/data.json',
'[' +
' "title",' +
' ["types", 0],' +
' ["types", 1],' +
' ["types", 2],' +
' ["types", 3],' +
' ["threeWrites", "e"],' +
' ["threeWrites", "o"],' +
' ["threeWrites", "w"]' +
']');
console.log(JSON.stringify(json, null, 2));
test/fixtures/extract006/data/data.json
{
"title": "This is an error.",
"types": ["error", "log", "info", "warn"],
"threeWrites" : {
"e": "ewrite",
"o": "owrite",
"w": "write"
}
}
test/fixtures/extract006
├── data
│ └── data.json
├── index.js
├── intl
│ ├── de
│ │ └── messages.json
│ ├── en
│ │ └── messages.json
│ ├── es
│ │ └── messages.json
│ ├── fr
│ │ └── messages.json
│ ├── it
│ │ └── messages.json
│ ├── ja
│ │ └── messages.json
│ ├── ko
│ │ └── messages.json
│ ├── pt
│ │ └── messages.json
│ ├── ru
│ ├── zh-Hans
│ │ └── messages.json
│ ├── zh-Hant
│ │ └── messages.json
│ └── zz
│ ├── messages.json
│ └── messages_inverted.json
├── node_modules
│ └── strong-globalize
│ ├── ...
│ ...
│
└── package.json
strong-globalize provides 'persistent logging' by passing all the localized messages as well as the original English messages to client-supplied callback function.
SG.SetPersistentLogging(logCallback, disableConsole)logCallback is called when a user message is sent to stdout or stderr to show to the user. Two arguments passed to logCallback are: level (string) and msg (object) which has three properties: message (UTF8 string) which is the localized message shown to the user, orig (UTF8 string) the corresponding original English message with placeholder(s), and vars (an array of argument(s) for the placeholder(s)).
{
language: 'ja',
message: 'ホスト:localhostのポート:8123へ送っています。',
orig: 'Sending to host: %s, port: %d ...',
vars: ['localhost', 8123],
}
disableConsole (default: false) is a boolean to specify whether to send the messsage to stdout or stderr. disableConsole should be set to true in case the client controls the user communication. For example, if the client uses winston file transport for logging, the client code would look like this:
Client:
var SG = require('strong-globalize');
SG.SetRootDir(__dirname);
SG.SetDefaultLanguage();
var g = SG(); // strong-globalize handle
var w = require('winston'); // winston handle
initWinston(w);
// let strong-globalize to show it to the user
var disableConsole = false;
SG.SetPersistentLogging(w.log, disableConsole);
function initWinston(w) {
var options = {
filename: __dirname + '/system.log',
maxsize: 1000000,
maxFiles: 10,
zippedArchive: true,
};
w.add(w.transports.File, options);
// let strong-globalize to show it to the user
w.remove(w.transports.Console);
}
gmain/index.jsvar express = require('express');
var request = require('request');
var app = express();
var SG = require('strong-globalize');
SG.SetRootDir(__dirname);
var gsub = require('gsub');
var w = require('winston'); // winston handle
var g = SG(); // strong-globalize handle
initWinston(w); // see the Client initialization
var disableConsole = false;
SG.SetPersistentLogging(w.log, disableConsole);
app.get('/', function(req, res) {
var helloMessage = g.f('%s Hello World', g.d(new Date()));
w.info(helloMessage); // write only to the log file with 'info' level
res.end(helloMessage);
});
var port = process.env.PORT || 8123;
app.listen(port, function() {
g.log('Listening on %s by %s.', port, gsub.getUserName());
});
setInterval(function(){
g.owrite('Sending request to %s ...', port);
request('http://localhost:' + port,
function(error, response, body) {console.log(body);});
},1000);
g.info(gsub.getHelpText()); // write to both console and the log file with 'info' level
Note:
w.info(helloMessage) directly calls the winston API info and write helpMessage to the log file.
g.info(gsub.getHelpText()) writes the localized help text to both console and the log file with info level. The other strong-globalize API calls, i.e., g.log and g.owrite also write the localized message to both console and the log file with info level.
[1] https://github.com/Setogit/sg-example-001-date-currency
A complete strong-globalized application with machine-translated messages. In addition to message formatting, date and currency formatting examples are included. You can install and quickly see how the strong-globalized (or SG'ed in short) app works. Just install and node index.js
[2] https://github.com/Setogit/sg-example-002-glob-pipeline
Detailed 15-step instruction with 15 screen-shots to set up IBM Globalization Pipeline on Bluemix
npm install -g strong-globalizeYou can safely ignore these warnings because strong-globalize statically bundles cldr-data for production use.
npm WARN EPEERINVALID globalize@1.1.1 requires a peer of cldr-data@>=25 but none was installed.
npm WARN EPEERINVALID cldrjs@0.4.4 requires a peer of cldr-data@>=25 but none was installed.
slt-globalize [options]Options:
-d,--deepextract [black list] Deep-extract resource strings.-e,--extract [black list] Extract resource strings to en/messages.json except for directories on [black list] separated by a space.-h,--help Print this message and exit.-l,--lint Check validity of string resource.-t,--translate Translate string resource.-v,--version Print version and exit.To access Globalization Pipeline on Bluemix service for machine translation, credentials should be provided in one of the two ways:
(1) By strong-globalize/lib/local-credentials.json
Copy and paste your credentials look like the following from the dashboard of Globalization Pipeline on Bluemix service into strong-globalize/lib/local-credentials.json.
{
"credentials": {
"url": "https://gp-beta-rest.ng.bluemix.net/translate/rest",
"userId": "6e41ceac9f14b493faxxxxxxxxxxxxxx",
"password": "vLbqlkjPhJiwJlkjwou8woO82hk2huku",
"instanceId": "6888888888888e6d2f458b1b4b5fd010"
}
}
(2) By environment variables
For example,
BLUEMIX_URL="https://gp-beta-rest.ng.bluemix.net/translate/rest"
BLUEMIX_USER=6e41ceac9f14b493faxxxxxxxxxxxxxx
BLUEMIX_PASSWORD=vLbqlkjPhJiwJlkjwou8woO82hk2huku
BLUEMIX_INSTANCE=6888888888888e6d2f458b1b4b5fd010
slt-globalize -t
Please see Other Resources for step-by-step instructions to set up the service.
var SG = require('strong-globalize);SG.SetRootDir(rootPath, options)rootPath : {string} App's root directory full path. Every client must set its root directory where package.json and intl directory exist. All resources under this directory including dependent modules are loaded in runtime. SetRootDir must be called once and only once usually in the main js module.options : {autonomousMsgLoading: ['none' | 'all' | <an array of strings]} (optional)
'none' (default) -- load string resources at the master rootDir, but not load from dependency packages
'all' -- load string resources from all packages
<an array of package name strings> -- load string resources at the master rootDir and the specified packages if the master package depends on them.SG.SetDefaultLanguage(lang)lang : {string} (optional) Language ID such as de, en, es, fr, it, ja, ko, pt, ru, zh-Hans, and zh-Hant. If omitted, strong-globalize tries to use the OS language, then falls back to 'en' It must be called at least once. By default, it's called in SetRootDir, so it can be omitted completely. Can be called multiple times.strong-globalize uses the language code in a form of a combination of ISO 639-1 language code and ISO 15924 script code such as zh-Hans for Chinese - Han (Simplified variant).
SG.SetHtmlRegex(regex, regexHead, regexTail)regex : {RegExp} to extract the whole string out of the HTML textregexHead : {RegExp} to trim the head portion from the extracted stringregexTail : {RegExp} to trim the tail portion from the extracted stringMost clients do not need to setHtmlRegex. See the Globalize HTML Templates section for details.
g.setLanguage(lang)lang : {string} (optional) Language ID such as de, en, es, fr, it, ja, ko, pt, ru, zh-Hans, and zh-Hant. If omitted, strong-globalize tries to use the OS language, then falls back to 'en' It must be called at least once. Can be called multiple times.g.getLanguage()string} Language ID such as de, en, es, fr, it, ja, ko, pt, ru, zh-Hans, and zh-Hant.var g = SG({language: 'en'});g.formatMessage(path, variables)path {string} The message keyvariables {object} (optional, default: null) List of placeholder key and content value pairg.t(path, variables)alias of formatMessage
g.m(path, variables)alias of formatMessage
g.formatCurrency(value, currencySymbol, options)value {number} integer or floatcurrencySymbol {string} ISO 4217 three-letter currency code such as 'USD' for US Dollarsoptions {object} (optional) jquery/globalize option format. If omitted, StrongLoop default is used.g.c(value, currencySymbol, options)alias of formatCurrency
g.formatDate(value, options)value {Date object} Dateoptions {object} (optional) jquery/globalize option format. If omitted, StrongLoop default is used.g.d(value, options)alias of formatDate
g.formatNumber(value, options)value {number} integer or floatoptions {object} (optional) jquery/globalize option format. If omitted, StrongLoop default is used.g.n(value, options)alias of formatNumber
%s place holders are supported. Intended to directly globalize strings embedded in the first parameter of Error, console.error, console.log, etc. and util.format by simply replacing console or util with require('strong-globalize'). 'path' is the literal string. 'path' cannot be a variable. If a variable is used as path the off-line extraction won't be able to extract because string data assigned to a variable is known only in runtime.
g.Error(path, ...)(capital Error)returns Error with a formatted message.
g.format(path, ...)returns the result message from formatMessage. intended to replace util.format.
g.f(path, ...)alias of format
g.ewrite(path, ...)passes the result message from formatMessage to process.stderr.write, and log to file with error level if persistent logging is set.
g.owrite(path, ...)passes the result message from formatMessage to process.stdout.write, and log to file with info level if persistent logging is set.
g.write(path, ...)alias of owrite
g.emergency(path, ...)passes the result message from formatMessage to console.error, and log to file with emergency level if persistent logging is set.
g.alert(path, ...)passes the result message from formatMessage to console.error, and log to file with alert level if persistent logging is set.
g.critical(path, ...)passes the result message from formatMessage to console.error, and log to file with critical level if persistent logging is set.
g.error(path, ...)(small error)passes the result message from formatMessage to console.error, and log to file with error level if persistent logging is set.
g.warning(path, ...)passes the result message from formatMessage to console.error, and log to file with warning level if persistent logging is set.
g.notice(path, ...)passes the result message from formatMessage to console.log, and log to file with notice level if persistent logging is set.
g.informational(path, ...)passes the result message from formatMessage to console.log, and log to file with informational level if persistent logging is set.
g.debug(path, ...)passes the result message from formatMessage to console.log, and log to file with debug level if persistent logging is set.
g.warn(path, ...)passes the result message from formatMessage to console.error, and log to file with warn level if persistent logging is set.
g.info(path, ...)passes the result message from formatMessage to console.log, and log to file with info level if persistent logging is set.
g.log(path, ...)passes the result message from formatMessage to console.log, and log to file with log level if persistent logging is set.
g.help(path, ...)passes the result message from formatMessage to console.log, and log to file with help level if persistent logging is set.
g.data(path, ...)passes the result message from formatMessage to console.log, and log to file with data level if persistent logging is set.
g.prompt(path, ...)passes the result message from formatMessage to console.log, and log to file with prompt level if persistent logging is set.
g.verbose(path, ...)passes the result message from formatMessage to console.log, and log to file with verbose level if persistent logging is set.
g.input(path, ...)passes the result message from formatMessage to console.log, and log to file with input level if persistent logging is set.
g.silly(path, ...)passes the result message from formatMessage to console.log, and log to file with silly level if persistent logging is set.
Rule of thumb for auto-extraction with slt-globalize -e:
path) of the APIs is extracted.before:
Error(util.format('Directory %s does not exist', workingDir));
after:
Error(g.f('Directory %s does not exist', workingDir));
or
g.Error('Directory %s does not exist', workingDir);
before globalization:
// don't concatenate string. word order varies from language to language.
process.stdout.write('Directory ' + workingDir + ' does not exist...');
wrong globalization: (don't concatenate words; word order varies from language to language)
process.stdout.write(g.t('Directory ') + workingDir + g.t(' does not exist...'));
right globalization:
g.write('Directory %s does not exist...', workingDir);
You can use place holders and parameters in one of these four ways if you'd like:
before globalization:
util.format('Deploy %s to %s failed: %s', what, url, err);
right globalization (4 ways)
// 1 (recommended; simply replace `util` with `g`)
g.f('Deploy %s to %s failed: %s', what, url, err);
// 2
g.f('Deploy {0} to {1} failed: {2}', [what, url, err]);
// 3
g.f('Deploy {0} to {1} failed: {2}', {0: what, 1: url, 2: err});
// 4
g.f('Deploy {what} to {url} failed: {err}', {what: what, url: url, err: err});
When you put placeholders in help txt and msg messages, named or ordered placeholders should be used. Named placeholder is something like {userName}. Ordered placeholder is {0}, {1}, {2}, etc. which should be zero-base.
Curly brace characters are reserved by strong-globalize. In case curly brace characters are used in literal strings, escape them. For example, {User} is a placeholder and '\x7bUser\x7d' is an escaped literal string rendered as '{User}'
Use double curly braces {{ }} as "don't translate" indicator.
before globalization:
console.error('Invalid usage (near option \'%s\'), try `%s --help`.', option, cmd);
right globalization:
g.error('Invalid usage (near option \'%s\'), try {{`%s --help`}}.', option, cmd);
before globalization:
var help = fs.readFileSync(require.resolve('./help.txt'), 'utf-8');
right globalization:
var help = g.t('help.txt'); // or g.f('help.txt');
and store help.txt file under intl/en.
They must be uniquely named because they are used as-is in runtime message database where the messages come from other modules will be merged. In case there are duplicate .txt or msg, it could be overwritten by other module(s) with the same name whichever is loaded later. Best practice is to use your package name as part of the name. For example, msgMyPackage_ErrorMessage.
The rule of thumb is strong-globalize extracts messages from JS and HTML template files and creates the messages.json file (or appends extracted messages to the messages.json if it exists), but does not edit the help txt files, msg messages, or JS/HTML files provided by the client.
Note that strong-globalize supports multiple txt and multiple json files under intl/--/ directory.
slt-globalize -e command extracts message strings from your source JS files and HTML templates. In case translation is needed for strings which are not in the source files, you can manually add them to the resource JSON files. To manually add message strings to the resource file, use a key that begins with msg such as msgPortNumber. Those keys are kept intact in auto-extraction and the value text will be properly translated.
To quickly switch the locale, change the OS's system locale or set STRONGLOOP_GLOBALIZE_APP_LANGUAGE environment variable to one of the supported languages such as ja for Japanese or de for German.
For example, on OSX:
cd gmain
LANG=ja node index.js
gsub/index.jsbefore:
var fs = require('fs');
var util = require('util');
exports.getHelpText = getHelpText;
exports.getUserName = getUserName;
function getUserName() {
var userName = util.format('user: %s', process.env.USER);
return userName;
}
function getHelpText() {
var helpText = fs.readFileSync(require.resolve('./gsub.txt'), 'utf-8');
return helpText;
}
after:
var g = require('strong-globalize')();util with greadFile *.txt with simply g.t and move ./gsub.txt to ./intl/en/gsub.txtslt-globalize -e to extract and slt-globalize -t to machine translate the string resource.var g = require('strong-globalize')();
exports.getHelpText = getHelpText;
exports.getUserName = getUserName;
function getUserName() {
var userName = g.f('user: %s', process.env.USER);
return userName;
}
function getHelpText() {
return g.t('gsub.txt');
}
gmain/index.jsbefore:
var express = require('express');
var request = require('request');
var app = express();
var util = require('util');
var gsub = require('gsub');
app.get('/', function(req, res) {
var helloMessage = util.format('%s Hello World', new Date());
res.end(helloMessage);
});
var port = process.env.PORT || 8123;
app.listen(port, function() {
console.log('Listening on %s by %s.', port, gsub.getUserName());
});
setInterval(function(){
process.stdout.write('Sending request to ' + port + '...');
request('http://localhost:' + port,
function(error, response, body) {console.log(body);});
},1000);
console.log(gsub.getHelpText());
after:
var SG = require('strong-globalize');SG.SetRootDir( ... );var g = SG();util with gconsole with gprocess.stdout with gnew Date() with g.d()slt-globalize -e to extract and slt-globalize -t to machine translate the string resource.var SG = require('strong-globalize');
SG.SetRootDir(__dirname);
var express = require('express');
var request = require('request');
var app = express();
var gsub = require('gsub');
var g = SG();
app.get('/', function(req, res) {
var helloMessage = g.f('%s Hello World', g.d(new Date()));
res.end(helloMessage);
});
var port = process.env.PORT || 8123;
app.listen(port, function() {
g.log('Listening on %s by %s.', port, gsub.getUserName());
});
setInterval(function(){
g.owrite('Sending request to %s ...', port);
request('http://localhost:' + port,
function(error, response, body) {console.log(body);});
},1000);
console.log(gsub.getHelpText());
Sample code is included under examples directory. Let's browse the code and quickly study the standard coding pattern of strong-globalize.
examples
├── gmain
│ ├── index.js
│ ├── intl
│ │ ├── en
│ │ │ └── messages.json
│ │ └── zz
│ │ ├── messages.json
│ │ └── messages_inverted.json
│ └── package.json
└── gsub
├── index.js
├── intl
│ ├── en
│ │ ├── help.txt
│ │ └── messages.json
│ └── zz
│ ├── messages.json
│ └── messages_inverted.json
├── lib
│ └── util.js
└── package.json
strong-globalize extracts literal strings passed as the first argument of the strong-globalize functions. In globalizing existing modules, most code changes you are going to make will be to make sure all literal strings are in that form. Usually, you do not need to globalize debug text.
From strong-globalize point of view, the role of every JS file is one of the three types:
a. master main -- SetRootDir(__dirname) is declared right after require('strong-globalize') which is placed at the very first line of the main JS module of the root package in the application. See examples/gmain/index.js. SG.SetDefaultLanguage(); is optional if the lang parameter is omitted or 'en' (English) is used as the default language.
b. main -- The main JS module of all the other packages in the application must call SetRootDir(__dirname) in the first line of the main JS module of all the other (non-root) packages. See examples/gsub/index.js.
c. sub -- All the other JS modules that call the strong-globalize function require strong-globalize as var g = require('strong-globalize')(); See examples/gsub/lib/util.js In case you need multiplestrong-globalize` instances, do the following:
var SG = require('strong-globalize');
var gFrench = SG('fr');
var gSpanish = SG('es');
// parallel use
gFrench.log('text in French');
gSpanish.log('text in Spanish');
gFrench.log('second text in French');
You can also re-use one instance multiple times as follows:
var g = require('strong-globalize')();
g.setLanguage('fr');
g.log('text in French');
g.setLanguage('es');
g.log('text in Spanish');
g.setLanguage('fr');
g.log('second text in French');
FAQs
StrongLoop Globalize - API
The npm package strong-globalize receives a total of 171,262 weekly downloads. As such, strong-globalize popularity was classified as popular.
We found that strong-globalize demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.