View our GitHub

Please visit sails-docs on GitHub to view documentation on your mobile device.

Edit Page



The i18n hook reads JSON-formatted translation files from your project's "locales" directory (config/locales by default). Each file corresponds with a locale (usually a language) that your Sails backend will support.

These files contain locale-specific strings (as JSON key-value pairs) that you can use in your views, controllers, etc.

Here is an example locale file (config/locales/es.json):

    "Hello!": "Hola!",
    "Hello %s, how are you today?": "¿Hola %s, como estas?"

Note that the keys in your stringfiles (e.g. "Hello %s, how are you today?") are case sensitive and require exact matches. There are a few different schools of thought on the best approach here, and it really depends on who/how often you'll be editing the stringfiles vs. HTML in the future. Especially if you'll be editing the translations by hand, simpler, all-lowercase key names may be preferable for maintainability.

For example, here's another pass at config/locales/es.json:

    "hello": "Hola!",
    "hello-how-are-you-today": "Hola %s, ¿cómo estás?"

And here's config/locales/en.json:

    "hello": "Hello!",
    "hello-how-are-you-today": "Hello, how are you today?"

You can also nest locale strings. But a better approach would be to use . to represent nested strings. For example, here's the list of labels for the index page of a user controller:

    "": "User ID",
    "": "User Name"

Detecting and/or overriding the desired locale for a request

To determine the current locale used by the request, use req.getLocale().

To override the auto-detected language/localization preference for a request, use req.setLocale(), calling it with the unique code for the new locale, e.g.:

// Force the language to German for the remainder of the request:
// (this will use the strings located in `config/locales/de.json` for translation)

By default, node-i18n will detect the desired language of a request by examining its language headers. Language headers are set in your users' browser settings, and while they're correct most of the time, you may need the flexibility to override this detected locale and provide your own.

For instance, if your app allows users to pick their preferred language, you might create a policy which checks for a custom language in the user's session, and if one exists, sets the appropriate locale for use in subsequent policies, controller actions, and views:

// api/policies/localize.js
module.exports = function(req, res, next) {

Is something missing?

If you notice something we've missed or could be improved on, please follow this link and submit a pull request to the sails-docs repo. Once we merge it, the changes will be reflected on the website the next time it is deployed.