octave-bug-tracker
[Top][All Lists]
Advanced

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

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


From: anonymous
Subject: [Octave-bug-tracker] [bug #44029] Decimal number input parsing depends on locale
Date: Sat, 17 Jan 2015 16:30:56 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:35.0) Gecko/20100101 Firefox/35.0

URL:
  <http://savannah.gnu.org/bugs/?44029>

                 Summary: Decimal number input parsing depends on locale
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Sa 17 Jan 2015 16:30:55 UTC
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: Mirko Hessel-von Molo
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.8.2
        Operating System: GNU/Linux

    _______________________________________________________

Details:

I am using a freshly compiled Version 3.8.2 with GUI on Ubuntu 14.04 with
German localization (i. e. de_DE.UTF-8 chosen in locale configuration). I
experience obviously incorrect interpretation of decimal number input. Both
interactively or from a script file, a statement like


>> a = 1.3


results in the answer


a = 1


i. e. returning only the integer part of the input. Saying instead 


>> a = 1+3/10


using only integers gives the correct answer


a = 1.3000


I suspected that it might be an issue with the point character not being
interpreted as a decimal point due to the German locale and tried starting
Octave by issueing


LANG=en_US.UTF-8 GDM_LANG=en_US LANGUAGE=en_US
/usr/local/libexec/octave/3.8.2/exec/i686-pc-linux-gnu/octave-gui --force-gui


from the command line. In the GUI now starting, 
decimal input appears to be interpreted correctly. 

This behaviour is not found in the CLI version.

I use the above workaround for the time being. It might also be used in the
install script, however I am not able to provide a properly formulated patch
for this. 




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44029>

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/




reply via email to

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