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