No. 45/622 Index Prev Next
Relay-Version: version B 2.10.2 9/5/84; site titcca.UUCP
Posting-Version: version B 2.10.2 9/18/84; site titnce.UUCP
Path: titcca!titnca!titnce!kawarada
From: kawarada@titnce.UUCP
Newsgroups: fj.kanji
Subject: Adapting to transient state.(in broken English)
Message-ID: < 268@titnce.UUCP>
Date: 16 Jun 86 08:00:07 GMT
Date-Received: 16 Jun 86 08:03:08 GMT
Reply-To: kawarada@clapton.UUCP (Hiroshi Kawarada 2049)
Distribution: fj
Organization: Tokyo Institute of Tech. Japan
Lines: 63
I think many poster joining in this article may agree with followings.
That is, all poster should use JIS kanji and any other JIS escape code.
ESC $ @ ---> jis(1978)
ESC $ B ---> jis(1983)
ESC ( J ---> jis(romaji)
ESC ( B ---> ascii
It's good to determine standard code for JUNET.And I also agree with foregoing
" standard" .
But can all reader adapt to this " standard" ? No one can dominate JUNET,so we
should try to read the article whitch is out of " standard" .And we try to post
in " standard" code.
It's said that each user have to change escape to accept " standard" code for
JUNET.Can all joiner change that? We hope no joiner left alone by standariza-
tion.
To avoid this problem,I proposed funnel type filter named " kc" .
It's very easy way that most joiner can follow after this standarization.
*
*
*
*
*
*
* " kc"
poster ************************
------> mail or news (in "standard")
(in various ************************
type of *
escape code)*
*
*
*
*
*
*
*
*
*
*
*
" kc" *
reader ************************** news or mail
(in his or her < ------- (in "standard" or
own escape code) ************************** any other escape code)
*
*
*
*
*
*
*
How do you think about this.
P.S. there are bugs in " kc.c" .Corrected version of " kc.c" posted in fj.sources.
Sorry.
Mon. June 16 wada toshikazu (T.I.T nagatsuta)
Next
Continue