i18n does not support the objectNotation config option

[davesag]

As discussed in this Stackoverflow question, I can't work out how to get Sails' i18n to support anything other than the most trivial of i18n examples.

I've had a look through the code, and, looking at lines 54 to 59 of sails/lib/hooks/i18n/index.js the configuration I set in my projects own config/i18n.js file, namely:

module.exports.i18n = {
  locales: ['en', 'es', 'fr', 'de'],
  objectNotation: true
};

are indeed passed through to the i18n.configure() method, but still I can't actually use the objectNotation options. I just get my keys returned back to me.

I've generated a new Sails project that demonstrates this error. See https://github.com/davesag/sails-i18n-example

In view homepage.jade

• line 23: works — The simple translation at line https://github.com/davesag/sails-i18n-example/blob/master/views/homepage.jade#L23 works fine
• line 26: fails — The objectNotation translation at line https://github.com/davesag/sails-i18n-example/blob/master/views/homepage.jade#L26 is not translated.

In config/i18n.js

https://github.com/davesag/sails-i18n-example/blob/master/config/i18n.js#L17 shows that the objectNotation: true flag is set.

In config/locales/en.json

https://github.com/davesag/sails-i18n-example/blob/master/config/locales/en.json#L4 shows the expected translation.

[mdunisch]

+1
We have the same Problem

[davesag]

It might actually make more sense to include i18next rather than the old i18n-node package. Just a thought.

[davesag]

Okay I have worked out what's wrong. The objectNotation feature was added to i18n-node in version 0.5.0 about a week ago, and the version in Sails.js's package.js is 0.4.1