[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #41326] textread gives unnecessary warning on
|
From: |
H. G. |
|
Subject: |
[Octave-bug-tracker] [bug #41326] textread gives unnecessary warning on umlauts |
|
Date: |
Thu, 23 Jan 2014 22:01:03 +0000 |
|
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 |
Follow-up Comment #2, bug #41326 (project octave):
You are right: My original csv file was coded in UTF-8. Then it worked fine as
described.
Once I save the umlaut in a file with "Windows-1252/WinLatin" for example, I
only get a funny symbol instead of my umlaut.
Note: When I switch to textscan command instead, like aa =
textscan('test.csv','%s') , then I do get a nice umlaut even with the WinLatin
encoding.
Is this a bug? I mean: Can Matlab read umlauts properly with textread /
textscan? There seem to be Matlab commands like detect_encoding and
unicode2native in Matlab. This might suggest that textread/textscan in Matlab
isn't any better either.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?41326>
_______________________________________________
Nachricht gesendet von/durch Savannah
http://savannah.gnu.org/