[Octave-bug-tracker] [bug #53842] Handle m-files with arbitrary character encoding

[Markus Mützel]

Follow-up Comment #12, bug #53842 (project octave):

@Andrew: The first part of your comment #11 is bug #49685 which is on hold to
keep compatibility with Matlab.

I don't understand the last part of comment #11: UTF-8 is an encoding that
covers all Unicode characters. What do you mean by changing the default
encoding from "utf-8" to "unicode"?

Wrt your comment #10: Unfortunately(?) the C++ standard doesn't define any
character encodings. To make matters worse wchar_t and wstring have different
sizes on different platforms. So a compatible character encoding could be
either UTF-16 or UTF-32 (not both). While C++ 11 added u16string and
u32string, I don't know of any iostreams that support these types out of the
box.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53842>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/