Marcus Spiegel
Marcus Spiegel
Maybe you can add some code to reproduce your setup?
ok, I think one could setup such like so with fallbacks (https://github.com/mashpie/i18n-node#list-of-configuration-options): ``` js fallbacks: { 'es': 'es_MZ', 'es_MZ': 'es_MZ-something' }, ``` tests don't cover that scenario at the moment...
you may configure a function that acts as middleware on every call for a missing key: ```js // used to alter the behaviour of missing keys missingKeyFn: function (locale, value)...
defaults as intended: https://github.com/mashpie/i18n-node/blob/master/test/i18n.missingPhrases.js#L27 hook for customization: https://github.com/mashpie/i18n-node/blob/master/test/i18n.missingPhrases.js#L42
....well, yes. When started, I decided to leave cases and names of any locale completely untouched and up to the developers or frameworks responsibility to handle it "their way" File...
as for docs: https://github.com/mashpie/i18n-node#storage should be more expressive either way :) feel free to send a pr - or wait until I‘ll manage to write some more words. > Am...
you could setup fallbacks, ie.: ``` i18n.configure({ // setup some locales - other locales default to en silently locales: ['en', 'de'], // fallback from Dutch to German and from any...
Looks like you are looking for https://github.com/mashpie/i18n-node#defaults so in your case: ``` i18n.__("error:Server error") ``` should do
Hey :) in short: this is intended. Let me explain what happens: by default i18n will return the "key" as is, as long there is no translation found for current...
both scenarios have their pros and cons (actually I do use both depending on use case, for more than 15years now). OK no need to discuss as there is a...