[Octave-bug-tracker] [bug #43099] utf-8 files: editor, command windows issues, workspace pane shows correctly

[Markus Mützel]

Follow-up Comment #28, bug #43099 (project octave):

After some tests (see below), I'd like to propose to change the default
codepage for the editor and the command window to UTF-8 on Windows and
distribute a version that is compiled against QT5.

I cross-compiled Octave with QT5 and most of the issues seem to be resolved
after I change the following manually:
- Change encoding of the editor from "SYSTEM" to "UTF-8" in the properties.
- Execute 'system ("chcp 65001")' in the command window.

After this, when I run Colin's "testing_UTF8.m", I get the following correct
output:

>> testing_utf8

timesstr = ×
ellipsize = …
lquot = “
rquot = ”
mice_and_rice = 我爱你 爱着你 就像老鼠爱大米


The characters also display fine in the "Workspace" view. They look weird in
4.2.0-rc2.

Selecting all and pressing F9 yields the following:

>> timesstr = '\303\227'

timesstr = ×
>> ellipsize = '\342\200\246'

ellipsize = …
>> lquot = '\342\200\234'

lquot = “
>> rquot = '\342\200\235'

rquot = ”
>> mice_and_rice = '\346\210\221\347\210\261\344\275\240
\347\210\261\347\235\200\344\275\240
\345\260\261\345\203\217\350\200\201\351\274\240\347\210\261\345\244\2>

mice_and_rice = 我爱你 爱着你 就像老鼠爱大米


This looks like the decoded bytestream in UTF-8.

I still cannot enter umlauts like "äöü" or "ß" in the command window (bug
#47571). The keystrokes to these letters are silently ignored. Just a wild
guess because I don't know how that actually works: Could this be an issue
with readline on Windows which drops non-ASCII characters?

    _______________________________________________________

Reply to this item at:

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

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