[Top][All Lists]

[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: Sat, 8 Dec 2018 07:16:26 -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.4.1 => dev                    


Follow-up Comment #10:

The "äöü" example works for me with the SYSTEM encoding when I test with a
recent version from the default branch. I am still un-sure whether it will
work for everyone cause I have some local modifications to relevant packages
in MXE Octave.

However, "help sym" displays a lot of scrambled characters. That is because
that file is encoded in UTF-8 but we assume it to be encoded in the SYSTEM
encoding. Converting it from SYSTEM (CP1252 in my case) to UTF-8 creates these
odd characters.

That conversion is done in input.cc in function "file_reader::get_input".
Can we differentiate between .m files from the core or packages (which
probably always are UTF-8) on the one hand and user created .m files (which
could have any encoding) on the other hand at that point? Does the lexer keep
track of this?


Reply to this item at:


  Message sent via Savannah

reply via email to

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