[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #52681] Bad reading for UTF-8 characters with fscanf()
Date: Sun, 17 Dec 2017 16:13:09 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

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:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]