From: Anthony Mandic <og@hotmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] input methods for non-ascii languages
Date: Tue, 29 Jul 2003 15:07:19 +0000 [thread overview]
Message-ID: <3F2686CC.3A108AAC@hotmail.com> (raw)
In-Reply-To: <010c01c355c4$af2cb6c0$b9844051@insultant.net>
"boyd, rounin" wrote:
> japanese is a special case 'cos it has 4 character sets:
>
> - hiragana [phonetic set for japanese words]
> - katakana [phonetic set for foreign words]
These two could be considered to be different cases for the
same syllabic sound. So they'd be something akin to upper and
lower case in European character sets (although I don't know
how they are actually generated on Japanese keyboards, I had
thought it might be by using the shift key). Hence one character
set.
> - kanji [the ideographs]
> - romaji [romanised representation]
>
> i've seen numerous systems and keyboards for doing this
> and other things (the various japanese on 9fans know better
> than i, obviously) and it's pretty nasty.
>
> some keyboards have the kana imposed on a qwerty keyboard
> and you use a 'shift' key to get at them.
>
> for typing the kanji, well the system i like is that you type the
> stem of the pronounciation and you then cycle through a
> set of ideographs until the one you want turns up. i'm
> not sure, but there should be no reason why such a
> system couldn't sort them by frequency, on a personalised
> basis.
I recall seeing a science show on the (Australian) ABC a
few years back where a team from an Australian university
came up with using the numeric keypad and working off
stroke order. Since Chinese characters have specific strokes
and a stroke order, they claimed it was easy to assign the
strokes to the numeric keys and let the computer determine
the character from the stroke order. I don't know what became
of this method - perhaps it just never took off.
> iirc the basic set of kanji is around 800, then there's a jump
> to 2000 and most newspapers use around 6000.
>
> reading them is hard enough, but in writing them you have
> to remember the 'stroke order', not some random set of
> strokes that will get you the character (this goes for the
> kana as well, but they are simple).
Stroke order isn't too hard and easy to learn once you get
the hang of it. Its fairly natural actually. What I found
to be hard was getting the correct pronunciation of the kanji.
Since you had On and Kun etc. it wasn't easy.
-am © 2003
next prev parent reply other threads:[~2003-07-29 15:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 7:42 sasa
2003-07-29 7:56 ` okamoto
2003-07-29 10:44 ` Skip Tavakkolian
2003-07-29 11:29 ` boyd, rounin
2003-07-29 12:20 ` David Presotto
2003-07-30 0:51 ` okamoto
2003-07-30 1:14 ` okamoto
2003-07-30 1:19 ` boyd, rounin
2003-07-30 2:06 ` okamoto
2003-07-30 2:17 ` boyd, rounin
2003-07-30 2:33 ` okamoto
2003-07-30 2:40 ` boyd, rounin
2003-07-30 4:45 ` Skip Tavakkolian
2003-07-30 8:26 ` Anthony Mandic
2003-07-29 15:07 ` Anthony Mandic [this message]
2003-07-29 20:47 ` boyd, rounin
2003-07-30 8:26 ` Anthony Mandic
2003-07-30 11:35 ` boyd, rounin
2003-07-29 12:23 ` David Presotto
2003-07-29 12:06 sasa
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=3F2686CC.3A108AAC@hotmail.com \
--to=og@hotmail.com \
--cc=9fans@cse.psu.edu \
/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).