This changes i18n format from i18next json to message format 2. See mf2 workgroup
You will need to polyfill Intl.MessageFormat
using following polyfill
When using this module, only the mf2 message format is respected, this means the i18next format interpolation will not work.
So for example instead of Hi {{name}}!
it is {Hi {$name}!}
Source can be loaded via npm or downloaded from this repo.
# npm package
$ npm install i18next-mf2
# peer dependencies
$ npm install --save-exact messageformat@next
Wiring up:
import i18next from 'i18next'
import mf2 from 'i18next-mf2'
i18next.use(mf2).init(i18nextOptions)
- As with all modules you can either pass the constructor function (class) to the i18next.use or a concrete instance.
- If you don't use a module loader it will be added to
window.i18nextMf2
{
// per default mf2 functions are parsed once and cached for subsequent calls
memoize: true,
// memoize if not having a lookup and just using the key fallback as value
memoizeFallback: false,
// which events should clear the cache, can be set to false or string of events separated by " "
bindI18n: '',
// which events on resourceSource should clear the cache, can be set to false or string of events separated by " "
bindI18nStore: '',
// Will be run when parser throws an error. Can return any string, which can be used as a fallback, in case of broken translation.
// If omitted, the default swallows the error and returns the unsubstituted string (res)
parseErrorHandler: (err, key, res, options) => {},
// Transform the language code prior to mf2 locale parsing, useful for supporting psuedo-locales like en-ZZ
// If omitted, the default leaves the language code as is
parseLngForMf2: (lng) => lng,
}
Options can be passed in by setting options.i18nFormat in i18next.init:
import i18next from 'i18next'
import mf2 from 'i18next-mf2'
i18next.use(mf2).init({
i18nFormat: options
})
import i18next from 'i18next'
import mf2 from 'i18next-mf2'
i18next.use(mf2).init({
lng: 'en',
resources: {
en: {
translation: {
key: '{Today is {$today :datetime dateStyle=medium}}'
}
}
}
})
i18next.t('key', { today: new Date('2022-02-02') }) // -> 'Today is Feb 2, 2022'
Using i18next-mf2 - non of the i18next specific stuff will be available. You will have to rely on what intl-messageformat provides by calling the t
function with needed options.
All extra features build around i18next plurals, interpolation, context do not get applied to messageformat based keys.
# i18next-mf2