iso-2022-jp
"Erik M. van der Poel" <erik@poel.juice.or.jp> Wed, 26 August 1992 16:22 UTC
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa04003; 26 Aug 92 12:22 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa03997; 26 Aug 92 12:22 EDT
Received: from dimacs.rutgers.edu by NRI.Reston.VA.US id aa11651; 26 Aug 92 12:23 EDT
Received: by dimacs.rutgers.edu (5.59/SMI4.0/RU1.4/3.08) id AA07909; Wed, 26 Aug 92 11:55:19 EDT
Received: from relay2.UU.NET by dimacs.rutgers.edu (5.59/SMI4.0/RU1.4/3.08) id AA07905; Wed, 26 Aug 92 11:55:17 EDT
Received: from uunet.uu.net (via LOCALHOST.UU.NET) by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA01319; Wed, 26 Aug 92 11:55:19 -0400
Received: from kddlab.UUCP by uunet.uu.net with UUCP/RMAIL (queueing-rmail) id 115400.2907; Wed, 26 Aug 1992 11:54:00 EDT
Received: from kddfuji by kddlab.kddlabs.co.jp (5.61/6.2Junet) id AA17509; Thu, 27 Aug 92 00:37:02 +0900
Received: from ccut.cc.u-tokyo.ac.jp by kddfuji.kddlabs.co.jp (5.65+1.6W/KDD-1.02MX) id AA27629; Thu, 27 Aug 92 00:36:53 JST
Received: by ccut.cc.u-tokyo.ac.jp (5.67+1.6W/6.4J.6-ut3.146) id AA26107; Thu, 27 Aug 92 00:36:48 JST
Received: by juicegw.juice.or.jp (4.0/6.4J.6-juice01) id AA14294; Thu, 27 Aug 92 00:26:31 JST
Received: by green.lime.juice.or.jp (4.1/6.4J.6-juice01) id AA09798; Wed, 26 Aug 92 23:42:35 JST
Received: from localhost by samrat.poel.juice.or.jp (4.0/6.4J.6-juice01) id AA22464; Wed, 26 Aug 92 22:33:36 JST
Return-Path: <erik@samrat.poel.juice.or.jp>
Message-Id: <9208261333.AA22464@samrat.poel.juice.or.jp>
Reply-To: erik@poel.juice.or.jp
From: "Erik M. van der Poel" <erik@poel.juice.or.jp>
To: ietf-822@dimacs.rutgers.edu
Cc: mime@etl.go.jp
Subject: iso-2022-jp
Date: Wed, 26 Aug 1992 22:33:36 +0900
Sender: erik@samrat.poel.juice.or.jp
Ietf-822 folks, Those of you also on the ietf list will know that the iso-2022-jp document has finally been made available, in the Internet Drafts directories. The iso-2022-jp draft describes the Japanese character encoding for email (and netnews) messages. So please review the document (if you are interested :-) and send comments to this list within the next three weeks. The document will be reviewed simultaneously in the newsgroup fj.kanji (in Japanese, of course). After the review period the document will be sent to the RFC editor and IANA to register "ISO-2022-JP" as a MIME charset. Just in case some of you are not on the ietf list, here's the info: ftp host: nnsc.nsf.net (128.89.1.178) login: anonymous password: guest directory: internet-drafts file: draft-ietf-822ext-iso2022jp-00.txt You can also retrieve it by email, by sending a message to mail-server@nisc.sri.com In the body type: SEND internet-drafts/draft-ietf-822ext-iso2022jp-00.txt Best Regards, Erik
- iso-2022-jp Randall Atkinson
- iso-2022-jp Erik M. van der Poel
- Re: iso-2022-jp Olle Jarnefors
- Re: iso-2022-jp Erik M. van der Poel
- Re: iso-2022-jp Erik M. van der Poel
- Re: iso-2022-jp Hitoshi Doi 土井仁志
- Re: iso-2022-jp Keld J|rn Simonsen
- Re: iso-2022-jp Yutaka Sato 佐藤豊
- Re: iso-2022-jp Nathaniel Borenstein
- iso-2022-jp Erik M. van der Poel