[Octave-bug-tracker] [bug #33580] dlmread does not interpret CR as a newline

[Jordi Gutiérrez Hermoso]

Update of bug #33580 (project octave):

                Severity:              3 - Normal => 2 - Minor              
                Priority:              5 - Normal => 3 - Low                

    _______________________________________________________

Follow-up Comment #3:

> The most direct fix that works is to open the file in Excel 2011 and
> save as Windows formatted text.

Simple byte substitution seems more direct to me. You're using a Unix
system, and one of the guiding principles of Unix philosphy is that
text is the default format because it's the format that all Unix tools
can understand. It is not necessary to open Excel to manipulate a text
CSV file or to use Word to needlessly give formatting to a plaintext
Octave session as RTF. Perl as above is one simple example of how to
do this without all that Microsoft faff.

> The suggested fix perl -pi -e 's,r,n,gs' shanghai_node_list2.csv did
> not work.

I didn't think you would type the perl command in Octave, because I
had forgotten that Octave has a perl command. I meant in bash. Double
up the backslashes if you type it from Octave:


     perl -pi -e 's,\r,\n,gs' shanghai_node_list2.csv


Regardless, while I think it's still a valid point about making
dlmread and other Octave commands recognise Mac OS 9 line endings, I'm
marking this bug low priority for now. I hope you agree. If you don't,
I'll revert its severity.



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?33580>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/