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

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

[Octave-bug-tracker] [bug #51210] Non-ASCII text displays incorrectly in


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #51210] Non-ASCII text displays incorrectly in plots
Date: Fri, 9 Jun 2017 07:58:29 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:54.0) Gecko/20100101 Firefox/54.0

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

                 Summary: Non-ASCII text displays incorrectly in plots
                 Project: GNU Octave
            Submitted by: mmuetzel
            Submitted on: Fri 09 Jun 2017 11:58:28 AM UTC
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: Confirmed
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

As described in bug #51203, text is messed up in plots if the encoding
selected for the text editor does not match the system codepage.

Steps to reproduce:
1. Select an encoding for the editor that does not match the system codepage
(e.g. UTF-8 on Windows).
2. Add text that contains characters that cannot be encoded in the system
codepage (e.g. any non-ASCII character for UTF-8 on Windows).

Even if this mainly affects Windows. This could also occur on other platform
when working with files that are not UTF-8 encoded. (Haven't checked.)

I think the locale for C-strings should match the encoding selected in Octave.
Otherwise std::mbrtowc fails to correctly convert the multi byte string to a
wide character string in ft-text-renderer.cc. Something like this should be
set:

std::setlocale (LC_CTYPE, octave_encoding);


However, I do not know neither where this should be done (the interpreter?)
nor how to query Octave's current encoding.




    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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