[Top][All Lists]

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

[Octave-bug-tracker] [bug #53646] Wrong character encoding in axes label

From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #53646] Wrong character encoding in axes labels, titles etc.
Date: Sun, 10 Feb 2019 04:39:50 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0

Follow-up Comment #26, bug #53646 (project octave):

The last part is probably because the script is stored in the symbol table.
Executing "clear functions" should reset the symbol table and give different
results after changing the m-file encoding.
The file editor sometimes lacks a little bit behind when the encoding is
changed. Usually, closing the file and reopening it should display it

As to your problem with the command window not displaying utf-8 encoded
characters correctly: I have no clue what is going on there. The fact that you
see 4 diamonds when executing the utf-8 encoded file with your system encoding
(probably code page 1251 for an English Windows) suggests that the correct
utf-8 encoded characters are sent to the console.
I suspect this shows that the Windows console in Windows 10 still only
half-heartedly supports utf-8. I hope that jwe's plan to switch to a
cross-platform text widget for the command window will solve this in the

In the meantime, could you please open a new bug report for the issue you are
seeing? The original issue of this bug report (character encoding wrong when
plotting) seems to be resolved.


Reply to this item at:


  Message sent via Savannah

reply via email to

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