[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #61839] fputs() + fdisp() do not use the fopen
From: |
Markus Mützel |
Subject: |
[Octave-bug-tracker] [bug #61839] fputs() + fdisp() do not use the fopen() character encoding |
Date: |
Mon, 17 Jan 2022 09:04:12 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36 Edg/97.0.1072.55 |
Update of bug #61839 (project octave):
Release: 7.0.90 => dev
_______________________________________________________
Follow-up Comment #1:
Thanks for reporting.
I haven't checked. But it's very well possible that `fputs` and `fdisp` use
different code paths (from `fprintf`) that don't respect the encoding setting
yet.
I'll try to look into this when I come around to it.
Like you've already written, a possible workaround until this is fixed is to
use:
fprintf(fid, "%s", str);
(It might be a good idea to use this "basic" format string to avoid surprises
in case `str` happens to contain parts that look like format strings or escape
sequences...)
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?61839>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/