The SO Post was in the right direction, but there are several environment variables which can be tested by an application. I use this script for example to reliably set the locale for commands:
#!/bin/sh
# $Id: with-locale,v 1.6 2011/10/27 22:51:45 tom Exp $
unset LANG
unset LC_ALL
unset LC_CTYPE
unset LESSCHARSET
unset LANGUAGE
LANG=$1
LC_ALL=$1
GDM_LANG=$1
export LANG
export LC_ALL
export GDM_LANG
shift
exec "$@"
That is, having with-locale
in my path, I might do
with-locale C mmmmmm
to verify that it has no hardcoded messages.
You can always check to see what variables apply to your environment by running the locale
command.
One of the comments asked about dpkg-reconfigure locales
. That is,
sudo dpkg-reconfigure locales
would provide you with the way to alter the default locale settings on the machine (see for example How do I fix my locale issue? on AskUbuntu). Your shell initialization could of course override those. Note that because there are several variables, they can be set inconsistently. The locale(7) manual page mentions a few of the possibilities, including the LANGUAGE
variable which can be the source of problems because it overrides the POSIX standard variables.
\u041a\u043e\u043c\u0430\u043d\u0434\u0430 'mmmm' \u043d\u0435 \u043d\u0430\u0439\u0434\u0435\u043d\u0430