From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 60750@debbugs.gnu.org
Subject: bug#60750: 29.0.60; encode-coding-char fails for utf-8-auto coding system
Date: Thu, 12 Jan 2023 15:28:49 +0100 [thread overview]
Message-ID: <87wn5resim.fsf@gmail.com> (raw)
In-Reply-To: <83bkn3c0iw.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 12 Jan 2023 16:04:07 +0200")
>>>>> On Thu, 12 Jan 2023 16:04:07 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: 60750@debbugs.gnu.org
>> Date: Thu, 12 Jan 2023 14:44:29 +0100
>>
>> One minor nit, the description for ':endian' says:
>>
>> `:endian'
>>
>> VALUE must be `big' or `little' specifying big-endian and
>> little-endian respectively. The default value is `big'.
>>
>> This attribute is meaningful only when `:coding-type' is `utf-16'.
>>
>> That last sentence seems untrue, as ':endian' is meaningful for
>> 'utf-8-auto'
Eli> That depends on what you mean by "meaningful". What it wants to say
Eli> is that it's meaningless to change the value of this property for any
Eli> coding-system other than UTF-16.
OK
Eli> Who does set utf-8-auto? where did you originally bump into this?
Eli> This is an obscure coding-system, and the fix to make it work as
Eli> documented will produce an incompatible change in behavior. So before
Eli> I decide whether to make the change and on what branch, I'd like to
Eli> know how in the world did you encounter this.
>>
>> Itʼs entirely my own fault:
>>
>> The file where I noticed this is shared between a GNU/Linux and a
>> macOS machine, which means I foolishly added the following a year ago,
>> even though itʼs unnecessary (perhaps I was thinking I was going to be
>> sharing it with a Windows machine?):
>>
>> ;; -*- lexical-binding: t; coding: utf-8-auto; -*-
Eli> So you thought the "-auto" part was about the EOL format?
yes. Iʼm having a reading incomprehension day, obviously (just like a
year ago when I made the change originally).
>> I think that means we can leave the code as it is.
Eli> ??? "As it is" means this coding-system behaves contrary to
Eli> documentation: it should produce BOM on encoding. Leaving it as is
Eli> doesn't sound TRT, so I'd like to have this fixed. From your
Eli> description, it sounds like you bumped into this by mistake, and I see
Eli> only one other use of it -- in the test suite. So I'm inclined to
Eli> installing this on the emacs-29 release branch.
Oh, I thought you were proposing *not* to fix it at all, since itʼs
such an obscure coding system. I have no opinion on where a fix should
go: Iʼm not going to be using that coding system again.
Robert
--
next prev parent reply other threads:[~2023-01-12 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 9:08 bug#60750: 29.0.60; encode-coding-char fails for utf-8-auto coding system Robert Pluim
2023-01-12 12:32 ` Eli Zaretskii
2023-01-12 13:44 ` Robert Pluim
2023-01-12 14:04 ` Eli Zaretskii
2023-01-12 14:28 ` Robert Pluim [this message]
2023-01-12 14:39 ` Eli Zaretskii
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=87wn5resim.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=60750@debbugs.gnu.org \
--cc=eliz@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 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.