[Top][All Lists]

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

[Octave-bug-tracker] [bug #55452] fopen() does not support encoding argu

From: Andrew Janke
Subject: [Octave-bug-tracker] [bug #55452] fopen() does not support encoding argument
Date: Wed, 13 Mar 2019 02:39:16 -0400 (EDT)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36

Follow-up Comment #26, bug #55452 (project octave):

Hmm. If we're going to change "fgetl", it seems like "fgets" should change
too. The only difference between "fgetl" and "fgets" is whether they keep the
newline character.

It might make more sense to track Matlab's "fgets" behavior instead of POSIX
C's "fgets". And according to the Matlab doco, it reads characters in an
encoding-aware manner. https://www.mathworks.com/help/matlab/ref/fgets.html
(See "Tips" down at the bottom.) Interpreting the Matlab doco in this light is
a little hard, because Matlab uses 2-byte UTF-16 chars, so a Matlab char is
typically a single Unicode character, and vice versa.

I think you're right about POSIX C, though: when they say "character", I think
they usually mean C char.


Reply to this item at:


  Message sent via Savannah

reply via email to

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