[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] * etc/NEWS: Announce addition of BOM to utf-8-auto
From: |
Tom Gillespie |
Subject: |
Re: [PATCH] * etc/NEWS: Announce addition of BOM to utf-8-auto |
Date: |
Sun, 29 Jan 2023 14:11:13 -0500 |
> > +** 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?
- [PATCH] * etc/NEWS: Announce addition of BOM to utf-8-auto, Tom Gillespie, 2023/01/29
- Re: [PATCH] * etc/NEWS: Announce addition of BOM to utf-8-auto, Andreas Schwab, 2023/01/29
- Re: [PATCH] * etc/NEWS: Announce addition of BOM to utf-8-auto, Eli Zaretskii, 2023/01/29
- Re: [PATCH] * etc/NEWS: Announce addition of BOM to utf-8-auto,
Tom Gillespie <=
- Re: [PATCH] * etc/NEWS: Announce addition of BOM to utf-8-auto, Eli Zaretskii, 2023/01/29
- Re: [PATCH] * etc/NEWS: Announce addition of BOM to utf-8-auto, Tom Gillespie, 2023/01/29
- Re: [PATCH] * etc/NEWS: Announce addition of BOM to utf-8-auto, Eli Zaretskii, 2023/01/30
- Re: [PATCH] * etc/NEWS: Announce addition of BOM to utf-8-auto, Stefan Monnier, 2023/01/30
- Re: [PATCH] * etc/NEWS: Announce addition of BOM to utf-8-auto, Eli Zaretskii, 2023/01/30