unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 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 19:22:06 +0300	[thread overview]
Message-ID: <83wnfpyp5d.fsf@gnu.org> (raw)
In-Reply-To: <87a6clds9c.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat,  16 Apr 2022 16:20:31 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Van Ly <van.ly@sdf.org>,  54971@debbugs.gnu.org
> Date: Sat, 16 Apr 2022 16:20:31 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > What is that \265 octal escape?  You use it in the URL below as well:
> 
> The mail from Van Ly used a very odd charset -- GB2312 -- so perhaps
> rmail had difficulties with it?

I don't think so: the encoding of the buffer was shown correctly, and
the decoding uses the usual Emacs primitives.

> It came across fine in Gnus:
> 
> ----
> The character entered by typing "C-x 8 RET 794a" for 祊 is incapable
> of being entered using the chinese-ctlaub input method.
> 
> At the following website, the Sidney Lau "Cant. Scheme" has
> "Canton. Syllables" for typing in 祊 using
> 
> * bang
> * paang
> 
> => https://humanum.arts.cuhk.edu.hk/Lexis/lexi-mf/search.php?word=祊
> Multi-function Chinese Character Database

OK, but I don't understand what I see on that page.  And anyway, I
think the conclusion is the same: we don't have that character in the
file we use as the source for the chinese-ctlaub input method.





  parent reply	other threads:[~2022-04-16 16:22 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
2022-04-16 16:22     ` Eli Zaretskii [this message]
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

  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=83wnfpyp5d.fsf@gnu.org \
    --to=eliz@gnu.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 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).