comparison man/tm/tm-en.texi @ 8:4b173ad71786 r19-15b5

Import from CVS: tag r19-15b5
author cvs
date Mon, 13 Aug 2007 08:47:35 +0200
parents
children 49a24b4fd526
comparison
equal deleted inserted replaced
7:c153ca296910 8:4b173ad71786
1 \input texinfo.tex
2 @setfilename tm-en.info
3 @settitle{tm 7.90 Manual (English Version)}
4 @titlepage
5 @title tm 7.90 Manual (English Version)
6 @author MORIOKA Tomohiko <morioka@@jaist.ac.jp>
7 @subtitle 1996/10/15
8 @end titlepage
9 @node Top, Introduction, (dir), (dir)
10 @top tm 7.90 Manual (English Version)
11
12 @ifinfo
13
14 This file documents tm, a MIME package for GNU Emacs.
15 @end ifinfo
16
17 @menu
18 * Introduction:: What is tm?
19 * Setting::
20 * Bug report:: How to report bug and about mailing list of tm
21 * Concept Index::
22 * Variable Index::
23 @end menu
24
25 @node Introduction, Setting, Top, Top
26 @chapter What is tm?
27
28 The tm package is a set of modules to enjoy MIME on GNU Emacs. Using
29 tm, you can
30
31 @itemize @bullet
32 @item
33 playback or view the MIME messages using tm-view
34 @item
35 compose MIME message using tm-edit
36 @item
37 use the enhanced MIME features with mh-e, GNUS, Gnus, RMAIL and VM
38 @end itemize
39
40 @noindent
41 and more.
42
43 Please read following about each topics:
44
45 @itemize @bullet
46 @item
47 tm-MUA for Gnus (@ref{(gnus-mime-en)})
48 @item
49 tm-MUA for GNUS (@ref{(tm-gnus-en)})
50 @item
51 tm-MUA for mh-e (@ref{(tm-mh-e-en)})
52 @item
53 mime/viewer-mode (@ref{(tm-view-en)})
54 @item
55 mime/editor-mode (@ref{(tm-edit-en)})
56 @end itemize
57
58
59
60 @menu
61 * Glossary::
62 @end menu
63
64 @node Glossary, , Introduction, Introduction
65 @section Glossary
66
67
68 @menu
69 * 7bit::
70 * 8bit::
71 * 94-character set::
72 * 96-character set::
73 * 94x94-character set::
74 * ASCII::
75 * Base64::
76 * binary::
77 * graphic character set:: Graphic Character Set
78 * cn-gb:: cn-gb, gb2312
79 * cn-big5:: cn-big5, big5
80 * CNS:: CNS 11643-1992
81 * coded character set:: Coded character set, Character code
82 * code extension:: Code extension
83 * Content-Disposition:: Content-Disposition field
84 * media type::
85 * Content-Type field::
86 * Emacs::
87 * encoded-word::
88 * encapsulation::
89 * euc-kr::
90 * FTP:: FTP
91 * GB 2312:: GB 2312-1980
92 * GB 8565.2:: GB 8565.2-1988
93 * hz-gb2312::
94 * ISO 2022::
95 * iso-2022-cn::
96 * iso-2022-cn-ext::
97 * iso-2022-jp::
98 * iso-2022-jp-2::
99 * iso-2022-kr::
100 * ISO 646::
101 * ISO 8859-1::
102 * iso-8859-1::
103 * ISO 8859-2::
104 * iso-8859-2::
105 * ISO 8859-3::
106 * ISO 8859-4::
107 * ISO 8859-5::
108 * iso-8859-5::
109 * ISO 8859-6::
110 * ISO 8859-7::
111 * iso-8859-7::
112 * ISO 8859-8::
113 * ISO 8859-9::
114 * ISO-IR-165:: ISO-IR-165, CCITT Extended GB
115 * JIS X0201::
116 * JIS C6226:: JIS C6226-1978
117 * JIS X0208::
118 * JIS X0212:: JIS X0212-1990
119 * koi8-r::
120 * KS C5601:: KS C5601-1987
121 * message::
122 * message/rfc822::
123 * method::
124 * MIME::
125 * MIME charset::
126 * MTA::
127 * MUA::
128 * MULE::
129 * multipart:: Multipart
130 * multipart/alternative::
131 * multipart/digest::
132 * multipart/encrypted::
133 * multipart/mixed::
134 * multipart/parallel::
135 * multipart/signed::
136 * PGP::
137 * PGP-kazu::
138 * PGP/MIME::
139 * Quoted-Printable::
140 * RFC 821::
141 * RFC 822::
142 * RFC 934::
143 * RFC 1036::
144 * RFC 1153::
145 * RFC 1557::
146 * RFC 1922::
147 * RFC 2045::
148 * RFC 2046::
149 * RFC 2048::
150 * RFC 2049::
151 * plain text::
152 * Security multipart::
153 * text/enriched::
154 * text/plain::
155 * tm-kernel:: tm-kernel, tm
156 * tm-MUA::
157 * us-ascii::
158 @end menu
159
160 @node 7bit, 8bit, Glossary, Glossary
161 @subsection 7bit
162
163 @cindex{7bit}@strong{7bit} means any integer between 0 .. 127.@refill
164
165 Any data represented by 7bit integers is called @cindex{7bit
166 data}@strong{7bit data}.@refill
167
168 Textual string consisted of Control characters between 0 .. 31 and 127,
169 and space represented by 32, and graphic characters between 33 .. 236
170 are called @cindex{7bit (textual) string}@strong{7bit (textual)
171 string}.@refill
172
173 Traditional Internet MTA (@ref{MTA}) can translate 7bit data, so it is
174 no need to translate by Quoted-Printable (@ref{Quoted-Printable}) or
175 Base64 (@ref{Base64}) for 7bit data.@refill
176
177 However if there are too long lines, it can not translate by 7bit MTA
178 even if it is 7bit data. RFC 821 (@ref{RFC 821}) and RFC 2045 (@ref{RFC
179 2045}) require lines in 7bit data must be less than 998 bytes. So if a
180 ``7bit data'' has a line more than 999 bytes, it is regarded as binary
181 (@ref{binary}). For example, Postscript file should be encoded by
182 Quoted-Printable.
183
184
185 @node 8bit, 94-character set, 7bit, Glossary
186 @subsection 8bit
187
188 @cindex{8bit}@strong{8bit} means any integer between 0 .. 255.@refill
189
190 Any data represented by 8bit integers is called @cindex{8bit
191 data}@strong{8bit data}.@refill
192
193 Textual string consisted of Control characters between 0 .. 31, 127, and
194 128 .. 159, and space represented by 32, and graphic characters between
195 33 .. 236 and 160 .. 255 are called @cindex{8bit (textual)
196 string}@strong{8bit (textual) string}.@refill
197
198 For example, iso-8859-1 (@ref{iso-8859-1}) or euc-kr (@ref{euc-kr}) are
199 coded-character-set represented by 8bit textual string.@refill
200
201 Traditional Internet MTA (@ref{MTA}) can translate only 7bit
202 (@ref{7bit}) data, so if a 8bit data will be translated such MTA, it
203 must be encoded by Quoted-Printable (@ref{Quoted-Printable}) or Base64
204 (@ref{Base64}).@refill
205
206 However 8bit MTA are increasing today.@refill
207
208 However if there are too long lines, it can not translate by 8bit MTA
209 even if it is 8bit data. RFC 2045 (@ref{RFC 2045}) require lines in
210 8bit data must be less than 998 bytes. So if a ``8bit data'' has a line
211 more than 999 bytes, it is regarded as binary (@ref{binary}), so it must
212 be encoded by Base64 or Quoted-Printable.
213
214
215 @node 94-character set, 96-character set, 8bit, Glossary
216 @subsection 94-character set
217
218 @cindex{94-character set}@strong{94-character set} is a kind of 1 byte
219 graphic character set (@ref{graphic character set}), each characters are
220 in positions 02/01 (33) to 07/14 (126) or 10/01 (161) to 15/14 (254).
221 (ex. ASCII (@ref{ASCII}), JIS X0201-Latin)
222
223
224 @node 96-character set, 94x94-character set, 94-character set, Glossary
225 @subsection 96-character set
226
227 @cindex{96-character set}@strong{96-character set} is a kind of 1 byte
228 graphic character set (@ref{graphic character set}), each characters are
229 in positions 02/00 (32) to 07/15 (126) or 10/00 (160) to 15/15
230 (255). (ex. ISO 8859)
231
232
233 @node 94x94-character set, ASCII, 96-character set, Glossary
234 @subsection 94x94-character set
235
236 @cindex{94x94-character set}@strong{94x94-character set} is a kind of 2
237 byte graphic character set (@ref{graphic character set}), each bytes are
238 in positions 02/01 (33) to 07/14 (126) or 10/01 (161) to 15/14 (254).
239 (ex. JIS X0208 (@ref{JIS X0208}), GB 2312 (@ref{GB 2312}))
240
241
242 @node ASCII, Base64, 94x94-character set, Glossary
243 @subsection ASCII
244
245 $B%"%a%j%+O"K.$G;H$o$l$kJ8;z$rId9f2=$7$?(B 94-character set
246 (@ref{94-character set}). A-Z, a-z $B$N(B Latin $BJ8;z$H?t;z!"4v$D$+$N5-9f$+(B
247 $B$i$J$k!#(BISO 646 (@ref{ISO 646}) $B$N0l$D!#(B
248
249 @cindex{ASCII}@cindex{ANSI X3.4:1986}
250 @noindent
251 [ASCII]
252 @quotation
253 ``Coded Character Set -- 7-Bit American Standard Code for Information
254 Interchange'', ANSI X3.4:1986.
255 @end quotation
256
257
258
259 @node Base64, binary, ASCII, Glossary
260 @subsection Base64
261
262 @cindex{Base64}@strong{Base64} is a transfer encoding method of MIME
263 (@ref{MIME}) defined in RFC 2045 (@ref{RFC 2045}).@refill
264
265 The encoding process represents 24-bit groups of input bits as output
266 strings of 4 encoded characters. Encoded characters represent integer 0
267 .. 63 or @cindex{pad}@strong{pad}. Base64 data must be 4 * n bytes, so
268 pad is used to adjust size.@refill
269
270 These 65 characters are subset of all versions of ISO 646, including
271 US-ASCII, and all versions of EBCDIC. So it is safe even if it is
272 translated by non-Internet gateways.
273
274
275 @node binary, graphic character set, Base64, Glossary
276 @subsection binary
277
278 $BG$0U$N(B byte $BNs$r(B @cindex{binary}@strong{binary} $B$H8F$V$3$H$K$7$^$9!#(B
279 @refill
280
281 8bit (@ref{8bit}) $B$H0[$J$k$N$O(B data $B$K9T$N9=B$$r2>Dj$7$J$$$3$H$G$9!#(B
282
283 $B$^$?!"9T$N9=B$$,$"$C$F$b!"(B999 byte $B0J>e$+$i$J$k9T$,$"$k>l9g$b(B binary$B$H8F(B
284 $B$V$3$H$K$7$^$9!#(B@refill
285
286 $B$A$J$_$K!"(B7bit (@ref{7bit}) $B$d(B 8bit $B$GI=8=$G$-$k(B data $B$O(B binary $B$G$bI=8=(B
287 $B$G$-$^$9!#$h$C$F!"(B@cindex{binary data}@strong{binary data} $B$H8@$C$?>l9g!"(B
288 $BG$0U$N(B data $B$r;X$9$3$H$,$"$j$^$9!#(B
289
290
291 @node graphic character set, cn-gb, binary, Glossary
292 @subsection Graphic Character Set
293
294 Coded character set (@ref{Coded character set}) for graphic characters.
295
296
297 @node cn-gb, cn-big5, graphic character set, Glossary
298 @subsection cn-gb, gb2312
299
300 $BCf9qBgN&$G$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B MIME
301 charset (@ref{MIME charset}) $B$N#1$D!#(B@refill
302
303 ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F(B ASCII (@ref{ASCII}) $B$K(B GB 2312
304 (@ref{GB 2312}) $B$r(B 8bit (@ref{8bit}) $B$GId9f3HD%(B (@ref{Code extension})$B$7(B
305 $B$F$$$k!#(B@refill
306
307 RFC 1922 (@ref{RFC 1922}) $B$GDj5A$5$l$F$$$k!#(B
308
309
310 @node cn-big5, CNS, cn-gb, Glossary
311 @subsection cn-big5, big5
312
313 $BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B
314 MIME charset (@ref{MIME charset}) $B$N#1$D!#(B@refill
315
316 ISO 2022 (@ref{ISO 2022}) $B$K4p$+$J$$(B 8bit (@ref{8bit}) $B$N(Bcoded character
317 set (@ref{coded character set})$B$G(B de-fact standard $B$G$"$k!#(BRFC 1922
318 (@ref{RFC 1922}) $B$GDj5A$5$l$F$$$k!#(B@refill
319
320 cf. @cindex{BIG5}
321 @noindent
322 [BIG5]
323 @quotation
324 Institute for Information Industry, ``Chinese Coded Character Set in
325 Computer'', March 1984.
326 @end quotation
327
328 CNS 11643-1986 (@ref{CNS}) $B$HBP1~4X78$,$"$k!#(B
329
330
331 @node CNS, coded character set, cn-big5, Glossary
332 @subsection CNS 11643-1992
333
334 $BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B
335 $BJ8;z=89g(B(@ref{Character set})$B!#BfOQ$NI8=`!#8=:_!"(B94$B!_(B94 (@ref{94x94
336 character set}) $B$NLL$,Bh#1LL$+$iBh#7LL$^$G$"$k!#(B@refill
337
338 ISO 2022 (@ref{ISO 2022}) $B$G$N=*C<J8;z$O!"Bh#1LL$,(B `G', $BBh#2LL$,(B `H', $BBh(B
339 $B#3LL$,(B `I', $BBh#4LL$,(B `J', $BBh#5LL$,(B `K', $BBh#6LL$,(B `L', $BBh#7LL$,(B `M' $B$G$"(B
340 $B$k!#(B
341
342 @cindex{CNS 11643-1992}@cindex{CNS 11643:1992}
343 @noindent
344 [CNS 11643-1992]
345 @quotation
346 ``Standard Interchange Code for Generally-Used Chinese Characters'', CNS
347 11643:1992.
348 @end quotation
349
350
351
352 @node coded character set, code extension, CNS, Glossary
353 @subsection Coded character set, Character code
354
355 A set of unambiguous rules that establishes a character set and the
356 one-to-one relationship between the characters of the set and their
357 bit combinations.
358
359
360 @node code extension, Content-Disposition, coded character set, Glossary
361 @subsection Code extension
362
363 The techniques for the encoding of characters that are not included in
364 the character set of a given code. (ex. ISO 2022 (@ref{ISO 2022}))
365
366
367 @node Content-Disposition, media type, code extension, Glossary
368 @subsection Content-Disposition field
369
370 Content $B$NI=<($N;EJ}$d(B file $BL>$rI=8=$9$k$?$a$N(B field. MIME (@ref{MIME})
371 $B$N3HD%$N#1$D!#(B@refill
372
373 @cindex{Experimental}@cindex{RFC 1806}
374 @noindent
375 [RFC 1806]
376 @quotation
377 E R. Troost and S. Dorner, ``Communicating Presentation Information in
378 Internet Messages: The Content-Disposition Header'', June 1995,
379 Experimental.
380 @end quotation
381
382
383
384 @node media type, Content-Type field, Content-Disposition, Glossary
385 @subsection media type
386
387 @cindex{media type}@strong{media type} specifies the nature of the data
388 in the body of MIME (@ref{MIME}) entity (@ref{entity}). It consists of
389 @cindex{type}@strong{type} and @cindex{subtype}@strong{subtype}. It is
390 defined in RFC 2046 (@ref{RFC 2046}).@refill
391
392 Currently there are following types:
393
394 @itemize @bullet
395 @item
396 @cindex{text}@strong{text}
397 @item
398 @cindex{image}@strong{image}
399 @item
400 @cindex{audio}@strong{audio}
401 @item
402 @cindex{video}@strong{video}
403 @item
404 @cindex{application}@strong{application}
405 @item
406 @cindex{multipart}@strong{multipart} (@ref{multipart})
407 @item
408 @cindex{message}@strong{message}
409 @end itemize
410
411
412 And there are various subtypes, for example, application/octet-stream,
413 audio/basic, image/jpeg, multipart/mixed (@ref{multipart/mixed}),
414 text/plain (@ref{text/plain}), video/mpeg...@refill
415
416 You can refer registered media types at MEDIA TYPES
417 (ftp://ftp.isi.edu/in-notes/iana/assignments/media-types).@refill
418
419 In addition, you can use private type or subtype using
420 @cindex{x-token}@strong{x-token}, which as the prefix `x-'. However you
421 can not use them in public.@refill
422
423 (cf. @ref{Content-Type field})
424
425
426
427 @node Content-Type field, Emacs, media type, Glossary
428 @subsection Content-Type field
429
430 Header field to represent information about body, such as media type
431 (@ref{media type}), MIME charset (@ref{MIME charset}). It is defined in
432 RFC 2045 (@ref{RFC 2045}).
433
434 @noindent
435 @strong{[Memo]}
436 @quotation
437
438 Historically, Content-Type field was proposed in RFC 1049. In it,
439 Content-Type did not distinguish type and subtype. However MIME parser
440 may be able to accept RFC 1049 based Content-Type as unknown type.
441 @end quotation
442
443
444 Content-Type field is defined as following:
445
446 @quotation
447 ``Content-Type'' ``:'' @cindex{type}@strong{type} ``/''
448 @cindex{subtype}@strong{subtype} *( ``;'' @cindex{parameter}@strong{parameter} )
449 @end quotation
450
451
452 For example:
453
454 @quotation
455 @example
456 Content-Type: image/jpeg
457 @end example
458 @end quotation
459
460
461 @quotation
462 @example
463 Content-Type: text/plain; charset=iso-2022-jp
464 @end example
465 @end quotation
466
467
468 @noindent
469 @strong{[Memo]}
470 @quotation
471
472 A part does not have content-type field is regarded as
473
474 @quotation
475 @example
476 Content-Type: text/plain; charset=us-ascii
477 @end example
478 @end quotation
479
480 @noindent
481 (cf. @ref{us-ascii})
482
483
484 And a part has unknown type/subtype is regarded as
485
486 @quotation
487 @example
488 Content-Type: application/octet-stream
489 @end example
490 @end quotation
491
492 @end quotation
493
494
495
496 @node Emacs, encoded-word, Content-Type field, Glossary
497 @subsection Emacs
498
499 $B$3$3$G$O(B `Emacs' $B$G(B FSF $B$,G[I[$7$F$$$k(B GNU Emacs $B$r;X$7!"(B`emacs' $B$G(B
500 GNU Emacs $B$NJQ<o$NAm>N$H$9$k!#(B
501
502
503 @node encoded-word, encapsulation, Emacs, Glossary
504 @subsection encoded-word
505
506 Representation non ASCII (@ref{ASCII}) characters in header. It is
507 defined in @cindex{RFC 2047}@strong{RFC 2047}.@refill
508
509 @cindex{Standards Track}@cindex{RFC 2047}
510 @noindent
511 [RFC 2047]
512 @quotation
513 K. Moore, ``MIME (Multipurpose Internet Mail Extensions) Part Three:
514 Message Header Extensions for Non-ASCII Text'', November 1996, Standards
515 Track (obsolete RFC 1521,1522,1590).
516 @end quotation
517
518
519
520 @node encapsulation, euc-kr, encoded-word, Glossary
521 @subsection encapsulation
522
523 Internet mail (@ref{RFC 822}) $B$rB>$N5-;v$K$^$k$4$HF~$l$kJ}K!!#(B@refill
524
525 $BNc$($P!"5-;v$rE>Aw$7$?$j$9$k$N$KMQ$$$k!#(B@refill
526
527 (cf. @ref{message/rfc822})
528
529
530
531 @node euc-kr, FTP, encapsulation, Glossary
532 @subsection euc-kr
533
534 $B4Z9q8l$rI=8=$9$k$?$a$N(B MIME charset (@ref{MIME charset}) $B$N#1$D!#(B
535
536 ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F(B ASCII (@ref{ASCII}) $B$K(BKS C5601
537 (@ref{KS C5601}) $B$r(B 8bit (@ref{8bit}) $B$GId9f3HD%(B (@ref{Code extension})
538 $B$7$F$$$k!#(B@refill
539
540 RFC 1557 (@ref{RFC 1557}) $B$GDj5A$5$l$F$$$k!#(B@refill
541
542 cf. @cindex{euc-kr}@cindex{KS C 5861:1992}
543 @noindent
544 [euc-kr]
545 @quotation
546 Korea Industrial Standards Association, ``Hangul Unix Environment'', KS
547 C 5861:1992.
548 @end quotation
549
550
551
552 @node FTP, GB 2312, euc-kr, Glossary
553 @subsection FTP
554
555 Internet $B$G(B file $B$rE>Aw$9$k$?$a$N(B protocol $B$N#1$D!#(BRFC 959 $B$GDj5A$5$l$F(B
556 $B$$$k!#(B@refill
557
558 @cindex{FTP}@cindex{STD 9}@cindex{RFC 959}
559 @noindent
560 [FTP: RFC 959]
561 @quotation
562 Postel, J. and J. Reynolds, ``File Transfer Protocol'', October 1985,
563 STD 9.
564 @end quotation
565
566
567
568 @node GB 2312, GB 8565.2, FTP, Glossary
569 @subsection GB 2312-1980
570
571 $BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=$9$?$a$N(B
572 94x94-character set (@ref{94x94-character set})$B!#Cf9q$N9q2HI8=`!#(BISO
573 2022 (@ref{ISO 2022}) $B$G$N=*C<J8;z$O(B `A'.@refill
574
575 $B$3$l$O(B GB $B$K$*$1$k4pK\=8$G$"$k!#(B
576
577 @cindex{GB 2312}@cindex{GB 2312:1980}
578 @noindent
579 [GB 2312]
580 @quotation
581 $B!X?.B)8r49MQ4A;zJTb{;zId=8(B -- $B4pK\=8!Y(B, ``Code of Chinese Graphic
582 Character Set for Information Interchange - Primary Set'', GB 2312:1980.
583 @end quotation
584
585
586
587 @node GB 8565.2, hz-gb2312, GB 2312, Glossary
588 @subsection GB 8565.2-1988
589
590 $BCf9q8l$N$?$a$NJd=uJ8;z=89g(B(@ref{Character set})$B!#Cf9q$N9q2HI8=`!#(BGB 2312
591 (@ref{GB 2312}) $B$N6u$-ItJ,$KJd=<$9$k$h$&$KDj5A$5$l$?$i$7$$!#(B
592
593 @cindex{GB 8565.2}@cindex{GB 8565.2:1988}
594 @noindent
595 [GB 8565.2]
596 @quotation
597 ``Information Processing - Coded Character Sets for Text Communication -
598 Part 2: Graphic Characters used with Primary Set'', GB 8565.2:1988.
599 @end quotation
600
601
602
603 @node hz-gb2312, ISO 2022, GB 8565.2, Glossary
604 @subsection hz-gb2312
605
606 $BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B MIME
607 charset (@ref{MIME charset}) $B$N#1$D!#(B@refill
608
609 ASCII (@ref{ASCII}) $B$K(B GB 2312 (@ref{GB 2312}) $B$r(B 7bit $B$GId9f3HD%(B
610 (@ref{Code extension})$B$7$?$b$N$r(B ASCII printable $B$K$J$k$h$&$K9)IW$7$F$$(B
611 $B$k!#(B@refill
612
613 RFC 1842, 1843 $B$GDj5A$5$l$F$$$k!#(B
614
615 @cindex{Informational}@cindex{RFC 1842}
616 @noindent
617 [RFC 1842]
618 @quotation
619 Y. Wei, Y. Zhang, J. Li, J. Ding and Y. Jiang, ``ASCII Printable
620 Characters-Based Chinese Character Encoding for Internet Messages'',
621 August 1995, Informational.
622 @end quotation
623
624 @cindex{Informational}@cindex{RFC 1843}
625 @noindent
626 [RFC 1843]
627 @quotation
628 F. Lee, ``HZ - A Data Format for Exchanging Files of Arbitrarily Mixed
629 Chinese and ASCII characters'', August 1995, Informational.
630 @end quotation
631
632
633
634 @node ISO 2022, iso-2022-cn, hz-gb2312, Glossary
635 @subsection ISO 2022
636
637 $BId9f3HD%(B(@ref{Code extension})$B$N$?$a$N9q:]I8=`!#(B@refill
638
639 $B$3$l$rMQ$$$FJ#?t$NJ8;z=89g(B(@ref{Character set})$B$rAH9g$;$F(B 7bit
640 (@ref{7bit}) $B$J$$$7(B 8bit (@ref{8bit}) $B$N(B $BId9f2=J8;z=89g(B(@ref{Coded
641 character set}) $B$r:n$k$3$H$,$G$-$k!#(B
642
643 @cindex{ISO 2022}@cindex{ISO/IEC 2022:1994}
644 @noindent
645 [ISO 2022]
646 @quotation
647 International Organization for Standardization (ISO), ``Information
648 Processing: ISO 7-bit and 8-bit coded character sets: Code extension
649 techniques'', ISO/IEC 2022:1994.
650 @end quotation
651
652
653
654 @node iso-2022-cn, iso-2022-cn-ext, ISO 2022, Glossary
655 @subsection iso-2022-cn
656
657 $BCf9q8l$rI=8=$9$k$?$a$N(B MIME charset (@ref{MIME charset}) $B$N#1$D!#(B
658
659 ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F(B ASCII (@ref{ASCII}) $B$K(B GB 2312
660 (@ref{GB 2312}), CNS 11643 plain 1, plain 2 (@ref{CNS}) $B$r(B 7bit
661 (@ref{7bit}) $B$GId9f3HD%(B (@ref{Code extension})$B$7$F$$$k!#(B@refill
662
663 RFC 1922 (@ref{RFC 1922}) $B$GDj5A$5$l$F$$$k!#(B
664
665
666 @node iso-2022-cn-ext, iso-2022-jp, iso-2022-cn, Glossary
667 @subsection iso-2022-cn-ext
668
669 $BCf9q8l$rI=8=$9$k$?$a$N(B MIME charset (@ref{MIME charset}) $B$N#1$D!#(B
670
671 ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F(B ASCII (@ref{ASCII}) $B$K(B GB 2312
672 (@ref{GB 2312}), CNS 11643 plain 1 .. 7 (@ref{CNS}), ISO-IR-165
673 (@ref{ISO-IR-165}) $BEy$r(B 7bit (@ref{7bit}) $B$GId9f3HD%(B (@ref{Code
674 extension})$B$7$F$$$k!#(B@refill
675
676 RFC 1922 (@ref{RFC 1922}) $B$GDj5A$5$l$F$$$k!#(B@refill
677
678 @noindent
679 @strong{[Memo]}
680 @quotation
681 MULE 2.3 $B$*$h$S!"8=:_$N(B XEmacs/mule $B$G$O@5$7$/07$&$3$H$O$G$-$J$$!#(B
682
683 Emacs/mule $B$G$OMxMQ2DG=$G$"$k!#(B
684 @end quotation
685
686
687
688 @node iso-2022-jp, iso-2022-jp-2, iso-2022-cn-ext, Glossary
689 @subsection iso-2022-jp
690
691 $BF|K\8l$rI=8=$9$k$?$a$N(B MIME charset (@ref{MIME charset}) $B$N0l$D!#(B
692
693 $B8E$$(B ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F(B ASCII (@ref{ASCII}), JIS
694 X0201-Latin, JIS X0208-1978 (@ref{JIS C6226-1978}), JIS X0208-1983
695 (@ref{JIS X0208}) $B$r@Z$jBX$($k(B 7bit (@ref{7bit}) $BJ8;zId9f!#(B@refill
696
697 RFC 1468 $B$GDj5A$5$l$F$$$k!#(B@refill
698
699 @noindent
700 @strong{[Memo]}
701 @quotation
702 JIS X0208-1996? $B$G$O(B ISO 2022 (@ref{ISO 2022}) $B$HFHN)$KDj5A$5$l$kM=Dj!#(B
703 @end quotation
704
705
706 @cindex{iso-2022-jp}@cindex{RFC 1468}
707 @noindent
708 [iso-2022-jp: RFC 1468]
709 @quotation
710 Murai J., M. Crispin, and E. van der Poel, ``Japanese Character Encoding
711 for Internet Messages'', June 1993.
712 @end quotation
713
714
715
716 @node iso-2022-jp-2, iso-2022-kr, iso-2022-jp, Glossary
717 @subsection iso-2022-jp-2
718
719 A MIME charset (@ref{MIME charset}), which is a multilingual extension
720 of iso-2022-jp (@ref{iso-2022-jp}).@refill
721
722 It is defined in RFC 1554.
723
724 @cindex{iso-2022-jp-2}@cindex{Informational}@cindex{RFC 1554}
725 @noindent
726 [iso-2022-jp-2: RFC 1554]
727 @quotation
728 Ohta M. and Handa K., ``ISO-2022-JP-2: Multilingual Extension of
729 ISO-2022-JP'', December 1993, Informational.
730 @end quotation
731
732
733
734 @node iso-2022-kr, ISO 646, iso-2022-jp-2, Glossary
735 @subsection iso-2022-kr
736
737 A MIME charset (@ref{MIME charset}) for Korean language (Hangul
738 script).@refill
739
740 It is based on ISO 2022 (@ref{ISO 2022}) code extension (@ref{code
741 extension}) technique to extends ASCII (@ref{ASCII}) to use KS C5601
742 (@ref{KS C5601}) as 7bit (@ref{7bit}) text.@refill
743
744 It is defined in RFC 1557 (@ref{RFC 1557}).
745
746
747 @node ISO 646, ISO 8859-1, iso-2022-kr, Glossary
748 @subsection ISO 646
749
750 $B3F9q$G6&DL$K;H$($k:G>.8BEY$NJ8;z=89g(B(@ref{Character set})$B$rDj$a$?$b$N!#(B
751 94 $BJ8;z=89g(B (@ref{94 character set})$B$N#1$D!#(BISO 646 IRV$B!J9q:]4p=`HG!K$r(B
752 $B85$K4v$D$+$NJ8;z$O3F9q$G0c$&J8;z$r3dEv$k$3$H$r5v$7$F$$$F!"4v$D$+$NJQ<o$,(B
753 $BB8:_$9$k!#(BASCII (@ref{ASCII}) $B$d(B JIS X0201-Latin $B$O$=$N0l<o!#(B
754
755 @cindex{ISO 646}@cindex{ISO/IEC 646:1991}
756 @noindent
757 [ISO 646]
758 @quotation
759 International Organization for Standardization (ISO), ``Information
760 technology: ISO 7-bit coded character set for information interchange'',
761 ISO/IEC 646:1991.
762 @end quotation
763
764
765
766 @node ISO 8859-1, iso-8859-1, ISO 646, Glossary
767 @subsection ISO 8859-1
768
769 @cindex{ISO 8859-1}@cindex{ISO 8859-1:1987}
770 @noindent
771 [ISO 8859-1]
772 @quotation
773 International Organization for Standardization (ISO), ``Information
774 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 1:
775 Latin Alphabet No.1'', ISO 8859-1:1987.
776 @end quotation
777
778
779
780 @node iso-8859-1, ISO 8859-2, ISO 8859-1, Glossary
781 @subsection iso-8859-1
782
783 @cindex{iso-8859-1}@strong{iso-8859-1} is a MIME charset (@ref{MIME
784 charset}) for west-European languages written by Latin script.@refill
785
786 ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F!"(BASCII (@ref{ASCII}) $B$K(B ISO 8859-1
787 (@ref{ISO 8859-1}) $B$r(B 8bit (@ref{8bit}) $B$GId9f3HD%(B (@ref{Code
788 extension})$B$7$F$$$k!#(B@refill
789
790 It is defined in RFC 2046 (@ref{RFC 2046}).
791
792
793 @node ISO 8859-2, iso-8859-2, iso-8859-1, Glossary
794 @subsection ISO 8859-2
795
796 @cindex{ISO 8859-2}@cindex{ISO 8859-2:1987}
797 @noindent
798 [ISO 8859-2]
799 @quotation
800 International Organization for Standardization (ISO), ``Information
801 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 2:
802 Latin alphabet No.2'', ISO 8859-2:1987.
803 @end quotation
804
805
806
807 @node iso-8859-2, ISO 8859-3, ISO 8859-2, Glossary
808 @subsection iso-8859-2
809
810 @cindex{iso-8859-2}@strong{iso-8859-2} is a MIME charset (@ref{MIME
811 charset}) for east-European languages written by Latin script.@refill
812
813 ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F!"(BASCII (@ref{ASCII}) $B$K(B ISO 8859-2
814 (@ref{ISO 8859-2}) $B$r(B 8bit (@ref{8bit}) $B$GId9f3HD%(B (@ref{Code
815 extension})$B$7$F$$$k!#(B@refill
816
817 It is defined in RFC 2046 (@ref{RFC 2046}).
818
819
820 @node ISO 8859-3, ISO 8859-4, iso-8859-2, Glossary
821 @subsection ISO 8859-3
822
823 @cindex{ISO 8859-3}@cindex{ISO 8859-3:1988}
824 @noindent
825 [ISO 8859-3]
826 @quotation
827 International Organization for Standardization (ISO), ``Information
828 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 3:
829 Latin alphabet No.3'', ISO 8859-3:1988.
830 @end quotation
831
832
833
834 @node ISO 8859-4, ISO 8859-5, ISO 8859-3, Glossary
835 @subsection ISO 8859-4
836
837 @cindex{ISO 8859-4}@cindex{ISO 8859-4:1988}
838 @noindent
839 [ISO 8859-4]
840 @quotation
841 International Organization for Standardization (ISO), ``Information
842 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 4:
843 Latin alphabet No.4'', ISO 8859-4:1988.
844 @end quotation
845
846
847
848 @node ISO 8859-5, iso-8859-5, ISO 8859-4, Glossary
849 @subsection ISO 8859-5
850
851 @cindex{ISO 8859-5}@cindex{ISO 8859-5:1988}
852 @noindent
853 [ISO 8859-5]
854 @quotation
855 International Organization for Standardization (ISO), ``Information
856 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 5:
857 Latin/Cyrillic alphabet'', ISO 8859-5:1988.
858 @end quotation
859
860
861
862 @node iso-8859-5, ISO 8859-6, ISO 8859-5, Glossary
863 @subsection iso-8859-5
864
865 @cindex{iso-8859-5}@strong{iso-8859-5} is a MIME charset (@ref{MIME
866 charset}) for Cyrillic script.@refill
867
868 ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F!"(BASCII (@ref{ASCII}) $B$K(B ISO 8859-5
869 (@ref{ISO 8859-5}) $B$r(B 8bit (@ref{8bit}) $B$GId9f3HD%(B (@ref{Code
870 extension})$B$7$F$$$k!#(B@refill
871
872 It is defined in RFC 2046 (@ref{RFC 2046}).
873
874
875 @node ISO 8859-6, ISO 8859-7, iso-8859-5, Glossary
876 @subsection ISO 8859-6
877
878 @cindex{ISO 8859-6}@cindex{ISO 8859-6:1987}
879 @noindent
880 [ISO 8859-6]
881 @quotation
882 International Organization for Standardization (ISO), ``Information
883 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 6:
884 Latin/Arabic alphabet'', ISO 8859-6:1987.
885 @end quotation
886
887
888
889 @node ISO 8859-7, iso-8859-7, ISO 8859-6, Glossary
890 @subsection ISO 8859-7
891
892 @cindex{ISO 8859-7}@cindex{ISO 8859-7:1987}
893 @noindent
894 [ISO 8859-7]
895 @quotation
896 International Organization for Standardization (ISO), ``Information
897 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 7:
898 Latin/Greek alphabet'', ISO 8859-7:1987.
899 @end quotation
900
901
902
903 @node iso-8859-7, ISO 8859-8, ISO 8859-7, Glossary
904 @subsection iso-8859-7
905
906 @cindex{iso-8859-7}@strong{iso-8859-7} is a MIME charset (@ref{MIME
907 charset}) for Greek script.@refill
908
909 ISO 2022 (@ref{ISO 2022}) $B$K4p$$$F!"(BASCII (@ref{ASCII}) $B$K(B ISO 8859-7
910 (@ref{ISO 8859-7}) $B$r(B 8bit (@ref{8bit}) $B$GId9f3HD%(B (@ref{Code
911 extension})$B$7$F$$$k!#(B@refill
912
913 It is defined in RFC 1947.
914
915 @cindex{iso-8859-7}@cindex{Informational}@cindex{RFC 1947}
916 @noindent
917 [iso-8859-7: RFC 1947]
918 @quotation
919 D. Spinellis, ``Greek Character Encoding for Electronic Mail Messages'',
920 May 1996, Informational.
921 @end quotation
922
923
924
925 @node ISO 8859-8, ISO 8859-9, iso-8859-7, Glossary
926 @subsection ISO 8859-8
927
928 @cindex{ISO 8859-8}@cindex{ISO 8859-8:1988}
929 @noindent
930 [ISO 8859-8]
931 @quotation
932 International Organization for Standardization (ISO), ``Information
933 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 8:
934 Latin/Hebrew alphabet'', ISO 8859-8:1988.
935 @end quotation
936
937
938
939 @node ISO 8859-9, ISO-IR-165, ISO 8859-8, Glossary
940 @subsection ISO 8859-9
941
942 @cindex{ISO 8859-9}@cindex{ISO 8859-9:1990}
943 @noindent
944 [ISO 8859-9]
945 @quotation
946 International Organization for Standardization (ISO), ``Information
947 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 9:
948 Latin alphabet No.5'', ISO 8859-9:1990.
949 @end quotation
950
951
952
953 @node ISO-IR-165, JIS X0201, ISO 8859-9, Glossary
954 @subsection ISO-IR-165, CCITT Extended GB
955
956 CCITT $B$,EPO?$7$?!"Cf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=(B
957 $B$9$k$?$a$N(B 94x94-character set (@ref{94x94-character set})$B!#(B@refill
958
959 GB 2312 (@ref{GB 2312}) $B$H(B GB 8565 $BI=#2(B (@ref{GB 8865.2}) $B$K(B 150 $BJ8;z$[(B
960 $B$I$rDI2C$7$?$b$N$i$7$$!#(B@refill
961
962 ISO 2022 (@ref{ISO 2022}) $B$G$N=*C<J8;z$O(B `E' $B$G$"$k!#(B
963
964
965 @node JIS X0201, JIS C6226, ISO-IR-165, Glossary
966 @subsection JIS X0201
967
968 ISO 646 (@ref{ISO 646}) $B$NJQ<o$N#1$D$G$"$k(B Latin $BJ8;z=89g$H(B 1 byte $B$N%+(B
969 $B%?%+%JJ8;z=89g$+$i$J$k!#(B@refill
970
971 $B85$O(B @cindex{JIS C6220-1976}@strong{JIS C6220-1976} $B$H8@$C$?$,(B @cindex{JIS
972 X0201}@strong{JIS
973 X0201} $B$KHV9f$,JQ99$5$l$?!#(B
974
975 @cindex{JIS X0201-1976}@cindex{JIS X 0201-1976:}
976 @noindent
977 [JIS X0201-1976]
978 @quotation
979 $BF|K\5,3J6(2q(B (Japanese Standards Association),$B!X>pJs8r49MQId9f!Y(B, ``Code
980 for Information Interchange'', JIS X 0201-1976:.
981 @end quotation
982
983
984 $B$^$?!"(B1996 $BG/$K2~DjHG$,=P$kM=Dj!#(B
985
986 @cindex{JIS X0201-1996?}@cindex{JIS X 0201:1996? draft}
987 @noindent
988 [JIS X0201-1996?]
989 @quotation
990 $BF|K\5,3J6(2q(B (Japanese Standards Association),$B!X#7%S%C%H5Z$S#8%S%C%H$N>p(B
991 $BJs8r49MQId9f2=J8;z=89g!Y(B, ``7-bit and 8-bit coded character sets for
992 information interchange'', JIS X 0201:1996? draft.
993 @end quotation
994
995
996
997 @node JIS C6226, JIS X0208, JIS X0201, Glossary
998 @subsection JIS C6226-1978
999
1000 $BF|K\8l$rI=$9$?$a$K:n$i$l$?(B 94x94-character set (@ref{94x94-character
1001 set})$B!#F|K\$N9q2HI8=`!#(BJIS X0208-1978 $B$H$b$$$&!#(B@refill
1002
1003 (cf. @ref{JIS X0208})
1004
1005
1006
1007 @node JIS X0208, JIS X0212, JIS C6226, Glossary
1008 @subsection JIS X0208
1009
1010 $BF|K\8l$rI=$9$?$a$K:n$i$l$?(B 94x94-character set (@ref{94x94-character
1011 set})$B!#F|K\$N9q2HI8=`!#(B1978 $BG/HG!"(B1983 $BG/HG!"(B1990 $BG/HG$,$"$k$,!"(BInternet
1012 $B$G$O(B 1983 $BG/HG$,$b$C$H$bNI$/;H$o$l$F$$$k!#(B@refill
1013
1014 JIS X0208 $B$O5-9f!"?t;z!"%m!<%^;z!"$R$i$,$J!"%+%?%+%J!"%.%j%7%cJ8;z!"%-%j(B
1015 $B%kJ8;z!"7S@~AG!"Bh#1?e=`!"Bh#2?e=`$N4A;z$,4^$^$l$k!#C"$7!"(B1983 $BG/HG$N0l(B
1016 $BIt$N5-9f$H7S@~AG$O(B 1978 $BG/HG$K$O$J$$!#$^$?!"0lIt$N4A;z$N;z7A$,(B 1983 $BG/HG(B
1017 $B$G$OJQ99$5$l!"$^$?!"Bh#1?e=`$HBh#2?e=`$,F~$lBX$o$C$F$$$?$j$9$k!#$3$N$?$a!"(B
1018 1978 $BG/HG$H(B 1983 $BG/HG$O0[$J$kJ8;z=89g$H$7$F07$o$l$k!#(B@refill
1019
1020 1990 $BG/$N2~Dj$G$O(B 1983 $BG/HG$KBP$9$kDI2C$,9T$o$l$?!#$3$N$?$a!"(B1990 $BG/HG(B
1021 $B$r;X<($9$k>l9g$OA0$K99?7%7!<%1%s%9$rMQ$$$k!#(B
1022
1023 @cindex{JIS X0208-1978}@cindex{JIS C6226:1978}
1024 @noindent
1025 [JIS X0208-1978]
1026 @quotation
1027 $BF|K\5,3J6(2q(B (Japanese Standards Association),$B!X>pJs8r49MQ4A;zId9f7O!Y(B,
1028 ``Code of the Japanese graphic character set for information
1029 interchange'', JIS C6226:1978.
1030 @end quotation
1031
1032 @cindex{JIS X0208-1983,1990}@cindex{JIS X0208:1983,1990}
1033 @noindent
1034 [JIS X0208-1983,1990]
1035 @quotation
1036 $BF|K\5,3J6(2q(B (Japanese Standards Association),$B!X>pJs8r49MQ4A;zId9f7O!Y(B,
1037 ``Code of the Japanese graphic character set for information
1038 interchange'', JIS X0208:1983,1990.
1039 @end quotation
1040
1041
1042 $B$^$?!"(B1996 $BG/$K2~DjHG$,=PHG$5$l$kM=Dj!#!J;z7A$NJQ99$O9T$o$l$J$$$N$GJ8(B
1043 $B;z=89g$H$7$F$O(B 1990 $BG/HG$HF10l$G$"$k!K(B
1044
1045 @cindex{JIS X0208-1996?}@cindex{JIS X 0208:1996? draft}
1046 @noindent
1047 [JIS X0208-1996?]
1048 @quotation
1049 $BF|K\5,3J6(2q(B (Japanese Standards Association),$B!X#7%S%C%H5Z$S#8%S%C%H$N(B
1050 $B#2%P%$%H>pJs8r49MQId9f2=4A;z=89g!Y(B, ``7-bit and 8-bit double byte coded
1051 Kanji sets for information interchange'', JIS X 0208:1996? draft.
1052 @end quotation
1053
1054
1055
1056 @node JIS X0212, koi8-r, JIS X0208, Glossary
1057 @subsection JIS X0212-1990
1058
1059 JIS X0208 (@ref{JIS X0208}) $B$K$J$+$C$?J8;z$r=8$a$?(B 94x94-character set
1060 (@ref{94x94-character set})$B!#!VJd=u4A;z!W$H$b8F$P$l$k!#F|K\$N9q2HI8=`!#(B
1061 ISO 2022 (@ref{ISO 2022}) $B$G$N=*C<J8;z$O(B `D'.
1062
1063
1064 @node koi8-r, KS C5601, JIS X0212, Glossary
1065 @subsection koi8-r
1066
1067 A MIME charset (@ref{MIME charset}) for Cyrillic script for Russian or
1068 other languages.@refill
1069
1070 It is a 1 byte 8bit (@ref{8bit}) coded character set (@ref{coded
1071 character set}), not based on ISO 2022 (@ref{ISO 2022}). It is a
1072 de-fact standard.@refill
1073
1074 It is defined in RFC 1489.@refill
1075
1076 @cindex{RFC 1489}
1077 @noindent
1078 [RFC 1489]
1079 @quotation
1080 A. Chernov, ``Registration of a Cyrillic Character Set'', July 1993.
1081 @end quotation
1082
1083
1084
1085 @node KS C5601, message, koi8-r, Glossary
1086 @subsection KS C5601-1987
1087
1088 A 94x94-character set (@ref{94x94-character set}) for Korean language
1089 (Hangul script). Korean Standard. Final byte of ISO 2022 (@ref{ISO
1090 2022}) is `C'.
1091
1092 @cindex{KS C5601}@cindex{KS C 5601:1987}
1093 @noindent
1094 [KS C5601]
1095 @quotation
1096 Korea Industrial Standards Association, ``Code for Information
1097 Interchange (Hangul and Hanja)'', KS C 5601:1987.
1098 @end quotation
1099
1100
1101
1102 @node message, message/rfc822, KS C5601, Glossary
1103 @subsection message
1104
1105 $B$3$3$G$O(B RFC 822 (@ref{RFC 822}) $B$GDj5A$5$l$k(B mail $B$H(B RFC 1036 (@ref{RFC
1106 1036}) $B$GDj5A$5$l$k(B news $B5-;v$NAm>N$H$7$FMQ$$$k!#(B
1107
1108
1109 @node message/rfc822, method, message, Glossary
1110 @subsection message/rfc822
1111
1112 @cindex{message/rfc822}@strong{message/rfc822} indicates that the body
1113 contains an encapsulated message, with the syntax of an RFC 822
1114 (@ref{RFC 822}) message. It is the replacement of traditional RFC 934
1115 (@ref{RFC 934}) encapsulation. It is defined in RFC 2046 (@ref{RFC
1116 2046}).
1117
1118
1119 @node method, MIME, message/rfc822, Glossary
1120 @subsection method
1121
1122 tm $B$GFCDj$N<oN`$N(B data $B$r:F@8$7$?$H$-<B:]$K$=$N=hM}$r9T$J$&(B
1123 program. Emacs Lisp $B$G=q$+$l$?(B @cindex{internal method}@strong{internal
1124 method} $B$H(B C $B$d(B script $B8@8l$J$I$G=q$+$l$?(B @cindex{external
1125 method}@strong{external method} $B$,$"$k!#(B@refill
1126
1127 (cf. @ref{(tm-view-en)method})
1128
1129
1130
1131 @node MIME, MIME charset, method, Glossary
1132 @subsection MIME
1133
1134 MIME stands for @cindex{Multipurpose Internet Mail
1135 Extensions}@strong{Multipurpose Internet Mail Extensions}, it is an
1136 extension for RFC 822 (@ref{RFC 822}).@refill
1137
1138 According to RFC 2045:@refill
1139
1140 STD 11, RFC 822, defines a message representation protocol specifying
1141 considerable detail about US-ASCII message headers, and leaves the
1142 message content, or message body, as flat US-ASCII text. This set of
1143 documents, collectively called the Multipurpose Internet Mail
1144 Extensions, or MIME, redefines the format of messages to allow
1145 for@refill
1146
1147 @enumerate
1148 @item
1149 textual message bodies in character sets other than US-ASCII,
1150 @item
1151 an extensible set of different formats for non-textual message
1152 bodies,
1153 @item
1154 multi-part message bodies, and
1155 @item
1156 textual header information in character sets other than US-ASCII.
1157 @end enumerate
1158
1159
1160 It is defined in RFC 2045 (@ref{RFC 2045}), RFC 2046 (@ref{RFC 2046}),
1161 RFC 2047 (@ref{encoded-word}), RFC 2048 (@ref{RFC 2048}) and RFC 2049
1162 (@ref{RFC 2049}).
1163
1164
1165 @node MIME charset, MTA, MIME, Glossary
1166 @subsection MIME charset
1167
1168 Coded character set (@ref{Coded character set}) used in Content-Type
1169 field (@ref{Content-Type field}) or charset parameter of encoded-word
1170 (@ref{encoded-word}).@refill
1171
1172 It is defined in RFC 2045 (@ref{RFC 2045}).@refill
1173
1174 iso-2022-jp (@ref{iso-2022-jp}) $B$d(B euc-kr (@ref{euc-kr}) $B$O$=$N#1$D!#(B
1175 $B!J$3$3$G$O!"(BMIME charset $B$OJ8;z=89g(B (@ref{Character set})$B$H6hJL$7$F>.J8(B
1176 $B;z$G=q$$$F$$$k!K(B
1177
1178
1179 @node MTA, MUA, MIME charset, Glossary
1180 @subsection MTA
1181
1182 @cindex{Message Transfer Agent}@strong{Message Transfer Agent} $B$NN,$G!"(B
1183 sendmail $B$J$I$N(B mail $BG[Aw(B program $B$H(B news server $B$NAm>N!#(B@refill
1184
1185 (cf. @ref{MUA})
1186
1187
1188
1189 @node MUA, MULE, MTA, Glossary
1190 @subsection MUA
1191
1192 @cindex{Message User Agent}@strong{Message User Agent} $B$NN,$G!"(Bmail
1193 reader $B$H(B news reader $B$NAm>N!#(B@refill
1194
1195 (cf. @ref{MTA})
1196
1197
1198
1199 @node MULE, multipart, MUA, Glossary
1200 @subsection MULE
1201
1202 $BH>ED(B $B7u0l;a$i$,:n$C$?!"B?8@8l$5$l$?(B Emacs (@ref{Emacs}).@refill
1203
1204 [MULE] Nishikimi M., Handa K. and Tomura S., ``Mule: MULtilingual
1205 Enhancement to GNU Emacs'', Proc. of INET'93, August, 1993.@refill
1206
1207 $B8=:_!"(BMULE $B$N5!G=$r(B Emacs $B$K(B merge $B$9$k:n6H$,9T$o$l$F$*$j!"(Balpha $BHG(B
1208 (ftp://etlport.etl.go.jp/pub/mule/mule-19.33-gamma.taz) $B$,B8:_$9$k!#(B
1209
1210 $B$=$NB>!"(BXEmacs $B$K(B merge $B$7$?$b$N$bB8:_$9$k!#(B@refill
1211
1212 $B$3$N$?$a!"8=:_$G$OB?8@8l(B Emacs $B$O!"85!9$N(B MULE $B$r4^$a$F#3<oN`$"$k$3$H$K(B
1213 $B$J$k!#(B@refill
1214
1215 $B$=$3$G!"$3$3$G$O!"B?8@8l(B Emacs $B$NAm>N$r(B @cindex{mule}@strong{mule}, $B85!9(B
1216 $B$N(B MULE $B$r(B @cindex{MULE}@strong{MULE}, mule $B5!G=$r(B merge $B$7$?(B Emacs $B$r(B
1217 @cindex{Emacs/mule}@strong{Emacs/mule}, mule $B5!G=$r(B merge $B$7$?(B XEmacs $B$r(B
1218 @cindex{XEmacs/mule}@strong{XEmacs/mule} $B$H8F$V$3$H$K$9$k!#(B
1219
1220
1221 @node multipart, multipart/alternative, MULE, Glossary
1222 @subsection Multipart
1223
1224 @cindex{multipart}@strong{multipart} means media type (@ref{media type})
1225 to insert multiple entities (@ref{entities}) in a single body. Or it
1226 also indicates a message consists of multiple entities.@refill
1227
1228 There are following subtypes registered in RFC 2046 (@ref{RFC 2046}):
1229
1230 @itemize @bullet
1231 @item
1232 multipart/mixed (@ref{multipart/mixed})
1233 @item
1234 multipart/alternative (@ref{multipart/alternative})
1235 @item
1236 multipart/digest (@ref{multipart/digest})
1237 @item
1238 multipart/parallel (@ref{multipart/parallel})
1239 @end itemize
1240
1241 @noindent
1242 and registered in RFC 1847 (@ref{Security multipart}):
1243
1244 @itemize @bullet
1245 @item
1246 multipart/signed (@ref{multipart/signed})
1247 @item
1248 multipart/encrypted (@ref{multipart/encrypted})
1249 @end itemize
1250
1251
1252
1253 @node multipart/alternative, multipart/digest, multipart, Glossary
1254 @subsection multipart/alternative
1255
1256 @cindex{multipart/digest}@strong{multipart/digest} is one of multipart
1257 (@ref{multipart}) media types. This type is syntactically identical to
1258 multipart/mixed (@ref{multipart/mixed}), but the semantics are
1259 different. In particular, each of the body parts is an ``alternative''
1260 version of the same information.@refill
1261
1262 (cf. @ref{RFC 2046})
1263
1264
1265
1266 @node multipart/digest, multipart/encrypted, multipart/alternative, Glossary
1267 @subsection multipart/digest
1268
1269 @cindex{multipart/digest}@strong{multipart/digest} is one of multipart
1270 (@ref{multipart}) media types. This type is syntactically identical to
1271 multipart/mixed (@ref{multipart/mixed}), but the semantics are
1272 different. In particular, in a digest, the default Content-Type value
1273 for a body part is changed from text/plain (@ref{text/plain}) to
1274 message/rfc822 (@ref{message/rfc822}).@refill
1275
1276 This is the replacement of traditional RFC 1153 (@ref{RFC 1153}) based
1277 encapsulation (@ref{encapsulation}).@refill
1278
1279 (cf. @ref{RFC 2046})
1280
1281
1282
1283 @node multipart/encrypted, multipart/mixed, multipart/digest, Glossary
1284 @subsection multipart/encrypted
1285
1286 RFC 1847 $B$GDj5A$5$l$?(B Security multipart (@ref{Security multipart}) $B$N#1(B
1287 $B$D$G!"0E9f2=$5$l$?(B message $B$rI=8=$9$k$N$KMQ$$$k!#(B@refill
1288
1289 (cf. @ref{PGP/MIME})
1290
1291
1292
1293 @node multipart/mixed, multipart/parallel, multipart/encrypted, Glossary
1294 @subsection multipart/mixed
1295
1296 Primary and default subtype of multipart (@ref{multipart}), it is used
1297 when the body parts are independent and need to be bundled in a
1298 particular order.@refill
1299
1300 (cf. @ref{RFC 2046})
1301
1302
1303
1304 @node multipart/parallel, multipart/signed, multipart/mixed, Glossary
1305 @subsection multipart/parallel
1306
1307 @cindex{multipart/parallel}@strong{multipart/parallel} is a subtype of
1308 multipart (@ref{multipart}). This type is syntactically identical to
1309 multipart/mixed (@ref{multipart/mixed}), but the semantics are
1310 different. In particular, in a parallel entity, the order of body parts
1311 is not significant.@refill
1312
1313 (cf. @ref{RFC 2046})
1314
1315
1316
1317 @node multipart/signed, PGP, multipart/parallel, Glossary
1318 @subsection multipart/signed
1319
1320 RFC 1847 $B$GDj5A$5$l$?(B Security multipart (@ref{Security multipart}) $B$N#1(B
1321 $B$D$G!"EE;R=pL>$rI=8=$9$k$N$KMQ$$$k!#(B@refill
1322
1323 (cf. @ref{PGP/MIME})
1324
1325
1326
1327 @node PGP, PGP-kazu, multipart/signed, Glossary
1328 @subsection PGP
1329
1330 Phil Zimmermann $B;a$,:n@.$7$?8x3+800E9f=hM}7O$N#1$D!#(Bmessage
1331 (@ref{message}) $B$N0E9f2=$dEE;R=pL>$r9T$&$3$H$,$G$-$k!#(BPretty Good
1332 Privacy $B$NN,!#(B@refill
1333
1334 $BEAE}E*$J(B PGP $B$G$O(B encapsulation (@ref{encapsulation}) $B$K(B RFC 934
1335 (@ref{RFC 934})$B$K=`$8$?J}K!$rMQ$$$k!#$3$l$O(B MIME (@ref{MIME}) $B$HL7=b$9$k(B
1336 $B$N$G(B PGP/MIME (@ref{PGP/MIME}) $B$,Ds0F$5$l$F$$$k!#0lJ}!"(BMIME $B$K$*$$$F(B PGP
1337 $B$N(Bencapsulation $B$rMQ$$$kJ}K!(B (cf. @ref{PGP-kazu})
1338 $B$bMxMQ$5$l$F$-$?!#$7$+$7!":#8e$O(B PGP/MIME $B$KE}0l$7$F$$$/J}$,K>$^$7$$!#(B
1339 @refill
1340
1341 @cindex{PGP}@cindex{Informational}@cindex{RFC 1991}
1342 @noindent
1343 [PGP: RFC 1991]
1344 @quotation
1345 D. Atkins, W. Stallings and P. Zimmermann, ``PGP Message Exchange
1346 Formats'', August 1996, Informational.
1347 @end quotation
1348
1349
1350
1351
1352 @node PGP-kazu, PGP/MIME, PGP, Glossary
1353 @subsection PGP-kazu
1354
1355 $B;3K\(B $BOBI'(B $B;a$,Ds0F$7$?(B MIME (@ref{MIME}) $B$G(B PGP (@ref{PGP}) $B$rMxMQ$9$k$?(B
1356 $B$a$NJ}K!$r$3$3$G$O(B @cindex{PGP-kazu}@strong{PGP-kazu} $B$H8F$V$3$H$K$9$k!#(B
1357
1358 PGP-kazu $B$O(B @cindex{application/pgp}@strong{application/pgp} $B$H$$$&(B
1359 content-type (@ref{content-type}) $B$rDj5A$9$k!#(B@refill
1360
1361 application/pgp $B$N(B part $B$G$O(B PGP $B$N(B encapsulation (@ref{encapsulation})
1362 $B$,MQ$$$i$l$k!#(BPGP $B$N(B encapsulation (cf. @ref{RFC 934})
1363 $B$H(B MIME $B$N(B encapsulation $B$OL7=b$9$k$N$G!"(BPGP $B$N(B encapsulation $B$r2r$+$J(B
1364 $B$$8B$j!"Cf$K4^$^$l$?(B MIME message $B$rFI$`$3$H$,$G$-$J$/$J$k!#B($A!"(B
1365 PGP-kazu $B$KBP1~$7$F$$$J$$(B MIME $B$KBP1~$7$?(B MUA (@ref{MUA}) $B$O$=$N(B part $B$,(B
1366 $BFI$a$J$/$J$k!#$=$NBe$o$j!"(BMIME $B$KBP1~$7$F$$$J$$(B PGP $BBP1~$N(B MUA
1367 (@ref{MUA}) $B$G$b(B message $B$rFI$`$3$H$,$G$-$k!#(B@refill
1368
1369 PGP-kazu $B$G$O(B MUA $B$O(B PGP $B$N$H(B MIME $B$N$H$$$&#2$D$N(B encapsulation $B$rCN$i$J(B
1370 $B$1$l$P$J$i$J$$!#$^$?!"(Bapplication/pgp part $B$r(B parse $B$9$k$?$a$K$O!"$^$:!"(B
1371 pgp $B$N=hM}$r9T$o$J$1$l$P$J$i$J$$$N$G!"(Bparse $B=hM}$,J#;($K$J$k!#(B@refill
1372
1373 $B$^$?!"(BInternet $B$G$O:#8e(B PGP/MIME (@ref{PGP/MIME}) $B$NJ}8~$GI8=`2=$7$F$$$3(B
1374 $B$&$H$$$&$3$H$G9g0U$,<h$l$F$$$k!#$h$C$F!":#8e$O(B PGP-kazu $B$OMQ$$$J$$$N$,K>(B
1375 $B$^$7$$!#(B@refill
1376
1377 [draft-kazu-pgp-mime-00.txt] Yamamoto K., ``PGP MIME Integration'',
1378 October, 1995
1379
1380
1381 @node PGP/MIME, Quoted-Printable, PGP-kazu, Glossary
1382 @subsection PGP/MIME
1383
1384 Michael Elkins $B;a$,Ds0F$7$?(B MIME (@ref{MIME}) $B$G(B PGP (@ref{PGP}) $B$rMxMQ(B
1385 $B$9$k$?$a$NJ}K!!#(B@refill
1386
1387 RFC 1847 (@ref{Security multipart}) $B$K4p$-!"(BMIME $B$N(B multipart $B$K$h$k(B
1388 encapsulation (@ref{encapsulation}) $B$r9T$&!#$3$N$?$a!"(BMIME $B$N<+A3$J3HD%(B
1389 $B$K$J$C$F$$$k!#$7$+$7!"EAE}E*$J(B PGP$B$H$N8_49@-$,<:$o$l$F$$$k!#(B@refill
1390
1391 PGP/MIME $B$G$O(B PGP-kazu (@ref{PGP-kazu}) $B$H0[$J$j!"(BMIME $B$N(B encapsulation
1392 $B$N$_$rMQ$$$k!#$^$?!"$3$N$?$a!"(BPGP $B$N=hM}$r9T$&A0$K(B message $B$N(B parse $B$r9T(B
1393 $B$&$3$H$,$G$-$k!#(B@refill
1394
1395 Internet $B$G$O:#8e(B PGP/MIME (@ref{PGP/MIME}) $B$NJ}8~$GI8=`2=$7$F$$$3$&$H$$(B
1396 $B$&$3$H$G9g0U$,<h$l$F$$$k!#$h$C$F!":#8e$O(B PGP $B$rMQ$$$k>l9g$O(B PGP/MIME$B$rMQ(B
1397 $B$$$k$N$,K>$^$7$$!#(B
1398
1399 @cindex{PGP/MIME}@cindex{Standards Track}@cindex{RFC 2015}
1400 @noindent
1401 [PGP/MIME: RFC 2015]
1402 @quotation
1403 M. Elkins, ``MIME Security with Pretty Good Privacy (PGP)'', October
1404 1996, Standards Track.
1405 @end quotation
1406
1407
1408
1409 @node Quoted-Printable, RFC 821, PGP/MIME, Glossary
1410 @subsection Quoted-Printable
1411
1412 @cindex{Quoted-Printable}@strong{Quoted-Printable} is a transfer
1413 encoding method of MIME (@ref{MIME}) defined in RFC 2045 (@ref{RFC
1414 2045}).@refill
1415
1416 If the data being encoded are mostly US-ASCII text, the encoded form of
1417 the data remains largely recognizable by humans.@refill
1418
1419 (cf. @ref{Base64})
1420
1421
1422
1423 @node RFC 821, RFC 822, Quoted-Printable, Glossary
1424 @subsection RFC 821
1425
1426 @cindex{SMTP}@strong{SMTP} $B$H8F$P$l$k(B Internet mail $B$NG[AwK!$NI8=`$rDj$a(B
1427 $B$F$$$k(B RFC.
1428
1429 @cindex{SMTP}@cindex{STD 10}@cindex{RFC 821}
1430 @noindent
1431 [SMTP: RFC 821]
1432 @quotation
1433 J. Postel, ``Simple Mail Transfer Protocol'', August 1982, STD 10.
1434 @end quotation
1435
1436
1437
1438 @node RFC 822, RFC 934, RFC 821, Glossary
1439 @subsection RFC 822
1440
1441 Internet mail $B$N<g$K(B @cindex{message header}@strong{message header} $B$K4X$9$k7A<0$K(B
1442 $B4X$9$kI8=`$rDj$a$F$$$k(B RFC.
1443
1444 @noindent
1445 @strong{[Memo]}
1446 @quotation
1447
1448 news message $B$b$3$l$K=`$8$F$$$k$N$G!"(B@cindex{Internet
1449 mail}@strong{Internet mail} $B$H=q$/$h$j$b!"(B@cindex{Internet
1450 message}@strong{Internet message} $B$H=q$$$?J}$,NI$$$+$b$7$l$J$$!#(B
1451 @end quotation
1452
1453
1454 @cindex{STD 11}@cindex{RFC 822}
1455 @noindent
1456 [RFC 822]
1457 @quotation
1458 D. Crocker, ``Standard for the Format of ARPA Internet Text Messages'',
1459 August 1982, STD 11.
1460 @end quotation
1461
1462
1463
1464 @node RFC 934, RFC 1036, RFC 822, Glossary
1465 @subsection RFC 934
1466
1467 Internet mail (@ref{RFC 822}) $B$N(B
1468 @cindex{encapsulation}@strong{encapsulation} (@ref{encapsulation}) $B$NJ}(B
1469 $BK!$rDj$a$?(B RFC.@refill
1470
1471 MIME (@ref{MIME}) $B$HL7=b$9$k$N$G!"8=:_$G$O(B message/rfc822
1472 (@ref{message/rfc822}) $B$rMQ$$$k$Y$-$G$"$k!#(B
1473
1474
1475 @cindex{RFC 934}
1476 @noindent
1477 [RFC 934]
1478 @quotation
1479 Marshall T. Rose and Einar A. Stefferud, ``Proposed Standard for Message
1480 Encapsulation'', January 1985.
1481 @end quotation
1482
1483
1484
1485 @node RFC 1036, RFC 1153, RFC 934, Glossary
1486 @subsection RFC 1036
1487
1488 USENET $B$G$N(B message $B$N7A<0$rDj$a$?(B RFC. RFC 822 (@ref{RFC 822})$B$N(B subset
1489 $B$K$J$C$F$$$k!#(BInternet $B$NI8=`$G$O$J$$$,!"(BUSENET $B0J30$N(B netnews $B$G$b$3$l(B
1490 $B$K=`$8$F$$$k$b$N$,B?$$!#(B
1491
1492 @cindex{USENET}@cindex{RFC 1036}
1493 @noindent
1494 [USENET: RFC 1036]
1495 @quotation
1496 M. Horton and R. Adams, ``Standard for Interchange of USENET Messages'',
1497 December 1987, (obsolete RFC 850).
1498 @end quotation
1499
1500
1501
1502 @node RFC 1153, RFC 1557, RFC 1036, Glossary
1503 @subsection RFC 1153
1504
1505 $BJ#?t$N(B Internet mail (@ref{RFC 822}) $B$r(B
1506 @cindex{encapsulation}@strong{encapsulation} (@ref{encapsulation}) $B$9$k(B
1507 $B$?$a$NJ}K!$rDj$a$?(B RFC. RFC 934 (@ref{RFC 934}) $B$rMQ$$$k!#(B@refill
1508
1509 MIME (@ref{MIME}) $B$HL7=b$9$k$N$G!"8=:_$G$O(B message/rfc822
1510 (@ref{message/rfc822}) $B$rMQ$$$?(B multipart (@ref{multipart}) $B$rMQ$$$k$Y$-(B
1511 $B$G$"$k!#(B@refill
1512
1513 (cf. @ref{multipart/digest})
1514
1515
1516 @cindex{RFC 1153}
1517 @noindent
1518 [RFC 1153]
1519 @quotation
1520 F. Wancho, ``Digest Message Format'', April 1990.
1521 @end quotation
1522
1523
1524
1525 @node RFC 1557, RFC 1922, RFC 1153, Glossary
1526 @subsection RFC 1557
1527
1528 euc-kr (@ref{euc-kr}) $B$H(B iso-2022-kr (@ref{iso-2022-kr}) $B$H$$$&4Z9q8l$N(B
1529 $B$?$a$N(B MIME charset (@ref{MIME charset}) $B$rDj5A$7$F$$$k(B RFC.
1530
1531 @cindex{Informational}@cindex{RFC 1557}
1532 @noindent
1533 [RFC 1557]
1534 @quotation
1535 U. Choi, K. Chon and H. Park, ``Korean Character Encoding for Internet
1536 Messages'', December 1993, Informational.
1537 @end quotation
1538
1539
1540
1541 @node RFC 1922, RFC 2045, RFC 1557, Glossary
1542 @subsection RFC 1922
1543
1544 iso-2022-cn (@ref{iso-2022-cn}), iso-2022-cn-ext
1545 (@ref{iso-2022-cn-ext}), cn-gb (@ref{cn-gb}), cn-big5 (@ref{cn-big5}) $B$H(B
1546 $B$$$C$?Cf9q8l$N$?$a$N(B MIME charset (@ref{MIME charset}) $B$rDj5A$7$F$$$k(B
1547 RFC.@refill
1548
1549 $B$3$l$K2C$($F!"(B@cindex{charset-edition}@strong{charset-edition} $B$H(B
1550 @cindex{charset-extension}@strong{charset-extension} $B$H$$$&(B Content-Type
1551 field (@ref{Content-Type field}) $B$N(B parameter $B$rDj5A$7$F$$$k!#(B
1552
1553 @cindex{Informational}@cindex{RFC 1922}
1554 @noindent
1555 [RFC 1922]
1556 @quotation
1557 Zhu, HF., Hu, DY., Wang, ZG., Kao, TC., Chang, WCH. and Crispin, M.,
1558 ``Chinese Character Encoding for Internet Messages'', March 1996,
1559 Informational.
1560 @end quotation
1561
1562
1563
1564 @node RFC 2045, RFC 2046, RFC 1922, Glossary
1565 @subsection RFC 2045
1566
1567 @cindex{Standards Track}@cindex{RFC 2045}
1568 @noindent
1569 [RFC 2045]
1570 @quotation
1571 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1572 (MIME) Part One: Format of Internet Message Bodies'', November 1996,
1573 Standards Track (obsolete RFC 1521, 1522, 1590).
1574 @end quotation
1575
1576
1577
1578 @node RFC 2046, RFC 2048, RFC 2045, Glossary
1579 @subsection RFC 2046
1580
1581 @cindex{Standards Track}@cindex{RFC 2046}
1582 @noindent
1583 [RFC 2046]
1584 @quotation
1585 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1586 (MIME) Part Two: Media Types'', November 1996, Standards Track (obsolete
1587 RFC 1521, 1522, 1590).
1588 @end quotation
1589
1590
1591
1592 @node RFC 2048, RFC 2049, RFC 2046, Glossary
1593 @subsection RFC 2048
1594
1595 @cindex{Standards Track}@cindex{RFC 2048}
1596 @noindent
1597 [RFC 2048]
1598 @quotation
1599 N. Freed, J. Klensin and J. Postel, ``Multipurpose Internet Mail
1600 Extensions (MIME) Part Four: Registration Procedures'', November 1996,
1601 Standards Track (obsolete RFC 1521, 1522, 1590).
1602 @end quotation
1603
1604
1605
1606 @node RFC 2049, plain text, RFC 2048, Glossary
1607 @subsection RFC 2049
1608
1609 @cindex{Standards Track}@cindex{RFC 2049}
1610 @noindent
1611 [RFC 2049]
1612 @quotation
1613 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1614 (MIME) Part Five: Conformance Criteria and Examples'', November 1996,
1615 Standards Track (obsolete RFC 1521, 1522, 1590).
1616 @end quotation
1617
1618
1619
1620 @node plain text, Security multipart, RFC 2049, Glossary
1621 @subsection plain text
1622
1623 $B=qBN$dAHHG$K4X$9$k>pJs$r;}$?$J$$(B $BJ8;zId9f(B(@ref{Coded character set})$B$N$_(B
1624 $B$GI=8=$5$l$k(B text $B>pJs!#(B(cf. @ref{text/plain})
1625
1626
1627
1628 @node Security multipart, text/enriched, plain text, Glossary
1629 @subsection Security multipart
1630
1631 MIME (@ref{MIME}) $B$G0E9f$dEE;R=qL>$rMQ$$$k$?$a$N7A<0!#(B
1632 @cindex{multipart/signed}@strong{multipart/signed}
1633 (@ref{multipart/signed}) $B$H(B
1634 @cindex{multipart/encrypted}@strong{multipart/encrypted}
1635 (@ref{multipart/encrypted}) $B$H$$$&(B multipart $B$rMQ$$$k!#(BMOSS $B$d(B PGP/MIME
1636 (@ref{PGP/MIME}) $B$O$3$l$K4p$$$F$$$k!#(B
1637
1638 @cindex{Security multipart}@cindex{Standards Track}@cindex{RFC 1847}
1639 @noindent
1640 [Security multipart: RFC 1847]
1641 @quotation
1642 James Galvin, Gale Murphy, Steve Crocker and Ned Freed, ``Security
1643 Multiparts for MIME: Multipart/Signed and Multipart/Encrypted'', October
1644 1995, Standards Track.
1645 @end quotation
1646
1647
1648
1649 @node text/enriched, text/plain, Security multipart, Glossary
1650 @subsection text/enriched
1651
1652 RFC 1521 $B$GDj5A$5$l$?(B @cindex{text/richtext}@strong{text/richtext} $B$KBe(B
1653 $B$o$C$F!"=qBN$dAHHG$K4X$9$k>pJs$r;}$C$?(B text$B$rI=8=$9$k$?$a$N(B media type
1654 (@ref{media type}).
1655
1656 @cindex{text/enriched}@cindex{RFC 1896}
1657 @noindent
1658 [text/enriched: RFC 1896]
1659 @quotation
1660 P. Resnick and A. Walker, ``The text/enriched MIME Content-type'',
1661 February 1996, (obsolete RFC 1563).
1662 @end quotation
1663
1664
1665
1666 @node text/plain, tm-kernel, text/enriched, Glossary
1667 @subsection text/plain
1668
1669 @cindex{text/plain}@strong{text/plain} is a media type (@ref{media
1670 type}) for plain text (@ref{plain text}), defined in RFC 2046 (@ref{RFC
1671 2046}).@refill
1672
1673 The default media type of ``text/plain; charset=us-ascii'' for Internet
1674 mail describes existing Internet practice. That is, it is the type of
1675 body defined by RFC 822 (@ref{RFC 822}).@refill
1676
1677 (cf. @ref{MIME charset}) (cf. @ref{us-ascii})
1678
1679
1680
1681 @node tm-kernel, tm-MUA, text/plain, Glossary
1682 @subsection tm-kernel, tm
1683
1684 Emacs $B$G(B MIME (@ref{MIME}) $B$rMxMQ$9$k$?$a$N(B user interface $B$rDs6!$9$k(B
1685 library $B72!#(B`tools for MIME' $B$NN,!#(B
1686
1687 @noindent
1688 @strong{[$B$I$&$G$bNI$$$3$H(B(^-^;]}
1689 @quotation
1690
1691 @itemize @bullet
1692 @item
1693 tm $B$O(B ``tiny-mime'' $B$NN,$8$c$J$$$i$7$$$>(B (^-^;
1694
1695 @item
1696 tm $B$O:n<T$N%$%K%7%c%k$8$c$J$$$i$7$$$>(B (^-^;
1697
1698 @item
1699 ``Tools for MIME'' $B$NN,$H$$$&$N$O$3$8$D$1$i$7$$$>(B (^-^;
1700 @end itemize
1701 @end quotation
1702
1703
1704
1705 @node tm-MUA, us-ascii, tm-kernel, Glossary
1706 @subsection tm-MUA
1707
1708 tm (@ref{tm-kernel}) $B$rMQ$$$?(B MUA (@ref{MUA}) $B$b$7$/$O(B MUA $B$KBP$9$k(B
1709 extender.@refill
1710
1711 @cindex{tm $BBg@9$j(B package}@strong{tm $BBg@9$j(B package} $B$K$O(B
1712
1713 @itemize @bullet
1714 @item
1715 mh-e (@ref{(mh-e)}) $BMQ$N(B @cindex{tm-mh-e}@strong{tm-mh-e}
1716 @item
1717 GNUS $BMQ$N(B @cindex{tm-gnus}@strong{tm-gnus}
1718 @item
1719 Gnus $BMQ$N(B @cindex{gnus-mime}@strong{gnus-mime} (@ref{(gnus-mime-en)})
1720 @item
1721 VM $BMQ$N(B @cindex{tm-vm}@strong{tm-vm}
1722 @item
1723 RMAIL $BMQ$N(B @cindex{tm-rmail}@strong{tm-rmail}
1724 @end itemize
1725
1726 @noindent
1727 $B$,4^$^$l$F$$$k!#(B
1728
1729 $BFHN)$7$?(B MUA $B$H$7$F$O(B cmail (@ref{(cmail)}) $B$,(B tm $B$rMxMQ2DG=$G$"$k!#(B
1730
1731
1732 @node us-ascii, , tm-MUA, Glossary
1733 @subsection us-ascii
1734
1735 $B%"%a%j%+O"K.$J$I$G;H$o$l$k1Q8l$J$I$rI=8=$9$k$?$a$N(B MIME charset
1736 (@ref{MIME charset}) $B$N#1$D!#(B@refill
1737
1738 ASCII (@ref{ASCII}) $B$N$_$+$i$J$j(B ISO 2022 (@ref{ISO 2022}) $B$K$h$kId9f3H(B
1739 $BD%(B (@ref{Code extension})$B$O5v$5$l$J$$!#(B@refill
1740
1741 Internet mail $B$K$*$1$kI8=`$NId9f2=J8;z=89g(B(@ref{Coded character set})$B$G(B
1742 $B$"$j!"L@<(E*$K(B MIME charset $B$,<($5$l$J$$>l9g$O86B'$H$7$F(B
1743 @cindex{us-ascii}@strong{us-ascii} $B$,;H$o$l$k!#(B@refill
1744
1745 $B$^$?!"(BRFC 822 (@ref{RFC 822}) $B$K$*$1$k(B @cindex{ASCII}@strong{ASCII} $B$O(B
1746 us-ascii $B$r;X$9$b$N$H2r<a$9$Y$-$G$"$k!#(B
1747
1748
1749 @node Setting, Bug report, Introduction, Top
1750 @chapter Setting
1751
1752 In the tm package, two files, @file{mime-setup.el} and
1753 @file{tm-setup.el}, are provided to ease the setup.@refill
1754
1755 The @file{mime-setup.el} is used for the whole MIME related
1756 setup including MIME encoding using @file{tm-edit.el}, while
1757 @file{tm-setup.el} is used to set up tm-MUA only.
1758
1759
1760 @menu
1761 * mime-setup:: Normal setting
1762 * tm-setup:: Setting not to use tm-edit
1763 * setting for VM:: Setting for VM
1764 * manual setting:: Setting up without loading provided setup files
1765 @end menu
1766
1767 @node mime-setup, tm-setup, Setting, Setting
1768 @section Normal setting
1769
1770 If you want normal setting, please use @cindex{mime-setup}@strong{mime-setup}.
1771 For example, please insert following into @file{~/.emacs}:
1772
1773 @lisp
1774 (load "mime-setup")
1775 @end lisp
1776
1777
1778 As @file{mime-setup.el} loads @file{tm-setup.el}, you
1779 don't need to load @file{tm-setup.el} when you use
1780 @file{mime-setup.el} (Description of old version of Gnus FAQ is
1781 wrong!)
1782
1783
1784 @menu
1785 * signature::
1786 * Notice about GNUS:: Notices for GNUS
1787 @end menu
1788
1789 @node signature, Notice about GNUS, mime-setup, mime-setup
1790 @subsection signature
1791
1792 You can set up the @cindex{automatic signature selection
1793 tool}@strong{automatic signature selection
1794 tool} using @file{mime-setup}. If you want to
1795 automatically select the signature file depending on how the message
1796 headers show, add lines like shown below to your .emacs (Refer to the
1797 reference manual of @file{signature.el} for more details).
1798
1799 @lisp
1800 (setq signature-file-alist
1801 '((("Newsgroups" . "jokes") . "~/.signature-jokes")
1802 (("Newsgroups" . ("zxr" "nzr")) . "~/.signature-sun")
1803 (("To" . ("ishimaru" "z-suzuki")) . "~/.signature-sun")
1804 (("To" . "tea") . "~/.signature-jokes")
1805 (("To" . ("sim" "oku" "takuo")) . "~/.signature-formal")
1806 ))
1807 @end lisp
1808
1809
1810
1811 @defvar mime-setup-use-signature
1812
1813 If it is not @code{nil}, @file{mime-setup.el} sets up for
1814 @file{signature.el}. Its default value is @code{t}.
1815 @end defvar
1816
1817
1818
1819 @defvar mime-setup-signature-key-alist
1820
1821 It defines key to bind signature inserting command for each
1822 major-mode. Its default value is following:
1823
1824 @lisp
1825 ((mail-mode . "\C-c\C-w"))
1826 @end lisp
1827
1828
1829 If you want to change, please rewrite it. For example:
1830
1831 @lisp
1832 (set-alist 'mime-setup-signature-key-alist
1833 'news-reply-mode "\C-c\C-w")
1834 @end lisp
1835
1836 @end defvar
1837
1838
1839
1840 @defvar mime-setup-default-signature-key
1841
1842 If key to bind signature inserting command for a major-mode is not found
1843 from @code{mime-setup-signature-key-alist}, its value is used as key.
1844 Its default value is @code{"\C-c\C-s"}.
1845 @end defvar
1846
1847
1848
1849 @node Notice about GNUS, , signature, mime-setup
1850 @subsection Notices for GNUS
1851
1852 When @file{mime-setup.el} sets up for @file{signature.el}, it sets
1853 variable @code{gnus-signature-file} to @code{nil}. Therefore GNUS does
1854 not insert signature automatically when it is sending a message. Reason
1855 of this setting is following:@refill
1856
1857 GNUS inserts signature after @file{tm-edit.el} composed as MIME message.
1858 Therefore signature inserted by GNUS is not processed as a valid MIME
1859 part. In particular, for multipart message, signature places in outside
1860 of MIME part. So MIME MUA might not display it.@refill
1861
1862 Other notice is key bind. In historical reason, key bind to insert
1863 signature is @kbd{C-c C-s} (like mh-e (@ref{(mh-e)})) instead of
1864 @kbd{C-c C-w}. If you change to GNUS's default, please set following:
1865
1866 @lisp
1867 (set-alist 'mime-setup-signature-key-alist 'news-reply-mode "\C-c\C-w")
1868 @end lisp
1869
1870
1871
1872 @node tm-setup, setting for VM, mime-setup, Setting
1873 @section Setting not to use tm-edit
1874
1875 @cindex{tm-setup}@strong{tm-setup} only sets up tm-MUA (@ref{tm-MUA})s.
1876 In other words, it is a setting to avoid to use tm-edit. If you don't
1877 want to compose MIME message or want to use other MIME composer, please
1878 use it instead of @file{mime-setup.el}.@refill
1879
1880 For example, please insert following into @file{~/.emacs}:
1881
1882 @lisp
1883 (load "tm-setup")
1884 @end lisp
1885
1886
1887
1888 @noindent
1889 @strong{[Memo]}
1890 @quotation
1891
1892 If you use @file{mime-setup.el}, you you don't need to load
1893 @file{tm-setup.el}.
1894 @end quotation
1895
1896
1897
1898 @node setting for VM, manual setting, tm-setup, Setting
1899 @section Setting for VM
1900
1901 If you use @cindex{vm}@strong{vm}, please insert following in
1902 @file{~/.vm}:
1903
1904 @lisp
1905 (require 'tm-vm)
1906 @end lisp
1907
1908
1909
1910 @noindent
1911 @strong{[Notice]}
1912 @quotation
1913
1914 If you use @cindex{BBDB}@strong{BBDB}, please insert @code{(require
1915 'tm-vm)} @strong{after} @code{(bbdb-insinuate-vm)}.
1916 @end quotation
1917
1918
1919
1920 @node manual setting, , setting for VM, Setting
1921 @section Setting up without loading provided setup files
1922
1923 You may find the valuable hints in @file{mime-setup.el} or
1924 @file{tm-setup.el} if you want to set up MIME environment
1925 without loading the tm-provided setup files.
1926
1927 @noindent
1928 @strong{[Memo]}
1929 @quotation
1930
1931 Current tm provides some convenient features to expect tm-edit, and
1932 they can not use if @file{mime-setup.el} is not used. If you
1933 want to set up original setting to use tm-edit, please declare
1934 following setting:
1935
1936 @lisp
1937 (provide 'mime-setup)
1938 @end lisp
1939
1940 @end quotation
1941
1942
1943
1944 @node Bug report, Concept Index, Setting, Top
1945 @chapter How to report bug and about mailing list of tm
1946
1947 If you write bug-reports and/or suggestions for improvement, please
1948 send them to the tm Mailing List:
1949
1950 @itemize @bullet
1951 @item
1952 Japanese <bug-tm-ja@@chamonix.jaist.ac.jp>
1953 @item
1954 English <bug-tm-en@@chamonix.jaist.ac.jp>
1955 @end itemize
1956
1957
1958 Notice that, we does not welcome bug reports about too old version.
1959 Bugs in old version might be fixed. So please try latest version at
1960 first.@refill
1961
1962 You should write @cindex{good bug report}@strong{good bug report}. If
1963 you write only ``tm does not work'', we can not find such situations.
1964 At least, you should write name, type, variants and version of OS,
1965 emacs, tm and MUA, and setting. In addition, if error occurs, to send
1966 backtrace is very important. (cf. @ref{(emacs)Bugs}) @refill
1967
1968 Bug may not appear only your environment, but also in a lot of
1969 environment (otherwise it might not bug). Therefor if you send mail to
1970 author directly, we must write a lot of mails. So please send mail to
1971 address for tm bugs instead of author.@refill
1972
1973 Via the tm ML, you can report tm bugs, obtain the latest release of
1974 tm, and discuss future enhancements to tm. To join the tm ML, send
1975 e-mail to:
1976
1977 @itemize @bullet
1978 @item
1979 Japanese <tm-ja-admin@@chamonix.jaist.ac.jp>
1980 @item
1981 English <tm-en-admin@@chamonix.jaist.ac.jp>
1982 @end itemize
1983
1984 @noindent
1985 Since the user registration is done manually, please write the mail
1986 body in human-recognizable language (^_^).
1987
1988
1989 @node Concept Index, Variable Index, Bug report, Top
1990 @chapter Concept Index
1991
1992 @printindex cp
1993
1994 @node Variable Index, , Concept Index, Top
1995 @chapter Variable Index
1996
1997 @printindex vr
1998 @bye