|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #53842] Handle m-files with arbitrary character encoding |
Date: | Mon, 25 Jun 2018 07:47:19 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0 |
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/
[Prev in Thread] | Current Thread | [Next in Thread] |