Unclear workflow when missing translations about go-i18n HOT 7 CLOSED

You are the second person to bring this up so I will think about it some more.

In the meantime, you should be able to just wrap your Tfunc in another function to make the fallback behavior explicit.

Something like this (pseudocode, not tested)

func MyTfunc(pref string, prefs ...string) TranslateFunc {
    t := i18n.MustTfunc(pref, prefs...)
    return func(translationID string, args ...interface{}) string {
        if translated := t(translationID, args...); translated != translationID {
            return translated
        }
        return i18n.MustTfunc("en-US", args...) // assuming en-US is your "default" locale
    }
}

from go-i18n.

Thanks, I'll give that a shot. I'll report back on any performance penalty I see with that approach.

from go-i18n.

We ran into the same problem. A global fallback would be great since something is better than nothing.

from go-i18n.

@coreyhulen You can see our implementation of @nicksnyder's suggestion above here: https://github.com/cloudfoundry/cli/blob/master/cf/i18n/i18n.go#L59

from go-i18n.

thanks @krishicks

from go-i18n.

v2 includes a proposal to perform fallbacks on a per-message basis. See #92

from go-i18n.

I just tagged 2.0.0.beta.1. Please start using it and report any issues that you have.

from go-i18n.