Mercurial > hg > xemacs-beta
diff man/tm/tm-en.texi @ 74:54cc21c15cbb r20-0b32
Import from CVS: tag r20-0b32
| author | cvs |
|---|---|
| date | Mon, 13 Aug 2007 09:04:33 +0200 |
| parents | 131b0175ea99 |
| children | c0c698873ce1 |
line wrap: on
line diff
--- a/man/tm/tm-en.texi Mon Aug 13 09:03:47 2007 +0200 +++ b/man/tm/tm-en.texi Mon Aug 13 09:04:33 2007 +0200 @@ -58,79 +58,30 @@ @menu -* What is MIME?:: -* How is MIME?:: * Glossary:: @end menu -@node What is MIME?, How is MIME?, Introduction, Introduction -@section What is MIME? - -@cindex{MIME}@strong{MIME} stands for @cindex{Multipurpose Internet Mail -Extensions}@strong{Multipurpose Internet Mail Extensions}, it is a -proposed internet standard for including content and headers other than -(ASCII) plain text in messages.@refill - -Current MIME standard consists of RFC 1521 and RFC 1522. RFC 1521 -describes multipurpose content in message bodies, while RFC 1522 -describes multilingual characters in headers. - - -@node How is MIME?, Glossary, What is MIME?, Introduction -@section How is MIME? - -In multipurpose message side, MIME can represent various contents such -as images, sounds, videos, ... as against traditional Internet mail/news -message can represent only (us-ascii (@ref{us-ascii})) plain -text.@refill - -Interestingly, MIME can send ``procedure'', such as ftp (@ref{FTP}), ftp -mail, file extraction, applying patch, ...@refill - -# Of course, it has security problem.@refill - -These various kinds of contents are defined by media types written in -@cindex{Content-Type}@strong{Content-Type} (@ref{Content-Type field}) -field. Namely MIME message has information about content in header. So -if reader defines processes for each content-type (@ref{content-type}), -he/she can display image, or play video or sound, or get file by ftp, or -extract file, ... only read the message.@refill - -In addition, MIME message can represent message includes plural parts, -called @cindex{Multipart}@strong{Multipart} (@ref{multipart}) message. -So it is possible to include picture and sound in one message.@refill - -MIME seems have philosophy of ``declaration''. In other words, MIME is -a message description language to represent various kinds of things uses -us-ascii (@ref{us-ascii}) as its ``alphabet''. Encoded-word defined in -RFC 1522 (@ref{encoded-word}) is same.@refill - -In addition, MUA displays only what it can understand and ignore what -can not understand. So content is saved from non-supported MUA and -MUA is saved from unknown data. - - -@node Glossary, , How is MIME?, Introduction +@node Glossary, , Introduction, Introduction @section Glossary @menu * 7bit:: * 8bit:: -* 94 character set:: 94 $BJ8;z=89g(B -* 96 character set:: 96 $BJ8;z=89g(B -* 94x94 character set:: 94$B!_(B94 $BJ8;z=89g(B +* 94-character set:: +* 96-character set:: +* 94x94-character set:: * ASCII:: * Base64:: * binary:: -* Character Set:: Character Set$B!JJ8;z=89g!K(B +* graphic character set:: Graphic Character Set * cn-gb:: cn-gb, gb2312 * cn-big5:: cn-big5, big5 * CNS:: CNS 11643-1992 -* Coded character set:: Coded character set$B!JId9f2=J8;z=89g!K(B, Character code$B!JJ8;zId9f!K(B -* Code extension:: Code extension$B!JId9f3HD%!K(B +* coded character set:: Coded character set, Character code +* code extension:: Code extension * Content-Disposition:: Content-Disposition field -* content-type:: +* media type:: * Content-Type field:: * Emacs:: * encoded-word:: @@ -191,9 +142,12 @@ * RFC 934:: * RFC 1036:: * RFC 1153:: -* RFC 1521:: RFC 1521 * RFC 1557:: * RFC 1922:: +* RFC 2045:: +* RFC 2046:: +* RFC 2048:: +* RFC 2049:: * plain text:: * Security multipart:: * text/enriched:: @@ -206,93 +160,91 @@ @node 7bit, 8bit, Glossary, Glossary @subsection 7bit -$B$3$3$G$O(B 0 $B$+$i(B 127 $B$N@0?t$r;X$7$^$9!#(B@refill - -0 $B$+$i(B 127 $B$N@0?t$NNs$GI=8=$G$-$k$h$&$J(B data $B$r(B ``7bit $B$N(B data'' $B$H8F$S(B -$B$^$9!#(B@refill - -$B$^$?!"(B0 $B$+$i(B 31 $B$*$h$S(B 127 $B$GI=8=$5$l$k@)8fJ8;z$H(B 32 $B$GI=8=$5$l$k6uGr$H(B -33 $B$+$i(B 126 $B$GI=8=$5$l$k?^7AJ8;z$+$i$J$kJ8;zNs$N$3$H$r(B ``7bit $B$NJ8;zNs(B'' -$B$H8F$S$^$9!J$3$l$O(B ISO 2022 (@ref{ISO 2022}) $B$N!V(B7 $BC10L7O!W$HF1MM$G$9!K!#(B - -$BEAE}E*$J(B Internet $B$N(B MTA (@ref{MTA}) $B$O(B 7bit $B$N(B data $B$rE>Aw$G$-$k$N$G!"(B -7bit $B$N(B data $B$O(B Quoted-Printable (@ref{Quoted-Printable}) $B$d(B Base64 -(@ref{Base64}) $B$H$$$C$?JQ49$r9T$o$J$/$F$b$=$N$^$^E>Aw$G$-$^$9!#(B@refill - -$B$7$+$7!"(B7bit $B$G$"$l$P$I$s$J(B data $B$G$bNI$$$H$O$$$($^$;$s!#$J$<$J$i!"#19T(B -$B$ND9$5$,$"$^$j$KD9$$$H!"(BMTA $B$O$=$N(B message $B$rE>Aw$9$k$3$H$,$G$-$J$$$+$i(B -$B$G$9!#$A$J$_$K!"(BRFC 821 (@ref{RFC 821}) $B$O#19T$O2~9TJ8;z$r=|$$$F(B 998 -byte $B0JFb$G$"$k$3$H$r5a$a$F$$$^$9!#$h$C$F!"$3$l0J>e$N9T$,4^$^$l$k2DG=@-(B -$B$N$"$k(B data, $BNc$($P!"(BPostscript $B$N(B data $B$J$I$O(B Quoted-Printable $BEy$G(B -encode$B$9$kI,MQ$,$"$j$^$9!#(B - - -@node 8bit, 94 character set, 7bit, Glossary +@cindex{7bit}@strong{7bit} means any integer between 0 .. 127.@refill + +Any data represented by 7bit integers is called @cindex{7bit +data}@strong{7bit data}.@refill + +Textual string consisted of Control characters between 0 .. 31 and 127, +and space represented by 32, and graphic characters between 33 .. 236 +are called @cindex{7bit (textual) string}@strong{7bit (textual) +string}.@refill + +Traditional Internet MTA (@ref{MTA}) can translate 7bit data, so it is +no need to translate by Quoted-Printable (@ref{Quoted-Printable}) or +Base64 (@ref{Base64}) for 7bit data.@refill + +However if there are too long lines, it can not translate by 7bit MTA +even if it is 7bit data. RFC 821 (@ref{RFC 821}) and RFC 2045 (@ref{RFC +2045}) require lines in 7bit data must be less than 998 bytes. So if a +``7bit data'' has a line more than 999 bytes, it is regarded as binary +(@ref{binary}). For example, Postscript file should be encoded by +Quoted-Printable. + + +@node 8bit, 94-character set, 7bit, Glossary @subsection 8bit -$B$3$3$G$O(B 0 $B$+$i(B 255 $B$N@0?t$r;X$7$^$9!#(B@refill - -0 $B$+$i(B 255 $B$N@0?t$NNs$GI=8=$G$-$k$h$&$J(B data $B$r(B ``8bit $B$N(B data'' $B$H8F$S(B -$B$^$9!#(B@refill - -$B$^$?!"(B0 $B$+$i(B 31, 127 $B$*$h$S(B 128 $B$+$i(B 159 $B$GI=8=$5$l$k@)8fJ8;z$H(B 32 $B$GI=(B -$B8=$5$l$k6uGr$H(B 33 $B$+$i(B 126 $B$H(B 160 $B$+$i(B 255 $B$GI=8=$5$l$k?^7AJ8;z$+$i$J$k(B -$BJ8;zNs$N$3$H$r(B ``8bit $B$NJ8;zNs(B'' $B$H8F$S$^$9!J$3$l$O(B ISO 2022 (@ref{ISO -2022}) $B$N!V(B8 $BC10L7O!W$HF1MM$G$9!K!#(B@refill - -iso-8859-1 (@ref{iso-8859-1}) $B$d(B euc-kr (@ref{euc-kr}) $B$H$$$C$?Id9f2=J8(B -$B;z=89g$O(B 8bit $B$NJ8;zNs$G$9!#(B@refill - -$BEAE}E*$J(B Internet $B$N(B MTA (@ref{MTA}) $B$O(B 7bit (@ref{7bit}) $B$N(B data $B$7$+E>(B -$BAw$G$-$J$$$N$G!"$=$&$7$?(B MTA $B$r7PM3$9$k>l9g!"(BQuoted-Printable -(@ref{Quoted-Printable}) $B$d(B Base64 (@ref{Base64}) $B$H$$$C$?JQ49$r9T$o$J$/(B -$B$F$O$J$j$^$;$s!#(B@refill - -$B$7$+$7!":G6a$G$O(B 8bit $B$NJ8;zNs$r$=$N$^$^DL$9$3$H$,$G$-$k(B MTA $B$bEP>l$7$F(B -$B$-$?$N$G!"$=$N$^$^Aw$k$3$H$,$G$-$k>l9g$bA}$($F$-$^$7$?!#(B@refill - -$B$7$+$7!"(B8bit $B$G$"$l$P$I$s$J(B data $B$G$bNI$$$H$O$$$($^$;$s!#$J$<$J$i!"#19T(B -$B$ND9$5$,$"$^$j$KD9$$$H!"(BMTA $B$O$=$N(B message $B$rE>Aw$9$k$3$H$,$G$-$J$$$+$i(B -$B$G$9!#$A$J$_$K!"(BRFC 821 $B$O#19T$O2~9TJ8;z$r=|$$$F(B 998 byte $B0JFb$G$"$k$3$H(B -$B$r5a$a$F$$$^$9!#$h$C$F!"$3$l0J>e$N9T$,4^$^$l$k2DG=@-$N$"$k(B data, $BNc$($P!"(B -Postscript $B$N(B data $B$J$I$O(B Quoted-Printable $BEy$G(B encode$B$9$kI,MQ$,$"$j$^$9!#(B -@refill - -$B$^$?!"$3$&$7$?M}M3$+$i!"#19T$,(B 999 byte $B0J>e$N9T$,B8:_$9$k2DG=@-$N$"$k(B -data $B$O(B @cindex{binary}@strong{binary} (@ref{binary}) $B$H8F$V$3$H$K$7$^$9!#(B - -$B$A$J$_$K!"(B7bit $B$GI=8=$G$-$k(B data $B$O(B 8bit $B$G$bI=8=$G$-$^$9!#$h$C$F!"(B -``8bit'' $B$H8@$C$?>l9g!"#19T$,(B 998 byte $B0J2<$NG$0U$N(B data $B$r;X$9$3$H$,(B -$B$"$j$^$9!#(B - - -@node 94 character set, 96 character set, 8bit, Glossary -@subsection 94 $BJ8;z=89g(B - -33 $B$+$i(B 126 $B$NHO0O$N(B 1 byte $B$+$i$J$k(B $BJ8;z=89g(B(@ref{Character set})$B!#(B -ASCII (@ref{ASCII}) $B$d(B JIS X0201-Latin $B$O$=$N0l<o!#(B - - -@node 96 character set, 94x94 character set, 94 character set, Glossary -@subsection 96 $BJ8;z=89g(B - -32 $B$+$i(B 127 $B$NHO0O$N(B 1 byte $B$+$i$J$k(B $BJ8;z=89g(B(@ref{Character set})$B!#(BISO -8859 $B%7%j!<%:$O$=$N0l<o!#(B - - -@node 94x94 character set, ASCII, 96 character set, Glossary -@subsection 94$B!_(B94 $BJ8;z=89g(B - -33 $B$+$i(B 126 $B$NHO0O$N(B 2 byte $B$+$i$J$k(B $BJ8;z=89g(B(@ref{Character set})$B!#(BJIS -X0208 (@ref{JIS X0208}) $B$d(B GB 2312 (@ref{GB 2312}) $B$O$=$N0l<o!#(B - - -@node ASCII, Base64, 94x94 character set, Glossary +@cindex{8bit}@strong{8bit} means any integer between 0 .. 255.@refill + +Any data represented by 8bit integers is called @cindex{8bit +data}@strong{8bit data}.@refill + +Textual string consisted of Control characters between 0 .. 31, 127, and +128 .. 159, and space represented by 32, and graphic characters between +33 .. 236 and 160 .. 255 are called @cindex{8bit (textual) +string}@strong{8bit (textual) string}.@refill + +For example, iso-8859-1 (@ref{iso-8859-1}) or euc-kr (@ref{euc-kr}) are +coded-character-set represented by 8bit textual string.@refill + +Traditional Internet MTA (@ref{MTA}) can translate only 7bit +(@ref{7bit}) data, so if a 8bit data will be translated such MTA, it +must be encoded by Quoted-Printable (@ref{Quoted-Printable}) or Base64 +(@ref{Base64}).@refill + +However 8bit MTA are increasing today.@refill + +However if there are too long lines, it can not translate by 8bit MTA +even if it is 8bit data. RFC 2045 (@ref{RFC 2045}) require lines in +8bit data must be less than 998 bytes. So if a ``8bit data'' has a line +more than 999 bytes, it is regarded as binary (@ref{binary}), so it must +be encoded by Base64 or Quoted-Printable. + + +@node 94-character set, 96-character set, 8bit, Glossary +@subsection 94-character set + +@cindex{94-character set}@strong{94-character set} is a kind of 1 byte +graphic character set (@ref{graphic character set}), each characters are +in positions 02/01 (33) to 07/14 (126) or 10/01 (161) to 15/14 (254). +(ex. ASCII (@ref{ASCII}), JIS X0201-Latin) + + +@node 96-character set, 94x94-character set, 94-character set, Glossary +@subsection 96-character set + +@cindex{96-character set}@strong{96-character set} is a kind of 1 byte +graphic character set (@ref{graphic character set}), each characters are +in positions 02/00 (32) to 07/15 (126) or 10/00 (160) to 15/15 +(255). (ex. ISO 8859) + + +@node 94x94-character set, ASCII, 96-character set, Glossary +@subsection 94x94-character set + +@cindex{94x94-character set}@strong{94x94-character set} is a kind of 2 +byte graphic character set (@ref{graphic character set}), each bytes are +in positions 02/01 (33) to 07/14 (126) or 10/01 (161) to 15/14 (254). +(ex. JIS X0208 (@ref{JIS X0208}), GB 2312 (@ref{GB 2312})) + + +@node ASCII, Base64, 94x94-character set, Glossary @subsection ASCII -$B%"%a%j%+O"K.$G;H$o$l$kJ8;z$rId9f2=$7$?(B 94 $BJ8;z=89g(B(@ref{94 character -set})$B!#(BA-Z, a-z $B$N(B Latin $BJ8;z$H?t;z!"4v$D$+$N5-9f$+$i$J$k!#(BISO 646 -(@ref{ISO 646}) $B$N0l$D!#(B +$B%"%a%j%+O"K.$G;H$o$l$kJ8;z$rId9f2=$7$?(B 94-character set +(@ref{94-character set}). A-Z, a-z $B$N(B Latin $BJ8;z$H?t;z!"4v$D$+$N5-9f$+(B +$B$i$J$k!#(BISO 646 (@ref{ISO 646}) $B$N0l$D!#(B @cindex{ASCII}@cindex{ANSI X3.4:1986} @noindent @@ -307,19 +259,20 @@ @node Base64, binary, ASCII, Glossary @subsection Base64 -RFC 1521 (@ref{RFC 1521}) $B$GDj5A$5$l$F$$$k(B MIME (@ref{MIME}) $B$K$*$1$k(B -binary data (@ref{binary}) $B$N(B network $B$G$NJQ49K!$N#1$D!#(B@refill - -$B!X(B64 $B?J?t!Y$H$$$&0UL#$G!"(B3 byte $B$N(B data $B$r(B 0 $B$+$i(B 63 $B$N?t$rI=$9(B ASCII -(@ref{ASCII}) 4 $BJ8;z$KJQ49$9$kJ}K!!#!J$b$7!"(B4 $BJ8;z$K$J$i$J$1$l$P(B -@cindex{pad}@strong{pad} $B$H8F$P$l$k5M$aJ*$r$7$FD9$5$rD4@0$9$k!K(B@refill - -$B$3$N(B 65 $B<oN`$NJ8;z$O(B ASCII $B$H(B EBCDIC $B$N6&DLItJ,$+$iA*$P$l$F$*$j!"(B -Internet $B0J30$N(B network $B$r7PM3$9$k>l9g$G$b0BA4$KE>Aw$G$-$k$h$&$K@_7W$5(B -$B$l$F$$$k!#(B - - -@node binary, Character Set, Base64, Glossary +@cindex{Base64}@strong{Base64} is a transfer encoding method of MIME +(@ref{MIME}) defined in RFC 2045 (@ref{RFC 2045}).@refill + +The encoding process represents 24-bit groups of input bits as output +strings of 4 encoded characters. Encoded characters represent integer 0 +.. 63 or @cindex{pad}@strong{pad}. Base64 data must be 4 * n bytes, so +pad is used to adjust size.@refill + +These 65 characters are subset of all versions of ISO 646, including +US-ASCII, and all versions of EBCDIC. So it is safe even if it is +translated by non-Internet gateways. + + +@node binary, graphic character set, Base64, Glossary @subsection binary $BG$0U$N(B byte $BNs$r(B @cindex{binary}@strong{binary} $B$H8F$V$3$H$K$7$^$9!#(B @@ -335,15 +288,13 @@ $BG$0U$N(B data $B$r;X$9$3$H$,$"$j$^$9!#(B -@node Character Set, cn-gb, binary, Glossary -@subsection Character Set$B!JJ8;z=89g!K(B - -$BId9f2=J8;z=89g(B(@ref{Coded character set})$B!#C"$7!"$3$3$G$O(B $BId9f3HD%(B -(@ref{Code extension}) $B$5$l$F$J$$J8;z=89g$H$$$&%K%e%"%s%9$r9~(B -$B$a$F$$$k!#(B - - -@node cn-gb, cn-big5, Character Set, Glossary +@node graphic character set, cn-gb, binary, Glossary +@subsection Graphic Character Set + +Coded character set (@ref{Coded character set}) for graphic characters. + + +@node cn-gb, cn-big5, graphic character set, Glossary @subsection cn-gb, gb2312 $BCf9qBgN&$G$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B MIME @@ -362,8 +313,8 @@ $BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B MIME charset (@ref{MIME charset}) $B$N#1$D!#(B@refill -ISO 2022 (@ref{ISO 2022}) $B$K4p$+$J$$(B 8bit (@ref{8bit}) $B$NId9f2=J8;z=89g(B -(@ref{Coded character set})$B$G(B de-fact standard $B$G$"$k!#(BRFC 1922 +ISO 2022 (@ref{ISO 2022}) $B$K4p$+$J$$(B 8bit (@ref{8bit}) $B$N(Bcoded character +set (@ref{coded character set})$B$G(B de-fact standard $B$G$"$k!#(BRFC 1922 (@ref{RFC 1922}) $B$GDj5A$5$l$F$$$k!#(B@refill cf. @cindex{BIG5} @@ -377,7 +328,7 @@ CNS 11643-1986 (@ref{CNS}) $B$HBP1~4X78$,$"$k!#(B -@node CNS, Coded character set, cn-big5, Glossary +@node CNS, coded character set, cn-big5, Glossary @subsection CNS 11643-1992 $BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B @@ -398,20 +349,22 @@ -@node Coded character set, Code extension, CNS, Glossary -@subsection Coded character set$B!JId9f2=J8;z=89g!K(B, Character code$B!JJ8;zId9f!K(B - -$BJ8;z$H(B byte $BNs$H#1BP#1$KBP1~IU$1$k[#Kf$G$J$$5,B'$N=89g!#(B - - -@node Code extension, Content-Disposition, Coded character set, Glossary -@subsection Code extension$B!JId9f3HD%!K(B - -$BM?$($i$l$?J8;z=89g(B(@ref{Character set})$B$K4^$^$l$F$$$J$$J8;z$NId9f2=$N$?(B -$B$a$KMQ$$$k<jK!!#(BISO 2022 (@ref{ISO 2022}) $B$O$=$N#1$D!#(B - - -@node Content-Disposition, content-type, Code extension, Glossary +@node coded character set, code extension, CNS, Glossary +@subsection Coded character set, Character code + +A set of unambiguous rules that establishes a character set and the +one-to-one relationship between the characters of the set and their +bit combinations. + + +@node code extension, Content-Disposition, coded character set, Glossary +@subsection Code extension + +The techniques for the encoding of characters that are not included in +the character set of a given code. (ex. ISO 2022 (@ref{ISO 2022})) + + +@node Content-Disposition, media type, code extension, Glossary @subsection Content-Disposition field Content $B$NI=<($N;EJ}$d(B file $BL>$rI=8=$9$k$?$a$N(B field. MIME (@ref{MIME}) @@ -428,60 +381,63 @@ -@node content-type, Content-Type field, Content-Disposition, Glossary -@subsection content-type - -MIME (@ref{MIME}) $B$K$*$1$k(B part (@ref{part}) $B$N<oN`!#(B -@cindex{type}@strong{type} $B$H(B @cindex{subtype}@strong{subtype} $B$+$i$J$k!#(B -RFC 1521 (@ref{RFC 1521}) $B$GDj5A$5$l$F$$$k!#(B@refill - -type $B$OI8=`$G$O(B @cindex{application}@strong{application}, -@cindex{audio}@strong{audio}, @cindex{image}@strong{image}, -@cindex{message}@strong{message}, @cindex{multipart}@strong{multipart} -(@ref{multipart}), @cindex{text}@strong{text}, -@cindex{video}@strong{video} $B$,Dj5A$5$l!"$=$l$>$l$K$O(B -application/octet-stream, audio/basic, image/jpeg, multipart/mixed -(@ref{multipart/mixed}), text/plain (@ref{text/plain}), video/mpeg $B$J$I(B -$B$N$5$^$6$^$J(B subtype $B$,Dj5A$5$l$F$$$k!#(B - -@noindent -@strong{[$BCm0U(B]} -@quotation - -$B$3$3$G$O!"(Btext/plain $B$J$I$N(B type/subtype $B$NAH$r$7$P$7$P(B -@cindex{content-type/subtype}@strong{content-type/subtype} $B$H=q$/!#(B -@end quotation - - -content-type $B$O!"(BRFC 1521 $B$GDj5A$5$l$F$$$k$b$N$K2C$($F!"EPO?$9$k$3$H$b$G(B -$B$-$k!#8=:_!"EPO?$5$l$F$$$k$b$N$O(B MEDIA TYPES -(ftp://ftp.isi.edu/in-notes/iana/assignments/media-types) $B$G;2>H$G$-$k!#(B - -$B$^$?!"(Btype $B$b$7$/$O(B subtype $B$K!"A0$K(B `x-' $B$rIU$1$?(B -@cindex{x-token}@strong{x-token} $B$rMQ$$$k$3$H$K$h$j!"EPO?$5$l$F$$$J$$$b(B -$B$N$r;dE*$KMQ$$$k$3$H$b$G$-$k!#$7$+$7!"EvA3$N$3$H$J$,$i!"$3$&$7$?;dE*$J(B -content-type $B$ONJ2r$rF@$?<T$N4V$G$7$+2r<a$G$-$J$$$N$GMxMQ$K$OCm0U$9$k$3(B -$B$H!#(B@refill +@node media type, Content-Type field, Content-Disposition, Glossary +@subsection media type + +@cindex{media type}@strong{media type} specifies the nature of the data +in the body of MIME (@ref{MIME}) entity (@ref{entity}). It consists of +@cindex{type}@strong{type} and @cindex{subtype}@strong{subtype}. It is +defined in RFC 2046 (@ref{RFC 2046}).@refill + +Currently there are following types: + +@itemize @bullet +@item +@cindex{text}@strong{text} +@item +@cindex{image}@strong{image} +@item +@cindex{audio}@strong{audio} +@item +@cindex{video}@strong{video} +@item +@cindex{application}@strong{application} +@item +@cindex{multipart}@strong{multipart} (@ref{multipart}) +@item +@cindex{message}@strong{message} +@end itemize + + +And there are various subtypes, for example, application/octet-stream, +audio/basic, image/jpeg, multipart/mixed (@ref{multipart/mixed}), +text/plain (@ref{text/plain}), video/mpeg...@refill + +You can refer registered media types at MEDIA TYPES +(ftp://ftp.isi.edu/in-notes/iana/assignments/media-types).@refill + +In addition, you can use private type or subtype using +@cindex{x-token}@strong{x-token}, which as the prefix `x-'. However you +can not use them in public.@refill (cf. @ref{Content-Type field}) -@node Content-Type field, Emacs, content-type, Glossary +@node Content-Type field, Emacs, media type, Glossary @subsection Content-Type field -Header field to represent information about part, such as content-type -(@ref{content-type}), MIME charset (@ref{MIME charset}). It is defined -in RFC 1521 (@ref{RFC 1521}). +Header field to represent information about body, such as media type +(@ref{media type}), MIME charset (@ref{MIME charset}). It is defined in +RFC 2045 (@ref{RFC 2045}). @noindent @strong{[Memo]} @quotation Historically, Content-Type field was proposed in RFC 1049. In it, -Content-Type did not distinguish type and subtype. However RFC 1521 -parser may be able to accept RFC 1049 based Content-Type as unknown -type. +Content-Type did not distinguish type and subtype. However MIME parser +may be able to accept RFC 1049 based Content-Type as unknown type. @end quotation @@ -548,15 +504,15 @@ @subsection encoded-word Representation non ASCII (@ref{ASCII}) characters in header. It is -defined in @cindex{RFC 1522}@strong{RFC 1522}.@refill - -@cindex{Standards Track}@cindex{RFC 1522} +defined in @cindex{RFC 2047}@strong{RFC 2047}.@refill + +@cindex{Standards Track}@cindex{RFC 2047} @noindent -[RFC 1522] +[RFC 2047] @quotation -K. Moore, ``MIME (Multipurpose Internet Mail Extensions) Part Two: -Message Header Extensions for Non-ASCII Text'', September 1993, -Standards Track. +K. Moore, ``MIME (Multipurpose Internet Mail Extensions) Part Three: +Message Header Extensions for Non-ASCII Text'', November 1996, Standards +Track (obsolete RFC 1521,1522,1590). @end quotation @@ -612,9 +568,9 @@ @node GB 2312, GB 8565.2, FTP, Glossary @subsection GB 2312-1980 -$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=$9$?$a$N(B 94$B!_(B94 $BJ8;z(B -$B=89g(B(@ref{94x94 character set})$B!#Cf9q$N9q2HI8=`!#(BISO 2022 (@ref{ISO -2022}) $B$G$N=*C<J8;z$O(B `A'.@refill +$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=$9$?$a$N(B +94x94-character set (@ref{94x94-character set})$B!#Cf9q$N9q2HI8=`!#(BISO +2022 (@ref{ISO 2022}) $B$G$N=*C<J8;z$O(B `A'.@refill $B$3$l$O(B GB $B$K$*$1$k4pK\=8$G$"$k!#(B @@ -760,10 +716,10 @@ @node iso-2022-jp-2, iso-2022-kr, iso-2022-jp, Glossary @subsection iso-2022-jp-2 -iso-2022-jp (@ref{iso-2022-jp}) $B$r3HD%$7$?(B MIME charset (@ref{MIME -charset}) $B$N0l$D!#(B@refill - -RFC 1554 $B$GDj5A$5$l$F$$$k!#(B +A MIME charset (@ref{MIME charset}), which is a multilingual extension +of iso-2022-jp (@ref{iso-2022-jp}).@refill + +It is defined in RFC 1554. @cindex{iso-2022-jp-2}@cindex{Informational}@cindex{RFC 1554} @noindent @@ -778,13 +734,14 @@ @node iso-2022-kr, ISO 646, iso-2022-jp-2, Glossary @subsection iso-2022-kr -$B4Z9q8l$rI=8=$9$k$?$a$N(B MIME charset (@ref{MIME charset}) $B$N#1$D!#(B - -ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F(B ASCII (@ref{ASCII}) $B$K(B KS C5601 -(@ref{KS C5601}) $B$r(B 7bit (@ref{7bit}) $B$GId9f3HD%(B (@ref{Code extension}) -$B$7$F$$$k!#(B@refill - -RFC 1557 (@ref{RFC 1557}) $B$GDj5A$5$l$F$$$k!#(B +A MIME charset (@ref{MIME charset}) for Korean language (Hangul +script).@refill + +It is based on ISO 2022 (@ref{ISO 2022}) code extension (@ref{code +extension}) technique to extends ASCII (@ref{ASCII}) to use KS C5601 +(@ref{KS C5601}) as 7bit (@ref{7bit}) text.@refill + +It is defined in RFC 1557 (@ref{RFC 1557}). @node ISO 646, ISO 8859-1, iso-2022-kr, Glossary @@ -809,9 +766,6 @@ @node ISO 8859-1, iso-8859-1, ISO 646, Glossary @subsection ISO 8859-1 -$B@>2$=t8l$GMQ$$$i$l$k3HD%(B Latin $BJ8;z$d5-9f$+$i$J$k(B 96 $BJ8;z=89g(B(@ref{96 -character set})$B!#(B - @cindex{ISO 8859-1}@cindex{ISO 8859-1:1987} @noindent [ISO 8859-1] @@ -826,21 +780,19 @@ @node iso-8859-1, ISO 8859-2, ISO 8859-1, Glossary @subsection iso-8859-1 -$B@>2$=t8l$J$I$rI=8=$9$k$?$a$N(B MIME charset (@ref{MIME charset}) $B$N#1$D!#(B +@cindex{iso-8859-1}@strong{iso-8859-1} is a MIME charset (@ref{MIME +charset}) for west-European languages written by Latin script.@refill ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F!"(BASCII (@ref{ASCII}) $B$K(B ISO 8859-1 (@ref{ISO 8859-1}) $B$r(B 8bit (@ref{8bit}) $B$GId9f3HD%(B (@ref{Code extension})$B$7$F$$$k!#(B@refill -RFC 1521 (@ref{RFC 1521}) $B$GDj5A$5$l$F$$$k!#(B +It is defined in RFC 2046 (@ref{RFC 2046}). @node ISO 8859-2, iso-8859-2, iso-8859-1, Glossary @subsection ISO 8859-2 -$BEl2$=t8l$GMQ$$$i$l$k3HD%(B Latin $BJ8;z$d5-9f$+$i$J$k(B 96 $BJ8;z=89g(B(@ref{96 -character set})$B!#(B - @cindex{ISO 8859-2}@cindex{ISO 8859-2:1987} @noindent [ISO 8859-2] @@ -855,13 +807,14 @@ @node iso-8859-2, ISO 8859-3, ISO 8859-2, Glossary @subsection iso-8859-2 -$BEl2$=t8l$rI=8=$9$k$?$a$N(B MIME charset (@ref{MIME charset}) $B$N#1$D!#(B +@cindex{iso-8859-2}@strong{iso-8859-2} is a MIME charset (@ref{MIME +charset}) for east-European languages written by Latin script.@refill ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F!"(BASCII (@ref{ASCII}) $B$K(B ISO 8859-2 (@ref{ISO 8859-2}) $B$r(B 8bit (@ref{8bit}) $B$GId9f3HD%(B (@ref{Code extension})$B$7$F$$$k!#(B@refill -RFC 1521 (@ref{RFC 1521}) $B$GDj5A$5$l$F$$$k!#(B +It is defined in RFC 2046 (@ref{RFC 2046}). @node ISO 8859-3, ISO 8859-4, iso-8859-2, Glossary @@ -895,8 +848,6 @@ @node ISO 8859-5, iso-8859-5, ISO 8859-4, Glossary @subsection ISO 8859-5 -$B%-%j%kJ8;z$d5-9f$+$i$J$k(B 96 $BJ8;z=89g(B(@ref{96 character set})$B!#(B - @cindex{ISO 8859-5}@cindex{ISO 8859-5:1988} @noindent [ISO 8859-5] @@ -911,13 +862,14 @@ @node iso-8859-5, ISO 8859-6, ISO 8859-5, Glossary @subsection iso-8859-5 -$B%-%j%kJ8;z$rI=8=$9$k$?$a$N(B MIME charset (@ref{MIME charset}) $B$N#1$D!#(B +@cindex{iso-8859-5}@strong{iso-8859-5} is a MIME charset (@ref{MIME +charset}) for Cyrillic script.@refill ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F!"(BASCII (@ref{ASCII}) $B$K(B ISO 8859-5 (@ref{ISO 8859-5}) $B$r(B 8bit (@ref{8bit}) $B$GId9f3HD%(B (@ref{Code extension})$B$7$F$$$k!#(B@refill -RFC 1521 (@ref{RFC 1521}) $B$GDj5A$5$l$F$$$k!#(B +It is defined in RFC 2046 (@ref{RFC 2046}). @node ISO 8859-6, ISO 8859-7, iso-8859-5, Glossary @@ -937,8 +889,6 @@ @node ISO 8859-7, iso-8859-7, ISO 8859-6, Glossary @subsection ISO 8859-7 -$B%.%j%7%"J8;z$d5-9f$+$i$J$k(B 96 $BJ8;z=89g(B(@ref{96 character set})$B!#(B - @cindex{ISO 8859-7}@cindex{ISO 8859-7:1987} @noindent [ISO 8859-7] @@ -953,13 +903,14 @@ @node iso-8859-7, ISO 8859-8, ISO 8859-7, Glossary @subsection iso-8859-7 -$B%.%j%7%"8l$rI=8=$9$k$?$a$N(B MIME charset (@ref{MIME charset}) $B$N#1$D!#(B +@cindex{iso-8859-7}@strong{iso-8859-7} is a MIME charset (@ref{MIME +charset}) for Greek script.@refill ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F!"(BASCII (@ref{ASCII}) $B$K(B ISO 8859-7 (@ref{ISO 8859-7}) $B$r(B 8bit (@ref{8bit}) $B$GId9f3HD%(B (@ref{Code extension})$B$7$F$$$k!#(B@refill -RFC 1947 $B$GDj5A$5$l$F$$$k!#(B +It is defined in RFC 1947. @cindex{iso-8859-7}@cindex{Informational}@cindex{RFC 1947} @noindent @@ -1003,7 +954,7 @@ @subsection ISO-IR-165, CCITT Extended GB CCITT $B$,EPO?$7$?!"Cf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=(B -$B$9$k$?$a$N(B 94$B!_(B94 $BJ8;z=89g(B(@ref{94x94 character set})$B!#(B@refill +$B$9$k$?$a$N(B 94x94-character set (@ref{94x94-character set})$B!#(B@refill GB 2312 (@ref{GB 2312}) $B$H(B GB 8565 $BI=#2(B (@ref{GB 8865.2}) $B$K(B 150 $BJ8;z$[(B $B$I$rDI2C$7$?$b$N$i$7$$!#(B@refill @@ -1036,7 +987,7 @@ @noindent [JIS X0201-1996?] @quotation -$BF|K\5,3J6(2q(B (Japanese Standards Association),$B!X#70C%H5Z$S#80C%H$N>p(B +$BF|K\5,3J6(2q(B (Japanese Standards Association),$B!X#7%S%C%H5Z$S#8%S%C%H$N>p(B $BJs8r49MQId9f2=J8;z=89g!Y(B, ``7-bit and 8-bit coded character sets for information interchange'', JIS X 0201:1996? draft. @end quotation @@ -1046,8 +997,8 @@ @node JIS C6226, JIS X0208, JIS X0201, Glossary @subsection JIS C6226-1978 -$BF|K\8l$rI=$9$?$a$K:n$i$l$?(B 94$B!_(B94 $BJ8;z=89g(B(@ref{94x94 character set})$B!#(B -$BF|K\$N9q2HI8=`!#(BJIS X0208-1978 $B$H$b$$$&!#(B@refill +$BF|K\8l$rI=$9$?$a$K:n$i$l$?(B 94x94-character set (@ref{94x94-character +set})$B!#F|K\$N9q2HI8=`!#(BJIS X0208-1978 $B$H$b$$$&!#(B@refill (cf. @ref{JIS X0208}) @@ -1056,9 +1007,9 @@ @node JIS X0208, JIS X0212, JIS C6226, Glossary @subsection JIS X0208 -$BF|K\8l$rI=$9$?$a$K:n$i$l$?(B 94$B!_(B94 $BJ8;z=89g(B(@ref{94x94 character set})$B!#(B -$BF|K\$N9q2HI8=`!#(B1978 $BG/HG!"(B1983 $BG/HG!"(B1990 $BG/HG$,$"$k$,!"(BInternet $B$G$O(B -1983 $BG/HG$,$b$C$H$bNI$/;H$o$l$F$$$k!#(B@refill +$BF|K\8l$rI=$9$?$a$K:n$i$l$?(B 94x94-character set (@ref{94x94-character +set})$B!#F|K\$N9q2HI8=`!#(B1978 $BG/HG!"(B1983 $BG/HG!"(B1990 $BG/HG$,$"$k$,!"(BInternet +$B$G$O(B 1983 $BG/HG$,$b$C$H$bNI$/;H$o$l$F$$$k!#(B@refill JIS X0208 $B$O5-9f!"?t;z!"%m!<%^;z!"$R$i$,$J!"%+%?%+%J!"%.%j%7%cJ8;z!"%-%j(B $B%kJ8;z!"7S@~AG!"Bh#1?e=`!"Bh#2?e=`$N4A;z$,4^$^$l$k!#C"$7!"(B1983 $BG/HG$N0l(B @@ -1095,8 +1046,8 @@ @noindent [JIS X0208-1996?] @quotation -$BF|K\5,3J6(2q(B (Japanese Standards Association),$B!X#70C%H5Z$S#80C%H$N(B -$B#2/set/ipe/ps6/WorkSpaces/xemacs-20.0-working/editor/man/tm/SCCS/s.tm-en.texi$%H>pJs8r49MQId9f2=4A;z=89g!Y(B, ``7-bit and 8-bit double byte coded +$BF|K\5,3J6(2q(B (Japanese Standards Association),$B!X#7%S%C%H5Z$S#8%S%C%H$N(B +$B#2%P%$%H>pJs8r49MQId9f2=4A;z=89g!Y(B, ``7-bit and 8-bit double byte coded Kanji sets for information interchange'', JIS X 0208:1996? draft. @end quotation @@ -1105,21 +1056,22 @@ @node JIS X0212, koi8-r, JIS X0208, Glossary @subsection JIS X0212-1990 -JIS X0208 (@ref{JIS X0208}) $B$K$J$+$C$?J8;z$r=8$a$?(B 94$B!_(B94 $BJ8;z=89g(B -(@ref{94x94 character set})$B!#!VJd=u4A;z!W$H$b8F$P$l$k!#F|K\$N9q2HI8=`!#(B +JIS X0208 (@ref{JIS X0208}) $B$K$J$+$C$?J8;z$r=8$a$?(B 94x94-character set +(@ref{94x94-character set})$B!#!VJd=u4A;z!W$H$b8F$P$l$k!#F|K\$N9q2HI8=`!#(B ISO 2022 (@ref{ISO 2022}) $B$G$N=*C<J8;z$O(B `D'. @node koi8-r, KS C5601, JIS X0212, Glossary @subsection koi8-r -$B%m%7%d8lEy$GMQ$$$i$l$k%-%j%kJ8;z$rI=8=$9$k$?$a$N(B MIME charset (@ref{MIME -charset}) $B$N#1$D!#(B@refill - -ISO 2022 (@ref{ISO 2022}) $B$K4p$+$J$$(B 8bit (@ref{8bit}) $B$NId9f2=J8;z=89g(B -(@ref{Coded character set})$B$G(B de-fact standard $B$G$"$k!#(B - -RFC 1489 $B$GDj5A$5$l$F$$$k!#(B@refill +A MIME charset (@ref{MIME charset}) for Cyrillic script for Russian or +other languages.@refill + +It is a 1 byte 8bit (@ref{8bit}) coded character set (@ref{coded +character set}), not based on ISO 2022 (@ref{ISO 2022}). It is a +de-fact standard.@refill + +It is defined in RFC 1489.@refill @cindex{RFC 1489} @noindent @@ -1133,8 +1085,9 @@ @node KS C5601, message, koi8-r, Glossary @subsection KS C5601-1987 -$B4Z9q8l$rI=$9$?$a$N(B 94$B!_(B94 $BJ8;z=89g(B(@ref{94x94 character set})$B!#4Z9q$N9q(B -$B2HI8=`!#(BISO 2022 (@ref{ISO 2022}) $B$G$N=*C<J8;z$O(B `C'. +A 94x94-character set (@ref{94x94-character set}) for Korean language +(Hangul script). Korean Standard. Final byte of ISO 2022 (@ref{ISO +2022}) is `C'. @cindex{KS C5601}@cindex{KS C 5601:1987} @noindent @@ -1156,9 +1109,11 @@ @node message/rfc822, method, message, Glossary @subsection message/rfc822 -$BEAE}E*$J(B RFC 934 (@ref{RFC 934}) $B$KBe$o$j!"(BRFC 822 (@ref{RFC 822}) $B$GDj(B -$B5A$5$l$k(B mail $B$rI=$9(B MIME $B$N7A<0!#(BRFC 1521 (@ref{RFC 1521}) $B$GDj5A$5$l$F(B -$B$$$k!#(B +@cindex{message/rfc822}@strong{message/rfc822} indicates that the body +contains an encapsulated message, with the syntax of an RFC 822 +(@ref{RFC 822}) message. It is the replacement of traditional RFC 934 +(@ref{RFC 934}) encapsulation. It is defined in RFC 2046 (@ref{RFC +2046}). @node method, MIME, message/rfc822, Glossary @@ -1176,26 +1131,45 @@ @node MIME, MIME charset, method, Glossary @subsection MIME -@cindex{Multipurpose Internet Mail Extensions}@strong{Multipurpose -Internet Mail Extensions} $B$NN,$G!"(BInternet $B$N(B mail $B$d(B news $B$G(B us-ascii -plain text (@ref{us-ascii}) $B0J30$NJ8;z$r;H$&$?$a$N(B RFC 822 (@ref{RFC -822}) $B$KBP$9$k3HD%!#(B@refill - -RFC 1521 (@ref{RFC 1521}) $B$H(B RFC 1522 (@ref{encoded-word}) $B$GDj5A$5$l$F(B -$B$$$k!#(B@refill - -(cf. @ref{What is MIME?}) - +MIME stands for @cindex{Multipurpose Internet Mail +Extensions}@strong{Multipurpose Internet Mail Extensions}, it is an +extension for RFC 822 (@ref{RFC 822}).@refill + +According to RFC 2045:@refill + +STD 11, RFC 822, defines a message representation protocol specifying +considerable detail about US-ASCII message headers, and leaves the +message content, or message body, as flat US-ASCII text. This set of +documents, collectively called the Multipurpose Internet Mail +Extensions, or MIME, redefines the format of messages to allow +for@refill + +@enumerate +@item +textual message bodies in character sets other than US-ASCII, +@item +an extensible set of different formats for non-textual message +bodies, +@item +multi-part message bodies, and +@item +textual header information in character sets other than US-ASCII. +@end enumerate + + +It is defined in RFC 2045 (@ref{RFC 2045}), RFC 2046 (@ref{RFC 2046}), +RFC 2047 (@ref{encoded-word}), RFC 2048 (@ref{RFC 2048}) and RFC 2049 +(@ref{RFC 2049}). @node MIME charset, MTA, MIME, Glossary @subsection MIME charset -Content-Type field (@ref{Content-Type field}) $B$d(B encoded-word -(@ref{encoded-word}) $B$N(B charset parameter $B$GMQ$$$i$l$kEPO?$5$l$?Id9f2=J8(B -$B;z=89g(B (@ref{Coded character set})$B!#(B@refill - -RFC 1521 (@ref{RFC 1521}) $B$GDj5A$5$l$F$$$k!#(B@refill +Coded character set (@ref{Coded character set}) used in Content-Type +field (@ref{Content-Type field}) or charset parameter of encoded-word +(@ref{encoded-word}).@refill + +It is defined in RFC 2045 (@ref{RFC 2045}).@refill iso-2022-jp (@ref{iso-2022-jp}) $B$d(B euc-kr (@ref{euc-kr}) $B$O$=$N#1$D!#(B $B!J$3$3$G$O!"(BMIME charset $B$OJ8;z=89g(B (@ref{Character set})$B$H6hJL$7$F>.J8(B @@ -1247,12 +1221,11 @@ @node multipart, multipart/alternative, MULE, Glossary @subsection Multipart -$B#1$D$N(B message (@ref{message}) $B$KJ#?t$N(B part $B$rF~$l$k$?$a$N(B MIME -(@ref{MIME}) $B$K$*$1$kI=8=K!!"$b$7$/$O!"J#?t$N(B part $B$+$i$J$k(B message $B$r;X(B -$B$9!#(B(cf. @ref{content-type}) @refill - -$B8=:_!"Dj5A$5$l$F$$$k(B @cindex{multipart}@strong{multipart} $B$H$7$F$O!"(BRFC -1521 (@ref{RFC 1521}) $B$GDj5A$5$l$?(B +@cindex{multipart}@strong{multipart} means media type (@ref{media type}) +to insert multiple entities (@ref{entities}) in a single body. Or it +also indicates a message consists of multiple entities.@refill + +There are following subtypes registered in RFC 2046 (@ref{RFC 2046}): @itemize @bullet @item @@ -1266,7 +1239,7 @@ @end itemize @noindent -$B$N$[$+(B RFC 1847 (@ref{Security multipart}) $B$GDj5A$5$l$?(B +and registered in RFC 1847 (@ref{Security multipart}): @itemize @bullet @item @@ -1275,33 +1248,35 @@ multipart/encrypted (@ref{multipart/encrypted}) @end itemize -@noindent -$B$J$I$,$"$k!#(B @node multipart/alternative, multipart/digest, multipart, Glossary @subsection multipart/alternative -multipart (@ref{multipart}) $B$N#1$D$G!"F1$8>pJs$r0[$C$?7A<0$GF~$l!"A*Br;h(B -$B$H$9$k>l9g$KMQ$$$k!#(B@refill - -(cf. @ref{RFC 1521}) +@cindex{multipart/digest}@strong{multipart/digest} is one of multipart +(@ref{multipart}) media types. This type is syntactically identical to +multipart/mixed (@ref{multipart/mixed}), but the semantics are +different. In particular, each of the body parts is an ``alternative'' +version of the same information.@refill + +(cf. @ref{RFC 2046}) @node multipart/digest, multipart/encrypted, multipart/alternative, Glossary @subsection multipart/digest -multipart (@ref{multipart}) $B$N#1$D$G!"4^$^$l$k(B part $B$N(B default $B$N(B -content-type (@ref{content-type}) $B$,(B multipart/mixed -(@ref{multipart/mixed}) $B$J$I$N>l9g(B text/plain (@ref{text/plain}) $B$G$"$k(B -$B$N$KBP$7!"(B@cindex{multipart/digest}@strong{multipart/digest}$B$G$O(B -message/rfc822 (@ref{message/rfc822}) $B$,MQ$$$i$l$kE@$,0[$J$k!#(B@refill - -$B$3$l$OEAE}E*$J(B RFC 1153 (@ref{RFC 1153}) $B$K4p$E$/(B encapsulation -(@ref{encapsulation}) $B$KBe$o$k$b$N$G$"$k!#(B@refill - -(cf. @ref{RFC 1521}) +@cindex{multipart/digest}@strong{multipart/digest} is one of multipart +(@ref{multipart}) media types. This type is syntactically identical to +multipart/mixed (@ref{multipart/mixed}), but the semantics are +different. In particular, in a digest, the default Content-Type value +for a body part is changed from text/plain (@ref{text/plain}) to +message/rfc822 (@ref{message/rfc822}).@refill + +This is the replacement of traditional RFC 1153 (@ref{RFC 1153}) based +encapsulation (@ref{encapsulation}).@refill + +(cf. @ref{RFC 2046}) @@ -1318,20 +1293,24 @@ @node multipart/mixed, multipart/parallel, multipart/encrypted, Glossary @subsection multipart/mixed -multipart (@ref{multipart}) $B$N<gMW$J(B subtype $B$G!"J#?t$N(B part $B$r=g=xIU$1(B -$B$FJB$Y$k>l9g$KMQ$$$k!#(B@refill - -(cf. @ref{RFC 1521}) +Primary and default subtype of multipart (@ref{multipart}), it is used +when the body parts are independent and need to be bundled in a +particular order.@refill + +(cf. @ref{RFC 2046}) @node multipart/parallel, multipart/signed, multipart/mixed, Glossary @subsection multipart/parallel -multipart (@ref{multipart}) $B$N#1$D$G!"J#?t$N(B part $B$r=g=xIU$1$:$K4^$a$k>l(B -$B9g$KMQ$$$k!#(B@refill - -(cf. @ref{RFC 1521}) +@cindex{multipart/parallel}@strong{multipart/parallel} is a subtype of +multipart (@ref{multipart}). This type is syntactically identical to +multipart/mixed (@ref{multipart/mixed}), but the semantics are +different. In particular, in a parallel entity, the order of body parts +is not significant.@refill + +(cf. @ref{RFC 2046}) @@ -1430,16 +1409,15 @@ @node Quoted-Printable, RFC 821, PGP/MIME, Glossary @subsection Quoted-Printable -RFC 1521 (@ref{RFC 1521}) $B$GDj5A$5$l$F$$$k(B MIME (@ref{MIME}) $B$K$*$1$k(B -binary data (@ref{binary}) $B$N(B network $B$G$NJQ49K!$N#1$D!#(B@refill - -`=' $B$d@)8fJ8;z$d(B 128 $B0J>e$NJ8;z$J$I$O(B `=AF' $B$N$h$&$K(B `=' $B$N8e$KB3$/(B 16 -$B?J?t$GI=8=$9$k!#$3$N$?$a!"(BASCII (@ref{ASCII}) $BJ8;zCf?4$N(B data $B$G$O(B -Base64 (@ref{Base64}) $B$KHf$Y$k$H2DFI@-$,9b$/$J$k2DG=@-$,$"$k!#(B@refill - -$B$7$+$7$J$,$i!"(BEBCDIC $B$K$OB8:_$7$J$$J8;z$rMxMQ$9$k>l9g!"(BEBCDIC $B$rMxMQ$7(B -$B$F$$$k(B network $B$G$O0BA4$KE>Aw$9$k$3$H$,$G$-$:!"(BBase64 $B$KHf$Y$F0BA4@-$O(B -$BDc$$!#(B +@cindex{Quoted-Printable}@strong{Quoted-Printable} is a transfer +encoding method of MIME (@ref{MIME}) defined in RFC 2045 (@ref{RFC +2045}).@refill + +If the data being encoded are mostly US-ASCII text, the encoded form of +the data remains largely recognizable by humans.@refill + +(cf. @ref{Base64}) + @node RFC 821, RFC 822, Quoted-Printable, Glossary @@ -1521,7 +1499,7 @@ -@node RFC 1153, RFC 1521, RFC 1036, Glossary +@node RFC 1153, RFC 1557, RFC 1036, Glossary @subsection RFC 1153 $BJ#?t$N(B Internet mail (@ref{RFC 822}) $B$r(B @@ -1544,26 +1522,7 @@ -@node RFC 1521, RFC 1557, RFC 1153, Glossary -@subsection RFC 1521 - -MIME (@ref{MIME}) $B$rDj5A$7$F$$$k(B RFC $B$N#1$D!#(B - -@cindex{Standards Track}@cindex{RFC 1521} -@noindent -[RFC 1521] -@quotation -N. Borenstein and N. Freed, ``MIME (Multipurpose Internet Mail -Extensions) Part One: Mechanisms for Specifying and Describing the -Format of Internet Message Bodies'', September 1993, Standards Track -(obsolete RFC 1341). -@end quotation - - -(RFC 1522 (@ref{encoded-word})) - - -@node RFC 1557, RFC 1922, RFC 1521, Glossary +@node RFC 1557, RFC 1922, RFC 1153, Glossary @subsection RFC 1557 euc-kr (@ref{euc-kr}) $B$H(B iso-2022-kr (@ref{iso-2022-kr}) $B$H$$$&4Z9q8l$N(B @@ -1579,7 +1538,7 @@ -@node RFC 1922, plain text, RFC 1557, Glossary +@node RFC 1922, RFC 2045, RFC 1557, Glossary @subsection RFC 1922 iso-2022-cn (@ref{iso-2022-cn}), iso-2022-cn-ext @@ -1602,7 +1561,63 @@ -@node plain text, Security multipart, RFC 1922, Glossary +@node RFC 2045, RFC 2046, RFC 1922, Glossary +@subsection RFC 2045 + +@cindex{Standards Track}@cindex{RFC 2045} +@noindent +[RFC 2045] +@quotation +N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions +(MIME) Part One: Format of Internet Message Bodies'', November 1996, +Standards Track (obsolete RFC 1521, 1522, 1590). +@end quotation + + + +@node RFC 2046, RFC 2048, RFC 2045, Glossary +@subsection RFC 2046 + +@cindex{Standards Track}@cindex{RFC 2046} +@noindent +[RFC 2046] +@quotation +N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions +(MIME) Part Two: Media Types'', November 1996, Standards Track (obsolete +RFC 1521, 1522, 1590). +@end quotation + + + +@node RFC 2048, RFC 2049, RFC 2046, Glossary +@subsection RFC 2048 + +@cindex{Standards Track}@cindex{RFC 2048} +@noindent +[RFC 2048] +@quotation +N. Freed, J. Klensin and J. Postel, ``Multipurpose Internet Mail +Extensions (MIME) Part Four: Registration Procedures'', November 1996, +Standards Track (obsolete RFC 1521, 1522, 1590). +@end quotation + + + +@node RFC 2049, plain text, RFC 2048, Glossary +@subsection RFC 2049 + +@cindex{Standards Track}@cindex{RFC 2049} +@noindent +[RFC 2049] +@quotation +N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions +(MIME) Part Five: Conformance Criteria and Examples'', November 1996, +Standards Track (obsolete RFC 1521, 1522, 1590). +@end quotation + + + +@node plain text, Security multipart, RFC 2049, Glossary @subsection plain text $B=qBN$dAHHG$K4X$9$k>pJs$r;}$?$J$$(B $BJ8;zId9f(B(@ref{Coded character set})$B$N$_(B @@ -1634,9 +1649,9 @@ @node text/enriched, text/plain, Security multipart, Glossary @subsection text/enriched -RFC 1521 (@ref{RFC 1521}) $B$GDj5A$5$l$?(B -@cindex{text/richtext}@strong{text/richtext} $B$KBe$o$C$F!"=qBN$dAHHG$K4X(B -$B$9$k>pJs$r;}$C$?(B text$B$rI=8=$9$k$?$a$N(B content-type (@ref{content-type}). +RFC 1521 $B$GDj5A$5$l$?(B @cindex{text/richtext}@strong{text/richtext} $B$KBe(B +$B$o$C$F!"=qBN$dAHHG$K4X$9$k>pJs$r;}$C$?(B text$B$rI=8=$9$k$?$a$N(B media type +(@ref{media type}). @cindex{text/enriched}@cindex{RFC 1896} @noindent @@ -1651,13 +1666,16 @@ @node text/plain, tm-kernel, text/enriched, Glossary @subsection text/plain -RFC 1521 (@ref{RFC 1521}) $B$GDj5A$5$l$?!"(Bplain text (@ref{plain text}) $B$r(B -$BI=8=$9$k$?$a$N(B content-type (@ref{content-type}).@refill - -$BHs(B MIME message $B$J$I$N(B content-type $B$,Dj5A$5$l$J$$(B part $B$O(B MIME charset -(@ref{MIME charset}) $B$,(B us-ascii (@ref{us-ascii}) $B$G$"$k(B -@cindex{text/plain}@strong{text/plain} $B$N(B part $B$G$"$k$H8+Pv$5$l$k$3$H$K(B -$B$J$C$F$$$k!#(B +@cindex{text/plain}@strong{text/plain} is a media type (@ref{media +type}) for plain text (@ref{plain text}), defined in RFC 2046 (@ref{RFC +2046}).@refill + +The default media type of ``text/plain; charset=us-ascii'' for Internet +mail describes existing Internet practice. That is, it is the type of +body defined by RFC 822 (@ref{RFC 822}).@refill + +(cf. @ref{MIME charset}) (cf. @ref{us-ascii}) + @node tm-kernel, tm-MUA, text/plain, Glossary @@ -1958,9 +1976,9 @@ @itemize @bullet @item - $BF|K\8l(B <tm-ja-admin@@chamonix.jaist.ac.jp> + Japanese <tm-ja-admin@@chamonix.jaist.ac.jp> @item - $B1Q8l(B <tm-en-admin@@chamonix.jaist.ac.jp> + English <tm-en-admin@@chamonix.jaist.ac.jp> @end itemize @noindent