To: 9fans <firstname.lastname@example.org>
Subject: Re: [9fans] Re: ctrans - Chinese language input for Plan9
Date: Fri, 22 Jul 2022 15:14:21 -0400 [thread overview]
Message-ID: <16585172610.dDC9.email@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1921 bytes --]
On Wednesday, 20 July 2022, at 11:15 PM, cigar562hfsp952fans wrote:
> I've often wondered that. What input methods do Chinese speakers use?
What do Chinese keyboards look like? How do they find/select the
character they want? Are different sets of characters available on
different computers, or are input methods standardized? I wonder.
Most Chinese speakers just use standard "British and American keyboards". There are keycaps engraved with Wubi or Cangjie or Bopomofo (or Zhuyin), but they are all compatible with QWERTY.
On Thursday, 21 July 2022, at 1:58 AM, sirjofri wrote:
> I was more referring to computers built without any american influence at
all, so no ansi, no ascii, no LTR, probably different keycodes...
Cangjie was the first solution to Chinese processing with *personal computers* (at the time of Apple ][ it was sold as extension boards.)
There used to be other encoding methods such as using only numpad (Four-Corner Method), or special keyboards (Ming Kwai typewriter), even an input method for Chinese had been invented in US https://patents.google.com/patent/US2412777A, but they were almost disappeared.
There are a few other considerations regards to adopting Cangjie besides https://9fans.topicbox.com/groups/9fans/Tba6835d445e07919-Mf1934dc65975e0ca3989d488/ctrans-chinese-language-input-for-plan9:
1. Cangjie is copyright free and related IMEs are distributed as free software, while (at least newer version of) Wubi is patented.
2. Personally, I realized the order of strokes has been changed during the last 10 years or so and similarly, the pronunciation of certain characters has also altered over the time.
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2900 bytes --]
next prev parent reply other threads:[~2022-07-22 19:14 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
2022-07-22 19:13 ` Jacob Moody
2022-07-22 19:14 ` andpuke [this message]
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
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).