From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: a.s@realize.ch, 20623@debbugs.gnu.org, sledergerber@gmx.net
Subject: bug#20623: XML and HTML files with encoding/charset="utf-8" declaration loose BOM; Coding system is reset from utf-8-with-signature to utf-8 on save
Date: Sat, 11 Aug 2018 20:04:05 -0400 [thread overview]
Message-ID: <jwvtvo05u5w.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83va8hko03.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 11 Aug 2018 16:54:04 +0300")
>> > > And I don't understand the comment about latin-1-mac: I don't think we
>> > > have such problems in Emacs. The -with-signature variety is
>> > > different, because it is not about EOL format.
>> > You might be right, but I don't know where/how this is handled.
>> I still don't know where the EOL part is handled.
> If you tell me what do you mean by "handled" in this context, I might
> be able to help you understand where that happens.
You say that the code I wrote is not needed to make sure an existing
latin-1-mac setting isn't overwritten by a latin-1 guess. I expect this
is indeed true (otherwise I think we'd have had bug-reports about it),
but I don't know where that is handled.
Stefan
next prev parent reply other threads:[~2018-08-12 0:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 18:50 bug#20623: XML and HTML files with encoding/charset="utf-8" declaration loose BOM; Coding system is reset from utf-8-with-signature to utf-8 on save Simon Ledergerber
2015-05-21 19:48 ` Eli Zaretskii
[not found] ` <555E44EB.6070604@gmx.net>
2015-05-22 7:11 ` Eli Zaretskii
2015-05-22 13:21 ` Simon Ledergerber
2016-10-12 21:44 ` Alain Schneble
2017-12-04 16:54 ` Glenn Morris
2017-12-04 17:38 ` Stefan Monnier
2017-12-04 20:28 ` Eli Zaretskii
2017-12-04 21:08 ` Stefan Monnier
2017-12-10 19:17 ` Eli Zaretskii
2017-12-15 9:08 ` Eli Zaretskii
2018-08-01 18:07 ` bug#20623: XML and HTML files with encoding/charset="utf-8" declaration lose " Glenn Morris
2018-08-01 18:41 ` Eli Zaretskii
2018-08-07 19:14 ` Glenn Morris
2018-08-11 12:45 ` bug#20623: XML and HTML files with encoding/charset="utf-8" declaration loose " Stefan Monnier
2018-08-11 13:54 ` Eli Zaretskii
2018-08-12 0:04 ` Stefan Monnier [this message]
2018-08-12 19:07 ` Eli Zaretskii
2018-08-08 9:47 ` Vincent Lefevre
2018-08-08 14:45 ` Stefan Monnier
2018-08-11 9:15 ` Eli Zaretskii
2018-08-11 10:13 ` Vincent Lefevre
2018-08-11 10:45 ` Eli Zaretskii
2018-08-11 15:41 ` Vincent Lefevre
2018-08-11 16:27 ` Eli Zaretskii
2018-08-12 1:34 ` Vincent Lefevre
2018-08-12 0:11 ` Stefan Monnier
2018-08-12 0:58 ` Vincent Lefevre
2015-05-22 15:22 ` Stefan Monnier
2015-05-22 15:26 ` Eli Zaretskii
2015-05-22 21:51 ` Stefan Monnier
2015-05-23 6:44 ` Eli Zaretskii
2015-05-23 17:11 ` Simon Ledergerber
2015-05-23 17:20 ` Eli Zaretskii
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvtvo05u5w.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=20623@debbugs.gnu.org \
--cc=a.s@realize.ch \
--cc=eliz@gnu.org \
--cc=sledergerber@gmx.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).