[Top][All Lists]

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

[Octave-bug-tracker] [bug #49386] Non-latin characters in GUI

From: Hartmut
Subject: [Octave-bug-tracker] [bug #49386] Non-latin characters in GUI
Date: Wed, 26 Oct 2016 06:38:03 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0

Follow-up Comment #15, bug #49386 (project octave):

I have now tested default-octave built via mxe-octave with
* my "cstrings-patch" (file #38798) 
* my (unpublished) "toLocal8Bit-patch" (explained in bug #49118 comment #25)

The results under WinXP are fully the same as without the "toLocal8Bit-patch":
GUI editor is fine, inputdlg is fine, variable explorer is fine, but the GUI
console is as bad as before. Typing umlauts in the GUI console also still does
not work. I will attach another screenshot to visualize this. So this
"toLocal8bit-patch" does NOT HELP for anything (at least not under WinXP).

So I would agree with Philip's conclusions in bug #43099 comment #34:
* We should use the "cstrings-patch", it fixes the text coding issues with
Octave GUI windows, except for the console.
* We should also use the "65001-patch", it fixes the GUI console at least for
* Making the GUI console work with utf8 characters under Win7 seems to be
harder. (But has this ever worked before under Windows? Otherwise this is
"only" a bug, but it is not a regression like some of the other mentioned

(file #38812)

Additional Item Attachment:

File name: WinXP defaultoctave+cstring-patch + tolocal8bit-patch
editor+dlg=nice, console=ugly.png Size:59 KB


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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