[Octave-bug-tracker] [bug #63930] fprintf problem

[Dmitri A. Sergatskov]

Follow-up Comment #38, bug #63930 (project octave):

As I mentioned in comment #28 https://savannah.gnu.org/bugs/?63930#comment28
all the "t" mode does is changes (or not) line endings \n <--> \r\n. 
From: https://www.mathworks.com/help/matlab/ref/fopen.html

<<<
On Windows® systems, in text mode:

Read operations that encounter a carriage return followed by a newline
character ('\r\n') remove the carriage return from the input.

Write operations insert a carriage return before any newline character in the
output.

Open or create a new file in text mode if you want to write to it in MATLAB
and then open it in Microsoft® Notepad, or any text editor that does not
recognize '\n' as a newline sequence. When writing to the file, end each line
with '\r\n'. For an example, see fprintf. Otherwise, open files in binary mode
for better performance.

>>>

The fact that "t" changed encodings in octave is manifestation of other bugs.

Dmitri.
-- 



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63930>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/