emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

emacs-29 be304bb3286: ; * etc/NEWS: Mention the 'utf-8-auto' bugfix (bug


From: Eli Zaretskii
Subject: emacs-29 be304bb3286: ; * etc/NEWS: Mention the 'utf-8-auto' bugfix (bug#60750).
Date: Thu, 2 Feb 2023 05:35:49 -0500 (EST)

branch: emacs-29
commit be304bb3286eb27e1aa8248eb3904925ed73dfcb
Author: Eli Zaretskii <eliz@gnu.org>
Commit: Eli Zaretskii <eliz@gnu.org>

    ; * etc/NEWS: Mention the 'utf-8-auto' bugfix (bug#60750).
---
 etc/NEWS | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/etc/NEWS b/etc/NEWS
index fb211f9b7d0..d402cc82c4a 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -563,6 +563,20 @@ The variable 'font-lock-support-mode' is occasionally 
useful for
 debugging purposes.  It is now a regular variable (instead of a user
 option) and can be set to nil to disable Just-in-time Lock mode.
 
++++
+** The 'utf-8-auto' coding-system now produces BOM on encoding.
+This is actually a bugfix, since this is how 'utf-8-auto' was
+documented from day one; it just didn't behave according to
+documentation.  It turns out some Lisp programs were using this
+coding-system on the wrong assumption that the "auto" part means some
+automagic handling of the end-of-line (EOL) format conversion; those
+program will now start to fail, because BOM signature in UTF-8 encoded
+text is rarely expected.  That is the reason we mention this bugfix
+here.
+
+In general, this coding-system should probably never be used for
+encoding, only for decoding.
+
 
 * Changes in Emacs 29.1
 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]