[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #63930] fprintf problem
From: |
Markus Mützel |
Subject: |
[Octave-bug-tracker] [bug #63930] fprintf problem |
Date: |
Fri, 31 Mar 2023 09:26:39 -0400 (EDT) |
Follow-up Comment #39, bug #63930 (project octave):
> The fact that "t" changed encodings in octave is manifestation of other
bugs.
Did it change something before
https://hg.savannah.gnu.org/hgweb/octave/rev/fcd97a68e5f7 ?
Given that it looks like the output stream is converted in chunks of 32 bytes
(see comment #8), a single byte "\n" in contrast to two bytes "\r\n" might
have pushed the issue to a position where it didn't matter...
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63930>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #63930] fprintf problem, (continued)
- [Octave-bug-tracker] [bug #63930] fprintf problem, Arun Giridhar, 2023/03/24
- [Octave-bug-tracker] [bug #63930] fprintf problem, Arun Giridhar, 2023/03/24
- [Octave-bug-tracker] [bug #63930] fprintf problem, Dmitri A. Sergatskov, 2023/03/24
- [Octave-bug-tracker] [bug #63930] fprintf problem, Markus Mützel, 2023/03/28
- [Octave-bug-tracker] [bug #63930] fprintf problem, Dmitri A. Sergatskov, 2023/03/28
- [Octave-bug-tracker] [bug #63930] fprintf problem, Markus Mützel, 2023/03/28
- [Octave-bug-tracker] [bug #63930] fprintf problem, Dmitri A. Sergatskov, 2023/03/28
- [Octave-bug-tracker] [bug #63930] fprintf problem, Markus Mützel, 2023/03/28
- [Octave-bug-tracker] [bug #63930] fprintf problem, Markus Mützel, 2023/03/31
- [Octave-bug-tracker] [bug #63930] fprintf problem, Dmitri A. Sergatskov, 2023/03/31
- [Octave-bug-tracker] [bug #63930] fprintf problem,
Markus Mützel <=
- [Octave-bug-tracker] [bug #63930] fprintf writes incorrect characters when converting the encoding, Markus Mützel, 2023/03/31