From: Steve Harris <scharris@worldnet.att.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pipefile input method
Date: Wed, 2 Aug 2000 22:02:48 -0500 [thread overview]
Message-ID: <20000802220248.A1902@tiger.home.net> (raw)
On Wed, 02 Aug 2000 16:19:35 rob pike wrote:
> Thus I wrote pipefile, with
> the belief that someone would write the obvious bytestream converter,
> with or without modes, that would convert a standard keyboard into
> some other style of input.
I'm trying!
I'll be finishing a basic Korean input method this weekend probably, and
pipefile
provides exactly what I asked about originally, a "stream filter" over
/dev/cons.
I didn't understand Dennis's reply about "kbd" in v2 and the qualms he
had about
notes handling if one were to just use a filter over cons. But after
seeing rio
running over a "tr" filter with pipefile, I know it will work now. The
code will
also be much simpler with Plan9 than it was with the (luxurious) Qt
toolkit on
Linux where I originally did it.
The only real problem I see is we need a good "go" key, which tells the
IM that the
user is done with the keystrokes so it's time to convert them to an
ideograph. The
IM can't usually tell by itself unless the user hits space bar to start
a new word,
or has entered a full 4 strokes. The problem is that 1) all of the
unshifted
keys are taken by the IM itself, 2) it's too awkward to do
CTRL-<something> or
SHIFT-<something> all the time, and 3) the cons isn't in raw mode (by
choice) so we
can't just use something like CAPS-LOCK. It's not a do or die issue but
it could be
an annoyance.
The other real problem is I need to find a Korean unicode font that
works on Plan 9!
What font format(s) are compatable? I've seen some of the asian font
directories (not
Korean, but sometimes there's overlap), but most of them don't work for
me.
E.g. the fonts in the /lib/font/bit/gb/ directory:
% font=/lib/font/bit/gb/<any from this dir>
% rio
imageinit: can't open font /lib/font/bit/gb/<...> : bad format for font
file
(I did find some Japanese fonts in the pelm directory which worked.)
-Steve
next reply other threads:[~2000-08-03 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-03 3:02 Steve Harris [this message]
2000-08-03 5:19 forsyth
2000-08-03 13:56 Stephen Harris
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=20000802220248.A1902@tiger.home.net \
--to=scharris@worldnet.att.net \
--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).