[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #52556] Octave stops writing to console
From: |
Markus Mützel |
Subject: |
[Octave-bug-tracker] [bug #52556] Octave stops writing to console |
Date: |
Fri, 7 Dec 2018 10:03:09 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0 |
Update of bug #52556 (project octave):
Release: 4.2.1 => 4.4.1
_______________________________________________________
Follow-up Comment #9:
This works correctly for me in 4.4.1 if I use UTF-8 as the .m file encoding.
However, if I set the .m file encoding to SYSTEM (the default on Windows,
"CP1252" on my German Windows 10), I can reproduce this bug.
There have been some changes how Octave handles the encoding in .m files in
the development branch of Octave which will eventually be released as Octave
5.0.
I will try to test whether this particular use case has been fixed already.
In the meantime, you could manually select to use UTF-8 as the encoding of
your .m files. But if you want to use your .m files both in Octave and in
Matlab, keep in mind that Matlab uses the SYSTEM codepage on Windows.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?52556>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/