From: Tom Gillespie <tgbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] * etc/NEWS: Announce addition of BOM to utf-8-auto
Date: Sun, 29 Jan 2023 14:11:13 -0500 [thread overview]
Message-ID: <CA+G3_PMd7qt-F0ycF1Mo92fSUEY8G0wKSupU9fNwS3PKThzL3g@mail.gmail.com> (raw)
In-Reply-To: <837cx56vpc.fsf@gnu.org>
> > +** The 'utf-8-auto' coding-system now includes a byte order mark
>
> This is inaccurate: the change is only on encoding, and saying that a
> coding-system "includes" a BOM is confusing English, IMO.
Hrm. I agree. Would it be better to say something like the following?
"Encoding 'utf-8-auto' now correctly produces a byte order mark"
> More importantly, it was a bugfix. utf-8-auto was previously behaving
> contrary to the documentation:
> We don't announce bugfixes in NEWS, mainly because doing so would make
> an already large file many times larger.
I understand that this is technically a bugfix, but it is also a major
change in the actual behavior that could catch users by surprise
and that is very difficult to detect and debug. Is it reasonable to
use NEWS to try to mitigate the potential blast radius in such cases?
next prev parent reply other threads:[~2023-01-29 19:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 17:58 [PATCH] * etc/NEWS: Announce addition of BOM to utf-8-auto Tom Gillespie
2023-01-29 18:14 ` Andreas Schwab
2023-01-29 18:29 ` Eli Zaretskii
2023-01-29 19:11 ` Tom Gillespie [this message]
2023-01-29 19:38 ` Eli Zaretskii
2023-01-29 19:56 ` Tom Gillespie
2023-01-30 14:16 ` Eli Zaretskii
2023-01-30 15:06 ` Stefan Monnier
2023-01-30 17:12 ` Eli Zaretskii
2023-02-02 10:36 ` Eli Zaretskii
2023-02-02 17:56 ` Tom Gillespie
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=CA+G3_PMd7qt-F0ycF1Mo92fSUEY8G0wKSupU9fNwS3PKThzL3g@mail.gmail.com \
--to=tgbugs@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.
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).