all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Van Ly <van.ly@sdf.org>, 54971@debbugs.gnu.org
Subject: bug#54971: 28.1; input method chinese-ctlaub unable to enter �p
Date: Sat, 16 Apr 2022 16:52:02 +0200	[thread overview]
Message-ID: <87tuatxer1.fsf@igel.home> (raw)
In-Reply-To: <87a6clds9c.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 16 Apr 2022 16:20:31 +0200")

On Apr 16 2022, Lars Ingebrigtsen wrote:

> The mail from Van Ly used a very odd charset -- GB2312 -- so perhaps
> rmail had difficulties with it?  It came across fine in Gnus:

That only works if you decode it with GB18030 instead of GB2312.

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





  reply	other threads:[~2022-04-16 14:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-16 13:05 bug#54971: 28.1; input method chinese-ctlaub unable to enter �p Van Ly
2022-04-16 13:47 ` Eli Zaretskii
2022-04-16 14:20   ` Lars Ingebrigtsen
2022-04-16 14:52     ` Andreas Schwab [this message]
2022-04-16 16:22     ` Eli Zaretskii
2022-04-16 18:00       ` Van Ly
2022-04-16 18:28         ` Eli Zaretskii
2022-04-16 19:23           ` Van Ly
2022-04-17  0:45             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-25  8:20               ` Van Ly
2022-04-26  0:39                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-26  5:53                   ` Van Ly
2022-04-26  6:35                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-26 14:31                       ` Van Ly
2022-04-27  0:38                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87tuatxer1.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=54971@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=van.ly@sdf.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.