|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #56782] GNU Octave encoding issues under windows |
Date: | Wed, 21 Aug 2019 04:36:28 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0 |
Follow-up Comment #1, bug #56782 (project octave): There is a problem in Octave 5.1 that the selected encoding for .m files is not restored on startup. You can either change the encoding in the settings and call "clear functions" to trigger the .m files being parsed again. Or you could call the internal function "__mfile_encoding__". For UTF-8 encoding that would be: __mfile_encoding__ ("utf-8"); clear functions You could also add these lines to your start-up file. The issue is already fixed for Octave 6.1 that might be released around the end of this year. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?56782> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |