locale LXM 17

1/   wine excel  +  libre office calc : munt format is in US format  
2/   mint : system time is in UK format

ward@lapwm2-lxm ~ $ locale
LANG=en_GB.UTF-8
LANGUAGE=
LC_CTYPE=”en_GB.UTF-8”
LC_NUMERIC=nl_BE@euro
LC_TIME=en_GB.UTF-8
LC_COLLATE=”en_GB.UTF-8”
LC_MONETARY=nl_BE@euro
LC_MESSAGES=”en_GB.UTF-8”
LC_PAPER=nl_BE@euro
LC_NAME=nl_BE@euro
LC_ADDRESS=nl_BE@euro
LC_TELEPHONE=nl_BE@euro
LC_MEASUREMENT=nl_BE@euro
LC_IDENTIFICATION=nl_BE@euro
LC_ALL=

2/ is logisch   , echter 1/ is het niet
https://www.linux.com/news/controlling-your-locale-environment-variables

LC_ zijn environment variables , gezet door

https://help.ubuntu.com/community/EnvironmentVariables :
Session-wide environment variables
Environment variable settings that should affect just a particular user
(rather then the >system as a whole) should be set into:
~/.pam_environment - This file is specifically meant for setting a
user’s  environment.

inhoud van  ~/.pam_environment :
LC_NUMERIC=nl_BE@euro
LC_TIME=en_GB.UTF-8
LC_MONETARY=nl_BE@euro
LC_PAPER=nl_BE@euro
LC_NAME=nl_BE@euro
LC_ADDRESS=nl_BE@euro
LC_TELEPHONE=nl_BE@euro
LC_MEASUREMENT=nl_BE@euro
LC_IDENTIFICATION=nl_BE@euro
PAPERSIZE=letter

zou het kunnen dat  ~/.pam_environment :: LC_MONETARY=nl_BE@euro  <>
system LC_MONETARY ??

The environment variable hierarchy
Most of the time you’ll want to set all of these variables to the same
value, but occasionally it makes sense to use different values. For
example, if you want your interface language to be English but are
sorting French data, you could set LC_MESSAGES to en_US but LC_COLLATE
to fr_FR.
When you don’t want to use different values, it isn’t necessary to set
all of the variables individually. Instead, you can set LC_ALL or LANG.
When a program looks at the environment variables to determine what
locale to use, it follows the following procedure:

• the LC_ALL environment variable is defined and is not null, its
  value is used.
• If the appropriate component-specific environment variable – e.g.
  LC_COLLATE – is set and non-null, its value is used.
• If the LANG environment variable is defined and is not null, its
  value is used.
• If the LANG environment variable is not set or is null, an
  implementation-dependent default locale is used.
• Notice that this means that if you want to use different locales for
  different purposes you should unset LC_ALL.

Changing Locale
Your Locale
You have a mix of several locales, at least en_US and ar_SA. These
actually come from environment variables (the names of which locale is
displaying for you).

If these are only for your user, they may be coming from a setting in
your desktop environment. Go into settings and look for language and/or
locale settings. There may also be a language selector on the login
screen.

System Default Locale
On Debian-like systems, the system default locale is stored in
/etc/default/locale. Not all locales are necessarily available
(generated), however; if the locales-all pac…

https://unix.stackexchange.com/questions/117608/changing-locale#117611

ward@lapwm2-lxm ~ $ locale -a
C
C.UTF-8
de_BE.utf8
en_GB.utf8
en_US.utf8
nl_AW
nl_AW.utf8
nl_BE@euro
nl_BE.iso885915@euro
nl_BE.utf8
nl_NL.utf8
POSIX
ward@lapwm2-lxm ~ $

C = de classic C shell output   /   C.UTF-8  C output using utf8

environment variable named LANG with the given value ru_RU.UTF-8. That
instructs internationalized programs to use the Russian language (ru),
variant from Russia (RU), and the UTF-8 encoding for console output.
export LC_CTYPE=ru_RU.UTF-8
Does a similar thing, but it tells the program not to change the
language, but only the CTYPE to Russian. If a program can change a text
to uppercase, then it will use the Russian rules to do so, even though
the text itself may be in English.
It is worth saying that mixing LANG and LC_CTYPE can give unexpected
results, because few people do that, so it is quite untested,

LC_CTYPE This variable determines the locale category for character
handling functions, such as tolower(), toupper() and isalpha(). This
environment variable determines the interpretation of sequences of bytes
of text data as characters (for example, single- as opposed to
multi-byte characters), the classification of characters (for example,
alpha, digit, graph) and the behaviour of character classes. Additional
semantics of this variable, if any, are implementation-dependent.