[Octave-bug-tracker] [bug #63930] fprintf writes incorrect characters when converting the encoding

[Markus Mützel]

Follow-up Comment #65, bug #63930 (project octave):

@dasergatskov: Thank you. Checking if `_LIBCPP_VERSION` is defined and
emitting an error if `fopen` is used with an encoding (other than "UTF-8")
would probably help to avoid unexpected behavior.
We'd probably also need a `HAVE_*` macro to be able to skip the corresponding
test on that platform.

@charprap: Current nightlies are available from
https://buildbot.octave.space/#/download now. The Windows versions shouldn't
be affected by the remaining issues with `libc++`. They should be working
correctly.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63930>

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