From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Van Ly <van.ly@sdf.org>
Cc: Eli Zaretskii <eliz@gnu.org>, 54971@debbugs.gnu.org, larsi@gnus.org
Subject: bug#54971: 28.1; input method chinese-ctlaub unable to enter �p
Date: Tue, 26 Apr 2022 14:35:52 +0800 [thread overview]
Message-ID: <875ymw4aif.fsf@yahoo.com> (raw)
In-Reply-To: <1ad85231-d582-70d7-18a0-9f8c23f9f5e9@SDF.ORG> (Van Ly's message of "Tue, 26 Apr 2022 05:53:29 +0000 (UTC)")
Van Ly <van.ly@sdf.org> writes:
> chinese-ctlaub is unable to enter Chinese character.
chinese-ctlaub is a Cantonese input method, and it isn't fair to expect
it to have every character that chinese-py has (and vice versa.)
> CTLau-b5.html is in need of an update to at least catchup to what
> chinese-py-b5 uses.
chinese-py-b5 is a standard Chinese input method. They input different
dialects of Chinese, which have different characters, pronunciations and
romanizations, so there is no way to update the chinese-ctlau(b) input
methods with the information used by any other Chinese input method.
next prev parent reply other threads:[~2022-04-26 6:35 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
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 [this message]
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=875ymw4aif.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=54971@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--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.