From: Eli Zaretskii <eliz@gnu.org>
To: "Nickolai Dobrynin" <ndobrynin@gmail.com>
Cc: 75397@debbugs.gnu.org
Subject: bug#75397: 29.4; GNUS message mode lacks Cyrillic support (GNU/Linux)
Date: Wed, 08 Jan 2025 14:47:22 +0200 [thread overview]
Message-ID: <868qrl4gmd.fsf@gnu.org> (raw)
In-Reply-To: <8734hulcf6.fsf@qUsTRXiEQl2mqe0RhRTCBvdMK1NPDFYUhwG8H6ChHv1t8DocVciblLlLbOcY.dobrynin.net> (ndobrynin@gmail.com)
> From: "Nickolai Dobrynin" <ndobrynin@gmail.com>
> Date: Tue, 07 Jan 2025 19:13:49 +0100
>
> 1. Can you suggest a workaround for this?
>
> 2. For clarity's sake, would it be better to change the title of the
> bug report to, e.g., "messages get corrupted after being saved to "drafts" b/c
> message-dont-send doesn't encode them before saving"? This would
> probably summarize the problem much better to the rest of the Emacs team.
No need. The Emacs team, such as it is, took good note of your
report, and will investigate the ways to fix this soon. At that time,
we may have suggestions for workarounds or patches for fixing the
problem. It's just that we didn't have yet time to do so.
For now, the only workaround to try I can suggest is to explicitly
bind the coding-system while saving the draft, like this:
C-x RET c utf-8-emacs RET C-c C-d
If after that "S D e" doesn't restore the original Cyrillic text, try
this instead:
C-x RET c utf-8-emacs RET S D e
P.S. Please don't change the Subject line when you respond to messages
in this thread: it makes it a bit harder to find the previous/next
messages when reading the discussions. I've restored the original
Subject on my response.
prev parent reply other threads:[~2025-01-08 12:47 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
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 ` Eli Zaretskii [this message]
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=868qrl4gmd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=75397@debbugs.gnu.org \
--cc=ndobrynin@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.