From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pipefile
Date: Thu, 3 Aug 2000 09:19:52 +0900 [thread overview]
Message-ID: <200008030018.UAA11187@cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
I'm using my version of ktrans to test this, where we can change
language. Yes, this is true. My point is that:
> When I input Japanese like below:
>
> term% 日本語の入力の練習です。<cr>
I wanted to input Japanese text as a false command for rc shell,
and then I expect shell will return with no such command etc. by
hiiting Enter key. However, it's still in raw mode, and I have no
clue to return back to cooked mode, and recognize the meaning
of newline.
Actually, I was also confused this nature of Enter key to newline
conversion, whence my version had a serious bug for conversion
from kana to kanji after hitting Enter key...
Kenji
[-- Attachment #2: Type: message/rfc822, Size: 3148 bytes --]
From: "James A. Robinson" <jim.robinson@stanford.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pipefile
Date: Wed, 02 Aug 2000 08:49:40 -0700
Message-ID: <200008021549.LAA27375@cse.psu.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2.1: Type: text/plain; charset="x-unknown", Size: 664 bytes --]
From: "James A. Robinson" <jim.robinson@stanford.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pipefile
Date: Wed, 02 Aug 2000 08:49:40 -0700
Message-ID: <200008021549.LAA27375@cse.psu.edu>
I think he was thinking of the v2 edition where, with ktrans, you
could hit a ctrl seq and switch into different modes. I assume that
functionality was always part of ktrans itself, in other words after it's
started it is always running and handles whether or not to do translation.
> > When I input Japanese like below:
> >
> > term% 日本語の入力の練習です。<cr>
> >
> >
> > I cannot now return to rc shell.
>
> I don't understand. Do you want just to enter one line of Japanese text?
> The idea was to switch the mode of /dev/cons permanently. I assumed
> your Japanese input methods could provide both ASCII and Japanese text.
next reply other threads:[~2000-08-03 0:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-03 0:19 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-03 23:46 okamoto
2000-08-03 4:49 rob pike
2000-08-03 4:15 okamoto
2000-08-03 3:44 okamoto
2000-08-03 7:14 ` Matt
2000-08-03 3:19 okamoto
2000-08-02 21:19 rob pike
[not found] <rob@plan9.bell-labs.com>
2000-08-02 14:48 ` rob pike
2000-08-02 15:49 ` James A. Robinson
2000-08-02 7:55 okamoto
2000-08-03 8:21 ` Boyd Roberts
2000-07-31 9:47 okamoto
2000-07-31 4:55 rob pike
2000-07-31 4:40 okamoto
2000-07-31 1:14 rob pike
2000-08-02 3:40 ` Skip Tavakkolian
2000-08-03 1:21 ` Skip Tavakkolian
2000-07-30 23:46 Steve Harris
2000-07-30 23:17 rob pike
2000-07-30 23:06 rob pike
2000-07-30 22:38 Steve Harris
2000-07-30 19:54 rob pike
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=200008030018.UAA11187@cse.psu.edu \
--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).