From: Van Ly <van.ly@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 62898@debbugs.gnu.org
Subject: bug#62898: 29.0.90; X can’t be input by the current input method [chinese-ctlaub]
Date: Thu, 20 Apr 2023 19:39:26 GMT [thread overview]
Message-ID: <202304201939.33KJdQhO013365@sdf.org> (raw)
In-Reply-To: <83354v6kis.fsf@gnu.org> (message from Eli Zaretskii on Thu, 20 Apr 2023 11:11:07 +0300)
> Date: Thu, 20 Apr 2023 11:11:07 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 62898@debbugs.gnu.org
> Content-type: text/plain; charset=utf-8
>
> The chinese-ctlaub input method is produced from the file
> CTLau-b5.html, and that file doesn't include #x6a59.
>
> I cannot find a newer version of CTLau-b5.html on the Internet, if
> there is a newer version. I also don't know why #x6a59 is missing
> from the file we have: whether it's a mistake, omission, or there's
> some real reason for that.
>
Perhaps at the time when this CTLau-b5.html was composed that was the
extent of what was known or the authors hadn't encountered a use for
it to be included. Those two codepoints are documented at page 185 of
U4E00.pdf . They represent two forms of citrus fruit.
- https://www.unicode.org/charts/index.html
- https://www.unicode.org/charts/PDF/U4E00.pdf
Looking at the below for #x6a58
- https://humanum.arts.cuhk.edu.hk/Lexis/lexi-mf/search.php?word=%E6%A9%98
The left margin section, at the bottom, has a drop down menu and the
CTLau phonology is obtained by selecting the bottom option.
There the phonological reading for #x6a58 is given by gat and gwat.
Looking at the CTLau-b input sequence for \foh
- https://humanum.arts.cuhk.edu.hk/Lexis/lexi-mf/search.php?word=%E7%85%92
the humanum gives the reading wai, is there any memory for some
CTLau-b input sequences having the backslash prefix? The sounding foh
refers to the fire character indexical is my guess which might have
been a mnemonic for the authors of CTLau-b5.html .
> Are there any newer sources for this input method which we could use?
- http://sdf.org/~van.ly/img/x6a58--gat--gwat--add-to-CTLau-b5.jpg
I would like to use the phonological readings gvien at the humanum website.
I've tried to contact them but got no reply. It would be neat if they
update the CTLau-b5.html file.
>
> > chart from Shuowen's tree section
> > - https://humanum.arts.cuhk.edu.hk/Lexis/lexi-mf/shuowenRadical.php?rad=%E6%9C%A8
>
> That page is in Chinese, and I cannot read nor understand it. What
> does it say that is relevant to this issue?
>
That page is a random page in the Shuowen dictionary with two
codepoints for orange and tangerine citrus fruit which I thought would
be in common use enough to be covered by the CTLaub input method. One
of them is not available. I am hoping for an accommodation to allow
updating the CTLaub input method. Perhaps the user can compose a
CTLau-b5-extend.html for use.
> > unexpected result
> > - the current input method won't learn new input key sequence for symbol
> >
> > expected result
> > - the current input method learns new input key sequence for symbol
> >
> > The current input method being chinese-ctlaub learns a new input key
> > sequence for symbol flowing the way a word that does not occur in the
> > wordlist can be added for future personal spell checking.
>
> I don't understand what you are saying here, sorry. What do you mean
> by "current input method learns new input key sequence"? AFAIK, input
> methods don't learn any key sequences, they just support key sequences
> that are part of the IM's definition.
>
I was likening the input method function to spellchecking. The input
method function does not accommodate updates but the spellchecker will
let you add new word spellings.
next prev parent reply other threads:[~2023-04-20 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 12:11 bug#62898: 29.0.90; X can’t be input by the current input method [chinese-ctlaub] Van Ly
2023-04-20 8:11 ` Eli Zaretskii
2023-04-20 19:39 ` Van Ly [this message]
2023-04-22 9:42 ` Eli Zaretskii
2023-04-22 17:10 ` Van Ly
2023-04-25 14:41 ` Eli Zaretskii
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=202304201939.33KJdQhO013365@sdf.org \
--to=van.ly@sdf.org \
--cc=62898@debbugs.gnu.org \
--cc=eliz@gnu.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.