2 @setfilename tm-en.info
3 @settitle{tm 7.98 Manual (English Version)}
5 @title tm 7.98 Manual (English Version)
6 @author MORIOKA Tomohiko <morioka@@jaist.ac.jp>
9 @node Top, Introduction, (dir), (dir)
10 @top tm 7.98 Manual (English Version)
14 This file documents tm, a MIME package for GNU Emacs.
18 * Introduction:: What is tm?
20 * Bug report:: How to report bug and about mailing list of tm
25 @node Introduction, Setting, Top, Top
28 The tm package is a set of modules to enjoy MIME on GNU Emacs. Using
33 playback or view the MIME messages using tm-view
35 compose MIME message using tm-edit
37 use the enhanced MIME features with mh-e, GNUS, Gnus, RMAIL and VM
43 Please read following about each topics:
47 tm-MUA for Gnus (@ref{(gnus-mime-en)})
49 tm-MUA for GNUS (@ref{(tm-gnus-en)})
51 tm-MUA for mh-e (@ref{(tm-mh-e-en)})
53 mime/viewer-mode (@ref{(tm-view-en)})
55 mime/editor-mode (@ref{(tm-edit-en)})
64 @node Glossary, , Introduction, Introduction
73 * 94x94-character set::
77 * cn-gb:: cn-gb, gb2312
78 * cn-big5:: cn-big5, big5
79 * CNS 11643:: CNS 11643-1992
80 * coded character set:: Coded character set, Character code
81 * code extension:: Code extension
82 * Content-Disposition:: Content-Disposition field
83 * Content-Type field::
89 * GB 2312:: GB 2312-1980
90 * GB 8565.2:: GB 8565.2-1988
91 * graphic character set:: Graphic Character Set
113 * ISO-IR-165:: ISO-IR-165, CCITT Extended GB
115 * JIS C6226:: JIS C6226-1978
117 * JIS X0212:: JIS X0212-1990
119 * KS C5601:: KS C5601-1987
129 * multipart:: Multipart
130 * multipart/alternative::
132 * multipart/encrypted::
134 * multipart/parallel::
152 * Security multipart::
155 * tm-kernel:: tm-kernel, tm
160 @node 7bit, 8bit, Glossary, Glossary
163 @cindex{7bit}@strong{7bit} means any integer between 0 .. 127.@refill
165 Any data represented by 7bit integers is called @cindex{7bit
166 data}@strong{7bit data}.@refill
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)
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
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
185 @node 8bit, 94-character set, 7bit, Glossary
188 @cindex{8bit}@strong{8bit} means any integer between 0 .. 255.@refill
190 Any data represented by 8bit integers is called @cindex{8bit
191 data}@strong{8bit data}.@refill
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
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
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
206 However 8bit MTA are increasing today.@refill
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.
215 @node 94-character set, 96-character set, 8bit, Glossary
216 @subsection 94-character set
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)
224 @node 96-character set, 94x94-character set, 94-character set, Glossary
225 @subsection 96-character set
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)
233 @node 94x94-character set, ASCII, 96-character set, Glossary
234 @subsection 94x94-character set
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}))
242 @node ASCII, Base64, 94x94-character set, Glossary
245 @cindex{ASCII}@strong{ASCII} is a 94-character set (@ref{94-character
246 set}) contains primary latin characters (A-Z, a-z), numbers and some
247 characters. It is a standard of the United States of America. It is a
248 variant of ISO 646 (@ref{ISO 646}).
250 @cindex{ASCII}@cindex{ANSI X3.4:1986}
254 ``Coded Character Set -- 7-Bit American Standard Code for Information
255 Interchange'', ANSI X3.4:1986.
260 @node Base64, binary, ASCII, Glossary
263 @cindex{Base64}@strong{Base64} is a transfer encoding method of MIME
264 (@ref{MIME}) defined in RFC 2045 (@ref{RFC 2045}).@refill
266 The encoding process represents 24-bit groups of input bits as output
267 strings of 4 encoded characters. Encoded characters represent integer 0
268 .. 63 or @cindex{pad}@strong{pad}. Base64 data must be 4 * n bytes, so
269 pad is used to adjust size.@refill
271 These 65 characters are subset of all versions of ISO 646, including
272 US-ASCII, and all versions of EBCDIC. So it is safe even if it is
273 translated by non-Internet gateways.
276 @node binary, cn-gb, Base64, Glossary
279 Any byte stream is called @cindex{binary}@strong{binary}.@refill
281 It does not require structureof lines. It differs from from 8bit
284 In addition, if line structured data contain too long line (more than
285 998 bytes), it is regarded as binary.
288 @node cn-gb, cn-big5, binary, Glossary
289 @subsection cn-gb, gb2312
291 A MIME charset (@ref{MIME charset}) for simplified Chinese mainly used
292 in the Chinese mainland.@refill
294 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
295 set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
296 (@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}).@refill
298 It is defined in RFC 1922 (@ref{RFC 1922}).
301 @node cn-big5, CNS 11643, cn-gb, Glossary
302 @subsection cn-big5, big5
304 A MIME charset (@ref{MIME charset}) for traditional Chinese mainly used
305 in Taiwan and Hon Kong.@refill
307 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
308 set}) not based on ISO 2022 (@ref{ISO 2022}). It is a de-fact
311 It is defined in RFC 1922 (@ref{RFC 1922}).@refill
317 Institute for Information Industry, ``Chinese Coded Character Set in
318 Computer'', March 1984.
321 It corresponds to CNS 11643 (@ref{CNS 11643}).
324 @node CNS 11643, coded character set, cn-big5, Glossary
325 @subsection CNS 11643-1992
327 Graphic character set (@ref{Graphic character set})s for Chinese mainly
328 written by traditional Chinese mainly used in Taiwan and Hong Kong. It
329 is a standard of Taiwan. Currently there are seven 94x94 character set
330 (@ref{94x94 character set}).@refill
332 Final byte of ISO 2022 (@ref{ISO 2022}) are following:
359 @cindex{CNS 11643-1992}@cindex{CNS 11643:1992}
363 ``Standard Interchange Code for Generally-Used Chinese Characters'', CNS
369 @node coded character set, code extension, CNS 11643, Glossary
370 @subsection Coded character set, Character code
372 A set of unambiguous rules that establishes a character set and the
373 one-to-one relationship between the characters of the set and their
377 @node code extension, Content-Disposition, coded character set, Glossary
378 @subsection Code extension
380 The techniques for the encoding of characters that are not included in
381 the character set of a given code. (ex. ISO 2022 (@ref{ISO 2022}))
384 @node Content-Disposition, Content-Type field, code extension, Glossary
385 @subsection Content-Disposition field
387 A field to specify presentation of entity or file name. It is an
388 extension for MIME (@ref{MIME}).@refill
390 @cindex{Experimental}@cindex{RFC 1806}
394 E R. Troost and S. Dorner, ``Communicating Presentation Information in
395 Internet Messages: The Content-Disposition Header'', June 1995,
401 @node Content-Type field, Emacs, Content-Disposition, Glossary
402 @subsection Content-Type field
404 Header field to represent information about body, such as media type
405 (@ref{media type}), MIME charset (@ref{MIME charset}). It is defined in
406 RFC 2045 (@ref{RFC 2045}).
412 Historically, Content-Type field was proposed in RFC 1049. In it,
413 Content-Type did not distinguish type and subtype. However MIME parser
414 may be able to accept RFC 1049 based Content-Type as unknown type.
418 Content-Type field is defined as following:
421 ``Content-Type'' ``:'' @cindex{type}@strong{type} ``/''
422 @cindex{subtype}@strong{subtype} *( ``;'' @cindex{parameter}@strong{parameter} )
430 Content-Type: image/jpeg
437 Content-Type: text/plain; charset=iso-2022-jp
446 A part does not have content-type field is regarded as
450 Content-Type: text/plain; charset=us-ascii
458 And a part has unknown type/subtype is regarded as
462 Content-Type: application/octet-stream
470 @node Emacs, encoded-word, Content-Type field, Glossary
473 In this document, `Emacs' means GNU Emacs released by FSF, and `emacs'
474 means any variants of GNU Emacs.
477 @node encoded-word, encapsulation, Emacs, Glossary
478 @subsection encoded-word
480 Representation non ASCII (@ref{ASCII}) characters in header. It is
481 defined in @cindex{RFC 2047}@strong{RFC 2047}.@refill
483 @cindex{Standards Track}@cindex{RFC 2047}
487 K. Moore, ``MIME (Multipurpose Internet Mail Extensions) Part Three:
488 Message Header Extensions for Non-ASCII Text'', November 1996, Standards
489 Track (obsolete RFC 1521,1522,1590).
494 @node encapsulation, euc-kr, encoded-word, Glossary
495 @subsection encapsulation
497 Method to insert whole Internet message (@ref{RFC 822}) into another
498 Internet message.@refill
500 For example, it is used to forward a message.@refill
502 (cf. @ref{message/rfc822})
506 @node euc-kr, FTP, encapsulation, Glossary
509 A MIME charset (@ref{MIME charset}) for Korean.@refill
511 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
512 set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
513 (@ref{ASCII}) to combine KS C5601 (@ref{KS C5601}).@refill
515 It is defined in RFC 1557 (@ref{RFC 1557}).@refill
517 cf. @cindex{euc-kr}@cindex{KS C 5861:1992}
521 Korea Industrial Standards Association, ``Hangul Unix Environment'', KS
527 @node FTP, GB 2312, euc-kr, Glossary
530 @cindex{FTP}@cindex{STD 9}@cindex{RFC 959}
534 Postel, J. and J. Reynolds, ``File Transfer Protocol'', October 1985,
540 @node GB 2312, GB 8565.2, FTP, Glossary
541 @subsection GB 2312-1980
543 A 94x94 character set (@ref{94x94 character set}) for Chinese mainly
544 written by simplified Chinese mainly used in the Chinese mainland. It
545 is a standard of China.@refill
547 Final byte of ISO 2022 (@ref{ISO 2022}) is 04/01 (`A').
549 @cindex{GB 2312}@cindex{GB 2312:1980}
553 ``Code of Chinese Graphic Character Set for Information Interchange -
554 Primary Set'', GB 2312:1980.
559 @node GB 8565.2, graphic character set, GB 2312, Glossary
560 @subsection GB 8565.2-1988
562 A 94x94 character set (@ref{94x94 character set}) for Chinese as
563 supplement to GB 2312 (@ref{GB 2312}). It is a standard of China.
565 @cindex{GB 8565.2}@cindex{GB 8565.2:1988}
569 ``Information Processing - Coded Character Sets for Text Communication -
570 Part 2: Graphic Characters used with Primary Set'', GB 8565.2:1988.
575 @node graphic character set, hz-gb2312, GB 8565.2, Glossary
576 @subsection Graphic Character Set
578 Coded character set (@ref{Coded character set}) for graphic characters.
581 @node hz-gb2312, ISO 2022, graphic character set, Glossary
582 @subsection hz-gb2312
584 A MIME charset (@ref{MIME charset}) for simplified Chinese mainly used
585 in the Chinese mainland.@refill
587 It extends ASCII (@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}), its
588 technique is like iso-2022-jp (@ref{iso-2022-jp}), but it is designed to
589 be ASCII printable to use special form for ESC sequence to designate GB
592 It is defined in RFC 1842 and 1843.
594 @cindex{Informational}@cindex{RFC 1842}
598 Y. Wei, Y. Zhang, J. Li, J. Ding and Y. Jiang, ``ASCII Printable
599 Characters-Based Chinese Character Encoding for Internet Messages'',
600 August 1995, Informational.
603 @cindex{Informational}@cindex{RFC 1843}
607 F. Lee, ``HZ - A Data Format for Exchanging Files of Arbitrarily Mixed
608 Chinese and ASCII characters'', August 1995, Informational.
613 @node ISO 2022, iso-2022-cn, hz-gb2312, Glossary
616 It is a standard for character code structure and code extension
617 (@ref{code extension}) technique.
619 @cindex{ISO 2022}@cindex{ISO/IEC 2022:1994}
623 International Organization for Standardization (ISO), ``Information
624 Processing: ISO 7-bit and 8-bit coded character sets: Code extension
625 techniques'', ISO/IEC 2022:1994.
630 @node iso-2022-cn, iso-2022-cn-ext, ISO 2022, Glossary
631 @subsection iso-2022-cn
633 A MIME charset (@ref{MIME charset}) for Chinese.@refill
635 It is a 7bit (@ref{7bit}) coded character set (@ref{coded character
636 set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
637 (@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}) and/or CNS 11643 plain
638 1, plain 2 (@ref{CNS 11643}).@refill
640 It is defined in RFC 1922 (@ref{RFC 1922}).
643 @node iso-2022-cn-ext, iso-2022-jp, iso-2022-cn, Glossary
644 @subsection iso-2022-cn-ext
646 A MIME charset (@ref{MIME charset}) for Chinese.@refill
648 It is a 7bit (@ref{7bit}) coded character set (@ref{coded character
649 set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
650 (@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}), CNS 11643 plain 1 .. 7
651 (@ref{CNS 11643}), ISO-IR-165 (@ref{ISO-IR-165}) and other Chinese
652 graphic character sets.@refill
654 It is defined in RFC 1922 (@ref{RFC 1922}).@refill
659 MULE 2.3 and current XEmacs/mule can not use it correctly.
661 Emacs/mule can use it.
666 @node iso-2022-jp, iso-2022-jp-2, iso-2022-cn-ext, Glossary
667 @subsection iso-2022-jp
669 A MIME charset (@ref{MIME charset}) for Japanese.@refill
671 It is a 7bit (@ref{7bit}) coded character set (@ref{coded character
672 set}) based on old ISO 2022 (@ref{ISO 2022}). It switches ASCII
673 (@ref{ASCII}), JIS X0201-Latin, JIS X0208-1978 (@ref{JIS C6226-1978})
674 and JIS X0208-1983 (@ref{JIS X0208}).@refill
676 It is defined in RFC 1468.@refill
681 JIS X0208-1997? will define it in annex as non-ISO 2022 (@ref{ISO 2022})
686 @cindex{iso-2022-jp}@cindex{RFC 1468}
688 [iso-2022-jp: RFC 1468]
690 Murai J., M. Crispin, and E. van der Poel, ``Japanese Character Encoding
691 for Internet Messages'', June 1993.
696 @node iso-2022-jp-2, iso-2022-kr, iso-2022-jp, Glossary
697 @subsection iso-2022-jp-2
699 A MIME charset (@ref{MIME charset}), which is a multilingual extension
700 of iso-2022-jp (@ref{iso-2022-jp}).@refill
702 It is defined in RFC 1554.
704 @cindex{iso-2022-jp-2}@cindex{Informational}@cindex{RFC 1554}
706 [iso-2022-jp-2: RFC 1554]
708 Ohta M. and Handa K., ``ISO-2022-JP-2: Multilingual Extension of
709 ISO-2022-JP'', December 1993, Informational.
714 @node iso-2022-kr, ISO 646, iso-2022-jp-2, Glossary
715 @subsection iso-2022-kr
717 A MIME charset (@ref{MIME charset}) for Korean language (Hangul
720 It is based on ISO 2022 (@ref{ISO 2022}) code extension (@ref{code
721 extension}) technique to extend ASCII (@ref{ASCII}) to use KS C5601
722 (@ref{KS C5601}) as 7bit (@ref{7bit}) text.@refill
724 It is defined in RFC 1557 (@ref{RFC 1557}).
727 @node ISO 646, ISO 8859-1, iso-2022-kr, Glossary
730 @cindex{ISO 646}@cindex{ISO/IEC 646:1991}
734 International Organization for Standardization (ISO), ``Information
735 technology: ISO 7-bit coded character set for information interchange'',
741 @node ISO 8859-1, iso-8859-1, ISO 646, Glossary
742 @subsection ISO 8859-1
744 @cindex{ISO 8859-1}@cindex{ISO 8859-1:1987}
748 International Organization for Standardization (ISO), ``Information
749 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 1:
750 Latin Alphabet No.1'', ISO 8859-1:1987.
755 @node iso-8859-1, ISO 8859-2, ISO 8859-1, Glossary
756 @subsection iso-8859-1
758 @cindex{iso-8859-1}@strong{iso-8859-1} is a MIME charset (@ref{MIME
759 charset}) for west-European languages written by Latin script.@refill
761 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
762 set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
763 (@ref{ASCII}) to combine ISO 8859-1 (@ref{ISO 8859-1}).@refill
765 It is defined in RFC 2046 (@ref{RFC 2046}).
768 @node ISO 8859-2, iso-8859-2, iso-8859-1, Glossary
769 @subsection ISO 8859-2
771 @cindex{ISO 8859-2}@cindex{ISO 8859-2:1987}
775 International Organization for Standardization (ISO), ``Information
776 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 2:
777 Latin alphabet No.2'', ISO 8859-2:1987.
782 @node iso-8859-2, ISO 8859-3, ISO 8859-2, Glossary
783 @subsection iso-8859-2
785 @cindex{iso-8859-2}@strong{iso-8859-2} is a MIME charset (@ref{MIME
786 charset}) for east-European languages written by Latin script.@refill
788 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
789 set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
790 (@ref{ASCII}) to combine ISO 8859-2 (@ref{ISO 8859-2}).@refill
792 It is defined in RFC 2046 (@ref{RFC 2046}).
795 @node ISO 8859-3, ISO 8859-4, iso-8859-2, Glossary
796 @subsection ISO 8859-3
798 @cindex{ISO 8859-3}@cindex{ISO 8859-3:1988}
802 International Organization for Standardization (ISO), ``Information
803 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 3:
804 Latin alphabet No.3'', ISO 8859-3:1988.
809 @node ISO 8859-4, ISO 8859-5, ISO 8859-3, Glossary
810 @subsection ISO 8859-4
812 @cindex{ISO 8859-4}@cindex{ISO 8859-4:1988}
816 International Organization for Standardization (ISO), ``Information
817 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 4:
818 Latin alphabet No.4'', ISO 8859-4:1988.
823 @node ISO 8859-5, iso-8859-5, ISO 8859-4, Glossary
824 @subsection ISO 8859-5
826 @cindex{ISO 8859-5}@cindex{ISO 8859-5:1988}
830 International Organization for Standardization (ISO), ``Information
831 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 5:
832 Latin/Cyrillic alphabet'', ISO 8859-5:1988.
837 @node iso-8859-5, ISO 8859-6, ISO 8859-5, Glossary
838 @subsection iso-8859-5
840 @cindex{iso-8859-5}@strong{iso-8859-5} is a MIME charset (@ref{MIME
841 charset}) for Cyrillic script.@refill
843 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
844 set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
845 (@ref{ASCII}) to combine ISO 8859-5 (@ref{ISO 8859-5}).@refill
847 It is defined in RFC 2046 (@ref{RFC 2046}).
850 @node ISO 8859-6, ISO 8859-7, iso-8859-5, Glossary
851 @subsection ISO 8859-6
853 @cindex{ISO 8859-6}@cindex{ISO 8859-6:1987}
857 International Organization for Standardization (ISO), ``Information
858 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 6:
859 Latin/Arabic alphabet'', ISO 8859-6:1987.
864 @node ISO 8859-7, iso-8859-7, ISO 8859-6, Glossary
865 @subsection ISO 8859-7
867 @cindex{ISO 8859-7}@cindex{ISO 8859-7:1987}
871 International Organization for Standardization (ISO), ``Information
872 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 7:
873 Latin/Greek alphabet'', ISO 8859-7:1987.
878 @node iso-8859-7, ISO 8859-8, ISO 8859-7, Glossary
879 @subsection iso-8859-7
881 @cindex{iso-8859-7}@strong{iso-8859-7} is a MIME charset (@ref{MIME
882 charset}) for Greek script.@refill
884 It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
885 set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
886 (@ref{ASCII}) to combine ISO 8859-7 (@ref{ISO 8859-7}).@refill
888 It is defined in RFC 1947.
890 @cindex{iso-8859-7}@cindex{Informational}@cindex{RFC 1947}
892 [iso-8859-7: RFC 1947]
894 D. Spinellis, ``Greek Character Encoding for Electronic Mail Messages'',
895 May 1996, Informational.
900 @node ISO 8859-8, ISO 8859-9, iso-8859-7, Glossary
901 @subsection ISO 8859-8
903 @cindex{ISO 8859-8}@cindex{ISO 8859-8:1988}
907 International Organization for Standardization (ISO), ``Information
908 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 8:
909 Latin/Hebrew alphabet'', ISO 8859-8:1988.
914 @node ISO 8859-9, ISO-IR-165, ISO 8859-8, Glossary
915 @subsection ISO 8859-9
917 @cindex{ISO 8859-9}@cindex{ISO 8859-9:1990}
921 International Organization for Standardization (ISO), ``Information
922 Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 9:
923 Latin alphabet No.5'', ISO 8859-9:1990.
928 @node ISO-IR-165, JIS X0201, ISO 8859-9, Glossary
929 @subsection ISO-IR-165, CCITT Extended GB
931 A 94x94-character set (@ref{94x94-character set}) for Chinese mainly
932 written by simplified Chinese mainly used in the Chinese mainland
933 registered by CCITT.@refill
935 It consists of GB 2312 (@ref{GB 2312}), GB 8865.2 (@ref{GB 8865.2}) and
936 additional 150 characters.@refill
938 Final byte of ISO 2022 (@ref{ISO 2022}) is 04/05 (`E').
941 @node JIS X0201, JIS C6226, ISO-IR-165, Glossary
942 @subsection JIS X0201
944 It defines two 94-character set (@ref{94-character set}), for Latin
945 script (a variant of ISO 646 (@ref{ISO 646})) and Katakana script, and
946 7bit and 8bit coded character set (@ref{coded character set})s.@refill
948 It was renamed from @cindex{JIS C6220-1976}@strong{JIS C6220-1976}.
950 @cindex{JIS X0201-1976}@cindex{JIS X 0201-1976:}
954 Japanese Standards Association, ``Code for Information Interchange'',
959 In addition, revised version will be published in 1997.
961 @cindex{JIS X0201-1997?}@cindex{JIS X 0201:1997? draft}
965 Japanese Standards Association, ``7-bit and 8-bit coded character sets
966 for information interchange'', JIS X 0201:1997? draft.
971 @node JIS C6226, JIS X0208, JIS X0201, Glossary
972 @subsection JIS C6226-1978
974 A 94x94-character set (@ref{94x94-character set}) for Japanese. It was
975 renamed to JIS X0208-1978.@refill
977 (cf. @ref{JIS X0208})
981 @node JIS X0208, JIS X0212, JIS C6226, Glossary
982 @subsection JIS X0208
984 A 94x94-character set (@ref{94x94-character set}) for Japanese.
985 Japanese standard. It was published in 1978, and revised in 1983 and
986 1990. In the Internet message, 1983 edition is major.@refill
988 JIS X0208 contains some symbols, numbers, primary Latin script, Hiragana
989 script, Katakana script, Greek script, Cyrillic script, box drawing
990 parts, Kanji (Ideographic characters used in Japanese). Notice that
991 some symbols and box drawing parts were added in 1983 and some Kanjis
992 were changed or swapped code points. So 1978 edition and 1983 edition
993 are regarded as different graphic character set.@refill
995 1990 edition added some characters, so designation of 1990 edition
996 requires `identify revised registration' sequence, ESC 02/06 4/0 as
997 prefix of designation sequence.
999 @cindex{JIS X0208-1978}@cindex{JIS C6226:1978}
1003 Japanese Standards Association, ``Code of the Japanese graphic character
1004 set for information interchange'', JIS C6226:1978.
1007 @cindex{JIS X0208-1983,1990}@cindex{JIS X0208:1983,1990}
1009 [JIS X0208-1983,1990]
1011 Japanese Standards Association, ``Code of the Japanese graphic character
1012 set for information interchange'', JIS X0208:1983,1990.
1016 In addition, revised version will be published in 1997. (It does not
1017 change graphic character set)
1019 @cindex{JIS X0208-1997?}@cindex{JIS X 0208:1997? draft}
1023 Japanese Standards Association, ``7-bit and 8-bit double byte coded
1024 Kanji sets for information interchange'', JIS X 0208:1997? draft.
1029 @node JIS X0212, koi8-r, JIS X0208, Glossary
1030 @subsection JIS X0212-1990
1032 A 94x94 character set (@ref{94x94 character set}) for Japanese as
1033 supplement to JIS X0208 (@ref{JIS X0208}). It is a standard of
1036 Final byte of ISO 2022 (@ref{ISO 2022}) is 04/04 (`D').
1039 @node koi8-r, KS C5601, JIS X0212, Glossary
1042 A MIME charset (@ref{MIME charset}) for Cyrillic script for Russian or
1043 other languages.@refill
1045 It is a 1 byte 8bit (@ref{8bit}) coded character set (@ref{coded
1046 character set}), not based on ISO 2022 (@ref{ISO 2022}). It is a
1047 de-fact standard.@refill
1049 It is defined in RFC 1489.@refill
1055 A. Chernov, ``Registration of a Cyrillic Character Set'', July 1993.
1060 @node KS C5601, media type, koi8-r, Glossary
1061 @subsection KS C5601-1987
1063 A 94x94-character set (@ref{94x94-character set}) for Korean language
1064 (Hangul script). Korean Standard. Final byte of ISO 2022 (@ref{ISO
1065 2022}) is 04/03 (`C').
1067 @cindex{KS C5601}@cindex{KS C 5601:1987}
1071 Korea Industrial Standards Association, ``Code for Information
1072 Interchange (Hangul and Hanja)'', KS C 5601:1987.
1077 @node media type, message, KS C5601, Glossary
1078 @subsection media type
1080 @cindex{media type}@strong{media type} specifies the nature of the data
1081 in the body of MIME (@ref{MIME}) entity (@ref{entity}). It consists of
1082 @cindex{type}@strong{type} and @cindex{subtype}@strong{subtype}. It is
1083 defined in RFC 2046 (@ref{RFC 2046}).@refill
1085 Currently there are following types:
1089 @cindex{text}@strong{text}
1091 @cindex{image}@strong{image}
1093 @cindex{audio}@strong{audio}
1095 @cindex{video}@strong{video}
1097 @cindex{application}@strong{application}
1099 @cindex{multipart}@strong{multipart} (@ref{multipart})
1101 @cindex{message}@strong{message}
1105 And there are various subtypes, for example, application/octet-stream,
1106 audio/basic, image/jpeg, multipart/mixed (@ref{multipart/mixed}),
1107 text/plain (@ref{text/plain}), video/mpeg...@refill
1109 You can refer registered media types at MEDIA TYPES
1110 (ftp://ftp.isi.edu/in-notes/iana/assignments/media-types).@refill
1112 In addition, you can use private type or subtype using
1113 @cindex{x-token}@strong{x-token}, which as the prefix `x-'. However you
1114 can not use them in public.@refill
1116 (cf. @ref{Content-Type field})
1120 @node message, message/rfc822, media type, Glossary
1123 In this document, it means mail defined in RFC 822 (@ref{RFC 822}) and
1124 news message defined in RFC 1036 (@ref{RFC 1036}).
1127 @node message/rfc822, method, message, Glossary
1128 @subsection message/rfc822
1130 @cindex{message/rfc822}@strong{message/rfc822} indicates that the body
1131 contains an encapsulated message, with the syntax of an RFC 822
1132 (@ref{RFC 822}) message. It is the replacement of traditional RFC 934
1133 (@ref{RFC 934}) encapsulation. It is defined in RFC 2046 (@ref{RFC
1137 @node method, MIME, message/rfc822, Glossary
1140 Application program of tm-view to process for specified media type
1141 (@ref{media type}) when user plays an entity.@refill
1143 There are two kinds of methods, @cindex{internal method}@strong{internal
1144 method} and @cindex{external method}@strong{external method}. Internal
1145 method is written by Emacs Lisp. External method is written by C or
1146 script languages and called by asynchronous process call.@refill
1148 (cf. @ref{(tm-view-en)method})
1152 @node MIME, MIME charset, method, Glossary
1155 MIME stands for @cindex{Multipurpose Internet Mail
1156 Extensions}@strong{Multipurpose Internet Mail Extensions}, it is an
1157 extension for RFC 822 (@ref{RFC 822}).@refill
1159 According to RFC 2045:@refill
1161 STD 11, RFC 822, defines a message representation protocol specifying
1162 considerable detail about US-ASCII message headers, and leaves the
1163 message content, or message body, as flat US-ASCII text. This set of
1164 documents, collectively called the Multipurpose Internet Mail
1165 Extensions, or MIME, redefines the format of messages to allow
1170 textual message bodies in character sets other than US-ASCII,
1172 an extensible set of different formats for non-textual message
1175 multi-part message bodies, and
1177 textual header information in character sets other than US-ASCII.
1181 It is defined in RFC 2045 (@ref{RFC 2045}), RFC 2046 (@ref{RFC 2046}),
1182 RFC 2047 (@ref{encoded-word}), RFC 2048 (@ref{RFC 2048}) and RFC 2049
1186 @node MIME charset, MTA, MIME, Glossary
1187 @subsection MIME charset
1189 Coded character set (@ref{Coded character set}) used in Content-Type
1190 field (@ref{Content-Type field}) or charset parameter of encoded-word
1191 (@ref{encoded-word}).@refill
1193 It is defined in RFC 2045 (@ref{RFC 2045}).@refill
1195 iso-2022-jp (@ref{iso-2022-jp}) or euc-kr (@ref{euc-kr}) are kinds of
1196 it. (In this document, MIME charsets are written by small letters to
1197 distinguish graphic character set (@ref{graphic character set}). For
1198 example, ISO 8859-1 is a graphic character set, and iso-8859-1 is a MIME
1202 @node MTA, MUA, MIME charset, Glossary
1205 @cindex{Message Transfer Agent}@strong{Message Transfer Agent}. It
1206 means mail transfer programs (ex. sendmail) and news servers.@refill
1212 @node MUA, MULE, MTA, Glossary
1215 @cindex{Message User Agent}@strong{Message User Agent}. It means mail
1216 readers and news readers.@refill
1222 @node MULE, multipart, MUA, Glossary
1225 Multilingual extension of GNU Emacs (@ref{Emacs}) by HANDA Ken'ichi et
1232 Nishikimi M., Handa K. and Tomura S., ``Mule: MULtilingual Enhancement
1233 to GNU Emacs'', Proc. of INET'93, August, 1993.
1236 Now, FSF and HANDA Ken'ichi et al. are working to merge MULE feature
1237 into Emacs, there is alpha version of mule merged emacs
1238 (ftp://etlport.etl.go.jp/pub/mule/mule-19.33-delta.taz).@refill
1240 In addition, there is XEmacs with mule feature.@refill
1242 So now, there are 3 kinds of mule variants.@refill
1244 In this document, @cindex{mule}@strong{mule} means any mule variants,
1245 @cindex{MULE}@strong{MULE} means original MULE (..2.3),
1246 @cindex{Emacs/mule}@strong{Emacs/mule} means mule merged Emacs,
1247 @cindex{XEmacs/mule}@strong{XEmacs/mule} means XEmacs with mule feature.
1250 @node multipart, multipart/alternative, MULE, Glossary
1251 @subsection Multipart
1253 @cindex{multipart}@strong{multipart} means media type (@ref{media type})
1254 to insert multiple entities (@ref{entities}) in a single body. Or it
1255 also indicates a message consists of multiple entities.@refill
1257 There are following subtypes registered in RFC 2046 (@ref{RFC 2046}):
1261 multipart/mixed (@ref{multipart/mixed})
1263 multipart/alternative (@ref{multipart/alternative})
1265 multipart/digest (@ref{multipart/digest})
1267 multipart/parallel (@ref{multipart/parallel})
1271 and registered in RFC 1847 (@ref{Security multipart}):
1275 multipart/signed (@ref{multipart/signed})
1277 multipart/encrypted (@ref{multipart/encrypted})
1282 @node multipart/alternative, multipart/digest, multipart, Glossary
1283 @subsection multipart/alternative
1285 @cindex{multipart/digest}@strong{multipart/digest} is one of multipart
1286 (@ref{multipart}) media types. This type is syntactically identical to
1287 multipart/mixed (@ref{multipart/mixed}), but the semantics are
1288 different. In particular, each of the body parts is an ``alternative''
1289 version of the same information.@refill
1291 (cf. @ref{RFC 2046})
1295 @node multipart/digest, multipart/encrypted, multipart/alternative, Glossary
1296 @subsection multipart/digest
1298 @cindex{multipart/digest}@strong{multipart/digest} is one of multipart
1299 (@ref{multipart}) media types. This type is syntactically identical to
1300 multipart/mixed (@ref{multipart/mixed}), but the semantics are
1301 different. In particular, in a digest, the default Content-Type value
1302 for a body part is changed from text/plain (@ref{text/plain}) to
1303 message/rfc822 (@ref{message/rfc822}).@refill
1305 This is the replacement of traditional RFC 1153 (@ref{RFC 1153}) based
1306 encapsulation (@ref{encapsulation}).@refill
1308 (cf. @ref{RFC 2046})
1312 @node multipart/encrypted, multipart/mixed, multipart/digest, Glossary
1313 @subsection multipart/encrypted
1315 It is a Security multipart (@ref{Security multipart}) defined in RFC
1316 1847, used to represent encrypted message.@refill
1318 (cf. @ref{PGP/MIME})
1322 @node multipart/mixed, multipart/parallel, multipart/encrypted, Glossary
1323 @subsection multipart/mixed
1325 Primary and default subtype of multipart (@ref{multipart}), it is used
1326 when the body parts are independent and need to be bundled in a
1327 particular order.@refill
1329 (cf. @ref{RFC 2046})
1333 @node multipart/parallel, multipart/signed, multipart/mixed, Glossary
1334 @subsection multipart/parallel
1336 @cindex{multipart/parallel}@strong{multipart/parallel} is a subtype of
1337 multipart (@ref{multipart}). This type is syntactically identical to
1338 multipart/mixed (@ref{multipart/mixed}), but the semantics are
1339 different. In particular, in a parallel entity, the order of body parts
1340 is not significant.@refill
1342 (cf. @ref{RFC 2046})
1346 @node multipart/signed, PGP, multipart/parallel, Glossary
1347 @subsection multipart/signed
1349 It is a Security multipart (@ref{Security multipart}) defined in RFC
1350 1847, used to represent signed message.@refill
1352 (cf. @ref{PGP/MIME})
1356 @node PGP, PGP-kazu, multipart/signed, Glossary
1359 A public key encryption program by Phil Zimmermann. It provides
1360 encryption and signature for message (@ref{message}). PGP stands for
1361 @cindex{Pretty Good Privacy}@strong{Pretty Good Privacy}.@refill
1363 Traditional PGP uses RFC 934 (@ref{RFC 934}) encapsulation
1364 (@ref{encapsulation}). It is conflict with MIME (@ref{MIME}). So
1365 PGP/MIME (@ref{PGP/MIME}) is defined. On the other hand, PGP-kazu
1366 (@ref{PGP-kazu}) was proposed to use PGP encapsulation in MIME. But it
1367 is obsoleted.@refill
1369 @cindex{PGP}@cindex{Informational}@cindex{RFC 1991}
1373 D. Atkins, W. Stallings and P. Zimmermann, ``PGP Message Exchange
1374 Formats'', August 1996, Informational.
1380 @node PGP-kazu, PGP/MIME, PGP, Glossary
1381 @subsection PGP-kazu
1383 In this document, @cindex{PGP-kazu}@strong{PGP-kazu} means a method to
1384 use traditional PGP encapsulation in MIME (@ref{MIME}), proposed by
1385 YAMAMOTO Kazuhiko.@refill
1387 PGP-kazu defines a media type (@ref{media type}),
1388 @cindex{application/pgp}@strong{application/pgp}.@refill
1390 In application/pgp entity, PGP encapsulation (@ref{encapsulation}) is
1391 used. PGP encapsulation conflicts with MIME, so it requires
1392 PGP-processing to read as MIME message.@refill
1394 It was obsoleted, so you should use PGP/MIME (@ref{PGP/MIME}). However
1395 if you want to use traditional PGP message, it might be available.
1398 @node PGP/MIME, Quoted-Printable, PGP-kazu, Glossary
1399 @subsection PGP/MIME
1401 PGP (@ref{PGP}) and MIME (@ref{MIME}) integration proposed by Michael
1404 It is based on RFC 1847 (@ref{Security multipart}), so it is harmonious
1405 with MIME, but it is not compatible with traditional PGP encapsulation.
1406 However MIME MUA can read PGP/MIME signed message even if it does not
1407 support PGP/MIME.@refill
1409 PGP/MIME (@ref{PGP/MIME}) will be standard of PGP message.
1411 @cindex{PGP/MIME}@cindex{Standards Track}@cindex{RFC 2015}
1413 [PGP/MIME: RFC 2015]
1415 M. Elkins, ``MIME Security with Pretty Good Privacy (PGP)'', October
1416 1996, Standards Track.
1421 @node Quoted-Printable, RFC 821, PGP/MIME, Glossary
1422 @subsection Quoted-Printable
1424 @cindex{Quoted-Printable}@strong{Quoted-Printable} is a transfer
1425 encoding method of MIME (@ref{MIME}) defined in RFC 2045 (@ref{RFC
1428 If the data being encoded are mostly US-ASCII text, the encoded form of
1429 the data remains largely recognizable by humans.@refill
1435 @node RFC 821, RFC 822, Quoted-Printable, Glossary
1438 @cindex{SMTP}@cindex{STD 10}@cindex{RFC 821}
1442 J. Postel, ``Simple Mail Transfer Protocol'', August 1982, STD 10.
1447 @node RFC 822, RFC 934, RFC 821, Glossary
1450 A RFC defines format of Internet mail message, mainly @cindex{message
1451 header}@strong{message
1458 news message is based on RFC 822, so @cindex{Internet
1459 message}@strong{Internet message} may be more suitable than
1460 @cindex{Internet mail}@strong{Internet mail} .
1464 @cindex{STD 11}@cindex{RFC 822}
1468 D. Crocker, ``Standard for the Format of ARPA Internet Text Messages'',
1469 August 1982, STD 11.
1474 @node RFC 934, RFC 1036, RFC 822, Glossary
1477 A RFC defines an @cindex{encapsulation}@strong{encapsulation}
1478 (@ref{encapsulation}) method for Internet mail (@ref{RFC 822}).@refill
1480 It conflicts with MIME (@ref{MIME}), so you should use message/rfc822
1481 (@ref{message/rfc822}).
1487 Marshall T. Rose and Einar A. Stefferud, ``Proposed Standard for Message
1488 Encapsulation'', January 1985.
1493 @node RFC 1036, RFC 1153, RFC 934, Glossary
1494 @subsection RFC 1036
1496 A RFC defines format of USENET message. It is a subset of RFC 822
1497 (@ref{RFC 822}). It is not Internet standard, but a lot of netnews
1498 excepting Usenet uses it.
1500 @cindex{USENET}@cindex{RFC 1036}
1504 M. Horton and R. Adams, ``Standard for Interchange of USENET Messages'',
1505 December 1987, (obsolete RFC 850).
1510 @node RFC 1153, RFC 1557, RFC 1036, Glossary
1511 @subsection RFC 1153
1517 F. Wancho, ``Digest Message Format'', April 1990.
1522 @node RFC 1557, RFC 1922, RFC 1153, Glossary
1523 @subsection RFC 1557
1525 A RFC defines MIME charset (@ref{MIME charset})s for Korean, euc-kr
1526 (@ref{euc-kr}) and iso-2022-kr (@ref{iso-2022-kr}).
1528 @cindex{Informational}@cindex{RFC 1557}
1532 U. Choi, K. Chon and H. Park, ``Korean Character Encoding for Internet
1533 Messages'', December 1993, Informational.
1538 @node RFC 1922, RFC 2045, RFC 1557, Glossary
1539 @subsection RFC 1922
1541 A RFC defines MIME charset (@ref{MIME charset})s for Chinese,
1542 iso-2022-cn (@ref{iso-2022-cn}), iso-2022-cn-ext
1543 (@ref{iso-2022-cn-ext}), cn-gb (@ref{cn-gb}), cn-big5 (@ref{cn-big5}),
1546 In addition, it defines additional parameters of Content-Type field
1547 (@ref{Content-Type field}) field,
1548 @cindex{charset-edition}@strong{charset-edition} and
1549 @cindex{charset-extension}@strong{charset-extension}.
1551 @cindex{Informational}@cindex{RFC 1922}
1555 Zhu, HF., Hu, DY., Wang, ZG., Kao, TC., Chang, WCH. and Crispin, M.,
1556 ``Chinese Character Encoding for Internet Messages'', March 1996,
1562 @node RFC 2045, RFC 2046, RFC 1922, Glossary
1563 @subsection RFC 2045
1565 @cindex{Standards Track}@cindex{RFC 2045}
1569 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1570 (MIME) Part One: Format of Internet Message Bodies'', November 1996,
1571 Standards Track (obsolete RFC 1521, 1522, 1590).
1576 @node RFC 2046, RFC 2048, RFC 2045, Glossary
1577 @subsection RFC 2046
1579 @cindex{Standards Track}@cindex{RFC 2046}
1583 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1584 (MIME) Part Two: Media Types'', November 1996, Standards Track (obsolete
1585 RFC 1521, 1522, 1590).
1590 @node RFC 2048, RFC 2049, RFC 2046, Glossary
1591 @subsection RFC 2048
1593 @cindex{Standards Track}@cindex{RFC 2048}
1597 N. Freed, J. Klensin and J. Postel, ``Multipurpose Internet Mail
1598 Extensions (MIME) Part Four: Registration Procedures'', November 1996,
1599 Standards Track (obsolete RFC 1521, 1522, 1590).
1604 @node RFC 2049, plain text, RFC 2048, Glossary
1605 @subsection RFC 2049
1607 @cindex{Standards Track}@cindex{RFC 2049}
1611 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1612 (MIME) Part Five: Conformance Criteria and Examples'', November 1996,
1613 Standards Track (obsolete RFC 1521, 1522, 1590).
1618 @node plain text, Security multipart, RFC 2049, Glossary
1619 @subsection plain text
1621 A textual data represented by only coded character set (@ref{coded
1622 character set}). It does not have information about font or
1623 typesetting. (cf. @ref{text/plain})
1627 @node Security multipart, text/enriched, plain text, Glossary
1628 @subsection Security multipart
1630 A format to represent signed/encrypted message in MIME
1631 (@ref{MIME}).@refill
1633 It defines two multipart media types,
1634 @cindex{multipart/signed}@strong{multipart/signed}
1635 (@ref{multipart/signed}) and
1636 @cindex{multipart/encrypted}@strong{multipart/encrypted}
1637 (@ref{multipart/encrypted}).@refill
1639 MOSS and PGP/MIME (@ref{PGP/MIME}) are based on it.
1641 @cindex{Security multipart}@cindex{Standards Track}@cindex{RFC 1847}
1643 [Security multipart: RFC 1847]
1645 James Galvin, Gale Murphy, Steve Crocker and Ned Freed, ``Security
1646 Multiparts for MIME: Multipart/Signed and Multipart/Encrypted'', October
1647 1995, Standards Track.
1652 @node text/enriched, text/plain, Security multipart, Glossary
1653 @subsection text/enriched
1655 @cindex{text/enriched}@cindex{RFC 1896}
1657 [text/enriched: RFC 1896]
1659 P. Resnick and A. Walker, ``The text/enriched MIME Content-type'',
1660 February 1996, (obsolete RFC 1563).
1665 @node text/plain, tm-kernel, text/enriched, Glossary
1666 @subsection text/plain
1668 @cindex{text/plain}@strong{text/plain} is a media type (@ref{media
1669 type}) for plain text (@ref{plain text}), defined in RFC 2046 (@ref{RFC
1672 The default media type of ``text/plain; charset=us-ascii'' for Internet
1673 mail describes existing Internet practice. That is, it is the type of
1674 body defined by RFC 822 (@ref{RFC 822}).@refill
1676 (cf. @ref{MIME charset}) (cf. @ref{us-ascii})
1680 @node tm-kernel, tm-MUA, text/plain, Glossary
1681 @subsection tm-kernel, tm
1683 A libraries to provide user interface about MIME (@ref{MIME}) for emacs.
1684 tm stands for `tools for MIME'.
1687 @strong{[Unimportant notice(^-^;]}
1692 tm may not stand for ``tiny-mime''(^-^;
1695 tm may not stand for initial of an author (^-^;
1698 ``Tools for MIME'' may be strained (^-^;
1704 @node tm-MUA, us-ascii, tm-kernel, Glossary
1707 MUA (@ref{MUA}) or MUA extender using tm (@ref{tm-kernel}).@refill
1709 @cindex{tm oomori package}@strong{tm oomori package} has following extenders:
1713 @cindex{tm-mh-e}@strong{tm-mh-e} (@ref{(tm-mh-e-en)})
1714 for mh-e (@ref{(mh-e)})
1716 @cindex{tm-gnus}@strong{tm-gnus} (@ref{(tm-gnus_en)}) for GNUS
1718 @cindex{gnus-mime}@strong{gnus-mime} (@ref{(gnus-mime-en)}) for Gnus
1720 @cindex{tm-vm}@strong{tm-vm} (@ref{(tm-vm_en)}) for VM
1722 @cindex{tm-rmail}@strong{tm-rmail} for RMAIL
1727 @node us-ascii, , tm-MUA, Glossary
1728 @subsection us-ascii
1730 A MIME charset (@ref{MIME charset}) for primary Latin script mainly
1731 written by English or other languages.@refill
1733 It is a 7bit coded character set (@ref{coded character set}) based on
1734 ISO 2022 (@ref{ISO 2022}), it contains only ASCII (@ref{ASCII}) and code
1735 extension (@ref{code extension}) is not allowed.@refill
1737 It is standard coded character set of Internet mail. If MIME charset is
1738 not specified, @cindex{us-ascii}@strong{us-ascii} is used as
1741 In addition, @cindex{ASCII}@strong{ASCII} of RFC 822 (@ref{RFC 822})
1742 should be interpreted as us-ascii.
1745 @node Setting, Bug report, Introduction, Top
1748 In the tm package, two files, @file{mime-setup.el} and
1749 @file{tm-setup.el}, are provided to ease the setup.@refill
1751 The @file{mime-setup.el} is used for the whole MIME related
1752 setup including MIME encoding using @file{tm-edit.el}, while
1753 @file{tm-setup.el} is used to set up tm-MUA only.
1757 * mime-setup:: Normal setting
1758 * tm-setup:: Setting not to use tm-edit
1759 * setting for VM:: Setting for VM
1760 * manual setting:: Setting up without loading provided setup files
1763 @node mime-setup, tm-setup, Setting, Setting
1764 @section Normal setting
1766 If you want normal setting, please use @cindex{mime-setup}@strong{mime-setup}.
1767 For example, please insert following into @file{~/.emacs}:
1774 As @file{mime-setup.el} loads @file{tm-setup.el}, you
1775 don't need to load @file{tm-setup.el} when you use
1776 @file{mime-setup.el} (Description of old version of Gnus FAQ is
1782 * Notice about GNUS:: Notices for GNUS
1785 @node signature, Notice about GNUS, mime-setup, mime-setup
1786 @subsection signature
1788 You can set up the @cindex{automatic signature selection
1789 tool}@strong{automatic signature selection
1790 tool} using @file{mime-setup}. If you want to
1791 automatically select the signature file depending on how the message
1792 headers show, add lines like shown below to your .emacs (Refer to the
1793 reference manual of @file{signature.el} for more details).
1796 (setq signature-file-alist
1797 '((("Newsgroups" . "jokes") . "~/.signature-jokes")
1798 (("Newsgroups" . ("zxr" "nzr")) . "~/.signature-sun")
1799 (("To" . ("ishimaru" "z-suzuki")) . "~/.signature-sun")
1800 (("To" . "tea") . "~/.signature-jokes")
1801 (("To" . ("sim" "oku" "takuo")) . "~/.signature-formal")
1807 @defvar mime-setup-use-signature
1809 If it is not @code{nil}, @file{mime-setup.el} sets up for
1810 @file{signature.el}. Its default value is @code{t}.
1815 @defvar mime-setup-signature-key-alist
1817 It defines key to bind signature inserting command for each
1818 major-mode. Its default value is following:
1821 ((mail-mode . "\C-c\C-w"))
1825 If you want to change, please rewrite it. For example:
1828 (set-alist 'mime-setup-signature-key-alist
1829 'news-reply-mode "\C-c\C-w")
1836 @defvar mime-setup-default-signature-key
1838 If key to bind signature inserting command for a major-mode is not found
1839 from @code{mime-setup-signature-key-alist}, its value is used as key.
1840 Its default value is @code{"\C-c\C-s"}.
1845 @node Notice about GNUS, , signature, mime-setup
1846 @subsection Notices for GNUS
1848 When @file{mime-setup.el} sets up for @file{signature.el}, it sets
1849 variable @code{gnus-signature-file} to @code{nil}. Therefore GNUS does
1850 not insert signature automatically when it is sending a message. Reason
1851 of this setting is following:@refill
1853 GNUS inserts signature after @file{tm-edit.el} composed as MIME message.
1854 Therefore signature inserted by GNUS is not processed as a valid MIME
1855 part. In particular, for multipart message, signature places in outside
1856 of MIME part. So MIME MUA might not display it.@refill
1858 Other notice is key bind. In historical reason, key bind to insert
1859 signature is @kbd{C-c C-s} (like mh-e (@ref{(mh-e)})) instead of
1860 @kbd{C-c C-w}. If you change to GNUS's default, please set following:
1863 (set-alist 'mime-setup-signature-key-alist 'news-reply-mode "\C-c\C-w")
1868 @node tm-setup, setting for VM, mime-setup, Setting
1869 @section Setting not to use tm-edit
1871 @cindex{tm-setup}@strong{tm-setup} only sets up tm-MUA (@ref{tm-MUA})s.
1872 In other words, it is a setting to avoid to use tm-edit. If you don't
1873 want to compose MIME message or want to use other MIME composer, please
1874 use it instead of @file{mime-setup.el}.@refill
1876 For example, please insert following into @file{~/.emacs}:
1888 If you use @file{mime-setup.el}, you you don't need to load
1894 @node setting for VM, manual setting, tm-setup, Setting
1895 @section Setting for VM
1897 If you use @cindex{vm}@strong{vm}, please insert following in
1910 If you use @cindex{BBDB}@strong{BBDB}, please insert @code{(require
1911 'tm-vm)} @strong{after} @code{(bbdb-insinuate-vm)}.
1916 @node manual setting, , setting for VM, Setting
1917 @section Setting up without loading provided setup files
1919 You may find the valuable hints in @file{mime-setup.el} or
1920 @file{tm-setup.el} if you want to set up MIME environment
1921 without loading the tm-provided setup files.
1927 Current tm provides some convenient features to expect tm-edit, and
1928 they can not use if @file{mime-setup.el} is not used. If you
1929 want to set up original setting to use tm-edit, please declare
1933 (provide 'mime-setup)
1940 @node Bug report, Concept Index, Setting, Top
1941 @chapter How to report bug and about mailing list of tm
1943 If you write bug-reports and/or suggestions for improvement, please
1944 send them to the tm Mailing List:
1948 Japanese <bug-tm-ja@@chamonix.jaist.ac.jp>
1950 English <bug-tm-en@@chamonix.jaist.ac.jp>
1954 Notice that, we does not welcome bug reports about too old version.
1955 Bugs in old version might be fixed. So please try latest version at
1958 You should write @cindex{good bug report}@strong{good bug report}. If
1959 you write only ``tm does not work'', we can not find such situations.
1960 At least, you should write name, type, variants and version of OS,
1961 emacs, tm and MUA, and setting. In addition, if error occurs, to send
1962 backtrace is very important. (cf. @ref{(emacs)Bugs}) @refill
1964 Bug may not appear only your environment, but also in a lot of
1965 environment (otherwise it might not bug). Therefor if you send mail to
1966 author directly, we must write a lot of mails. So please send mail to
1967 address for tm bugs instead of author.@refill
1969 Via the tm ML, you can report tm bugs, obtain the latest release of
1970 tm, and discuss future enhancements to tm. To join the tm ML, send
1975 Japanese <tm-ja-admin@@chamonix.jaist.ac.jp>
1977 English <tm-en-admin@@chamonix.jaist.ac.jp>
1981 Since the user registration is done manually, please write the mail
1982 body in human-recognizable language (^_^).
1985 @node Concept Index, Variable Index, Bug report, Top
1986 @chapter Concept Index
1990 @node Variable Index, , Concept Index, Top
1991 @chapter Variable Index