[Top][All Lists]

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

[Octave-bug-tracker] [bug #41326] textread gives unnecessary warning on

From: anonymous
Subject: [Octave-bug-tracker] [bug #41326] textread gives unnecessary warning on umlauts
Date: Mon, 27 Jan 2014 08:11:17 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0

Follow-up Comment #5, bug #41326 (project octave):

For the record, after testing I have come to the following conclusion (at
least for my linux system): there indeed is no encoding handling in octave,
but interaction through the terminal (don't know about the GUI) -- supposedly
via external libraries or terminal emulators -- assumes (and works correct
with) UTF-8. So you can say a='ü' and it will display correctly, whos will
show you that it occupies two bytes, and double(a) gives you the UTF-8
representation of this code point (and this also holds for unicode code points
that do not coincide with ISO 8859-1, as is here the case). So when saving
your text files in UTF-8, this interfaces nicely with fread/fwrite,
This is a very desirable behaviour, whatever matlab may do, and there is
definitely no need for any magic involving encoding guessing (such as text
editors do) on the octave side.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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