From: Kenji Okamoto okamoto@earth.cias.osakafu-u.ac.jp
Subject: Japanese input
Date: Sat, 30 Sep 1995 07:11:20 -0400 [thread overview]
Message-ID: <19950930111120.oabyVEBIWA_PugRy41YNDdWk_1VuNFB1zsW-xu8TlVI@z> (raw)
======continued from the former post==========
First of all, please don't get angry to read my posting. I have good
impression of Plan 9, particulary, by the reason why it tried to carry
an eastern language in itself from the first.
==========================================
I tried ktrans to test its ability to enter Japanese text for these
several hours. I've gotten an impression that no native Japanese has
been connected to this project.....
This Japanese input method is based on a very simple table searching,
so it's very fast because the size of Hiragana-->Kanji conversion
dictionary is not so huge. Unfortunately, it means it's not so
intelligent for my use. According to my understanding, this kind of
dictionary reference method seems to be there about a decade ago,
and has gone.
If we limit our usage of this input method into a very short letter,
it might be usefull, at least, better than nothing. However, if we
try to write everyday Japanese document, this cannot be my tool, because
it's too much frustrating to correct the wrong conversion....
We have already much powerful many kinds of Kana->Kanji conversion
engine for unix, such as Wnn and Canna servers which are included
in the X11 distribution. Of course, I don't saticefied enough by
those conversion engines, however, those are better.
On the contrary mentioned above, ktrans is much better than nothing.
Therefore, standing as this viewpoint, I have some proposal to
improve the present conversion engine.
1) introduce a "non-transfer" key
This is very important to give a chance not to transform
intentionally. There are many cases where we need to input Hiragana
not Kanji. In the present situation, I have to hit ctl+E, then ctl+G
again. Hmmm.... It can do! .... OK! please forget this.
The other stuffs we need, if we use it for heavy use of Japanese input.
2) introduce a chance to add a word into the dictionary
3) introduce a learning mechanism for individual's different habit of
kanji usage.
Anyway, it's very interesting to see the functionality of this kind
from the first in an operatiog system.
Kenji
next reply other threads:[~1995-09-30 11:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-09-30 11:11 Kenji [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-10-05 4:28 Kenji
1995-10-04 15:39 Reed
1995-10-04 14:50 rob
1995-10-04 4:41 Naoki
1995-10-04 4:02 Kenji
1995-10-04 3:23 philw
1995-10-04 2:42 Kenji
1995-10-03 7:31 Naoki
1995-10-03 6:56 dmr
1995-09-30 7:27 Kenji
1995-09-30 7:03 Kenji
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=19950930111120.oabyVEBIWA_PugRy41YNDdWk_1VuNFB1zsW-xu8TlVI@z \
--to=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).