GNU bug report logs - #20623
XML and HTML files with encoding/charset="utf-8" declaration lose BOM; Coding system is reset from utf-8-with-signature to utf-8 on save

Previous Next

Package: emacs;

Reported by: Simon Ledergerber <sledergerber <at> gmx.net>

Date: Thu, 21 May 2015 18:53:02 UTC

Severity: normal

Found in version 26.1

Fixed in version 26.2

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Vincent Lefevre <vincent <at> vinc17.net>
Cc: rgm <at> gnu.org, a.s <at> realize.ch, monnier <at> iro.umontreal.ca, 20623 <at> debbugs.gnu.org, sledergerber <at> 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 13:45:17 +0300
> Date: Sat, 11 Aug 2018 12:13:41 +0200
> From: Vincent Lefevre <vincent <at> vinc17.net>
> Cc: monnier <at> iro.umontreal.ca, rgm <at> gnu.org, sledergerber <at> gmx.net,
> 	a.s <at> realize.ch, 20623 <at> debbugs.gnu.org
> 
> On 2018-08-11 12:15:31 +0300, Eli Zaretskii wrote:
> > In this case, I cannot but express my extreme surprise to see such a
> > minor issue described as "grave".  The alleged data loss is minor, if
> > it exists at all (the BOM is not data important for the user,
> 
> You're completely wrong. The presence of BOM or not is very important
> for some applications, such as Firefox (not to determine the charset,
> but the MIME type of local files).

Please provide the details, including the use case, if possible.  I'm
still in the dark regarding the importance of the BOM in UTF-8 encoded
HTML stuff.

> It can be repaired, but the problems are the user doesn't know
> what's going on and this breaks things.

I agree about the user not knowing, but that doesn't yet qualify as
"data loss", which has an widely accepted meaning.

> If some package removed the execute permission of some utility in
> /bin, this would also be a grave bug, though it can easily been
> repaired.

Well, I disagree about the "grave" part, because that means the
package is unusable, causes data loss, or introduces a security hole
allowing access to the user account.  None of that is true in the case
in point.




This bug report was last modified 6 years and 279 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.