|
From: | Philip Nienhuis |
Subject: | [Octave-bug-tracker] [bug #43099] utf-8 files: editor, command windows issues, workspace pane shows correctly |
Date: | Sat, 21 Mar 2015 10:05:25 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33 |
Update of bug #43099 (project octave): Release: 3.8.2 => dev _______________________________________________________ Follow-up Comment #15: _"on GNU/Linux we have beauty. Which is of course true on many levels"_ Sure, point taken :-) [OT] (BTW I'm no windows fan or so. I just happen to work in a "culture" where Windows (and much other proprietary SW) is used for about everything; if they could make coffee with it they'd do that as well. So my primary interest here, apart from fun/hobby, is simply to get/keep Octave running in that environment/culture. No more, no less. [Back to topic] So, had this bug better be renamed to "Unicode doesn't work on Windows"? Or just leave it as is, enter a new bug report for unicode-on-windows (if it isn't already there) and add that as a dependency? (that seems to be possible) What I will do is set "Release" to "dev" _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?43099> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |