Support i18n

Any plans to support i18n? I could help…

I’ve been thinking on something like that:

var superloginConfig = {
  ...
  i18n: {
    en: {
      validation_failed: 'Form validation error',
      email_already_in_use: 'This email has already been taken'
      ...
    },

    'pt-BR': {
      validation_failed: 'Erro na validação do formulário',
      email_already_in_use: 'Este email já está sendo utilizado'
      ...
    }
  }  
  ...
};

Then, somehow, a valid lang will be passed as a parameter in the URL. Maybe when using the superlogin client…

Any thoughts? Thanks!

[micky2be]

You could already have something based on the browser/os language using accept-language

const acceptLanguage = require('accept-language');
acceptLanguage.languages(['en', 'pt-BR']); // list of language you can manage
const clientLanguage = req.headers['accept-language']; // Header added by browsers
console.log(acceptLanguage.get(clientLanguage)); // will display the most suitable language

I already used it on a project and it’s working pretty well. Additionally the client could send a preferred language through config.

[colinskow]

I would prefer something very simple like:

res.status(200).json({
  ok: true, 
  code: 'logged_out',
  message: 'Logged out'
});

The message would be in whichever language was requested in the header, with English as a fallback.