From: "Silvan Jegen" <me@sillymon.ch>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Re: ctrans - Chinese language input for Plan9
Date: Fri, 22 Jul 2022 21:09:05 +0200 [thread overview]
Message-ID: <3TEY11MK62P0P.2KN2XQB6037MX@homearch.localdomain> (raw)
In-Reply-To: <TYYP286MB1955DD09E0F84ABBCBD1B9A4CC909@TYYP286MB1955.JPNP286.PROD.OUTLOOK.COM>
Heyhey!
Sebastian Higgins <bctnry@outlook.com> wrote:
> A few things:
>
> 1. Cangjie is still widely used in places that uses traditional
> Chinese characters. You would still be required to be good at it if
> you apply for text-heavy office jobs in these places.
Ah, I didn't know that! I also don't know anyone who does office work
in a place where traditional Chinese characters are used though ...
> 2. Radical-based/shape-based methods were extremely popular when
> the prediction technology wasn't as good (which means Pinyin was
> significantly slower). It wasn't until late 2000s to early 2010s
> before this situation has changed.
At least in Japan I have never met anyone using a
radical-based/shape-based input method. I have not even met anyone using
direct Kana input, only through romaji. That said, may be an earlier
generation used it more commonly ...
> 3. Pinyin without prediction is slow because of what we called the
> 重码 (lit. "overlap of encoding") problem. For Pinyin the encoding
> overlaps because many characters may have the same Pinyin; the purpose
> of all shape-based method is to reduce the overlap problem and thus
> increase the input speed.
Yeah, it's due to the high homophones count. Only the tones differ and
these are not supported in pinyin input methods (as far as I know ...)
> 4. ctrans uses cangjie because (1) implementing shape-based methods
> was much, much more simpler than phonetic-based methods because most
> (if not all) of the job is table lookup; (2) if we were to use the
> same UI (or lack thereof) as ktrans the overlap-of-encoding problem
> of Pinyin would very probably drive you nuts when using it; (3) it is
> the input method the author uses, however I do admit using Cangjie for
> simplified Chinese input is kinda peculiar.
>
> Source: me who is a native Chinese speaker and have learned Wubi
> (a shape-based method for simplified Chinese) in primary school.
Thanks for the insights. I appreciate it!
Cheers,
Silvan
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tba6835d445e07919-M977f609261cd764b55ad5dbf
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-07-22 19:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 3:20 [9fans] " smj
2022-07-20 3:54 ` Lucio De Re
2022-07-20 6:50 ` sirjofri
2022-07-21 2:44 ` [9fans] " cigar562hfsp952fans
2022-07-21 6:57 ` sirjofri
2022-07-21 9:46 ` adr
2022-07-21 9:45 ` Lucio De Re
2022-07-21 10:20 ` adr
2022-07-22 12:30 ` Silvan Jegen
2022-07-22 14:43 ` adr
2022-07-22 18:06 ` Sebastian Higgins
2022-07-22 19:09 ` Silvan Jegen [this message]
2022-07-22 19:13 ` Jacob Moody
2022-07-22 19:14 ` andpuke
2022-07-22 19:24 ` andpuke
2022-07-22 20:37 ` Silvan Jegen
2022-07-22 22:29 ` LdBeth
2022-07-26 12:29 ` adr
2022-07-29 8:04 ` Silvan Jegen
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=3TEY11MK62P0P.2KN2XQB6037MX@homearch.localdomain \
--to=me@sillymon.ch \
--cc=9fans@9fans.net \
/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.
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 NNTP newsgroup(s).