[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #33580] dlmread does not interpret CR as a new
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #33580] dlmread does not interpret CR as a newline |
Date: |
Sun, 23 Oct 2016 05:37:06 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 |
Update of bug #33580 (project octave):
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #5:
Octave internally uses C++ getline() function to get a line of text. This
reads characters up to a newline and then discards the newline. Because no
one sat down to agree on this, a newline is CR on MAC, LF on UNIX, and CRLF on
Windows. The C++ standard library on the platform where Octave is executing
determines which character(s) are interpreted as newline. It is the user's
responsibility, and always has been, to change text files to the correct
encoding when moving between operating systems. This is not Octave specific
in any way.
There are utilities for this like dos2unix and unix2dos. Use these, or a
simple script like the Perl one posted earlier, when transferring files
between operating systems.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?33580>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #33580] dlmread does not interpret CR as a newline,
Rik <=