Since I am one in favor of localization in the most extent possible,
here is my contribute (not the first time, we talk about this).
Leaving the GUI aside (considering that solved), I think that we could
have a directive (or environmental variable setting) that a script
author would add in the script. The omission of that setting would go
for EN (as it is now).
But to guarantee that the setting defined by the script's author is
kept in the script, the setting would be explicit. For example, jut to
see the idea:
set number_style(',' , '.')
I also say that this setting is independent from the position in the
script where it's invoked. This allows to use it in the command line,
meaning that all numbers processed from that point, would use the
We can expect some performance degradation if the user decides to have
all input to be processed before being used in calculations when
having a setting other than default.
If a solution of this kind is implemented, I would not mind to
"translate" the example scripts. I can also make a utility program to
translate those numbers styles inside scripts.