From: Eli Zaretskii <eliz@gnu.org>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] * etc/NEWS: Announce addition of BOM to utf-8-auto
Date: Sun, 29 Jan 2023 20:29:19 +0200 [thread overview]
Message-ID: <837cx56vpc.fsf@gnu.org> (raw)
In-Reply-To: <CA+G3_PMvgP4Ua6Y7kYy1hOEHOfcmXf789WE0gqDFSdu_h=bt1A@mail.gmail.com> (message from Tom Gillespie on Sun, 29 Jan 2023 12:58:38 -0500)
> From: Tom Gillespie <tgbugs@gmail.com>
> Date: Sun, 29 Jan 2023 12:58:38 -0500
>
> --- a/etc/NEWS
> +++ b/etc/NEWS
> @@ -563,6 +563,9 @@ 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 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.
More importantly, it was a bugfix. utf-8-auto was previously behaving
contrary to the documentation:
‘:bom’
This attributes specifies whether the coding system uses a "byte order
mark". VALUE must be nil, t, or a cons cell of coding systems whose
‘:coding-type’ is ‘utf-16’ or ‘utf-8’.
[...]
If the value is a cons cell, on decoding, check the first two bytes.
If they are 0xFE 0xFF, use the car part coding system of the value.
If they are 0xFF 0xFE, use the cdr part coding system of the value.
Otherwise, treat them as bytes for a normal character. On encoding,
produce BOM bytes according to the value of ‘:endian’.
Note the last sentence.
We don't announce bugfixes in NEWS, mainly because doing so would make
an already large file many times larger.
next prev parent reply other threads:[~2023-01-29 18:29 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 [this message]
2023-01-29 19:11 ` Tom Gillespie
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837cx56vpc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tgbugs@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.