bugGNU Octave - Bugs: bug #46848, text file format not documented


bug #46848: text file format not documented

Submitted by:  Francesco Potortì <pot>
Submitted on:  Fri 08 Jan 2016 11:06:06 AM UTC  
Category:  Documentation Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Feature Request
Status:  Confirmed Assigned to:  None
Originator Name:  Open/Closed:  Open
Release:  4.0.0 Operating System:  GNU/Linux

Add a New Comment (Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


Fri 08 Jan 2016 11:06:06 AM UTC, original submission:  

As far as I can find in the manual, the text file format of Octave is not documented.

For example, the -ascii option to save() does not mention how the text file is written: it should mention save_precision(), should say what the separator is, should say that rows are separated by newlines.

As another example, load() is said to be able to read Octave text files, but to understand what is the used format, one must resort to looking at how Octave creates text files. And this is not enough: only today after years of use of Octave, while reading the help mailing list I discovered that load can read comma-separated text files, which is important information indeed.

Francesco Potortì <pot>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by siko1056 (Updated the item)
  • -email is unavailable- added by pot (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.




    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-01-08 siko1056 StatusNone => Confirmed

    Back to the top

    Powered by Savane 3.7