From: dmr@plan9.att.com dmr@plan9.att.com
Subject: Japanese input
Date: Tue, 3 Oct 1995 02:56:51 -0400 [thread overview]
Message-ID: <19951003065651.2sg612cLM4YT9M-dSOo3K0v_2ioOfkpUVCyMV8gYiLE@z> (raw)
Okamoto-san is quite correct to observe that the input
method for Japanese provided by ktrans is very naive;
it was intended only as a demonstration. Certainly it
is less capable than ordinary word-processing software
used in Japan years ago; it just provides for phonetic
romaji input of the kana characters, and a last-"word"
lookup in a hiragana->kanji table.
I found the bug that caused ktrans to get a fault when
trying to look up his name--it's an array overrun.
In /sys/src/cmd/ktrans/translate.c, the v array in
dotrans() is too small. Full fix is in boddle
format in the plan9/update/cmd/ktrans directory
for WWW and ftp access at plan9.att.com.
Dennis
next reply other threads:[~1995-10-03 6:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-10-03 6:56 dmr [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-09-30 11:11 Kenji
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=19951003065651.2sg612cLM4YT9M-dSOo3K0v_2ioOfkpUVCyMV8gYiLE@z \
--to=dmr@plan9.att.com \
/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).