From: Jean Abou Samra <jean@abou-samra.fr>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-user@gnu.org
Subject: Re: UTF16 encoding adds BOM everywhere?
Date: Wed, 20 Jul 2022 23:45:23 +0200 [thread overview]
Message-ID: <de2c93c3-7758-1005-571b-4189283ffb2e@abou-samra.fr> (raw)
In-Reply-To: <87pmhz347r.fsf@netris.org>
Hi Mark,
Thanks for your reply!
Le 20/07/2022 à 22:42, Mark H Weaver a écrit :
> Hi,
>
> No, this is certainly a bug. It sounds like the
> 'at_stream_start_for_bom_write' port flag is not being cleared, as it
> should be, after the first character is written. I suspect that it
> worked correctly when I first implemented proper BOM handling in 2013
> (commit cdd3d6c9f423d5b95f05193fe3c27d50b56957e9), but the ports code
> has seen some major reworking since then. I guess that BOM handling was
> broken somewhere along the way.
>
> I would suggest filing a bug report.
OK, opened
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56675
> I don't have time to look into it, sorry. I don't work on Guile anymore.
A pity :-)
Cheers,
Jean
prev parent reply other threads:[~2022-07-20 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 19:16 UTF16 encoding adds BOM everywhere? Jean Abou Samra
2022-07-20 20:42 ` Mark H Weaver
2022-07-20 21:45 ` Jean Abou Samra [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de2c93c3-7758-1005-571b-4189283ffb2e@abou-samra.fr \
--to=jean@abou-samra.fr \
--cc=guile-user@gnu.org \
--cc=mhw@netris.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).