bug#75397: 29.4; GNUS message mode lacks Cyrillic support (GNU/Linux)

bug#75397: 29.4; GNUS message mode lacks Cyrillic support (GNU/Linux)

[Nickolai Dobrynin]

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.

Incidentally, a similar problem, though not as bad, occurs with German
characters (e.g. ä) which get replaced with \number after pressing S D e.

Many thanks.

bug#75397: 29.4; GNUS message mode lacks Cyrillic support (GNU/Linux)

[Andreas Schwab]

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.  gnus-summary-resend-message-edit assumes that the stored
message is encoded and goes through an unibyte buffer while trying to
decode it, which then strips off all non-ascii bits from the characters.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

bug#75397: Any workarounds for this?

[Nickolai Dobrynin]

Hi Andreas,

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.

bug#75397: 29.4; GNUS message mode lacks Cyrillic support (GNU/Linux)

[Eli Zaretskii]

> 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.