Waterhole uses the following algorithm to determine which language to use:
If the user has selected a language, use that. (If they are logged in, it's stored in their preferences; otherwise it's stored in the session.)
Otherwise, use the closest matching preferred language from the Accept-Language header sent by the browser.
The app.locale setting is not actually used for Waterhole requests.
You should keep app.fallback_locale set to en so that any strings that don't have a zh translation will fall back to English instead of printing out the translation key.
You don't have permission to do this.
You're going a bit too fast! Take a break and try again in a moment.
Something went wrong! Please reload the page and try again.
I'm not sure I quite understand the problem, so I'll just explain how the language system works.
In order to become available, languages must be registered using the
Localesextender. For example, inWaterholeServiceProvider, you would add:Waterhole uses the following algorithm to determine which language to use:
Accept-Languageheader sent by the browser.The
app.localesetting is not actually used for Waterhole requests.You should keep
app.fallback_localeset toenso that any strings that don't have azhtranslation will fall back to English instead of printing out the translation key.