* Re: [9fans] pipefile input method
@ 2000-08-03 5:19 forsyth
0 siblings, 0 replies; 3+ messages in thread
From: forsyth @ 2000-08-03 5:19 UTC (permalink / raw)
To: 9fans
>>scharris@worldnet.att.net:
>>% font=/lib/font/bit/gb/<any from this dir>
>>% rio
>>imageinit: can't open font /lib/font/bit/gb/<...> : bad format for font file
you're giving it a subfont when it expects a font, and need
to see font(6) for reference and existing .font files as a guide.
there are some that refer to gb:
pick one of /lib/font/bit/pelm/*song*.font
for example.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [9fans] pipefile input method
@ 2000-08-03 13:56 Stephen Harris
0 siblings, 0 replies; 3+ messages in thread
From: Stephen Harris @ 2000-08-03 13:56 UTC (permalink / raw)
To: 9fans
forsyth wrote:
>>imageinit: can't open font /lib/font/bit/gb/<...> : bad format for font file
> you're giving it a subfont
Thanks, that would explain the number ranges in the file names
in that directory. Duh.
Everything you do from now on will be more fun - Windows 95 installation
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [9fans] pipefile input method
@ 2000-08-03 3:02 Steve Harris
0 siblings, 0 replies; 3+ messages in thread
From: Steve Harris @ 2000-08-03 3:02 UTC (permalink / raw)
To: 9fans
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2000-08-03 13:56 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-08-03 5:19 [9fans] pipefile input method forsyth
-- strict thread matches above, loose matches on Subject: below --
2000-08-03 13:56 Stephen Harris
2000-08-03 3:02 Steve Harris
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).