From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 75397@debbugs.gnu.org, ndobrynin@gmail.com
Subject: bug#75397: 29.4; GNUS message mode lacks Cyrillic support (GNU/Linux)
Date: Wed, 08 Jan 2025 17:30:18 +0200 [thread overview]
Message-ID: <86tta92uid.fsf@gnu.org> (raw)
In-Reply-To: <87ldvo9tct.fsf@linux-m68k.org> (message from Andreas Schwab on Mon, 06 Jan 2025 10:36:34 +0100)
> Cc: 75397@debbugs.gnu.org
> From: Andreas Schwab <schwab@linux-m68k.org>
> Date: Mon, 06 Jan 2025 10:36:34 +0100
>
> On Jan 06 2025, Nickolai Dobrynin wrote:
>
> > 1. Type M-gnus to start GNUS.
> > 2. Start composing a message by pressing 'm'.
> > 3. Enter the first, say, 5 letters of the Cyrillic alphabet, i.e. абвгд.
> > 4. Press C-c C-d to save the draft.
> > 5. Press S D e to resume editing.
> > 6. Bizarrely enough, instead of "абвгд", you will see a sequence of digits "01234".
> >
> > Is this even real?? By the way, this does not occur with ordinary text
> > files. And everything works fine in the view mode inside the draft
> > group. Pressing S D e, on the other hand, makes things go haywire.
>
> The problem is that message-dont-send doesn't encode the message when it
> saves it.
I must be missing something here, because I don't see what you
describe above:
(defun message-dont-send ()
"Don't send the message you have been editing.
Instead, just auto-save the buffer and then bury it."
(interactive nil message-mode)
(set-buffer-modified-p t)
(save-buffer) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
(let ((actions message-postpone-actions))
(message-bury (current-buffer))
(message-do-actions actions)))
So message-dont-send saves the buffer. And that buffer has a
buffer-file-coding-system set in message-set-auto-save-file-name,
which is called when message-mode is turned on (which is supposed to
happen when you press 'm' in Gnus):
(setq buffer-file-coding-system message-draft-coding-system)))
And message-draft-coding-system is:
(defvar message-draft-coding-system mm-auto-save-coding-system
"Coding system to compose mail.")
which in my testing, starting from "emacs -Q", produces utf-8-emacs,
as I'd expect.
In my testing, the draft is saved using utf-8-emacs, and if I them
visit it, I get the Cyrillic text back. As expected.
So where does the above breaks? Is the value of
mm-auto-save-coding-system different? Otherwise, save-buffer should
have encoded the draft's text. What did I miss?
next prev parent reply other threads:[~2025-01-08 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 0:49 bug#75397: 29.4; GNUS message mode lacks Cyrillic support (GNU/Linux) Nickolai Dobrynin
2025-01-06 9:36 ` Andreas Schwab
2025-01-08 15:30 ` Eli Zaretskii [this message]
2025-01-08 16:53 ` Andreas Schwab
2025-01-08 17:12 ` Robert Pluim
2025-01-08 18:42 ` Eli Zaretskii
2025-01-07 18:13 ` bug#75397: Any workarounds for this? Nickolai Dobrynin
2025-01-08 12:47 ` bug#75397: 29.4; GNUS message mode lacks Cyrillic support (GNU/Linux) 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
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=86tta92uid.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=75397@debbugs.gnu.org \
--cc=ndobrynin@gmail.com \
--cc=schwab@linux-m68k.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).