From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] x
Date: Fri, 31 Jan 2003 11:42:43 +0900 [thread overview]
Message-ID: <ba6ff39e97f98f71cdadd825036c5e0d@granite.cias.osakafu-u.ac.jp> (raw)
>> I'm pretty sure 'most cases' doesn't include for Japanese
>> input...
>
> Is it any easier with the X port?
I don't know, however, it may be possible.
I'm now troubled in pulling-off the serious bugs of our software,
so, I've not read Steve's port though.
However, the reason why I don't use vns is that point, particularly
for web browsing. If the language encoding is not problem,
I agree vns is the better solution.
Kenji
next reply other threads:[~2003-01-31 2:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 2:42 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-31 18:40 Joel Salomon
2003-01-31 1:59 okamoto
2003-01-31 2:27 ` Russ Cox
2003-01-30 17:40 Russ Cox
2003-01-30 17:44 ` andrey mirtchovski
2003-01-30 17:46 ` Russ Cox
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=ba6ff39e97f98f71cdadd825036c5e0d@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).