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

[Dan Sebald]

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

Just adding that there seems to be a great deal of UTF-8-related code scripts
in the project...and some poorly documented routines such as:


octave:7> unicode2native("TEST")
ans =

  84  69  83  84

octave:8> str = unicode2native("TEST")
str =

  84  69  83  84

octave:9> str = unicode2native("TESTñó")
str =

   84   69   83   84  195  177  195  179

octave:10> native2unicode(str)
ans = TESTñó


As a work-around, is it possible to somehow scan your file data as signed
8-bit chars searching for the NULL character, then run native2unicode() on
that data?

    _______________________________________________________

Reply to this item at:

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

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