[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #44029] Decimal number input parsing depends o

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #44029] Decimal number input parsing depends on locale
Date: Mon, 02 Feb 2015 04:35:20 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.91 Safari/537.36

Update of bug #44029 (project octave):

                  Status:                    None => Works For Me           


Follow-up Comment #4:

The only way I can get this to happen on my system is by commenting out the
following lines in libinterp/octave.cc:

  //setlocale (LC_NUMERIC, "C");
  //setlocale (LC_TIME, "C");

If I then set my locale to de_DE.utf8 or fr_FR.utf8, I get the same incorrect
results reported here. If I leave those lines compiled in, then the locale in
my environment doesn't affect how numbers are read or written.

Is it possible that the "C" locale doesn't exist or is configured differently
on some systems?

For the reporter or other people affected by this bug, what do the following
display in a bash shell?

$ printf "%.6f\n" 1
$ LC_NUMERIC=C printf "%.6f\n" 1


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]