I18n (internationalisation) support

[stanislas-m]

As a plugin / module, I think we can provide a way to manage translations.

Common solutions:

• GNU gettext with po/pot/mo files
• ini files
• yaml or json files

[u007]

will this help?
https://gist.github.com/u007/fda1dd4f92f424242732b5f7a82d5fc3

i think it needs to have the files in config/locales/* in watch

it seems to be not so good, because i need to detect language from header, anyone have any suggestion?

[stanislas-m]

@u007 Hum, if you look at the comments in the code:

// Use Tfunc or MustTfunc to fetch a TranslateFunc that will return the translated string for a specific language.
//     func handleRequest(w http.ResponseWriter, r *http.Request) {
//         cookieLang := r.Cookie("lang")
//         acceptLang := r.Header.Get("Accept-Language")
//         defaultLang = "en-US"  // known valid language
//         T, err := i18n.Tfunc(cookieLang, acceptLang, defaultLang)
//         fmt.Println(T("Hello world"))
//     }

I think it just have to be called like this in a custom middleware.

[markbates]

We also need to think about, make sure, that translation files get bundled into the binary that is built.

[u007]

ive done fix in the gist, made a middleware to setup velvet with context
and pass shared i18n setup to another sub directory so it can be shared among actions