Article View: fj.net.mime
Article #33Re: iso-2022-jp or ISO-2022-JP ?
From: Takuya ASADA
Date: Fri, 13 Sep 1996 00:00
Date: Fri, 13 Sep 1996 00:00
12 lines
851 bytes
851 bytes
$BNS$5$s(B> > rfc $B$r$$$/$D$+D/$a$F$_$^$7$?$,!"@5<0$K$OBgJ8;z$G$b>.J8;z$G$bNI$$$b$N$J$N$+!"(B > $BBgJ8;z$G$"$k$Y$-$b$N$J$N$+!"$h$/$o$+$j$^$;$s$G$7$?!#(B $B$I$C$A$G$b%$%$$b$N$G$9!#(BRFC1522 $B$K$O(B Both "encoding" and "charset" names are case-independent. $B$HL@5-$5$l$F$$$^$9!#(B $B$"$5$@(B $B$?$/$d(B
Technical Details
Message-ID:
<51apej$9mj@daikoku.three-a.co.jp>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<CHIFUMI.96Sep13111842@inu.tamacc.chuo-u.ac.jp>Show Full Headers
Complete Article Headers
X-Google-Language: Japanese,JIS X-Google-Thread: 106028,f95db0a4979105e7 X-Google-Attributes: gid106028,public X-Google-Thread: 100bbf,f95db0a4979105e7 X-Google-Attributes: gid100bbf,public From: asada@three-a.co.jp (Takuya ASADA) Subject: Re: iso-2022-jp or ISO-2022-JP ? Date: 1996/09/13 Message-ID: <51apej$9mj@daikoku.three-a.co.jp> X-Deja-AN: 180632877 references: <CHIFUMI.96Sep13111842@inu.tamacc.chuo-u.ac.jp> organization: Gakken THREE-A SYSTEMS Co.Ltd. newsgroups: fj.net.mime,fj.mail