This is a known issue that we are currently working on fixing. I have opened bug 21433 to address the issue of the client not honoring the browser's locale setting.
If you are running 5.0.0 RC1 and know that your users are going to use a specific language, then you can set that preferred locale for all users of a COS (or domain, server, etc). Here's how you would set the default locale to US English for all users of the default COS:
Code:
% zmprov mc default zimbraPrefLocale en_US
Substitute your preferred locale, as {language}_{country} (or just {language}) as needed.
While this is necessary for now, it is
not recommended once the bug is fixed because once a locale is set, the client will ignore the browser locale. Each user will then have to go their Preferences and change their preferred locale. And, once changed, the client will use that local ignoring the browser's setting.
The ability to set a default locale by the administrator (and also by the user) was requested by Zimbra customers that wanted to control what the default language would be, regardless of the browser setting. For those customers, they should set the zimbraPrefLocale setting; for others, this setting should remain unset so as to allow the browser's locale to take precedence.
Perhaps the best short-term solution is setting the server's locale via LC_ALL.
P.S. The reason why the login/splash are always correct is that they are rendered by the server via a JSP before the user has been authenticated. Without authentication, we do not know the preferred locale setting so we just revert to the browser's locale.