|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #53646] Different character set in plot, in console and in the editor |
Date: | Sat, 14 Apr 2018 09:18:31 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 |
Update of bug #53646 (project octave): Status: Need Info => Confirmed Release: 4.2.2 => dev _______________________________________________________ Follow-up Comment #2: That is a known problem on systems where the default editor/system encoding is not UTF-8 (can't find the most relevant bug report right now): "Windows ANSI" encoding is basically the same as "ISO 8859-1" or "Latin-1". The Command Window always uses UTF-8 encoding to be able to display all Unicode characters. The Command Window has its own problems in dealing with non-ASCII characters (bug #47571). But if you mark the whole file content and hit F9 the é is "correctly" encoded for the Command Window. But the strings in the plot will show odd. What Octave probably should do, is use UTF-8 internally as its string encoding everywhere (and convert from whatever encoding is used in the editor/.m files). While this bug mainly affects Windows (which unfortunately doesn't support UTF-8 as its system codepage), this problem arises on every system that has a system codepage different from UTF-8. Still present in dev. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?53646> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |