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

[Markus Mützel]

Update of bug #63930 (project octave):

                 Summary:         fprintf problem => fprintf writes incorrect
characters when converting the encoding

    _______________________________________________________

Follow-up Comment #40:

I pushed a change to the stable branch that defaults the encoding to UTF-8
when opening streams with `fopen`:
https://hg.savannah.gnu.org/hgweb/octave/rev/0ed6d1f01625

That fixes the issue with the scripts from comment #0 for me. The files are
successfully written (in UTF-8).
That is compatible to newer versions of Matlab which also write in UTF-8 if no
differing encoding is specified when opening the stream with `fopen`.

That will mitigate this regression for users that don't specify an encoding
when opening a stream with `fopen`. I'd guess that is the large majority of
cases.

With that in place, we could probably revert
https://hg.savannah.gnu.org/hgweb/octave/rev/fcd97a68e5f7 to restore Matlab
compatibility without re-introducing the regression for the large majority of
cases.

Re-titling the report to reflect the remaining issue.


    _______________________________________________________

Reply to this item at:

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

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