9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9fans@sirjofri.de>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Re: ctrans - Chinese language input for Plan9
Date: Thu, 21 Jul 2022 06:57:50 +0000 (UTC)	[thread overview]
Message-ID: <4b2a1169-1abb-4e94-8631-39a9263be81a@sirjofri.de> (raw)
In-Reply-To: <86fsivi3q2.fsf@cmarib.ramside>


21.07.2022 04:44:53 cigar562hfsp952fans@icebubble.org:

> 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 was more referring to computers built without any american influence at 
all, so no ansi, no ascii, no LTR, probably different keycodes...


I can't give you an answer as I'm not from an asian culture (although I 
studied it a little) and it's hard to answer anyway since I'm heavily 
influenced by american computers. I'd really need a few years studying 
those cultures heavily to be able to describe a possible tendency.

I can imagine though to look at early russian (and maybe even chinese, if 
there is) space technology. I know that the russian tech was very 
isolated compared to modern technology.

sirjofri

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tba6835d445e07919-M817c5719a75708c69b3cfd05
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2022-07-21  6:58 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 [this message]
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
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=4b2a1169-1abb-4e94-8631-39a9263be81a@sirjofri.de \
    --to=sirjofri+ml-9fans@sirjofri.de \
    --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).