From: Lucio De Re <lucio.dere@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Re: ctrans - Chinese language input for Plan9
Date: Thu, 21 Jul 2022 11:45:52 +0200 [thread overview]
Message-ID: <CAJQ9t7jYovowqn79spCHGz=EsefN32jU89F06SAzunDGwQX8MQ@mail.gmail.com> (raw)
In-Reply-To: <86fsivi3q2.fsf@cmarib.ramside>
On 7/21/22, cigar562hfsp952fans@icebubble.org
<cigar562hfsp952fans@icebubble.org> wrote:
> sirjofri <sirjofri+ml-9fans@sirjofri.de> writes:
>
>> I'm pretty sure that pure Chinese computers would look different.
>
> 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.
>
I stumbled onto an instructive video on youtube not that long ago. I'm
sure there are a few you'll be able to search for. If I understand
correctly, it's a combination of entering the phoneme by the nearest
Latin letter, then select from a diminishing range of suitable options
on the screen.
The video was more focused specifically on how this need - which
Chinese, Japanese and Koreans somewhat reacted differently to - caused
the Chinese to make great strides in computing.
Lucio.
> ------------------------------------------
> 9fans: 9fans
> Permalink:
> https://9fans.topicbox.com/groups/9fans/Tba6835d445e07919-Mfd7cc77a83bcefbc998c371e
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
>
--
Lucio De Re
2 Piet Retief St
Kestell (Eastern Free State)
9860 South Africa
Ph.: +27 58 653 1433
Cell: +27 83 251 5824
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tba6835d445e07919-M0df0a84a156b182c700ca96c
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-07-21 9:46 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 [this message]
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
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='CAJQ9t7jYovowqn79spCHGz=EsefN32jU89F06SAzunDGwQX8MQ@mail.gmail.com' \
--to=lucio.dere@gmail.com \
--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).