Thread View: fj.kanji
8 messages
8 total messages
Started by Erik M. van der Poel
Wed, 26 Aug 1992 14:16
JUNET Kanji code document review
Author: Erik M. van der Poel
Date: Wed, 26 Aug 1992 14:16
Date: Wed, 26 Aug 1992 14:16
300 lines
9348 bytes
9348 bytes
JUNET $B$G;H$o$l$F$$$k4A;z%3!<%I$r(J Internet $B$GEPO?$7$h$&$H;W$C$F$$$^$9!#(J
$B$=$NA0$K!"3'$5$s$K%I%-%e%a%s%H$r%A%'%C%/$7$FLc$&$?$a$K!"$3$3$GN.$7$^$9!#(J
$B%l%S%e!<4|4V$O#3=54V$G$9!#(Jfj.kanji $B$X%3%a%s%H$rAw$C$F2<$5$$!#(J
$BGX7J$r@bL@$7$^$9!#(JMIME $B$H$$$&?7$7$$EE;R%a!<%k%U%)!<%^%C%H$,Dj5A$5$l$^(J
$B$7$?!#(JMIME $B$G$O2;@<%G!<%?$H$+!"1Q8l0J30$NJ8;z$r%a!<%k$GAw$k$3$H$,=PMh(J
$B$^$9!#F|K\8l$NIaDL$N%a%C%;!<%8$O<!$N$h$&$J%X%C%@$r$D$1$^$9!'(J
Content-Type: text/plain; charset=iso-2022-jp
$B$@$,!"$=$N$?$a$K(J iso-2022-jp $B$H$$$&(J charset $B$r(J IANA (Internet Assigned
Numbers Authority) $B$GEPO?$9$kI,MW$,$"$j$^$9!#$=$l$,!"0J2<$N%I%-%e%a%s(J
$B%H$NL\E*$G$9!#(J
Network Working Group Jun Murai
Internet Draft Mark Crispin
Erik van der Poel
25th August 1992
Japanese Character Encoding for Internet Messages
Status of this Memo
This document is an Internet Draft. Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas,
and its Working Groups. Note that other groups may also distribute
working documents as Internet Drafts.
Internet Drafts are draft documents valid for a maximum of six
months. Internet Drafts may be updated, replaced, or obsoleted by
other documents at any time. It is not appropriate to use Internet
Drafts as reference material or to cite them other than as a "working
draft" or "work in progress."
Please check the I-D abstract listing contained in each Internet
Draft directory to learn the current status of this or any other
Internet Draft.
This draft document will be submitted to the RFC editor as an
informational document. This document will expire before 2nd March
1993. Distribution of this memo is unlimited. Please send comments
to ietf-822@dimacs.rutgers.edu.
Introduction
This document describes the encoding used in plain text electronic
mail and network news in several Japanese networks. It was first
specified by and used in JUNET [JUNET]. The encoding is now also
widely used in Japanese IP communities.
This document provides a name for the encoding which is intended to
be used in the "charset" parameter field of MIME [MIME] messages.
This document only describes the encoding of plain text. The encoding
of other subtypes of text, such as rich text, is not discussed here.
Murai et al Expires 2nd March 1993 [Page 1]
Internet Draft Updated 25th August 1992
Informal Description
The message body starts in ASCII, and switches to Japanese characters
through an escape sequence. For example, the escape sequence ESC $ B
(three bytes) indicates that the bytes following this escape sequence
are Japanese characters, which are encoded in two bytes each. To
switch back to ASCII, the escape sequence ESC ( B is used.
The following table gives the escape sequences and the character sets
used in JUNET messages.
ESC ( B ASCII
ESC ( J JIS X 0201-1976 (left-hand part)
ESC $ @ JIS X 0208-1978
ESC $ B JIS X 0208-1983
The left-hand part of JIS X 0201-1976 is identical to ASCII except
for backslash (\) and tilde (~). The backslash is replaced by the Yen
sign, and the tilde is replaced by macron (overline). This set is
Japan's national variant of ISO 646.
The JIS X 0208 character sets consist of Kanji, Hiragana, Katakana
and some other symbols and characters. Each character takes up two
bytes.
For further details about the JIS Japanese national character set
standards, refer to the JIS standards themselves. For further
information about the escape sequences, see ISO 2022 [ISO2022].
If there are JIS X 0208 characters on a line, there must be a switch
to ASCII or to the left-hand part of JIS X 0201 before the end of the
line (i.e. before the CRLF). This means that the next line starts in
the character set that was switched to before the end of the previous
line. Other restrictions are given in the Formal Description below.
Formal Description
This section provides a formal description of the JUNET encoding. In
the event that this description is not consistent with the above
informal description, this formal description shall take precedence.
The notational conventions used here are identical to those used in
RFC 822 [RFC822].
The * (asterisk) convention is as follows:
l*m something
Murai et al Expires 2nd March 1993 [Page 2]
Internet Draft Updated 25th August 1992
meaning at least l and at most m somethings, with l and m taking
default values of 0 and infinity, respectively.
line = *text *1( *segment single-byte-seq *text ) CRLF
segment = single-byte-segment / double-byte-segment
single-byte-segment = single-byte-seq 1*text
double-byte-segment = double-byte-seq 1*( one-of-94 one-of-94 )
single-byte-seq = ESC "(" ( "B" / "J" )
double-byte-seq = ESC "$" ( "@" / "B" )
; ( Octal, Decimal.)
ESC = <ISO 2022 ESC, escape> ; ( 33, 27.)
one-of-94 = <any char in 94-char set> ; (41-176, 33.-126.)
CHAR = <any ASCII character> ; ( 0-177, 0.-127.)
text = <any CHAR, including bare
CR & bare LF, but NOT
including CRLF>
Additional restrictions that are difficult to describe in the above
are as follows.
Adjacent segments should have different escape sequences. For
example, the following is not recommended:
ESC $ B .... ESC $ B ....
MIME Considerations
The name given to the JUNET character encoding is "ISO-2022-JP". This
name is intended to be used in MIME messages as follows:
Content-Type: text/plain; charset=iso-2022-jp
The JUNET encoding is already in 7-bit form, so it is not necessary
to use a Content-Transfer-Encoding header. It should be noted that
applying the Base64 or Quoted-Printable encoding will render the
Murai et al Expires 2nd March 1993 [Page 3]
Internet Draft Updated 25th August 1992
message unreadable in current JUNET software.
Background Information
The JUNET encoding was described in the JUNET User's Guide [JUNET]
(JUNET Riyou No Tebiki Dai Ippan).
The encoding is based on the particular usage of ISO 2022 [ISO2022]
announced by 4/1. However, the escape sequence normally used for this
announcement is not included in JUNET messages.
References
[ISO2022] International Organization for Standardization (ISO),
"Information processing -- ISO 7-bit and 8-bit coded character sets
-- Code extension techniques", International Standard, 1986, Ref. No.
ISO 2022-1986 (E)
[JUNET] JUNET Riyou No Tebiki Sakusei Iin Kai (JUNET User's Guide
Drafting Committee), "JUNET Riyou No Tebiki (Dai Ippan)" ("JUNET
User's Guide (First Edition)"), February 1988
[MIME] Nathaniel Borenstein and Ned Freed, "MIME (Multipurpose
Internet Mail Extensions): Mechanisms for Specifying and Describing
the Format of Internet Message Bodies", Proposed (Internet) standard,
June 1992, rfc1341
[RFC822] David H. Crocker, "Standard for the Format of ARPA Internet
Text Messages", Internet standard, August 1982, rfc822
Security Considerations
Security considerations are not discussed in this memo.
Acknowledgements
Many people assisted in drafting this document. The authors wish to
thank in particular Akira Kato, Masahiro Sekiguchi and Ken'ichi
Handa.
Murai et al Expires 2nd March 1993 [Page 4]
Internet Draft Updated 25th August 1992
Authors' Addresses
Jun Murai
Keio University
5322 Endo, Fujisawa
Fujisawa 252 Japan
Fax: +81 (466) 49-1101
EMail: jun@wide.ad.jp
Mark Crispin
Panda Programming
6158 Lariat Loop NE
Bainbridge Island, WA 98110-2098
USA
Phone: +1 (206) 842-2385
EMail: MRC@PANDA.COM
Erik M. van der Poel
A-105 Park Avenue
4-4-10 Ohta, Kisarazu
Chiba 292 Japan
Phone: +81 (438) 22-5836
Fax: +81 (438) 22-5837
EMail: erik@poel.juice.or.jp
Murai et al Expires 2nd March 1993 [Page 5]
$B$G$O!"$h$m$7$/$*4j$$$7$^$9!#(J
$B%(%j%C%/(J
--
Erik M. van der Poel erik@poel.juice.or.jp
Re: JUNET Kanji code document review
Author: Michael Knight
Date: Thu, 27 Aug 1992 00:51
Date: Thu, 27 Aug 1992 00:51
17 lines
1161 bytes
1161 bytes
In article <BtLGys.HFF@poel.juice.or.jp>,
erik@poel.juice.or.jp (Erik M. van der Poel) says:
> ESC $ @ JIS X 0208-1978
> ESC $ B JIS X 0208-1983
$B$R$H$D$@$1!#(B
$B@5<0$K$O(B ESC $ ( B $B$G$O$J$$$+$H;W$$$^$9$,(B ESC $ B $B$K$9$k(B
$BM}M3$O2?$G$9$+!)(B
( $B$b$A$m$s>JN,$,5v$5$l$F$$$k$N$OCN$C$F$$$^$9!#(B )
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Hideo Irie (Michael Knight) michael@sm.sony.co.jp
Work Station Division. SuperMicro Systems Group. Sony Corp.
1-22-1 Higashigotanada, Sinagawa-ku, Tokyo, JAPAN TEL: 03(3448)4015
Re: JUNET Kanji code document review
Author: Shiino Masayoshi
Date: Thu, 27 Aug 1992 15:44
Date: Thu, 27 Aug 1992 15:44
11 lines
906 bytes
906 bytes
In article <BtLGys.HFF@poel.juice.or.jp> erik@poel.juice.or.jp (Erik M. van der Poel) writes: > ESC ( B ASCII > ESC ( J JIS X 0201-1976 (left-hand part) > ESC $ @ JIS X 0208-1978 > ESC $ B JIS X 0208-1983 $@3N$+$K$3$NDL$j$J$s$G$9$,!"<BAu$K1w$$$F$O(J ESC-(-B $@$H(J ESC-(-J$@!"(J ESC-$-@ $@$H(J ESC-$-B$@$r$=$l$>$lF10l;k$9$k!J6hJL$7$J$$!KJ*$,>/(J $@$J$/$J$$$H1>$&<B>p$OJdB-$7$H$$$F$bNI$$$N$G$O$J$$$G$7$g$&$+!#(J -- $@DGLn@585!!!J$7$$$N!!$^$5$h$7!K(J
Re: JUNET Kanji code document review
Author: Takashi Matsuzawa
Date: Fri, 28 Aug 1992 05:03
Date: Fri, 28 Aug 1992 05:03
17 lines
878 bytes
878 bytes
In fj.kanji, erik@poel.juice.or.jp (Erik M. van der Poel) writes: [$BBg$\$1$+$b$7$l$^$;$s$,(J :-)] > Background Information [...] > The encoding is based on the particular usage of ISO 2022 [ISO2022] > announced by 4/1. However, the escape sequence normally used for this 4/1 $B$C$F$J$s$G$9$+!#(J --- Takashi Matsuzawa Japan SDO, APPO, Hewlett-Packard Company Tel: +81 3-3335-8220, Fax: +81 3-3335-6454 E-Mail: mzw_t@yhp.co.jp (Japan), mzw_t@yhp.hp.com (Others)
Re: JUNET Kanji code document review
Author: Kiyo Inaba
Date: Tue, 01 Sep 1992 01:58
Date: Tue, 01 Sep 1992 01:58
16 lines
1293 bytes
1293 bytes
In article <26380001@hpjsdo.kobe.yhp.co.jp> mzw_t@hpjsdo.kobe.yhp.co.jp (Takashi Matsuzawa) writes: >In fj.kanji, erik@poel.juice.or.jp (Erik M. van der Poel) writes: >> The encoding is based on the particular usage of ISO 2022 [ISO2022] >> announced by 4/1. However, the escape sequence normally used for this >4/1 $B$C$F$J$s$G$9$+!#(J $B>e$N(J 4 $B%S%C%H$r(J decimal $B$KJQ49$7$?$b$N$H!"2<$N(J 4 $B%S%C%H$r(J decimal $B$KJQ49$7$?(J $B$b$N$r%9%i%C%7%e$G$D$J$$$@$b$N!#(J4/1 $B$@$H$b$H$N%S%C%HI=8=$G$O(J 01000001$B!"(Jhex $B$J$i(J 0x41 $B$K$J$k!#(J $B$3$NI=5-K!$N@bL@$O(J JIS $B$G$b(J ISO $B$G$b5,3JK\J8$K$O$N$C$F$$$J$$$H;W$C$?$1$I!"2r(J $B@b$K=P$F$/$k!#(Jhex $B$G=q$$$F$*$1$PI,$:$U$?$1$?$@$+$i%9%i%C%7%e$O$$$i$J$$$N$K!"(J $B$J$s$G$3$s$J$d$d$3$7$$$3$H$r$9$k$+$O$7$i$J$$!#(J $B0pMU(J $B@69b(J $B%j%3!<(J $B%=%U%H%&%'%"8&5f=j(J
Re: JUNET Kanji code document review
Author: Takanori ``Racsho'' Nishijima
Date: Tue, 01 Sep 1992 07:26
Date: Tue, 01 Sep 1992 07:26
19 lines
1615 bytes
1615 bytes
$B$K$7$8$^!w%-%d%N%s$G$9!#(B In article <4322@snoopy.src.ricoh.co.jp>, inaba@snoopy.src.ricoh.co.jp (Kiyo Inaba) writes: >>4/1 $B$C$F$J$s$G$9$+!#(B > $B>e$N(B 4 $B%S%C%H$r(B decimal $B$KJQ49$7$?$b$N$H!"2<$N(B 4 $B%S%C%H$r(B decimal $B$KJQ49$7$?(B > $B$b$N$r%9%i%C%7%e$G$D$J$$$@$b$N!#(B4/1 $B$@$H$b$H$N%S%C%HI=8=$G$O(B 01000001$B!"(Bhex > $B$J$i(B 0x41 $B$K$J$k!#(B > $B$3$NI=5-K!$N@bL@$O(B JIS $B$G$b(B ISO $B$G$b5,3JK\J8$K$O$N$C$F$$$J$$$H;W$C$?$1$I!"2r(B > $B@b$K=P$F$/$k!#(Bhex $B$G=q$$$F$*$1$PI,$:$U$?$1$?$@$+$i%9%i%C%7%e$O$$$i$J$$$N$K!"(B > $B$J$s$G$3$s$J$d$d$3$7$$$3$H$r$9$k$+$O$7$i$J$$!#(B $B$o$?$7$K$b??0U$O$o$+$j$^$;$s$1$I!"$H$j$"$($:(B16$B?J$G=q$$$A$c$&$H(B 4/1 $B$J$N$+(B 04/01 $B$J$N$+(B (7$BC10L7O$+(B8$BC10L7O$+(B) $B$O$o$+$j$^$;$s$M!#(B -- $B!H?)FyGd>l$K5mFy$,$"$k$N$OEv$?$jA0(B($B0UL#ITL@(B)$B!I(B $B@>Eg(B $B9'FA(B (NISHIJIMA, Takanori) $B%-%d%N%s3t<02q<R(B $B<~JU5!4oBh0l3+H/%;%s%?!<(B E-mail: racsho@cbs.canon.co.jp
form x/y
Author: Koiti YAMAZAKI
Date: Wed, 02 Sep 1992 00:21
Date: Wed, 02 Sep 1992 00:21
36 lines
2471 bytes
2471 bytes
$@;3:j!w#O#T#S#L$G$9!#(J Subject $@$rJQ$($^$7$?!#(J In article <RACSHO.92Sep1162605@cbsws1.cbs.canon.co.jp> racsho@cbs.canon.co.jp (Takanori ``Racsho'' Nishijima) writes: >>>4/1 $@$C$F$J$s$G$9$+!#(J >> $@>e$N(J 4 $@%S%C%H$r(J decimal $@$KJQ49(J$@$7$?$b$N$H!"2<$N(J 4 $@%S%C%H$r(J decimal $@$KJQ49$7$?(J >> $@$b$N$r%9%i%C%7%e$G$D$J$$$@$b$N!#(J4/1 $@$@$H$b$H$N%S%C%H(J$@I=8=$G$O(J 01000001$@!"(Jhex >> $@$J$i(J 0x41 $@$K$J$k!#(J > >> $@$3$NI=5-K!$N@bL@$O(J JIS $@$G$b(J ISO $@$G$b5,3JK\J8$K$O$N(J$@$C$F$$$J$$$H;W$C$?$1$I!"2r(J >> $@@b$K=P$F$/$k!#(Jhex $@$G=q$$$F$*$1$PI,$:$U$?$1$?$@$+$i%9%i%C%7%e$O$$$i$J$$$N(J$@$K!"(J >> $@$J$s$G$3$s$J$d$d$3$7$$$3$H$r$9$k$+$O$7$i$J$$!#(J > > $@$o$?$7$K$b??0U$O$o$+$j$^$;$s$1$I!"$H$j$"$((J$@$:(J16$@?J$G=q$$$A$c$&$H(J > 4/1 $@$J$N$+(J 04/01 $@$J$N$+(J (7$@C10L7O$+(J8$@C10L7O$+(J) $@$O$o$+$j$^$;$s$M!#(J ISO 646:1991 $@$N(J $@!V(J5.1 Notation$@!W$N:G8e$NCJMn$K(J The notations of the form x/y are the same as those used to identify code table positions, where x is the column number and y the row number (see 5.2). $@$H=q$$$F$"$j(J$@$^$9!#Id9fI=$N0LCV$r;2>H$9$k$N$KJXMx$@$+$i$H$$$&$N$,(J x/y $@$H(J $@$$$&5-K!$r;H$&M}M3$G$7$g$&$+!#$H$j$"$($:G<(J$@F@$7$F$$$^$9!#$A$J$_$K!V(J5.2 Code table$@!W$NBh#2CJMn$O0J2<$N$h$&$K=q$+$l$F$$$^$9!#(J The code table positions are identified by notations of the form x/y, where x is the column number and y is the row number. =========================================================== $@;3:j(J $@9/0l(J (Koiti YAMAZAKI) koiti@otsl.oki.co.jp $@3t<02q<R(J $@2-%F%/%N%7%9%F%`%:%i%\%i%H%j(J $@3+H/Bh#2It(J $@3+H/Bh#12](J Koiti's 'o' should be LATIN SMALL LETTER O WITH CIRCUMFLEX. ===========================================================
Re: JUNET Kanji code document review
Author: Erik M. van der Poel
Date: Thu, 10 Sep 1992 13:26
Date: Thu, 10 Sep 1992 13:26
347 lines
12211 bytes
12211 bytes
$B3'$5$s!"%3%a%s%H$"$j$,$H$&$4$6$$$^$7$?!#(Biso-2022-jp $B$N?7$7$$%I%i%U%H$,(B
$B=PMh$^$7$?$N$G!"%A%'%C%/$7$F2<$5$$!#A0$N%I%i%U%H$H$N0c$$$r$o$+$j$d$9$/(B
$B$9$k$?$a$K%G%#%U%^!<%/$_$?$$$J$b$N$r1&$NJ}$KF~$l$^$7$?!#!V(B!$B!W$OJQ99$G!"(B
$B!V(B+$B!W$ODI2C!"!V(B-$B!W$O:o=|!"$H$$$&0UL#$G$9!#(B
$B%l%S%e!<4|4V$O$b$=54V$K$7$h$&$+$H;W$$$^$9$,!"$$$+$,$G$9$+!)(B
$B%(%j%C%/(B
Network Working Group Jun Murai
Internet Draft Mark Crispin
Erik van der Poel
10th September 1992
Japanese Character Encoding for Internet Messages
Status of this Memo
This document is an Internet Draft. Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas,
and its Working Groups. Note that other groups may also distribute
working documents as Internet Drafts.
Internet Drafts are draft documents valid for a maximum of six
months. Internet Drafts may be updated, replaced, or obsoleted by
other documents at any time. It is not appropriate to use Internet
Drafts as reference material or to cite them other than as a "working
draft" or "work in progress."
Please check the I-D abstract listing contained in each Internet
Draft directory to learn the current status of this or any other
Internet Draft.
This draft document will be submitted to the RFC editor as an
informational document. This document will expire before 10th March
1993. Distribution of this memo is unlimited. Please send comments
to ietf-822@dimacs.rutgers.edu.
Introduction
This document describes the encoding used in the bodies of electronic !
mail and network news messages in several Japanese networks. It was !
first specified by and used in JUNET [JUNET]. The encoding is now
also widely used in Japanese IP communities.
This document provides a name for the encoding which is intended to
be used in the "charset" parameter field of MIME [MIME] messages and !
RFC 1342 [RFC1342] headers. !
This document only describes the encoding of plain text. The encoding
of other subtypes of text, such as rich text, is not discussed here.
Murai et al Expires 10th March 1993 [Page 1]
Internet Draft Updated 10th September 1992
Description !
The message body starts in ASCII, and switches to Japanese characters
through an escape sequence. For example, the escape sequence ESC $ B
(three bytes, hexadecimal values: 1B 24 42) indicates that the bytes !
following this escape sequence are Japanese characters, which are
encoded in two bytes each. To switch back to ASCII, the escape
sequence ESC ( B is used.
The following table gives the escape sequences and the character sets
used in JUNET messages.
ESC ( B ASCII
ESC ( J JIS X 0201-1976 ("Roman" set) !
ESC $ @ JIS X 0208-1978
ESC $ B JIS X 0208-1983
The "Roman" character set of JIS X 0201-1976 is identical to ASCII !
except for backslash (\) and tilde (~). The backslash is replaced by
the Yen sign, and the tilde is replaced by macron (overline). This
set is Japan's national variant of ISO 646.
The JIS X 0208 character sets consist of Kanji, Hiragana, Katakana
and some other symbols and characters. Each character takes up two
bytes.
For further details about the JIS Japanese national character set
standards, refer to the JIS standards themselves. For further
information about the escape sequences, see ISO 2022 [ISO2022].
If there are JIS X 0208 characters on a line, there must be a switch
to ASCII or to the "Roman" set of JIS X 0201 before the end of the !
line (i.e. before the CRLF). This means that the next line starts in
the character set that was switched to before the end of the previous
line. Other restrictions are given in the Formal Syntax below. !
Formal Syntax !
-
The notational conventions used here are identical to those used in
RFC 822 [RFC822].
The * (asterisk) convention is as follows:
l*m something
meaning at least l and at most m somethings, with l and m taking
default values of 0 and infinity, respectively.
Murai et al Expires 10th March 1993 [Page 2]
Internet Draft Updated 10th September 1992
line = *text *1( *segment single-byte-seq *text ) CRLF
segment = single-byte-segment / double-byte-segment
single-byte-segment = single-byte-seq 1*text
double-byte-segment = double-byte-seq 1*( one-of-94 one-of-94 )
single-byte-seq = ESC "(" ( "B" / "J" )
double-byte-seq = ESC "$" ( "@" / "B" )
; ( Octal, Decimal.)
ESC = <ISO 2022 ESC, escape> ; ( 33, 27.)
SI = <ISO 2022 SI, shift-in> ; ( 17, 15.) +
SO = <ISO 2022 SO, shift-out> ; ( 16, 14.) +
one-of-94 = <any char in 94-char set> ; (41-176, 33.-126.)
CHAR = <any ASCII character> ; ( 0-177, 0.-127.)
text = <any CHAR, including bare CR & bare LF, but NOT !
including CRLF, and not including ESC, SI, SO> !
-
MIME and RFC 1342 Considerations !
The name given to the JUNET character encoding is "ISO-2022-JP". This
name is intended to be used in MIME messages as follows:
Content-Type: text/plain; charset=iso-2022-jp
The JUNET encoding is already in 7-bit form, so it is not necessary
to use a Content-Transfer-Encoding header. It should be noted that
applying the Base64 or Quoted-Printable encoding will render the
message unreadable in current JUNET software.
The name ISO-2022-JP may also be used in RFC 1342 headers, though in +
this case, the text should be encoded using either the "B" or "Q" +
encoding, to avoid getting damaged by header-processing software. As +
ISO-2022-JP text often contains many bytes that have a special +
meaning in headers, it is probably easier to use the "B" encoding, +
rather than trying to determine which particular byte values need "Q" +
encoding. +
Murai et al Expires 10th March 1993 [Page 3]
Internet Draft Updated 10th September 1992
Background Information
The JUNET encoding was described in the JUNET User's Guide [JUNET]
(JUNET Riyou No Tebiki Dai Ippan).
The encoding is based on the particular usage of ISO 2022 announced !
by 4/1 (see [ISO2022] for details). However, the escape sequence !
normally used for this announcement is not included in JUNET
messages.
The so-called half-width (hankaku) Katakana, that is, the Kana set of +
JIS X 0201-1976, are not used in JUNET messages. +
In the past, some systems erroneously used the escape sequence ESC ( +
H in JUNET messages. This escape sequence is officially registered +
for a Swedish character set, and should not be used in JUNET +
messages. +
Some systems do not distinguish between ESC ( B and ESC ( J or +
between ESC $ @ and ESC $ B for display. However, when relaying a +
message to another system, the escape sequences must not be altered +
in any way. +
The human user (not implementor) should try to keep lines within 80 +
display columns, or, preferably, within 75 (or so) columns, to allow +
insertion of ">" at the beginning of each line in excerpts. Each JIS +
X 0208 character takes up two columns, and the escape sequences do +
not take up any columns. The implementor is reminded that JIS X 0208 +
characters take up two bytes and should not be split in the middle to +
break lines for displaying, etc. +
The JIS X 0208 standard was revised in 1990, to add two characters at +
the end of the table. Although ISO 2022 specifies special additional +
escape sequences to indicate the use of revised character sets, it is +
suggested here not to make use of this special escape sequence in +
ISO-2022-JP text, even if the two characters added to JIS X 0208 in +
1990 are used. +
References
[ISO2022] International Organization for Standardization (ISO),
"Information processing -- ISO 7-bit and 8-bit coded character sets
-- Code extension techniques", International Standard, 1986, Ref. No.
ISO 2022-1986 (E)
[JUNET] JUNET Riyou No Tebiki Sakusei Iin Kai (JUNET User's Guide
Drafting Committee), "JUNET Riyou No Tebiki (Dai Ippan)" ("JUNET
Murai et al Expires 10th March 1993 [Page 4]
Internet Draft Updated 10th September 1992
User's Guide (First Edition)"), February 1988
[MIME] Nathaniel Borenstein and Ned Freed, "MIME (Multipurpose
Internet Mail Extensions): Mechanisms for Specifying and Describing
the Format of Internet Message Bodies", Proposed (Internet) standard,
June 1992, rfc1341
[RFC822] David H. Crocker, "Standard for the Format of ARPA Internet
Text Messages", Internet standard, August 1982, rfc822
[RFC1342] Keith Moore, "Representation of Non-ASCII Text in Internet +
Message Headers", Proposed (Internet) standard, June 1992, rfc1342 +
Security Considerations
Security considerations are not discussed in this memo.
Acknowledgements
Many people assisted in drafting this document. The authors wish to
thank in particular Akira Kato, Masahiro Sekiguchi and Ken'ichi
Handa.
Authors' Addresses
Jun Murai
Keio University
5322 Endo, Fujisawa
Kanagawa 252 Japan !
Fax: +81 (466) 49-1101
EMail: jun@wide.ad.jp
Mark Crispin
Panda Programming
6158 Lariat Loop NE
Bainbridge Island, WA 98110-2098
USA
Phone: +1 (206) 842-2385
EMail: MRC@PANDA.COM
Murai et al Expires 10th March 1993 [Page 5]
Internet Draft Updated 10th September 1992
Erik M. van der Poel
A-105 Park Avenue
4-4-10 Ohta, Kisarazu
Chiba 292 Japan
Phone: +81 (438) 22-5836
Fax: +81 (438) 22-5837
EMail: erik@poel.juice.or.jp
Murai et al Expires 10th March 1993 [Page 6]
-
--
Erik M. van der Poel erik@poel.juice.or.jp
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads