9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] input methods for non-ascii languages
Date: Wed, 30 Jul 2003 09:51:54 +0900	[thread overview]
Message-ID: <cb9236de686821b1821589d0c5d9b072@granite.cias.osakafu-u.ac.jp> (raw)
In-Reply-To: <60dd568491e43f8b733ddd04f15cd129@plan9.bell-labs.com>


> Some years back I saw a grammar based editor at Sony.
> It allowed you to type a sentence in romaji and it would display
> a romaji/kanji/kana representation of the sentence at the bottom
> of the screen.  Since it 'understood' the sentence, by the time
> you got to the end of the sentence, it had a pretty high probability
> of having it right.  You could then tab over to any word and cycle
> through hiragana, katakana, romaji and the possible kanji equivs.
> Of course, as you fixed each word, it could be changing all of the
> unfixed part to match.  I'ld hate to think how much code was
> behind it.

I don't believe it got any acceptance from well skilled Japanese writers.
The strategy for translating Kana/Romaji input to Kanji may have
two ways, the first for Japanese beginners, where I don't mean them
as foreigners, and the other for well educated Japanese writers.
For the first writer, automatic translation would be helpful, however,
for the latter, it would be a deeply annoying thing.   I'm using ktrans for
everyday mail writings and fairy longer documents without any problem.
I added many words though.

In the ktrans, I know, we have no proper nouns, such as names of
humans or places etc. though.

Kenji



  reply	other threads:[~2003-07-30  0:51 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 [this message]
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
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=cb9236de686821b1821589d0c5d9b072@granite.cias.osakafu-u.ac.jp \
    --to=okamoto@granite.cias.osakafu-u.ac.jp \
    --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).