[Octave-bug-tracker] [bug #63930] fprintf problem

[Markus Mützel]

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

I'm assuming that you mean "char arrays" when you write "strings".

That'd be a major change. We can't do that to fix the issue in a dot-release.
But maybe you could bring that up in the next online meeting?

As a "low-hanging" short-term solution, defaulting to no conversion again
(i.e., UTF-8 output independent of the value set for `__mfile_encoding__`)
might help to reduce the number of users that are affected.



    _______________________________________________________

Reply to this item at:

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

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