[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #58860] [octave forge] (tsa) Use UTF-8 encodin
[Octave-bug-tracker] [bug #58860] [octave forge] (tsa) Use UTF-8 encoding
Fri, 18 Sep 2020 05:10:15 -0400 (EDT)
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.102 Safari/537.36 Edg/85.0.564.51
Follow-up Comment #3, bug #58860 (project octave):
Variables of type "char" are expected to be UTF-8 encoded inside Octave.
Missing conversions at the interfaces are bugs.
This seems to be one of those bugs.
You are right: Currently, the default .m file encoding is the "native"
encoding configured for the system Octave is running on. This is probably a
good choice imho.
However, there is currently no way of setting a file encoding on a
per-directory basis (like proposed in the thread to which you linked). I agree
that it would make sense to make that possible.
I believe there was a bug report about this. But I can't find it at the
If there is none, it would probably be best to open one and discuss the
general issue there.
Reply to this item at:
Message sent via Savannah