From: Eli Zaretskii <eliz@gnu.org>
To: Van Ly <van.ly@sdf.org>
Cc: larsi@gnus.org, 54971@debbugs.gnu.org
Subject: bug#54971: 28.1; input method chinese-ctlaub unable to enter �p
Date: Sat, 16 Apr 2022 21:28:54 +0300 [thread overview]
Message-ID: <83mtgkzxuh.fsf@gnu.org> (raw)
In-Reply-To: <e7ac80c9-a244-bd3f-3dc0-ff28e7d6af6a@SDF.ORG> (message from Van Ly on Sat, 16 Apr 2022 18:00:56 +0000 (UTC))
> Date: Sat, 16 Apr 2022 18:00:56 +0000 (UTC)
> From: Van Ly <van.ly@sdf.org>
> cc: Lars Ingebrigtsen <larsi@gnus.org>, 54971@debbugs.gnu.org
>
> >> => 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.
>
> Some fields on the database are presented in English by clicking on
> "ENG" where you find it on the left navigation menu if your web
> browser frame is wide enough.
I did click on "ENG"; nothing happened.
> There is a "Suggestions" link at the bottom of the webpage
>
> => https://humanum.arts.cuhk.edu.hk/Lexis/lexi-mf/feedback.php
> Suggestions
>
> Perhaps the Admin. there is willing to collaborate with the GNU Emacs
> Project and provide the needed file to keep chinese-ctlaub current
> with their wider repertoire of characters.
Feel free to submit feedback to them. Me, I'd be happy to know where
we can find an up-to-date version of the file from which we derived
the CTLau-b5.html file we keep in our repository and from which we
produce that input method. If you know, or can find out, please tell.
next prev parent reply other threads:[~2022-04-16 18:28 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 [this message]
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=83mtgkzxuh.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).