Re: [Gretl-users] decimal separator bug
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sven Schreiber wrote:
Hi,
Allin Cottrell schrieb:
> True. That's largely because I don't know how to write, e.g.
>
> X ~ N(1.5, 25)
In the present state of things, I translate statically with a space
separating values:
X ~ N(1.5 25)
Allin: I was having the impression that the "Test for Normality of the
Residuals" graphic was presenting the localized numbers, but it is not.
I guess I need new glasses :).
But can't you pass to GNUPlot the legends with the numbers parsed?
The translated msgstr would be; N(%s, %s) and then translator would use
whatever list separator he choose.
> in a comma-using locale. As in my question above, is it
>
> X ~ N(1,5; 25)
> or what? Is there a definite standard?
I don't think that there is a definite standard, but for example in
Excel formulas are entered according localized settings (so with decimal
commas and semi-column as separator). But also in this case the files
are saved with default locales (decimal point, comma for thousands and
lists). This is probably the best solution. Only at run time the inputs
and outputs are processed. The disadvantage is that the clear text file
would not be localized (thinking in educational purpose).
>
I can only speak for German habits: No, I'm afraid not. On the
blackboard, some people use spacing to indicate the difference
(something like N(1,5 , 25)), but of course that's no option for
computers. Others have switched to decimal periods (in handwriting) for
that reason even though it's not the German standard. Personally I use
the semicolon as you suggest above, but my impression is that it's not
too widespread. As you know, for programming one has to use decimal
periods anyway for all (?) numerical languages.
Here we do just the same. This is because of old habits of
pre-localization systems.
Helio
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG8vhRHvesJJ5UqvkRAhYuAKCmjewGZ6LWrE2iKCR5eA8ziYRpmACghAlC
TR8hXlO0+cKXtmuU+LQSc48=
=69ex
-----END PGP SIGNATURE-----