\input texinfo.tex
@setfilename tm-en.info
-@settitle{tm 7.98 Manual (English Version)}
+@settitle{tm 7.100 Manual (English Version)}
@titlepage
-@title tm 7.98 Manual (English Version)
+@title tm 7.100 Manual (English Version)
@author MORIOKA Tomohiko <morioka@@jaist.ac.jp>
-@subtitle 1996/12/24
+@subtitle 1996/12/25
@end titlepage
@node Top, Introduction, (dir), (dir)
-@top tm 7.98 Manual (English Version)
+@top tm 7.100 Manual (English Version)
@ifinfo
* Introduction:: What is tm?
* Setting::
* Bug report:: How to report bug and about mailing list of tm
+* Acknowledgments::
* Concept Index::
* Variable Index::
@end menu
* Emacs::
* encoded-word::
* encapsulation::
+* entity:: Entity
* euc-kr::
* FTP:: FTP
* GB 2312:: GB 2312-1980
@node 7bit, 8bit, Glossary, Glossary
@subsection 7bit
+@cindex 7bit (textual) string
+@cindex 7bit data
+@cindex 7bit
-@cindex{7bit}@strong{7bit} means any integer between 0 .. 127.@refill
+@strong{7bit} means any integer between 0 .. 127.@refill
-Any data represented by 7bit integers is called @cindex{7bit
-data}@strong{7bit data}.@refill
+Any data represented by 7bit integers is called @strong{7bit data}.@refill
Textual string consisted of Control characters between 0 .. 31 and 127,
and space represented by 32, and graphic characters between 33 .. 236
-are called @cindex{7bit (textual) string}@strong{7bit (textual)
-string}.@refill
+are called @strong{7bit (textual) string}.@refill
Traditional Internet MTA (@ref{MTA}) can translate 7bit data, so it is
no need to translate by Quoted-Printable (@ref{Quoted-Printable}) or
Base64 (@ref{Base64}) for 7bit data.@refill
However if there are too long lines, it can not translate by 7bit MTA
-even if it is 7bit data. RFC 821 (@ref{RFC 821}) and RFC 2045 (@ref{RFC
-2045}) require lines in 7bit data must be less than 998 bytes. So if a
+even if it is 7bit data. RFC 821 (@ref{RFC 821}) and RFC 2045 (@ref{RFC 2045}) require lines in 7bit data must be less than 998 bytes. So if a
``7bit data'' has a line more than 999 bytes, it is regarded as binary
(@ref{binary}). For example, Postscript file should be encoded by
Quoted-Printable.
@node 8bit, 94-character set, 7bit, Glossary
@subsection 8bit
+@cindex 8bit (textual) string
+@cindex 8bit data
+@cindex 8bit
-@cindex{8bit}@strong{8bit} means any integer between 0 .. 255.@refill
+@strong{8bit} means any integer between 0 .. 255.@refill
-Any data represented by 8bit integers is called @cindex{8bit
-data}@strong{8bit data}.@refill
+Any data represented by 8bit integers is called @strong{8bit data}.@refill
Textual string consisted of Control characters between 0 .. 31, 127, and
128 .. 159, and space represented by 32, and graphic characters between
-33 .. 236 and 160 .. 255 are called @cindex{8bit (textual)
-string}@strong{8bit (textual) string}.@refill
+33 .. 236 and 160 .. 255 are called @strong{8bit (textual) string}.@refill
For example, iso-8859-1 (@ref{iso-8859-1}) or euc-kr (@ref{euc-kr}) are
coded-character-set represented by 8bit textual string.@refill
@node 94-character set, 96-character set, 8bit, Glossary
@subsection 94-character set
+@cindex 94-character set
-@cindex{94-character set}@strong{94-character set} is a kind of 1 byte
-graphic character set (@ref{graphic character set}), each characters are
-in positions 02/01 (33) to 07/14 (126) or 10/01 (161) to 15/14 (254).
-(ex. ASCII (@ref{ASCII}), JIS X0201-Latin)
+@strong{94-character set} is a kind of 1 byte graphic character set
+(@ref{graphic character set}), each characters are in positions 02/01
+(33) to 07/14 (126) or 10/01 (161) to 15/14 (254). (ex. ASCII
+(@ref{ASCII}), JIS X0201-Latin)
@node 96-character set, 94x94-character set, 94-character set, Glossary
@subsection 96-character set
+@cindex 96-character set
-@cindex{96-character set}@strong{96-character set} is a kind of 1 byte
-graphic character set (@ref{graphic character set}), each characters are
-in positions 02/00 (32) to 07/15 (126) or 10/00 (160) to 15/15
-(255). (ex. ISO 8859)
+@strong{96-character set} is a kind of 1 byte graphic character set
+(@ref{graphic character set}), each characters are in positions 02/00
+(32) to 07/15 (126) or 10/00 (160) to 15/15 (255). (ex. ISO 8859)
@node 94x94-character set, ASCII, 96-character set, Glossary
@subsection 94x94-character set
+@cindex 94x94-character set
-@cindex{94x94-character set}@strong{94x94-character set} is a kind of 2
-byte graphic character set (@ref{graphic character set}), each bytes are
-in positions 02/01 (33) to 07/14 (126) or 10/01 (161) to 15/14 (254).
-(ex. JIS X0208 (@ref{JIS X0208}), GB 2312 (@ref{GB 2312}))
+@strong{94x94-character set} is a kind of 2 byte graphic character set
+(@ref{graphic character set}), each bytes are in positions 02/01 (33) to
+07/14 (126) or 10/01 (161) to 15/14 (254). (ex. JIS X0208 (@ref{JIS X0208}), GB 2312 (@ref{GB 2312}))
@node ASCII, Base64, 94x94-character set, Glossary
@subsection ASCII
+@cindex ANSI X3.4:1986
+@cindex ASCII
+@cindex ASCII
+
+@strong{ASCII} is a 94-character set (@ref{94-character set}) contains
+primary latin characters (A-Z, a-z), numbers and some characters. It is
+a standard of the United States of America. It is a variant of ISO 646
+(@ref{ISO 646}).
-@cindex{ASCII}@strong{ASCII} is a 94-character set (@ref{94-character
-set}) contains primary latin characters (A-Z, a-z), numbers and some
-characters. It is a standard of the United States of America. It is a
-variant of ISO 646 (@ref{ISO 646}).
-@cindex{ASCII}@cindex{ANSI X3.4:1986}
@noindent
[ASCII]
@quotation
@node Base64, binary, ASCII, Glossary
@subsection Base64
+@cindex pad
+@cindex Base64
-@cindex{Base64}@strong{Base64} is a transfer encoding method of MIME
-(@ref{MIME}) defined in RFC 2045 (@ref{RFC 2045}).@refill
+@strong{Base64} is a transfer encoding method of MIME (@ref{MIME})
+defined in RFC 2045 (@ref{RFC 2045}).@refill
The encoding process represents 24-bit groups of input bits as output
strings of 4 encoded characters. Encoded characters represent integer 0
-.. 63 or @cindex{pad}@strong{pad}. Base64 data must be 4 * n bytes, so
-pad is used to adjust size.@refill
+.. 63 or @strong{pad}. Base64 data must be 4 * n bytes, so pad is used
+to adjust size.@refill
These 65 characters are subset of all versions of ISO 646, including
US-ASCII, and all versions of EBCDIC. So it is safe even if it is
@node binary, cn-gb, Base64, Glossary
@subsection binary
+@cindex binary
-Any byte stream is called @cindex{binary}@strong{binary}.@refill
+Any byte stream is called @strong{binary}.@refill
It does not require structureof lines. It differs from from 8bit
(@ref{8bit}).@refill
A MIME charset (@ref{MIME charset}) for simplified Chinese mainly used
in the Chinese mainland.@refill
-It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
-set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
+It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
(@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}).@refill
It is defined in RFC 1922 (@ref{RFC 1922}).
@node cn-big5, CNS 11643, cn-gb, Glossary
@subsection cn-big5, big5
+@cindex BIG5
A MIME charset (@ref{MIME charset}) for traditional Chinese mainly used
in Taiwan and Hon Kong.@refill
-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
+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
standard.@refill
It is defined in RFC 1922 (@ref{RFC 1922}).@refill
-cf. @cindex{BIG5}
+cf.
@noindent
[BIG5]
@quotation
@node CNS 11643, coded character set, cn-big5, Glossary
@subsection CNS 11643-1992
+@cindex CNS 11643:1992
+@cindex CNS 11643-1992
-Graphic character set (@ref{Graphic character set})s for Chinese mainly
+Graphic character sets (@ref{graphic character set}) for Chinese mainly
written by traditional Chinese mainly used in Taiwan and Hong Kong. It
-is a standard of Taiwan. Currently there are seven 94x94 character set
-(@ref{94x94 character set}).@refill
+is a standard of Taiwan. Currently there are seven 94x94-character set
+(@ref{94x94-character set}).@refill
Final byte of ISO 2022 (@ref{ISO 2022}) are following:
@end table
-@cindex{CNS 11643-1992}@cindex{CNS 11643:1992}
+
@noindent
[CNS 11643-1992]
@quotation
@node Content-Disposition, Content-Type field, code extension, Glossary
@subsection Content-Disposition field
+@cindex RFC 1806
+@cindex Experimental
A field to specify presentation of entity or file name. It is an
extension for MIME (@ref{MIME}).@refill
-@cindex{Experimental}@cindex{RFC 1806}
+
@noindent
[RFC 1806]
@quotation
@node Content-Type field, Emacs, Content-Disposition, Glossary
@subsection Content-Type field
+@cindex parameter
+@cindex subtype
+@cindex type
Header field to represent information about body, such as media type
(@ref{media type}), MIME charset (@ref{MIME charset}). It is defined in
Content-Type field is defined as following:
@quotation
-``Content-Type'' ``:'' @cindex{type}@strong{type} ``/''
-@cindex{subtype}@strong{subtype} *( ``;'' @cindex{parameter}@strong{parameter} )
+``Content-Type'' ``:'' @strong{type} ``/''
+@strong{subtype} *( ``;'' @strong{parameter} )
@end quotation
@node encoded-word, encapsulation, Emacs, Glossary
@subsection encoded-word
+@cindex RFC 2047
+@cindex Standards Track
+@cindex RFC 2047
Representation non ASCII (@ref{ASCII}) characters in header. It is
-defined in @cindex{RFC 2047}@strong{RFC 2047}.@refill
+defined in @strong{RFC 2047}.@refill
+
-@cindex{Standards Track}@cindex{RFC 2047}
@noindent
[RFC 2047]
@quotation
-@node encapsulation, euc-kr, encoded-word, Glossary
+@node encapsulation, entity, encoded-word, Glossary
@subsection encapsulation
Method to insert whole Internet message (@ref{RFC 822}) into another
-@node euc-kr, FTP, encapsulation, Glossary
+@node entity, euc-kr, encapsulation, Glossary
+@subsection Entity
+
+Header fields and contents of a message or one of the parts in the body
+of a multipart (@ref{multipart}) entity.
+
+@noindent
+@strong{[Memo]}
+@quotation
+
+In this document, `entity' might be called ``part''.
+@end quotation
+
+
+
+@node euc-kr, FTP, entity, Glossary
@subsection euc-kr
+@cindex KS C 5861:1992
+@cindex euc-kr
A MIME charset (@ref{MIME charset}) for Korean.@refill
-It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
-set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
+It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
(@ref{ASCII}) to combine KS C5601 (@ref{KS C5601}).@refill
It is defined in RFC 1557 (@ref{RFC 1557}).@refill
-cf. @cindex{euc-kr}@cindex{KS C 5861:1992}
+cf.
@noindent
[euc-kr]
@quotation
@node FTP, GB 2312, euc-kr, Glossary
@subsection FTP
+@cindex RFC 959
+@cindex STD 9
+@cindex FTP
+
-@cindex{FTP}@cindex{STD 9}@cindex{RFC 959}
@noindent
[FTP: RFC 959]
@quotation
@node GB 2312, GB 8565.2, FTP, Glossary
@subsection GB 2312-1980
+@cindex GB 2312:1980
+@cindex GB 2312
-A 94x94 character set (@ref{94x94 character set}) for Chinese mainly
+A 94x94-character set (@ref{94x94-character set}) for Chinese mainly
written by simplified Chinese mainly used in the Chinese mainland. It
is a standard of China.@refill
Final byte of ISO 2022 (@ref{ISO 2022}) is 04/01 (`A').
-@cindex{GB 2312}@cindex{GB 2312:1980}
+
@noindent
[GB 2312]
@quotation
@node GB 8565.2, graphic character set, GB 2312, Glossary
@subsection GB 8565.2-1988
+@cindex GB 8565.2:1988
+@cindex GB 8565.2
-A 94x94 character set (@ref{94x94 character set}) for Chinese as
+A 94x94-character set (@ref{94x94-character set}) for Chinese as
supplement to GB 2312 (@ref{GB 2312}). It is a standard of China.
-@cindex{GB 8565.2}@cindex{GB 8565.2:1988}
+
@noindent
[GB 8565.2]
@quotation
@node graphic character set, hz-gb2312, GB 8565.2, Glossary
@subsection Graphic Character Set
-Coded character set (@ref{Coded character set}) for graphic characters.
+Coded character set (@ref{coded character set}) for graphic characters.
@node hz-gb2312, ISO 2022, graphic character set, Glossary
@subsection hz-gb2312
+@cindex RFC 1843
+@cindex Informational
+@cindex RFC 1842
+@cindex Informational
A MIME charset (@ref{MIME charset}) for simplified Chinese mainly used
in the Chinese mainland.@refill
It is defined in RFC 1842 and 1843.
-@cindex{Informational}@cindex{RFC 1842}
+
@noindent
[RFC 1842]
@quotation
August 1995, Informational.
@end quotation
-@cindex{Informational}@cindex{RFC 1843}
+
@noindent
[RFC 1843]
@quotation
@node ISO 2022, iso-2022-cn, hz-gb2312, Glossary
@subsection ISO 2022
+@cindex ISO/IEC 2022:1994
+@cindex ISO 2022
It is a standard for character code structure and code extension
(@ref{code extension}) technique.
-@cindex{ISO 2022}@cindex{ISO/IEC 2022:1994}
+
@noindent
[ISO 2022]
@quotation
A MIME charset (@ref{MIME charset}) for Chinese.@refill
-It is a 7bit (@ref{7bit}) coded character set (@ref{coded character
-set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
+It is a 7bit (@ref{7bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
(@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}) and/or CNS 11643 plain
1, plain 2 (@ref{CNS 11643}).@refill
A MIME charset (@ref{MIME charset}) for Chinese.@refill
-It is a 7bit (@ref{7bit}) coded character set (@ref{coded character
-set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
+It is a 7bit (@ref{7bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
(@ref{ASCII}) to combine GB 2312 (@ref{GB 2312}), CNS 11643 plain 1 .. 7
(@ref{CNS 11643}), ISO-IR-165 (@ref{ISO-IR-165}) and other Chinese
graphic character sets.@refill
@node iso-2022-jp, iso-2022-jp-2, iso-2022-cn-ext, Glossary
@subsection iso-2022-jp
+@cindex RFC 1468
+@cindex iso-2022-jp
A MIME charset (@ref{MIME charset}) for Japanese.@refill
-It is a 7bit (@ref{7bit}) coded character set (@ref{coded character
-set}) based on old ISO 2022 (@ref{ISO 2022}). It switches ASCII
-(@ref{ASCII}), JIS X0201-Latin, JIS X0208-1978 (@ref{JIS C6226-1978})
-and JIS X0208-1983 (@ref{JIS X0208}).@refill
+It is a 7bit (@ref{7bit}) coded character set (@ref{coded character set}) based on old ISO 2022 (@ref{ISO 2022}). It switches ASCII
+(@ref{ASCII}), JIS X0201-Latin, JIS X0208-1978 (@ref{JIS C6226}) and JIS
+X0208-1983 (@ref{JIS X0208}).@refill
It is defined in RFC 1468.@refill
@end quotation
-@cindex{iso-2022-jp}@cindex{RFC 1468}
+
@noindent
[iso-2022-jp: RFC 1468]
@quotation
@node iso-2022-jp-2, iso-2022-kr, iso-2022-jp, Glossary
@subsection iso-2022-jp-2
+@cindex RFC 1554
+@cindex Informational
+@cindex iso-2022-jp-2
A MIME charset (@ref{MIME charset}), which is a multilingual extension
of iso-2022-jp (@ref{iso-2022-jp}).@refill
It is defined in RFC 1554.
-@cindex{iso-2022-jp-2}@cindex{Informational}@cindex{RFC 1554}
+
@noindent
[iso-2022-jp-2: RFC 1554]
@quotation
A MIME charset (@ref{MIME charset}) for Korean language (Hangul
script).@refill
-It is based on ISO 2022 (@ref{ISO 2022}) code extension (@ref{code
-extension}) technique to extend ASCII (@ref{ASCII}) to use KS C5601
+It is based on ISO 2022 (@ref{ISO 2022}) code extension (@ref{code extension}) technique to extend ASCII (@ref{ASCII}) to use KS C5601
(@ref{KS C5601}) as 7bit (@ref{7bit}) text.@refill
It is defined in RFC 1557 (@ref{RFC 1557}).
@node ISO 646, ISO 8859-1, iso-2022-kr, Glossary
@subsection ISO 646
+@cindex ISO/IEC 646:1991
+@cindex ISO 646
+
-@cindex{ISO 646}@cindex{ISO/IEC 646:1991}
@noindent
[ISO 646]
@quotation
@node ISO 8859-1, iso-8859-1, ISO 646, Glossary
@subsection ISO 8859-1
+@cindex ISO 8859-1:1987
+@cindex ISO 8859-1
+
-@cindex{ISO 8859-1}@cindex{ISO 8859-1:1987}
@noindent
[ISO 8859-1]
@quotation
@node iso-8859-1, ISO 8859-2, ISO 8859-1, Glossary
@subsection iso-8859-1
+@cindex iso-8859-1
-@cindex{iso-8859-1}@strong{iso-8859-1} is a MIME charset (@ref{MIME
-charset}) for west-European languages written by Latin script.@refill
+@strong{iso-8859-1} is a MIME charset (@ref{MIME charset}) for
+west-European languages written by Latin script.@refill
-It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
-set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
+It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
(@ref{ASCII}) to combine ISO 8859-1 (@ref{ISO 8859-1}).@refill
It is defined in RFC 2046 (@ref{RFC 2046}).
@node ISO 8859-2, iso-8859-2, iso-8859-1, Glossary
@subsection ISO 8859-2
+@cindex ISO 8859-2:1987
+@cindex ISO 8859-2
+
-@cindex{ISO 8859-2}@cindex{ISO 8859-2:1987}
@noindent
[ISO 8859-2]
@quotation
@node iso-8859-2, ISO 8859-3, ISO 8859-2, Glossary
@subsection iso-8859-2
+@cindex iso-8859-2
-@cindex{iso-8859-2}@strong{iso-8859-2} is a MIME charset (@ref{MIME
-charset}) for east-European languages written by Latin script.@refill
+@strong{iso-8859-2} is a MIME charset (@ref{MIME charset}) for
+east-European languages written by Latin script.@refill
-It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
-set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
+It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
(@ref{ASCII}) to combine ISO 8859-2 (@ref{ISO 8859-2}).@refill
It is defined in RFC 2046 (@ref{RFC 2046}).
@node ISO 8859-3, ISO 8859-4, iso-8859-2, Glossary
@subsection ISO 8859-3
+@cindex ISO 8859-3:1988
+@cindex ISO 8859-3
+
-@cindex{ISO 8859-3}@cindex{ISO 8859-3:1988}
@noindent
[ISO 8859-3]
@quotation
@node ISO 8859-4, ISO 8859-5, ISO 8859-3, Glossary
@subsection ISO 8859-4
+@cindex ISO 8859-4:1988
+@cindex ISO 8859-4
+
-@cindex{ISO 8859-4}@cindex{ISO 8859-4:1988}
@noindent
[ISO 8859-4]
@quotation
@node ISO 8859-5, iso-8859-5, ISO 8859-4, Glossary
@subsection ISO 8859-5
+@cindex ISO 8859-5:1988
+@cindex ISO 8859-5
+
-@cindex{ISO 8859-5}@cindex{ISO 8859-5:1988}
@noindent
[ISO 8859-5]
@quotation
@node iso-8859-5, ISO 8859-6, ISO 8859-5, Glossary
@subsection iso-8859-5
+@cindex iso-8859-5
-@cindex{iso-8859-5}@strong{iso-8859-5} is a MIME charset (@ref{MIME
-charset}) for Cyrillic script.@refill
+@strong{iso-8859-5} is a MIME charset (@ref{MIME charset}) for Cyrillic
+script.@refill
-It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
-set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
+It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
(@ref{ASCII}) to combine ISO 8859-5 (@ref{ISO 8859-5}).@refill
It is defined in RFC 2046 (@ref{RFC 2046}).
@node ISO 8859-6, ISO 8859-7, iso-8859-5, Glossary
@subsection ISO 8859-6
+@cindex ISO 8859-6:1987
+@cindex ISO 8859-6
+
-@cindex{ISO 8859-6}@cindex{ISO 8859-6:1987}
@noindent
[ISO 8859-6]
@quotation
@node ISO 8859-7, iso-8859-7, ISO 8859-6, Glossary
@subsection ISO 8859-7
+@cindex ISO 8859-7:1987
+@cindex ISO 8859-7
+
-@cindex{ISO 8859-7}@cindex{ISO 8859-7:1987}
@noindent
[ISO 8859-7]
@quotation
@node iso-8859-7, ISO 8859-8, ISO 8859-7, Glossary
@subsection iso-8859-7
+@cindex RFC 1947
+@cindex Informational
+@cindex iso-8859-7
+@cindex iso-8859-7
-@cindex{iso-8859-7}@strong{iso-8859-7} is a MIME charset (@ref{MIME
-charset}) for Greek script.@refill
+@strong{iso-8859-7} is a MIME charset (@ref{MIME charset}) for Greek
+script.@refill
-It is a 8bit (@ref{8bit}) coded character set (@ref{coded character
-set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
+It is a 8bit (@ref{8bit}) coded character set (@ref{coded character set}) based on ISO 2022 (@ref{ISO 2022}). It extends ASCII
(@ref{ASCII}) to combine ISO 8859-7 (@ref{ISO 8859-7}).@refill
It is defined in RFC 1947.
-@cindex{iso-8859-7}@cindex{Informational}@cindex{RFC 1947}
+
@noindent
[iso-8859-7: RFC 1947]
@quotation
@node ISO 8859-8, ISO 8859-9, iso-8859-7, Glossary
@subsection ISO 8859-8
+@cindex ISO 8859-8:1988
+@cindex ISO 8859-8
+
-@cindex{ISO 8859-8}@cindex{ISO 8859-8:1988}
@noindent
[ISO 8859-8]
@quotation
@node ISO 8859-9, ISO-IR-165, ISO 8859-8, Glossary
@subsection ISO 8859-9
+@cindex ISO 8859-9:1990
+@cindex ISO 8859-9
+
-@cindex{ISO 8859-9}@cindex{ISO 8859-9:1990}
@noindent
[ISO 8859-9]
@quotation
written by simplified Chinese mainly used in the Chinese mainland
registered by CCITT.@refill
-It consists of GB 2312 (@ref{GB 2312}), GB 8865.2 (@ref{GB 8865.2}) and
+It consists of GB 2312 (@ref{GB 2312}), GB 8565.2 (@ref{GB 8565.2}) and
additional 150 characters.@refill
Final byte of ISO 2022 (@ref{ISO 2022}) is 04/05 (`E').
@node JIS X0201, JIS C6226, ISO-IR-165, Glossary
@subsection JIS X0201
+@cindex JIS X 0201:1997? draft
+@cindex JIS X0201-1997?
+@cindex JIS X 0201-1976:
+@cindex JIS X0201-1976
+@cindex JIS C6220-1976
It defines two 94-character set (@ref{94-character set}), for Latin
script (a variant of ISO 646 (@ref{ISO 646})) and Katakana script, and
7bit and 8bit coded character set (@ref{coded character set})s.@refill
-It was renamed from @cindex{JIS C6220-1976}@strong{JIS C6220-1976}.
+It was renamed from @strong{JIS C6220-1976}.
+
-@cindex{JIS X0201-1976}@cindex{JIS X 0201-1976:}
@noindent
[JIS X0201-1976]
@quotation
In addition, revised version will be published in 1997.
-@cindex{JIS X0201-1997?}@cindex{JIS X 0201:1997? draft}
+
@noindent
[JIS X0201-1997?]
@quotation
@node JIS X0208, JIS X0212, JIS C6226, Glossary
@subsection JIS X0208
+@cindex JIS X 0208:1997? draft
+@cindex JIS X0208-1997?
+@cindex JIS X0208:1983,1990
+@cindex JIS X0208-1983,1990
+@cindex JIS C6226:1978
+@cindex JIS X0208-1978
A 94x94-character set (@ref{94x94-character set}) for Japanese.
Japanese standard. It was published in 1978, and revised in 1983 and
requires `identify revised registration' sequence, ESC 02/06 4/0 as
prefix of designation sequence.
-@cindex{JIS X0208-1978}@cindex{JIS C6226:1978}
+
@noindent
[JIS X0208-1978]
@quotation
set for information interchange'', JIS C6226:1978.
@end quotation
-@cindex{JIS X0208-1983,1990}@cindex{JIS X0208:1983,1990}
+
@noindent
[JIS X0208-1983,1990]
@quotation
In addition, revised version will be published in 1997. (It does not
change graphic character set)
-@cindex{JIS X0208-1997?}@cindex{JIS X 0208:1997? draft}
+
@noindent
[JIS X0208-1997?]
@quotation
@node JIS X0212, koi8-r, JIS X0208, Glossary
@subsection JIS X0212-1990
-A 94x94 character set (@ref{94x94 character set}) for Japanese as
+A 94x94-character set (@ref{94x94-character set}) for Japanese as
supplement to JIS X0208 (@ref{JIS X0208}). It is a standard of
Japan.@refill
@node koi8-r, KS C5601, JIS X0212, Glossary
@subsection koi8-r
+@cindex RFC 1489
A MIME charset (@ref{MIME charset}) for Cyrillic script for Russian or
other languages.@refill
-It is a 1 byte 8bit (@ref{8bit}) coded character set (@ref{coded
-character set}), not based on ISO 2022 (@ref{ISO 2022}). It is a
+It is a 1 byte 8bit (@ref{8bit}) coded character set (@ref{coded character set}), not based on ISO 2022 (@ref{ISO 2022}). It is a
de-fact standard.@refill
It is defined in RFC 1489.@refill
-@cindex{RFC 1489}
+
@noindent
[RFC 1489]
@quotation
@node KS C5601, media type, koi8-r, Glossary
@subsection KS C5601-1987
+@cindex KS C 5601:1987
+@cindex KS C5601
A 94x94-character set (@ref{94x94-character set}) for Korean language
-(Hangul script). Korean Standard. Final byte of ISO 2022 (@ref{ISO
-2022}) is 04/03 (`C').
+(Hangul script). Korean Standard. Final byte of ISO 2022 (@ref{ISO 2022}) is 04/03 (`C').
+
-@cindex{KS C5601}@cindex{KS C 5601:1987}
@noindent
[KS C5601]
@quotation
@node media type, message, KS C5601, Glossary
@subsection media type
-
-@cindex{media type}@strong{media type} specifies the nature of the data
-in the body of MIME (@ref{MIME}) entity (@ref{entity}). It consists of
-@cindex{type}@strong{type} and @cindex{subtype}@strong{subtype}. It is
-defined in RFC 2046 (@ref{RFC 2046}).@refill
+@cindex x-token
+@cindex message
+@cindex multipart
+@cindex application
+@cindex video
+@cindex audio
+@cindex image
+@cindex text
+@cindex subtype
+@cindex type
+@cindex media type
+
+@strong{media type} specifies the nature of the data in the body of MIME
+(@ref{MIME}) entity (@ref{entity}). It consists of @strong{type} and
+@strong{subtype}. It is defined in RFC 2046 (@ref{RFC 2046}).@refill
Currently there are following types:
@itemize @bullet
@item
-@cindex{text}@strong{text}
+@strong{text}
@item
-@cindex{image}@strong{image}
+@strong{image}
@item
-@cindex{audio}@strong{audio}
+@strong{audio}
@item
-@cindex{video}@strong{video}
+@strong{video}
@item
-@cindex{application}@strong{application}
+@strong{application}
@item
-@cindex{multipart}@strong{multipart} (@ref{multipart})
+@strong{multipart} (@ref{multipart})
@item
-@cindex{message}@strong{message}
+@strong{message}
@end itemize
You can refer registered media types at MEDIA TYPES
(ftp://ftp.isi.edu/in-notes/iana/assignments/media-types).@refill
-In addition, you can use private type or subtype using
-@cindex{x-token}@strong{x-token}, which as the prefix `x-'. However you
-can not use them in public.@refill
+In addition, you can use private type or subtype using @strong{x-token},
+which as the prefix `x-'. However you can not use them in
+public.@refill
(cf. @ref{Content-Type field})
@node message/rfc822, method, message, Glossary
@subsection message/rfc822
+@cindex message/rfc822
-@cindex{message/rfc822}@strong{message/rfc822} indicates that the body
-contains an encapsulated message, with the syntax of an RFC 822
-(@ref{RFC 822}) message. It is the replacement of traditional RFC 934
-(@ref{RFC 934}) encapsulation. It is defined in RFC 2046 (@ref{RFC
-2046}).
+@strong{message/rfc822} indicates that the body contains an encapsulated
+message, with the syntax of an RFC 822 (@ref{RFC 822}) message. It is
+the replacement of traditional RFC 934 (@ref{RFC 934}) encapsulation.
+It is defined in RFC 2046 (@ref{RFC 2046}).
@node method, MIME, message/rfc822, Glossary
@subsection method
+@cindex external method
+@cindex internal method
Application program of tm-view to process for specified media type
(@ref{media type}) when user plays an entity.@refill
-There are two kinds of methods, @cindex{internal method}@strong{internal
-method} and @cindex{external method}@strong{external method}. Internal
-method is written by Emacs Lisp. External method is written by C or
-script languages and called by asynchronous process call.@refill
+There are two kinds of methods, @strong{internal method} and
+@strong{external method}. Internal method is written by Emacs Lisp.
+External method is written by C or script languages and called by
+asynchronous process call.@refill
(cf. @ref{(tm-view-en)method})
@node MIME, MIME charset, method, Glossary
@subsection MIME
+@cindex Multipurpose Internet Mail Extensions
-MIME stands for @cindex{Multipurpose Internet Mail
-Extensions}@strong{Multipurpose Internet Mail Extensions}, it is an
+MIME stands for @strong{Multipurpose Internet Mail Extensions}, it is an
extension for RFC 822 (@ref{RFC 822}).@refill
According to RFC 2045:@refill
@node MIME charset, MTA, MIME, Glossary
@subsection MIME charset
-Coded character set (@ref{Coded character set}) used in Content-Type
+Coded character set (@ref{coded character set}) used in Content-Type
field (@ref{Content-Type field}) or charset parameter of encoded-word
(@ref{encoded-word}).@refill
@node MTA, MUA, MIME charset, Glossary
@subsection MTA
+@cindex Message Transfer Agent
-@cindex{Message Transfer Agent}@strong{Message Transfer Agent}. It
-means mail transfer programs (ex. sendmail) and news servers.@refill
+@strong{Message Transfer Agent}. It means mail transfer programs
+(ex. sendmail) and news servers.@refill
(cf. @ref{MUA})
@node MUA, MULE, MTA, Glossary
@subsection MUA
+@cindex Message User Agent
-@cindex{Message User Agent}@strong{Message User Agent}. It means mail
-readers and news readers.@refill
+@strong{Message User Agent}. It means mail readers and news
+readers.@refill
(cf. @ref{MTA})
@node MULE, multipart, MUA, Glossary
@subsection MULE
+@cindex XEmacs/mule
+@cindex Emacs/mule
+@cindex MULE
+@cindex mule
+@cindex MULE
Multilingual extension of GNU Emacs (@ref{Emacs}) by HANDA Ken'ichi et
al.
-@cindex{MULE}
+
@noindent
[MULE]
@quotation
So now, there are 3 kinds of mule variants.@refill
-In this document, @cindex{mule}@strong{mule} means any mule variants,
-@cindex{MULE}@strong{MULE} means original MULE (..2.3),
-@cindex{Emacs/mule}@strong{Emacs/mule} means mule merged Emacs,
-@cindex{XEmacs/mule}@strong{XEmacs/mule} means XEmacs with mule feature.
+In this document, @strong{mule} means any mule variants,
+@strong{MULE} means original MULE (..2.3),
+@strong{Emacs/mule} means mule merged Emacs,
+@strong{XEmacs/mule} means XEmacs with mule feature.
@node multipart, multipart/alternative, MULE, Glossary
@subsection Multipart
+@cindex multipart
-@cindex{multipart}@strong{multipart} means media type (@ref{media type})
-to insert multiple entities (@ref{entities}) in a single body. Or it
-also indicates a message consists of multiple entities.@refill
+@strong{multipart} means media type (@ref{media type}) to insert
+multiple entities (@ref{entity}) in a single body. Or it also indicates
+a message consists of multiple entities.@refill
There are following subtypes registered in RFC 2046 (@ref{RFC 2046}):
@node multipart/alternative, multipart/digest, multipart, Glossary
@subsection multipart/alternative
+@cindex multipart/digest
-@cindex{multipart/digest}@strong{multipart/digest} is one of multipart
-(@ref{multipart}) media types. This type is syntactically identical to
-multipart/mixed (@ref{multipart/mixed}), but the semantics are
-different. In particular, each of the body parts is an ``alternative''
-version of the same information.@refill
+@strong{multipart/digest} is one of multipart (@ref{multipart}) media
+types. This type is syntactically identical to multipart/mixed
+(@ref{multipart/mixed}), but the semantics are different. In
+particular, each of the body parts is an ``alternative'' version of the
+same information.@refill
(cf. @ref{RFC 2046})
@node multipart/digest, multipart/encrypted, multipart/alternative, Glossary
@subsection multipart/digest
+@cindex multipart/digest
-@cindex{multipart/digest}@strong{multipart/digest} is one of multipart
-(@ref{multipart}) media types. This type is syntactically identical to
-multipart/mixed (@ref{multipart/mixed}), but the semantics are
-different. In particular, in a digest, the default Content-Type value
-for a body part is changed from text/plain (@ref{text/plain}) to
-message/rfc822 (@ref{message/rfc822}).@refill
+@strong{multipart/digest} is one of multipart (@ref{multipart}) media
+types. This type is syntactically identical to multipart/mixed
+(@ref{multipart/mixed}), but the semantics are different. In
+particular, in a digest, the default Content-Type value for a body part
+is changed from text/plain (@ref{text/plain}) to message/rfc822
+(@ref{message/rfc822}).@refill
This is the replacement of traditional RFC 1153 (@ref{RFC 1153}) based
encapsulation (@ref{encapsulation}).@refill
@node multipart/parallel, multipart/signed, multipart/mixed, Glossary
@subsection multipart/parallel
+@cindex multipart/parallel
-@cindex{multipart/parallel}@strong{multipart/parallel} is a subtype of
-multipart (@ref{multipart}). This type is syntactically identical to
-multipart/mixed (@ref{multipart/mixed}), but the semantics are
-different. In particular, in a parallel entity, the order of body parts
-is not significant.@refill
+@strong{multipart/parallel} is a subtype of multipart (@ref{multipart}).
+This type is syntactically identical to multipart/mixed
+(@ref{multipart/mixed}), but the semantics are different. In
+particular, in a parallel entity, the order of body parts is not
+significant.@refill
(cf. @ref{RFC 2046})
@node PGP, PGP-kazu, multipart/signed, Glossary
@subsection PGP
+@cindex RFC 1991
+@cindex Informational
+@cindex PGP
+@cindex Pretty Good Privacy
A public key encryption program by Phil Zimmermann. It provides
encryption and signature for message (@ref{message}). PGP stands for
-@cindex{Pretty Good Privacy}@strong{Pretty Good Privacy}.@refill
+@strong{Pretty Good Privacy}.@refill
Traditional PGP uses RFC 934 (@ref{RFC 934}) encapsulation
(@ref{encapsulation}). It is conflict with MIME (@ref{MIME}). So
(@ref{PGP-kazu}) was proposed to use PGP encapsulation in MIME. But it
is obsoleted.@refill
-@cindex{PGP}@cindex{Informational}@cindex{RFC 1991}
+
@noindent
[PGP: RFC 1991]
@quotation
@node PGP-kazu, PGP/MIME, PGP, Glossary
@subsection PGP-kazu
+@cindex application/pgp
+@cindex PGP-kazu
-In this document, @cindex{PGP-kazu}@strong{PGP-kazu} means a method to
-use traditional PGP encapsulation in MIME (@ref{MIME}), proposed by
-YAMAMOTO Kazuhiko.@refill
+In this document, @strong{PGP-kazu} means a method to use traditional
+PGP encapsulation in MIME (@ref{MIME}), proposed by YAMAMOTO
+Kazuhiko.@refill
PGP-kazu defines a media type (@ref{media type}),
-@cindex{application/pgp}@strong{application/pgp}.@refill
+@strong{application/pgp}.@refill
In application/pgp entity, PGP encapsulation (@ref{encapsulation}) is
used. PGP encapsulation conflicts with MIME, so it requires
@node PGP/MIME, Quoted-Printable, PGP-kazu, Glossary
@subsection PGP/MIME
+@cindex RFC 2015
+@cindex Standards Track
+@cindex PGP/MIME
PGP (@ref{PGP}) and MIME (@ref{MIME}) integration proposed by Michael
Elkins.@refill
PGP/MIME (@ref{PGP/MIME}) will be standard of PGP message.
-@cindex{PGP/MIME}@cindex{Standards Track}@cindex{RFC 2015}
+
@noindent
[PGP/MIME: RFC 2015]
@quotation
@node Quoted-Printable, RFC 821, PGP/MIME, Glossary
@subsection Quoted-Printable
+@cindex Quoted-Printable
-@cindex{Quoted-Printable}@strong{Quoted-Printable} is a transfer
-encoding method of MIME (@ref{MIME}) defined in RFC 2045 (@ref{RFC
-2045}).@refill
+@strong{Quoted-Printable} is a transfer encoding method of MIME
+(@ref{MIME}) defined in RFC 2045 (@ref{RFC 2045}).@refill
If the data being encoded are mostly US-ASCII text, the encoded form of
the data remains largely recognizable by humans.@refill
@node RFC 821, RFC 822, Quoted-Printable, Glossary
@subsection RFC 821
+@cindex RFC 821
+@cindex STD 10
+@cindex SMTP
+
-@cindex{SMTP}@cindex{STD 10}@cindex{RFC 821}
@noindent
[SMTP: RFC 821]
@quotation
@node RFC 822, RFC 934, RFC 821, Glossary
@subsection RFC 822
+@cindex RFC 822
+@cindex STD 11
+@cindex Internet mail
+@cindex Internet message
+@cindex message header
-A RFC defines format of Internet mail message, mainly @cindex{message
-header}@strong{message
-header}.
+A RFC defines format of Internet mail message, mainly @strong{message header}.
@noindent
@strong{[Memo]}
@quotation
-news message is based on RFC 822, so @cindex{Internet
-message}@strong{Internet message} may be more suitable than
-@cindex{Internet mail}@strong{Internet mail} .
+news message is based on RFC 822, so @strong{Internet message} may be
+more suitable than @strong{Internet mail} .
@end quotation
-@cindex{STD 11}@cindex{RFC 822}
+
@noindent
[RFC 822]
@quotation
@node RFC 934, RFC 1036, RFC 822, Glossary
@subsection RFC 934
+@cindex RFC 934
+@cindex encapsulation
-A RFC defines an @cindex{encapsulation}@strong{encapsulation}
-(@ref{encapsulation}) method for Internet mail (@ref{RFC 822}).@refill
+A RFC defines an @strong{encapsulation} (@ref{encapsulation}) method for
+Internet mail (@ref{RFC 822}).@refill
It conflicts with MIME (@ref{MIME}), so you should use message/rfc822
(@ref{message/rfc822}).
-@cindex{RFC 934}
+
@noindent
[RFC 934]
@quotation
@node RFC 1036, RFC 1153, RFC 934, Glossary
@subsection RFC 1036
+@cindex RFC 1036
+@cindex USENET
A RFC defines format of USENET message. It is a subset of RFC 822
(@ref{RFC 822}). It is not Internet standard, but a lot of netnews
excepting Usenet uses it.
-@cindex{USENET}@cindex{RFC 1036}
+
@noindent
[USENET: RFC 1036]
@quotation
@node RFC 1153, RFC 1557, RFC 1036, Glossary
@subsection RFC 1153
+@cindex RFC 1153
+
-@cindex{RFC 1153}
@noindent
[RFC 1153]
@quotation
@node RFC 1557, RFC 1922, RFC 1153, Glossary
@subsection RFC 1557
+@cindex RFC 1557
+@cindex Informational
A RFC defines MIME charset (@ref{MIME charset})s for Korean, euc-kr
(@ref{euc-kr}) and iso-2022-kr (@ref{iso-2022-kr}).
-@cindex{Informational}@cindex{RFC 1557}
+
@noindent
[RFC 1557]
@quotation
@node RFC 1922, RFC 2045, RFC 1557, Glossary
@subsection RFC 1922
+@cindex RFC 1922
+@cindex Informational
+@cindex charset-extension
+@cindex charset-edition
A RFC defines MIME charset (@ref{MIME charset})s for Chinese,
iso-2022-cn (@ref{iso-2022-cn}), iso-2022-cn-ext
etc.@refill
In addition, it defines additional parameters of Content-Type field
-(@ref{Content-Type field}) field,
-@cindex{charset-edition}@strong{charset-edition} and
-@cindex{charset-extension}@strong{charset-extension}.
+(@ref{Content-Type field}) field, @strong{charset-edition} and
+@strong{charset-extension}.
+
-@cindex{Informational}@cindex{RFC 1922}
@noindent
[RFC 1922]
@quotation
@node RFC 2045, RFC 2046, RFC 1922, Glossary
@subsection RFC 2045
+@cindex RFC 2045
+@cindex Standards Track
+
-@cindex{Standards Track}@cindex{RFC 2045}
@noindent
[RFC 2045]
@quotation
@node RFC 2046, RFC 2048, RFC 2045, Glossary
@subsection RFC 2046
+@cindex RFC 2046
+@cindex Standards Track
+
-@cindex{Standards Track}@cindex{RFC 2046}
@noindent
[RFC 2046]
@quotation
@node RFC 2048, RFC 2049, RFC 2046, Glossary
@subsection RFC 2048
+@cindex RFC 2048
+@cindex Standards Track
+
-@cindex{Standards Track}@cindex{RFC 2048}
@noindent
[RFC 2048]
@quotation
@node RFC 2049, plain text, RFC 2048, Glossary
@subsection RFC 2049
+@cindex RFC 2049
+@cindex Standards Track
+
-@cindex{Standards Track}@cindex{RFC 2049}
@noindent
[RFC 2049]
@quotation
@node plain text, Security multipart, RFC 2049, Glossary
@subsection plain text
-A textual data represented by only coded character set (@ref{coded
-character set}). It does not have information about font or
+A textual data represented by only coded character set (@ref{coded character set}). It does not have information about font or
typesetting. (cf. @ref{text/plain})
@node Security multipart, text/enriched, plain text, Glossary
@subsection Security multipart
+@cindex RFC 1847
+@cindex Standards Track
+@cindex Security multipart
+@cindex multipart/encrypted
+@cindex multipart/signed
A format to represent signed/encrypted message in MIME
(@ref{MIME}).@refill
-It defines two multipart media types,
-@cindex{multipart/signed}@strong{multipart/signed}
-(@ref{multipart/signed}) and
-@cindex{multipart/encrypted}@strong{multipart/encrypted}
+It defines two multipart media types, @strong{multipart/signed}
+(@ref{multipart/signed}) and @strong{multipart/encrypted}
(@ref{multipart/encrypted}).@refill
MOSS and PGP/MIME (@ref{PGP/MIME}) are based on it.
-@cindex{Security multipart}@cindex{Standards Track}@cindex{RFC 1847}
+
@noindent
[Security multipart: RFC 1847]
@quotation
@node text/enriched, text/plain, Security multipart, Glossary
@subsection text/enriched
+@cindex RFC 1896
+@cindex text/enriched
+
-@cindex{text/enriched}@cindex{RFC 1896}
@noindent
[text/enriched: RFC 1896]
@quotation
@node text/plain, tm-kernel, text/enriched, Glossary
@subsection text/plain
+@cindex text/plain
-@cindex{text/plain}@strong{text/plain} is a media type (@ref{media
-type}) for plain text (@ref{plain text}), defined in RFC 2046 (@ref{RFC
-2046}).@refill
+@strong{text/plain} is a media type (@ref{media type}) for plain text
+(@ref{plain text}), defined in RFC 2046 (@ref{RFC 2046}).@refill
The default media type of ``text/plain; charset=us-ascii'' for Internet
mail describes existing Internet practice. That is, it is the type of
@node tm-MUA, us-ascii, tm-kernel, Glossary
@subsection tm-MUA
+@cindex tm-rmail
+@cindex tm-vm
+@cindex gnus-mime
+@cindex tm-gnus
+@cindex tm-mh-e
+@cindex tm oomori package
MUA (@ref{MUA}) or MUA extender using tm (@ref{tm-kernel}).@refill
-@cindex{tm oomori package}@strong{tm oomori package} has following extenders:
+@strong{tm oomori package} has following extenders:
@itemize @bullet
@item
-@cindex{tm-mh-e}@strong{tm-mh-e} (@ref{(tm-mh-e-en)})
+@strong{tm-mh-e} (@ref{(tm-mh-e-en)})
for mh-e (@ref{(mh-e)})
@item
-@cindex{tm-gnus}@strong{tm-gnus} (@ref{(tm-gnus_en)}) for GNUS
+@strong{tm-gnus} (@ref{(tm-gnus_en)}) for GNUS
@item
-@cindex{gnus-mime}@strong{gnus-mime} (@ref{(gnus-mime-en)}) for Gnus
+@strong{gnus-mime} (@ref{(gnus-mime-en)}) for Gnus
@item
-@cindex{tm-vm}@strong{tm-vm} (@ref{(tm-vm_en)}) for VM
+@strong{tm-vm} (@ref{(tm-vm_en)}) for VM
@item
-@cindex{tm-rmail}@strong{tm-rmail} for RMAIL
+@strong{tm-rmail} for RMAIL
@end itemize
@node us-ascii, , tm-MUA, Glossary
@subsection us-ascii
+@cindex ASCII
+@cindex us-ascii
A MIME charset (@ref{MIME charset}) for primary Latin script mainly
written by English or other languages.@refill
extension (@ref{code extension}) is not allowed.@refill
It is standard coded character set of Internet mail. If MIME charset is
-not specified, @cindex{us-ascii}@strong{us-ascii} is used as
-default.@refill
+not specified, @strong{us-ascii} is used as default.@refill
-In addition, @cindex{ASCII}@strong{ASCII} of RFC 822 (@ref{RFC 822})
-should be interpreted as us-ascii.
+In addition, @strong{ASCII} of RFC 822 (@ref{RFC 822}) should be
+interpreted as us-ascii.
@node Setting, Bug report, Introduction, Top
@node mime-setup, tm-setup, Setting, Setting
@section Normal setting
+@cindex mime-setup
-If you want normal setting, please use @cindex{mime-setup}@strong{mime-setup}.
+If you want normal setting, please use @strong{mime-setup}.
For example, please insert following into @file{~/.emacs}:
@lisp
@node signature, Notice about GNUS, mime-setup, mime-setup
@subsection signature
+@cindex automatic signature selection tool
-You can set up the @cindex{automatic signature selection
-tool}@strong{automatic signature selection
-tool} using @file{mime-setup}. If you want to
+You can set up the @strong{automatic signature selection tool} using @file{mime-setup}. If you want to
automatically select the signature file depending on how the message
headers show, add lines like shown below to your .emacs (Refer to the
reference manual of @file{signature.el} for more details).
@node tm-setup, setting for VM, mime-setup, Setting
@section Setting not to use tm-edit
+@cindex tm-setup
-@cindex{tm-setup}@strong{tm-setup} only sets up tm-MUA (@ref{tm-MUA})s.
-In other words, it is a setting to avoid to use tm-edit. If you don't
-want to compose MIME message or want to use other MIME composer, please
-use it instead of @file{mime-setup.el}.@refill
+@strong{tm-setup} only sets up tm-MUA (@ref{tm-MUA})s. In other words,
+it is a setting to avoid to use tm-edit. If you don't want to compose
+MIME message or want to use other MIME composer, please use it instead
+of @file{mime-setup.el}.@refill
For example, please insert following into @file{~/.emacs}:
@node setting for VM, manual setting, tm-setup, Setting
@section Setting for VM
+@cindex BBDB
+@cindex vm
-If you use @cindex{vm}@strong{vm}, please insert following in
+If you use @strong{vm}, please insert following in
@file{~/.vm}:
@lisp
@strong{[Notice]}
@quotation
-If you use @cindex{BBDB}@strong{BBDB}, please insert @code{(require
-'tm-vm)} @strong{after} @code{(bbdb-insinuate-vm)}.
+If you use @strong{BBDB}, please insert @code{(require 'tm-vm)}
+@strong{after} @code{(bbdb-insinuate-vm)}.
@end quotation
-@node Bug report, Concept Index, Setting, Top
+@node Bug report, Acknowledgments, Setting, Top
@chapter How to report bug and about mailing list of tm
+@cindex good bug report
If you write bug-reports and/or suggestions for improvement, please
send them to the tm Mailing List:
Bugs in old version might be fixed. So please try latest version at
first.@refill
-You should write @cindex{good bug report}@strong{good bug report}. If
-you write only ``tm does not work'', we can not find such situations.
-At least, you should write name, type, variants and version of OS,
-emacs, tm and MUA, and setting. In addition, if error occurs, to send
-backtrace is very important. (cf. @ref{(emacs)Bugs}) @refill
+You should write @strong{good bug report}. If you write only ``tm does
+not work'', we can not find such situations. At least, you should write
+name, type, variants and version of OS, emacs, tm and MUA, and setting.
+In addition, if error occurs, to send backtrace is very
+important. (cf. @ref{(emacs)Bugs}) @refill
Bug may not appear only your environment, but also in a lot of
environment (otherwise it might not bug). Therefor if you send mail to
body in human-recognizable language (^_^).
-@node Concept Index, Variable Index, Bug report, Top
+@node Acknowledgments, Concept Index, Bug report, Top
+@chapter Acknowledgments
+
+I thank MASUTANI Yasuhiro. He requested me a lot of important features
+and gave me a lot of suggestions when tm-view was born. tm-view is
+based on his influence.@refill
+
+I thank ENAMI Tsugutomo for work of @file{mime.el}, which is an origin
+of @file{tm-ew-d.el} and @file{mel-b.el}, and permission to rewrite for
+tm.@refill
+
+I thank OKABE Yasuo for work of internal method for LaTeX and automatic
+assembling method for message/partial. I thank UENO Hiroshi for work of
+internal method for tar archive.@refill
+
+I thank UMEDA Masanobu for his work of @file{mime.el}, which is the
+origin of tm-edit, and permission to rewrite his work as tm-edit.@refill
+
+I thank KOBAYASHI Shuhei for his work as a tm maintainer. In addition,
+he often points out or suggests about conformity with RFCs.@refill
+
+I thank Oscar Figueiredo for his work as the maintainer of tm-vm. He
+improves tm-vm and wrote a good manual of tm-vm.@refill
+
+Last of all, I thank members of two tm mailing lists, Japanese and
+English version.
+
+
+@node Concept Index, Variable Index, Acknowledgments, Top
@chapter Concept Index
@printindex cp
projects / elisp / tm.git / blobdiff