[Octave-bug-tracker] [bug #52681] Bad reading for UTF-8 characters with fscanf()

[Dan Sebald]

Follow-up Comment #8, bug #52681 (project octave):

Yes, something needs to be corrected here, I was just looking for some way of
finding a quick solution for the OP.  "testscan" is more useful than
"textread" in that regard because we can get past the problem of UTF-8 (in
file) range-limited to [0,127] by first reading as uint8.

I was confused by "help unicode2native" myself, as there was no documentation.
 But I see now that I had some really simple home-grown version of
unicode2native() in my personal utilities path.  The current documentation
seems OK.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/