+Wed Dec 25 19:18:43 1996 MORIOKA Tomohiko <morioka@jaist.ac.jp>
+
+ * MEL: Version 6.2 was released.
+ * tm: Version 7.100 was released.
+ * tm-gnus: Version 7.28 was released.
+ * sinfo: Version 3.6 was released.
+
+ * Makefile (TM_FILES): forgot to add tm-edit-tipgp.el.
+ (TM_VM_FILES): forgot to add tm-vm_en.texi and tm-vm_en.info.
+
+Wed Dec 25 18:32:28 1996 MORIOKA Tomohiko <morioka@jaist.ac.jp>
+
+ * doc/tm-en.sgml (Entity): New node.
+
+Wed Dec 25 17:58:47 1996 MORIOKA Tomohiko <morioka@jaist.ac.jp>
+
+ * doc/tm-ja.sgml (Entity): New node.
+
+Wed Dec 25 17:39:02 1996 MORIOKA Tomohiko <morioka@jaist.ac.jp>
+
+ * doc/tm-en.sgml (Acknowledgments): New node.
+
+Wed Dec 25 17:30:09 1996 MORIOKA Tomohiko <morioka@jaist.ac.jp>
+
+ * doc/tm-ja.sgml (Acknowledgments): New node.
+
+Wed Dec 25 17:10:58 1996 MORIOKA Tomohiko <morioka@jaist.ac.jp>
+
+ * tm-edit.el (mime/editor-mode): modify DOC-string.
+
+Wed Dec 25 08:04:54 1996 MORIOKA Tomohiko <morioka@jaist.ac.jp>
+
+ * doc/tm-view-en.sgml, doc/tm-view-ja.sgml (Acknowledgments): New
+ node.
+
+Wed Dec 25 07:16:52 1996 MORIOKA Tomohiko <morioka@jaist.ac.jp>
+
+ * doc/tm-edit-en.sgml, doc/tm-edit-ja.sgml (Acknowledgments): New
+ node.
+
+\f
Tue Dec 24 16:00:05 1996 MORIOKA Tomohiko <morioka@jaist.ac.jp>
* tm: Version 7.99 was released.
#
-# $Id: Makefile,v 7.42 1996/12/10 14:57:42 morioka Exp morioka $
+# $Id: Makefile,v 7.43 1996/12/25 19:18:43 morioka Exp morioka $
#
-VERSION = 7.99
+VERSION = 7.100
SHELL = /bin/sh
MAKE = make
tm/tm-ftp.el tm/tm-latex.el tm/tm-html.el tm/tm-file.el \
tm/tm-tar.el \
tm/tm-bbdb.el \
- tm/tm-edit.el tm/tm-edit-mc.el tm/signature.el \
+ tm/tm-edit*.el tm/signature.el \
tm/tm-setup.el tm/mime-setup.el.in \
tm/sc-setup.el \
tm/methods/tm* tm/methods/ChangeLog \
TM_MAIL_FILES = tm-mail/TMAIL-ELS tm-mail/*.el tm-mail/ChangeLog
-TM_VM_FILES = tm-vm/TM-VM-ELS tm-vm/*.el tm-vm/ChangeLog
+TM_VM_FILES = tm-vm/TM-VM-ELS tm-vm/*.el tm-vm/*.texi tm-vm/*.info \
+ tm-vm/ChangeLog
TM_MUA_FILES = $(TM_MH_E_FILES) $(GNUS_MIME_FILES) $(TM_GNUS_FILES) \
$(TM_MAIL_FILES) $(TM_VM_FILES)
oomori:
cd doc; $(MAKE) tex
- cd ..; gtar cvf tm$(VERSION).tar $(FILES)
+ cd ..; gtar cvf tm-$(VERSION).tar $(FILES)
-cd ..; mkdir tm-$(VERSION)
cp ../tm-oomori/README.?? ../tm-$(VERSION)
- cd ../tm-$(VERSION); gtar xvf ../tm$(VERSION).tar
- cd ..; gtar cvzf tm$(VERSION).tar.gz tm-$(VERSION)
- cd ..; $(RM) -r tm-$(VERSION); rm tm$(VERSION).tar
+ cd ../tm-$(VERSION); gtar xvf ../tm-$(VERSION).tar
+ cd ..; gtar cvzf tm-$(VERSION).tar.gz tm-$(VERSION)
+ cd ..; $(RM) -r tm-$(VERSION); rm tm-$(VERSION).tar
release:
-Info file: tm-edit-en.info, -*-Text-*-
-produced by `texinfo-format-buffer'
-from file `tm-edit-en.texi'
-using `texinfmt.el' version 2.32 of 19 November 1993.
-
+This is Info file tm-edit-en.info, produced by Makeinfo-1.63 from the
+input file tm-edit-en.texi.
\1f
-File: tm-edit-en.info, Node: Top, Next: Introduction, Prev: (dir), Up: (dir)
-
-tm-edit 7.99 Reference Manual (English Version)
-***********************************************
+File: tm-edit-en.info, Node: Top, Next: Introduction, Prev: (dir), Up: (dir)
+tm-edit 7.100 Reference Manual (English Version)
+************************************************
-This file documents tm-edit, a MIME composer for GNU Emacs.
+ This file documents tm-edit, a MIME composer for GNU Emacs.
* Menu:
* Introduction:: What is tm-edit?
-* mime/editor-mode::
-* single-part operations::
-* enclosure operation::
-* other operations of mime/editor-mode::
+* mime/editor-mode::
+* single-part operations::
+* enclosure operation::
+* other operations of mime/editor-mode::
* tag specification for inserted file:: Default media-type or encoding for inserted file
-* transfer level::
+* transfer level::
* header:: Using non-ASCII characters in header
-* PGP::
-* Concept Index::
-* Function Index::
-* Variable Index::
-
+* PGP::
+* Acknowledgments::
+* Concept Index::
+* Function Index::
+* Variable Index::
\1f
-File: tm-edit-en.info, Node: Introduction, Next: mime/editor-mode, Prev: Top, Up: Top
+File: tm-edit-en.info, Node: Introduction, Next: mime/editor-mode, Prev: Top, Up: Top
What is tm-edit?
****************
-*tm-edit* is a general MIME composer for GNU
-Emacs.
+ *tm-edit* is a general MIME composer for GNU Emacs.
-tm-edit is based on mime.el by UMEDA Masanobu
+ tm-edit is based on mime.el by UMEDA Masanobu
<umerin@mse.kyutech.ac.jp>, who is famous as the author of GNUS.
tm-edit expands following points from `mime.el':
* based on RFC 1521/1522
- * Content-Disposition field (*Note (tm-en)Content-Disposition::) (RFC
- 1806) supports
+
+ * Content-Disposition field (*Note (tm-en)Content-Disposition::)
+ (RFC 1806) supports
+
* nested multi-part message (*Note (tm-en)multipart::)
+
* PGP (*Note PGP::) (PGP/MIME (RFC 2015) based on security multipart
(RFC 1847) and application/pgp based on traditional PGP)
- * strength automatic specification for parameter of file type
-
-
-In tm-MUA (*Note (tm-en)tm-MUA::), you can edit MIME message easily to
-use tm-edit.
+ * strength automatic specification for parameter of file type
+ In tm-MUA (*Note (tm-en)tm-MUA::), you can edit MIME message easily
+to use tm-edit.
\1f
-File: tm-edit-en.info, Node: mime/editor-mode, Next: single-part operations, Prev: Introduction, Up: Top
+File: tm-edit-en.info, Node: mime/editor-mode, Next: single-part operations, Prev: Introduction, Up: Top
mime/editor-mode
****************
-*mime/editor-mode* is a minor mode to
-compose MIME message. In this mode, *tag* represents various kinds of
-data, you can edit multi part (*Note (tm-en)multipart::) message.
+ *mime/editor-mode* is a minor mode to compose MIME message. In this
+mode, *tag* represents various kinds of data, you can edit multi part
+(*Note (tm-en)multipart::) message.
-There are 2 kinds of tags:
+ There are 2 kinds of tags:
* single-part tag
+
* multi-part tag
-single-part tag represents single part, this form is following:
+ single-part tag represents single part, this form is following:
--[[TYPE/SUBTYPE;PARAMETERS][ENCODING]
OPTIONAL-FIELDS]
-TYPE/SUBTYPE and PARAMETERS indicates type/subtype and parameters of
+ TYPE/SUBTYPE and PARAMETERS indicates type/subtype and parameters of
Content-Type field (*Note (tm-en)Content-Type field::). TYPE/SUBTYPE is
required, PARAMETERS is optional.
-ENCODING indicates Content-Transfer-Encoding field. It is optional too.
+ ENCODING indicates Content-Transfer-Encoding field. It is optional
+too.
-OPTIONAL-FIELDS is to represent another fields except Content-Type field
-and Content-Transfer-Encoding field.
+ OPTIONAL-FIELDS is to represent another fields except Content-Type
+field and Content-Transfer-Encoding field.
-multi-part tags represent multi part (*Note (tm-en)multipart::). They
-consist of a pair of *multi-part beginning tag* and *multi-part ending
-tag*.
+ multi-part tags represent multi part (*Note (tm-en)multipart::).
+They consist of a pair of *multi-part beginning tag* and *multi-part
+ending tag*.
-multi-part beginning tag's form is following:
+ multi-part beginning tag's form is following:
--<<TYPE>>-{
-multi-part ending tag's form is following:
+ multi-part ending tag's form is following:
--}-<<TYPE>>
-A region from multi-part beginning tag to multi-part ending tag is
+ A region from multi-part beginning tag to multi-part ending tag is
called as *enclosure*.
-
-
\1f
-File: tm-edit-en.info, Node: single-part operations, Next: enclosure operation, Prev: mime/editor-mode, Up: Top
+File: tm-edit-en.info, Node: single-part operations, Next: enclosure operation, Prev: mime/editor-mode, Up: Top
single-part operations
**********************
-Operations to make single-part are following:
+ Operations to make single-part are following:
`C-c C-x C-t'
Insert single-part tag indicates text part.
`C-c C-x t'
Insert any single-part tag.
-
-
-
-
\1f
-File: tm-edit-en.info, Node: enclosure operation, Next: other operations of mime/editor-mode, Prev: single-part operations, Up: Top
+File: tm-edit-en.info, Node: enclosure operation, Next: other operations of mime/editor-mode, Prev: single-part operations, Up: Top
enclosure operation
*******************
-Operations to make enclosure are following:
+ Operations to make enclosure are following:
`C-c C-x a'
Enclose specified region as multipart/alternative.
interpreted as such string. (In current version, it may be
incomplete. Maybe PGP-signature does not work for this enclosure.)
-
-
-
-
\1f
-File: tm-edit-en.info, Node: other operations of mime/editor-mode, Next: tag specification for inserted file, Prev: enclosure operation, Up: Top
+File: tm-edit-en.info, Node: other operations of mime/editor-mode, Next: tag specification for inserted file, Prev: enclosure operation, Up: Top
other operations of mime/editor-mode
************************************
-There are another operations in mime/editor-mode.
+ There are another operations in mime/editor-mode.
`C-c C-c'
Send current editing message.
`C-c C-x h'
Set current editing message to encrypt or not. (cf. *Note PGP::)
-
-
-
-
\1f
-File: tm-edit-en.info, Node: tag specification for inserted file, Next: transfer level, Prev: other operations of mime/editor-mode, Up: Top
+File: tm-edit-en.info, Node: tag specification for inserted file, Next: transfer level, Prev: other operations of mime/editor-mode, Up: Top
Default media-type or encoding for inserted file
************************************************
-When `C-c C-x C-i' (`mime-editor/insert-file') is pressed, tag
+ When `C-c C-x C-i' (`mime-editor/insert-file') is pressed, tag
parameters for inserted file, such as media-type or encoding, are
detected by variable `mime-file-types'.
-When `C-u' is followed by it or parameter is not found from the
+ When `C-u' is followed by it or parameter is not found from the
variable, it asks from user. (When `C-u' is followed by it, detected
value is used as default value)
-If you want to change default value for file names, please change
+ If you want to change default value for file names, please change
variable `mime-file-types'.
-
- -- Variable: mime-file-types
-
+ - Variable: mime-file-types
Specification of default value of tag for file name of inserted
file.
(FILE_PAT TYPE SUBTYPE PARAMS ENCODING
DISPOSITION_TYPE DISPOSITION_PARAMS)
-
Each elements of the list are following:
- `FILE_PAT'
+ `FILE_PAT'
regular expression of file name
- `TYPE'
+ `TYPE'
media type
- `SUBTYPE'
+ `SUBTYPE'
media subtype
- `PARAMS'
+ `PARAMS'
parameters of Content-Type field
- `ENCODING'
+ `ENCODING'
Content-Transfer-Encoding
- `DISPOSITION_TYPE'
+ `DISPOSITION_TYPE'
disposition-type
- `DISPOSITION_PARAMS'
+ `DISPOSITION_PARAMS'
parameters of Content-Disposition field
-
Example: Specify application/rtf as default media type for `*.rtf'
(call-after-loaded
"attachment" (("filename" . file)))
)))
-
-
-
\1f
-File: tm-edit-en.info, Node: transfer level, Next: header, Prev: tag specification for inserted file, Up: Top
+File: tm-edit-en.info, Node: transfer level, Next: header, Prev: tag specification for inserted file, Up: Top
transfer level
**************
-Contents inserted in a message are represented by 7bit (*Note
+ Contents inserted in a message are represented by 7bit (*Note
(tm-en)7bit::), 8bit (*Note (tm-en)8bit::) or binary (*Note
(tm-en)binary::).
-If a message is translated by 7bit-through MTA (*Note (tm-en)MTA::),
+ If a message is translated by 7bit-through MTA (*Note (tm-en)MTA::),
there is no need to encode 7bit data, but 8bit and binary data must be
encoded to 7bit data.
-Similarly, if a message is translated by 8bit-through MTA, there is no
-need to encode 7bit or 8bit data, but binary data must be encoded to
+ Similarly, if a message is translated by 8bit-through MTA, there is
+no need to encode 7bit or 8bit data, but binary data must be encoded to
7bit or 8bit data.
*[Memo]*
Maybe there are binary-through MTA, but I think it is not major.
-*transfer level* represents how range data is
-available. tm-edit has a variable `mime-editor/transfer-level' to
-represent transfer level.
-
-
- -- Variable: mime-editor/transfer-level
+ *transfer level* represents how range data is available. tm-edit
+has a variable `mime-editor/transfer-level' to represent transfer level.
+ - Variable: mime-editor/transfer-level
transfer level.
If transfer level of a data is over it, a data is encoded to 7bit.
In extension plan, EBCDIC will be 5, ASCII printable only will be
6, binary will be 9. But it will not be implemented.
-
-
*[Memo]*
transfer level is only for body, not for header (*Note header::).
RFC 1521 extends RFC 822 (*Note (tm-en)RFC 822::) to use 8bit data
in body, but it requires to use us-ascii (*Note (tm-en)us-ascii::)
in header.
-
-
-
\1f
-File: tm-edit-en.info, Node: header, Next: PGP, Prev: transfer level, Up: Top
+File: tm-edit-en.info, Node: header, Next: PGP, Prev: transfer level, Up: Top
Using non-ASCII characters in header
************************************
-RFC 1522 (*Note (tm-en)RFC 1522::) defines representation of non-ASCII
-characters in header.
-
-It is a format called as *encoded-word* (*Note (tm-en)encoded-word::),
-it is available to represent every non-ASCII characters by 7bit (*Note
-(tm-en)7bit::) to declare MIME charset (*Note (tm-en)MIME charset::).
+ RFC 1522 (*Note (tm-en)RFC 1522::) defines representation of
+non-ASCII characters in header.
+ It is a format called as *encoded-word* (*Note
+(tm-en)encoded-word::), it is available to represent every non-ASCII
+characters by 7bit (*Note (tm-en)7bit::) to declare MIME charset (*Note
+(tm-en)MIME charset::).
* Menu:
* evil setting in header:: If you can not allow encoded-word
* API about header:: Functions and variables about header
-
\1f
-File: tm-edit-en.info, Node: evil setting in header, Next: API about header, Prev: header, Up: header
+File: tm-edit-en.info, Node: evil setting in header, Next: API about header, Prev: header, Up: header
If you can not allow encoded-word
=================================
-It is wrong to use "raw" non-ASCII characters in header not to use
+ It is wrong to use "raw" non-ASCII characters in header not to use
encoded-word. Because there are various kinds of coded character set
(*Note (tm-en)Coded character set::) in the Internet, so we can not
distinguish them if MIME charset (*Note (tm-en)MIME charset::) is not
declared.
-For example, we can not distinguish iso-8859-1 (*Note
+ For example, we can not distinguish iso-8859-1 (*Note
(tm-en)iso-8859-1::) and iso-8859-2 (*Note (tm-en)iso-8859-2::) if MIME
charset is not declared.
-However you can not permit to use encoded-word, please set to following
-variables:
-
-
- -- Variable: mime/field-encoding-method-alist
+ However you can not permit to use encoded-word, please set to
+following variables:
+ - Variable: mime/field-encoding-method-alist
Association-list to specify field encoding method. Its key is
field-name, value is encoding method.
field-name allows string or `t' meaning any fields.
- Encoding method allows following: `nil' means no-conversion, `mime'
- means to convert as encoded-word, symbol represent MIME charset
- means to convert as the coded character set instead of to convert
- as encoded-word.
+ Encoding method allows following: `nil' means no-conversion,
+ `mime' means to convert as encoded-word, symbol represent MIME
+ charset means to convert as the coded character set instead of to
+ convert as encoded-word.
field-name is searched from string. If it is not found, `t' is
used.
(t . mime)
))
-
-In addition, if you want to specify by coded character set instead of
+ In addition, if you want to specify by coded character set instead of
field, please use `mime-eword/charset-encoding-alist'. (cf. *Note API
about header::)
-
-
-
\1f
-File: tm-edit-en.info, Node: API about header, Prev: evil setting in header, Up: header
+File: tm-edit-en.info, Node: API about header, Prev: evil setting in header, Up: header
Functions and variables about header
====================================
- -- Command: mime/encode-message-header &optional CODE-CONVERSION
-
+ - Command: mime/encode-message-header &optional CODE-CONVERSION
It translate non-ASCII characters in message header of current
buffer into network representation, such as encoded-words.
If CODE-CONVERSION is non-`nil', field not encoded by encoded-word
is converted by `mime/field-encoding-method-alist'.
-
- -- Function: mime/encode-field STRING
-
+ - Function: mime/encode-field STRING
It encodes STRING into encoded-words as a field.
Long lines are folded.
-
- -- Function: mime-eword/encode-string STRING &optional COLUMN MODE
-
+ - Function: mime-eword/encode-string STRING &optional COLUMN MODE
It encodes STRING into encoded-words.
Long lines are folded.
MODE specifies where STRING is in. Available values are `text',
`comment', `phrase'. If it is omitted, `phrase' is used.
-
- -- Variable: mime-eword/charset-encoding-alist
-
+ - Variable: mime-eword/charset-encoding-alist
Association-list of symbol represent MIME charset vs. nil, `"B"' or
`"Q"'.
`nil' means not to encode as encoded-word. `"B"' means to use
B-encoding. `"Q"' means to use Q-encoding.
-
-
-
\1f
-File: tm-edit-en.info, Node: PGP, Next: Concept Index, Prev: header, Up: Top
+File: tm-edit-en.info, Node: PGP, Next: Acknowledgments, Prev: header, Up: Top
PGP
***
-tm-edit provides PGP encryption, signature and inserting public-key
+ tm-edit provides PGP encryption, signature and inserting public-key
features based on *PGP/MIME* (*Note (tm-en)PGP/MIME::) (RFC 2015) or
*PGP-kazu* (*Note (tm-en)PGP-kazu::) (draft-kazu-pgp-mime-00.txt).
-This feature requires pgp command and Mailcrypt package (*Note
+ This feature requires pgp command and Mailcrypt package (*Note
(mailcrypt)::).
-If you want to use this feature, please set `pgp-elkins' or `pgp-kazu'
-to variable `mimed-editor/signing-type' and variable
+ If you want to use this feature, please set `pgp-elkins' or
+`pgp-kazu' to variable `mimed-editor/signing-type' and variable
`mime-editor/encrypting-type'.
-If `pgp-elkins' is specified, PGP/MIME is used. If `pgp-kazu' is
+ If `pgp-elkins' is specified, PGP/MIME is used. If `pgp-kazu' is
specified, PGP-kazu is used.
-
- -- Variable: mime-editor/signing-type
-
+ - Variable: mime-editor/signing-type
Format of PGP signature.
It allows `pgp-elkins' or `pgp-kazu'.
Default value is `nil'.
-
- -- Variable: mime-editor/encrypting-type
-
+ - Variable: mime-editor/encrypting-type
Format of PGP encryption.
It allows `pgp-elkins' or `pgp-kazu'.
Default value is `nil'.
+\1f
+File: tm-edit-en.info, Node: Acknowledgments, Next: Concept Index, Prev: PGP, Up: Top
+
+Acknowledgments
+***************
+ First of all, I thank UMEDA Masanobu for his work of `mime.el',
+which is the origin of tm-edit, and permission to rewrite his work as
+tm-edit.
+ I thank members of two tm mailing lists, Japanese and English
+version.
\1f
-File: tm-edit-en.info, Node: Concept Index, Next: Function Index, Prev: PGP, Up: Top
+File: tm-edit-en.info, Node: Concept Index, Next: Function Index, Prev: Acknowledgments, Up: Top
Concept Index
*************
-
* Menu:
-* enclosure: mime/editor-mode. 42.
-* encoded-word: header. 9.
-* mime/editor-mode: mime/editor-mode. 5.
-* multi-part beginning tag: mime/editor-mode. 30.
-* multi-part ending tag: mime/editor-mode. 31.
-* PGP-kazu: PGP. 8.
-* PGP/MIME: PGP. 7.
-* tag: mime/editor-mode. 7.
-* tm-edit: Introduction. 5.
-* transfer level: transfer level. 26.
-
+* enclosure: mime/editor-mode.
+* encoded-word: header.
+* mime/editor-mode: mime/editor-mode.
+* multi-part beginning tag: mime/editor-mode.
+* multi-part ending tag: mime/editor-mode.
+* PGP-kazu: PGP.
+* PGP/MIME: PGP.
+* tag: mime/editor-mode.
+* tm-edit: Introduction.
+* transfer level: transfer level.
\1f
-File: tm-edit-en.info, Node: Function Index, Next: Variable Index, Prev: Concept Index, Up: Top
+File: tm-edit-en.info, Node: Function Index, Next: Variable Index, Prev: Concept Index, Up: Top
Function Index
**************
-
* Menu:
-* mime/encode-field: API about header. 16.
-* mime/encode-message-header: API about header. 7.
-* mime-eword/encode-string: API about header. 23.
-
+* mime-eword/encode-string: API about header.
+* mime/encode-field: API about header.
+* mime/encode-message-header: API about header.
\1f
-File: tm-edit-en.info, Node: Variable Index, Prev: Function Index, Up: Top
+File: tm-edit-en.info, Node: Variable Index, Prev: Function Index, Up: Top
Variable Index
**************
-
* Menu:
-* mime-editor/encrypting-type: PGP. 31.
-* mime-editor/signing-type: PGP. 22.
-* mime-editor/transfer-level: transfer level. 33.
-* mime-eword/charset-encoding-alist: API about header. 35.
-* mime/field-encoding-method-alist: evil setting in header. 21.
-* mime-file-types: tag specification for inserted file. 19.
+* mime-editor/encrypting-type: PGP.
+* mime-editor/signing-type: PGP.
+* mime-editor/transfer-level: transfer level.
+* mime-eword/charset-encoding-alist: API about header.
+* mime-file-types: tag specification for inserted file.
+* mime/field-encoding-method-alist: evil setting in header.
+
+
+\1f
+Tag Table:
+Node: Top\7f99
+Node: Introduction\7f780
+Node: mime/editor-mode\7f1599
+Node: single-part operations\7f2919
+Node: enclosure operation\7f3937
+Node: other operations of mime/editor-mode\7f4785
+Node: tag specification for inserted file\7f5857
+Node: transfer level\7f7534
+Node: header\7f9167
+Node: evil setting in header\7f9785
+Node: API about header\7f11382
+Node: PGP\7f12593
+Node: Acknowledgments\7f13527
+Node: Concept Index\7f13875
+Node: Function Index\7f14556
+Node: Variable Index\7f14874
+\1f
+End Tag Table
<!doctype sinfo system>
-<!-- $Id: tm-edit-en.sgml,v 2.0 1996/12/24 16:00:05 morioka Exp $ -->
+<!-- $Id: tm-edit-en.sgml,v 3.1 1996/12/25 19:02:42 morioka Exp $ -->
<head>
-<title>tm-edit 7.99 Reference Manual (English Version)
+<title>tm-edit 7.100 Reference Manual (English Version)
<author>MORIOKA Tomohiko <mail>morioka@jaist.ac.jp</mail>
<date>1996/12/25
</defvar>
+<h1> Acknowledgments
+<node> Acknowledgments
+<p>
+First of all, I thank UMEDA Masanobu for his work of
+<file>mime.el</file>, which is the origin of tm-edit, and permission
+to rewrite his work as tm-edit.
+<p>
+I thank members of two tm mailing lists, Japanese and English version.
+
+
<h1> Concept Index
<node> Concept Index
\input texinfo.tex
@setfilename tm-edit-en.info
-@settitle{tm-edit 7.99 Reference Manual (English Version)}
+@settitle{tm-edit 7.100 Reference Manual (English Version)}
@titlepage
-@title tm-edit 7.99 Reference Manual (English Version)
+@title tm-edit 7.100 Reference Manual (English Version)
@author MORIOKA Tomohiko <morioka@@jaist.ac.jp>
@subtitle 1996/12/25
@end titlepage
@node Top, Introduction, (dir), (dir)
-@top tm-edit 7.99 Reference Manual (English Version)
+@top tm-edit 7.100 Reference Manual (English Version)
@ifinfo
* transfer level::
* header:: Using non-ASCII characters in header
* PGP::
+* Acknowledgments::
* Concept Index::
* Function Index::
* Variable Index::
@node Introduction, mime/editor-mode, Top, Top
@chapter What is tm-edit?
+@cindex tm-edit
-@cindex{tm-edit}@strong{tm-edit} is a general MIME composer for GNU
-Emacs.@refill
+@strong{tm-edit} is a general MIME composer for GNU Emacs.@refill
tm-edit is based on mime.el by UMEDA Masanobu
<umerin@@mse.kyutech.ac.jp>, who is famous as the author of
@node mime/editor-mode, single-part operations, Introduction, Top
@chapter mime/editor-mode
+@cindex enclosure
+@cindex multi-part ending tag
+@cindex multi-part beginning tag
+@cindex tag
+@cindex mime/editor-mode
-@cindex{mime/editor-mode}@strong{mime/editor-mode} is a minor mode to
-compose MIME message. In this mode, @cindex{tag}@strong{tag} represents
-various kinds of data, you can edit multi part (@ref{(tm-en)multipart})
-message.@refill
+@strong{mime/editor-mode} is a minor mode to compose MIME message. In
+this mode, @strong{tag} represents various kinds of data, you can edit
+multi part (@ref{(tm-en)multipart}) message.@refill
There are 2 kinds of tags:
and Content-Transfer-Encoding field.@refill
multi-part tags represent multi part (@ref{(tm-en)multipart}). They
-consist of a pair of @cindex{multi-part beginning tag}@strong{multi-part
-beginning tag} and @cindex{multi-part ending tag}@strong{multi-part
-ending tag}.@refill
+consist of a pair of @strong{multi-part beginning tag} and
+@strong{multi-part ending tag}.@refill
multi-part beginning tag's form is following:@refill
@end example
A region from multi-part beginning tag to multi-part ending tag is
-called as @cindex{enclosure}@strong{enclosure}.
+called as @strong{enclosure}.
@node single-part operations, enclosure operation, mime/editor-mode, Top
@node transfer level, header, tag specification for inserted file, Top
@chapter transfer level
+@cindex transfer level
Contents inserted in a message are represented by 7bit
(@ref{(tm-en)7bit}), 8bit (@ref{(tm-en)8bit}) or binary
Maybe there are binary-through MTA, but I think it is not major.
@end quotation
-@cindex{transfer level}@strong{transfer level} represents how range data is
+@strong{transfer level} represents how range data is
available. tm-edit has a variable
@code{mime-editor/transfer-level} to represent transfer level.
@node header, PGP, transfer level, Top
@chapter Using non-ASCII characters in header
+@cindex encoded-word
RFC 1522 (@ref{(tm-en)RFC 1522}) defines representation of non-ASCII
characters in header.@refill
-It is a format called as @cindex{encoded-word}@strong{encoded-word}
+It is a format called as @strong{encoded-word}
(@ref{(tm-en)encoded-word}), it is available to represent every
non-ASCII characters by 7bit (@ref{(tm-en)7bit}) to declare MIME charset
(@ref{(tm-en)MIME charset}).
-@node PGP, Concept Index, header, Top
+@node PGP, Acknowledgments, header, Top
@chapter PGP
+@cindex PGP-kazu
+@cindex PGP/MIME
tm-edit provides PGP encryption, signature and inserting public-key
-features based on @cindex{PGP/MIME}@strong{PGP/MIME}
-(@ref{(tm-en)PGP/MIME}) (RFC 2015) or @cindex{PGP-kazu}@strong{PGP-kazu}
-(@ref{(tm-en)PGP-kazu}) (draft-kazu-pgp-mime-00.txt).@refill
+features based on @strong{PGP/MIME} (@ref{(tm-en)PGP/MIME}) (RFC 2015)
+or @strong{PGP-kazu} (@ref{(tm-en)PGP-kazu})
+(draft-kazu-pgp-mime-00.txt).@refill
This feature requires pgp command and Mailcrypt package
(@ref{(mailcrypt)}).@refill
-@node Concept Index, Function Index, PGP, Top
+@node Acknowledgments, Concept Index, PGP, Top
+@chapter Acknowledgments
+
+First of all, 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 members of two tm mailing lists, Japanese and English version.
+
+
+@node Concept Index, Function Index, Acknowledgments, Top
@chapter Concept Index
@printindex cp
\1f
File: tm-edit-ja.info, Node: Top, Next: Introduction, Prev: (dir), Up: (dir)
-tm-edit 7.99 \e$B@bL@=q!JF|K\8lHG!K\e(B
-*******************************
+tm-edit 7.100 \e$B@bL@=q!JF|K\8lHG!K\e(B
+********************************
This file documents tm-edit, a MIME composer for GNU Emacs.
* transfer level::
* header:: header \e$B$G$NHs\e(B ASCII \e$BJ8;z$N;HMQ\e(B
* PGP::
+* Acknowledgments:: \e$B<U<-\e(B
* Concept Index:: \e$B35G0:w0z\e(B
* Function Index:: \e$B4X?t:w0z\e(B
* Variable Index:: \e$BJQ?t:w0z\e(B
What is tm-edit?
****************
-*tm-edit* \e$B$O\e(B GNU Emacs \e$B$GF0:n$9$kHFMQE*$J\e(B MIME
-composer \e$B$G$9!#\e(B
+*tm-edit* \e$B$O\e(B GNU Emacs \e$B$GF0:n$9$kHFMQE*$J\e(B MIME composer \e$B$G$9!#\e(B
+
tm-edit \e$B$O\e(B GNUS \e$B$N:n<T$H$7$F$bM-L>$J\e(B \e$BG_ED\e(B \e$B@/?.\e(B<umerin@mse.kyutech.ac.jp>
\e$B$5$s$,=q$+$l$?\e(B `mime.el' \e$B$r4p$K\e(B
mime/editor-mode
****************
-*mime/editor-mode* \e$B$O\e(B MIME message \e$B$r:n\e(B
-\e$B@.$9$k$?$a$N\e(B minor mode \e$B$G$9!#$3$N\e(B mode \e$B$G$O\e(B *tag* \e$B$r;H$C$F$5$^$6$^$J<o\e(B
-\e$BN`$N\e(B data \e$B$rI=8=$7!"J#?t$NItJ,$+$i$J$k\e(B message (*Note
-(tm-ja)multipart::) \e$B$rJT=8$9$k$3$H$r2DG=$K$7$F$$$^$9!#\e(B
+*mime/editor-mode* \e$B$O\e(B MIME message \e$B$r:n@.$9$k$?$a$N\e(B minor mode \e$B$G\e(B
+\e$B$9!#$3$N\e(B mode \e$B$G$O\e(B *tag* \e$B$r;H$C$F$5$^$6$^$J<oN`$N\e(B data \e$B$rI=8=$7!"J#?t$N\e(B
+\e$BItJ,$+$i$J$k\e(B message (*Note (tm-ja)multipart::) \e$B$rJT=8$9$k$3$H$r2DG=$K$7\e(B
+\e$B$F$$$^$9!#\e(B
tag \e$B$K$O\e(B
\1f
-File: tm-edit-ja.info, Node: PGP, Next: Concept Index, Prev: header, Up: Top
+File: tm-edit-ja.info, Node: PGP, Next: Acknowledgments, Prev: header, Up: Top
PGP
***
tm-edit \e$B$G$O\e(B *PGP/MIME* (*Note (tm-ja)PGP/MIME::) (RFC 2015) \e$B$*$h$S\e(B
-*PGP-kazu* (*Note (tm-ja)PGP-kazu::) (draft-kazu-pgp-mime-00.txt) \e$B$K$h$k\e(B
-\e$B0E9f2=!&EE;R=pL>!&8x3+80$NA^F~5!G=$rMxMQ$9$k$3$H$,$G$-$^$9!#\e(B
+*PGP-kazu* (*Note (tm-ja)PGP-kazu::) (draft-kazu-pgp-mime-00.txt)
+\e$B$K$h$k0E9f2=!&EE;R=pL>!&8x3+80$NA^F~5!G=$rMxMQ$9$k$3$H$,$G$-$^$9!#\e(B
\e$BC"$7!"$3$N5!G=$rMxMQ$9$k$K$O\e(B Mailcrypt package (*Note (mailcrypt)::) \e$B$H\e(B
pgp command \e$B$,I,MW$G$9!#\e(B
\1f
-File: tm-edit-ja.info, Node: Concept Index, Next: Function Index, Prev: PGP, Up: Top
+File: tm-edit-ja.info, Node: Acknowledgments, Next: Concept Index, Prev: PGP, Up: Top
+
+\e$B<U<-\e(B
+****
+
+\e$B:G=i$K!"\e(Btm-edit \e$B$NA0?H$H$J$C$?\e(B `mime.el' \e$B$r=q$-!"$=$NG[I[$H2~B$$r$*5v$7\e(B
+\e$B2<$5$C$?!"G_ED@/?.$5$s$K46<U$7$^$9!#\e(Btm-edit \e$B$N\e(B user interface \e$B$N4pK\E*$J\e(B
+\e$B@_7W$OG_ED$5$s$N<j$K$h$k$b$N$G!"$H$F$bNI$$@_7W$G$"$C$?$H;W$$$^$9!#\e(B
+
+
+\e$B<!$K!"\e(Bbeta test \e$B$K6(NO$7$F2<$5$C$?F|K\8lHG!"1Q8lHGAPJ}$N\e(B tm mailing list
+\e$B$N\e(B member \e$B$K46<U$7$^$9!#\e(B
+
+
+
+\1f
+File: tm-edit-ja.info, Node: Concept Index, Next: Function Index, Prev: Acknowledgments, Up: Top
\e$B35G0:w0z\e(B
********
* Menu:
-* enclosure: mime/editor-mode. 48.
-* encoded-word: header. 9.
-* mime/editor-mode: mime/editor-mode. 5.
-* multi-part \e$B3+;O\e(B tag: mime/editor-mode. 41.
-* multi-part \e$B=*N;\e(B tag: mime/editor-mode. 46.
-* PGP-kazu: PGP. 7.
-* PGP/MIME: PGP. 6.
-* tag: mime/editor-mode. 7.
-* tm-edit: Introduction. 5.
-* transfer level: transfer level. 27.
+* enclosure: mime/editor-mode. 4.
+* encoded-word: header. 4.
+* mime/editor-mode: mime/editor-mode. 4.
+* multi-part \e$B3+;O\e(B tag: mime/editor-mode. 4.
+* multi-part \e$B=*N;\e(B tag: mime/editor-mode. 4.
+* PGP-kazu: PGP. 4.
+* PGP/MIME: PGP. 4.
+* tag: mime/editor-mode. 4.
+* tm-edit: Introduction. 4.
+* transfer level: transfer level. 4.
\1f
<!doctype sinfo system>
-<!-- $Id: tm-edit-ja.sgml,v 6.0 1996/12/24 15:08:17 morioka Exp $ -->
+<!-- $Id: tm-edit-ja.sgml,v 6.3 1996/12/25 19:00:41 morioka Exp $ -->
<head>
-<title>tm-edit 7.99 \e$B@bL@=q!JF|K\8lHG!K\e(B
+<title>tm-edit 7.100 \e$B@bL@=q!JF|K\8lHG!K\e(B
<author>\e$B<i2,\e(B \e$BCNI'\e(B <mail>morioka@jaist.ac.jp</mail>
<date>1996/12/25
</defvar>
+<h1> \e$B<U<-\e(B
+<node> Acknowledgments
+<p>
+\e$B:G=i$K!"\e(Btm-edit \e$B$NA0?H$H$J$C$?\e(B <file>mime.el</file> \e$B$r=q$-!"$=$NG[I[$H\e(B
+\e$B2~B$$r$*5v$72<$5$C$?!"G_ED@/?.$5$s$K46<U$7$^$9!#\e(Btm-edit \e$B$N\e(B user
+interface \e$B$N4pK\E*$J@_7W$OG_ED$5$s$N<j$K$h$k$b$N$G!"$H$F$bNI$$@_7W$G$"$C\e(B
+\e$B$?$H;W$$$^$9!#\e(B
+<p>
+\e$B<!$K!"\e(Bbeta test \e$B$K6(NO$7$F2<$5$C$?F|K\8lHG!"1Q8lHGAPJ}$N\e(B tm mailing
+list \e$B$N\e(B member \e$B$K46<U$7$^$9!#\e(B
+
+
<h1> \e$B35G0:w0z\e(B
<node> Concept Index
\input texinfo.tex
@setfilename tm-edit-ja.info
-@settitle{tm-edit 7.99 \e$B@bL@=q!JF|K\8lHG!K\e(B}
+@settitle{tm-edit 7.100 \e$B@bL@=q!JF|K\8lHG!K\e(B}
@titlepage
-@title tm-edit 7.99 \e$B@bL@=q!JF|K\8lHG!K\e(B
+@title tm-edit 7.100 \e$B@bL@=q!JF|K\8lHG!K\e(B
@author \e$B<i2,\e(B \e$BCNI'\e(B <morioka@@jaist.ac.jp>
@subtitle 1996/12/25
@end titlepage
@node Top, Introduction, (dir), (dir)
-@top tm-edit 7.99 \e$B@bL@=q!JF|K\8lHG!K\e(B
+@top tm-edit 7.100 \e$B@bL@=q!JF|K\8lHG!K\e(B
@ifinfo
* transfer level::
* header:: header \e$B$G$NHs\e(B ASCII \e$BJ8;z$N;HMQ\e(B
* PGP::
+* Acknowledgments:: \e$B<U<-\e(B
* Concept Index:: \e$B35G0:w0z\e(B
* Function Index:: \e$B4X?t:w0z\e(B
* Variable Index:: \e$BJQ?t:w0z\e(B
@node Introduction, mime/editor-mode, Top, Top
@chapter What is tm-edit?
+@cindex tm-edit
-@cindex{tm-edit}@strong{tm-edit} \e$B$O\e(B GNU Emacs \e$B$GF0:n$9$kHFMQE*$J\e(B MIME
-composer \e$B$G$9!#\e(B@refill
+@strong{tm-edit} \e$B$O\e(B GNU Emacs \e$B$GF0:n$9$kHFMQE*$J\e(B MIME composer \e$B$G$9!#\e(B
+@refill
tm-edit \e$B$O\e(B GNUS \e$B$N:n<T$H$7$F$bM-L>$J\e(B \e$BG_ED\e(B \e$B@/?.\e(B
<umerin@@mse.kyutech.ac.jp> \e$B$5$s$,=q$+$l$?\e(B
@node mime/editor-mode, single-part operations, Introduction, Top
@chapter mime/editor-mode
+@cindex enclosure
+@cindex multi-part \e$B=*N;\e(B tag
+@cindex multi-part \e$B3+;O\e(B tag
+@cindex tag
+@cindex mime/editor-mode
-@cindex{mime/editor-mode}@strong{mime/editor-mode} \e$B$O\e(B MIME message \e$B$r:n\e(B
-\e$B@.$9$k$?$a$N\e(B minor mode \e$B$G$9!#$3$N\e(B mode \e$B$G$O\e(B @cindex{tag}@strong{tag} \e$B$r\e(B
-\e$B;H$C$F$5$^$6$^$J<oN`$N\e(B data \e$B$rI=8=$7!"J#?t$NItJ,$+$i$J$k\e(B message
-(@ref{(tm-ja)multipart}) \e$B$rJT=8$9$k$3$H$r2DG=$K$7$F$$$^$9!#\e(B@refill
+@strong{mime/editor-mode} \e$B$O\e(B MIME message \e$B$r:n@.$9$k$?$a$N\e(B minor mode \e$B$G\e(B
+\e$B$9!#$3$N\e(B mode \e$B$G$O\e(B @strong{tag} \e$B$r;H$C$F$5$^$6$^$J<oN`$N\e(B data \e$B$rI=8=$7!"\e(B
+\e$BJ#?t$NItJ,$+$i$J$k\e(B message (@ref{(tm-ja)multipart}) \e$B$rJT=8$9$k$3$H$r2DG=\e(B
+\e$B$K$7$F$$$^$9!#\e(B@refill
tag \e$B$K$O\e(B
@end example
@noindent
-\e$B$H$$$&7A$N\e(B @cindex{multi-part \e$B3+;O\e(B tag}@strong{multi-part \e$B3+;O\e(B tag} \e$B$H8F$P$l$k\e(B multi
+\e$B$H$$$&7A$N\e(B @strong{multi-part \e$B3+;O\e(B tag} \e$B$H8F$P$l$k\e(B multi
part \e$B$N3+;O$r<($9\e(B tag \e$B$H\e(B
@example
@end example
@noindent
-\e$B$H$$$&7A$N\e(B @cindex{multi-part \e$B=*N;\e(B tag}@strong{multi-part \e$B=*N;\e(B tag} \e$B$H8F$P$l$k\e(B multi
+\e$B$H$$$&7A$N\e(B @strong{multi-part \e$B=*N;\e(B tag} \e$B$H8F$P$l$k\e(B multi
part \e$B$N=*N;$r<($9\e(B tag \e$B$,$"$j$^$9!#\e(B
\e$B$^$?!"\e(Bmulti-part \e$B3+;O\e(B tag \e$B$H\e(B multi-part \e$B=*N;\e(B tag \e$B$G0O$^$l$?ItJ,$r\e(B
-@cindex{enclosure}@strong{enclosure} \e$B$H8F$S$^$9!#\e(B
+@strong{enclosure} \e$B$H8F$S$^$9!#\e(B
@node single-part operations, enclosure operation, mime/editor-mode, Top
@item @key{C-c C-x C-i}
file \e$B$r\e(B MIME part \e$B$H$7$FE:IU$7$^$9!#A0$K\e(B @kbd{C-u} \e$B$rIU$1$?>l9g!">o$K\e(B
-media-type, subtype \e$BEy$rJ9$$$FMh$^$9!#\e(B(cf. @ref{tag specification for
-inserted file})
+media-type, subtype \e$BEy$rJ9$$$FMh$^$9!#\e(B(cf. @ref{tag specification for inserted file})
@item @key{C-c C-x C-e}
external part \e$B$rA^F~$7$^$9!#\e(B
@node transfer level, header, tag specification for inserted file, Top
@chapter transfer level
+@cindex transfer level
message \e$B$KA^F~$9$k\e(B data \e$B$O\e(B 7bit (@ref{(tm-ja)7bit}) \e$B$J$$$7\e(B 8bit
(@ref{(tm-ja)8bit}) \e$B$b$7$/$O\e(B binary (@ref{(tm-ja)binary}) \e$B$GI=8=$9$k$3$H\e(B
\e$B$J$$$G$7$g$&!#\e(B
@end quotation
-@cindex{transfer level}@strong{transfer level} \e$B$H$$$&$N$O$I$NHO0O$N\e(B data \e$B$^$GAw$l$k\e(B
+@strong{transfer level} \e$B$H$$$&$N$O$I$NHO0O$N\e(B data \e$B$^$GAw$l$k\e(B
\e$B$+$H$$$&$3$H$rI=$9$b$N$G$9!#\e(Btm-edit \e$B$O\e(B
@code{mime-editor/transfer-level} \e$B$H$$$&JQ?t$r;}$C$F$*$j!"$3$l$G\e(B
transfer level \e$B$rI=8=$7$^$9!#\e(B
@strong{[Memo]}
@quotation
transfer level \e$B$O\e(B message header (@ref{header}) \e$B$K$O4X78$7$J$$!#\e(BRFC 1521
-\e$B$O\e(B body \e$B$K$*$$$F!"\e(B8bit \e$B$N\e(B data \e$B$r;H$($k$h$&$K\e(B RFC 822 (@ref{(tm-ja)RFC
-822}) \e$B$r3HD%$7$F$$$k$,!"\e(Bmessage header \e$B$G$O\e(B us-ascii
+\e$B$O\e(B body \e$B$K$*$$$F!"\e(B8bit \e$B$N\e(B data \e$B$r;H$($k$h$&$K\e(B RFC 822 (@ref{(tm-ja)RFC 822}) \e$B$r3HD%$7$F$$$k$,!"\e(Bmessage header \e$B$G$O\e(B us-ascii
(@ref{(tm-ja)us-ascii}) \e$B$N$_$rMQ$$$k$3$H$r5a$a$F$$$k!#\e(B
@end quotation
@node header, PGP, transfer level, Top
@chapter header \e$B$G$NHs\e(B ASCII \e$BJ8;z$N;HMQ\e(B
+@cindex encoded-word
RFC 1522 (@ref{(tm-ja)RFC 1522}) \e$B$G$O\e(B header \e$B$GHs\e(B ASCII \e$BJ8;z$rI=8=$9$k$?\e(B
\e$B$a$NJ}K!$rDj5A$7$F$$$^$9!#\e(B@refill
-\e$B$3$l$O\e(B @cindex{encoded-word}@strong{encoded-word}
-(@ref{(tm-ja)encoded-word}) \e$B$H8F$P$l$k7?<0$G!"\e(BMIME charset
-(@ref{(tm-ja)MIME charset}) \e$B$r@k8@$7!"$+$D!"\e(B7bit (@ref{(tm-ja)7bit}) \e$B$G\e(B
-\e$BI=8=$9$k$3$H$r2DG=$K$7$F$$$^$9!#\e(B
+\e$B$3$l$O\e(B @strong{encoded-word} (@ref{(tm-ja)encoded-word}) \e$B$H8F$P$l$k7?<0\e(B
+\e$B$G!"\e(BMIME charset (@ref{(tm-ja)MIME charset}) \e$B$r@k8@$7!"$+$D!"\e(B7bit
+(@ref{(tm-ja)7bit}) \e$B$GI=8=$9$k$3$H$r2DG=$K$7$F$$$^$9!#\e(B
@menu
-@node PGP, Concept Index, header, Top
+@node PGP, Acknowledgments, header, Top
@chapter PGP
+@cindex PGP-kazu
+@cindex PGP/MIME
-tm-edit \e$B$G$O\e(B @cindex{PGP/MIME}@strong{PGP/MIME} (@ref{(tm-ja)PGP/MIME})
-(RFC 2015) \e$B$*$h$S\e(B @cindex{PGP-kazu}@strong{PGP-kazu}
-(@ref{(tm-ja)PGP-kazu}) (draft-kazu-pgp-mime-00.txt) \e$B$K$h$k0E9f2=!&EE;R\e(B
-\e$B=pL>!&8x3+80$NA^F~5!G=$rMxMQ$9$k$3$H$,$G$-$^$9!#\e(B@refill
+tm-edit \e$B$G$O\e(B @strong{PGP/MIME} (@ref{(tm-ja)PGP/MIME}) (RFC 2015) \e$B$*$h$S\e(B
+@strong{PGP-kazu} (@ref{(tm-ja)PGP-kazu}) (draft-kazu-pgp-mime-00.txt)
+\e$B$K$h$k0E9f2=!&EE;R=pL>!&8x3+80$NA^F~5!G=$rMxMQ$9$k$3$H$,$G$-$^$9!#\e(B
\e$BC"$7!"$3$N5!G=$rMxMQ$9$k$K$O\e(B Mailcrypt package (@ref{(mailcrypt)}) \e$B$H\e(B
pgp command \e$B$,I,MW$G$9!#\e(B@refill
-@node Concept Index, Function Index, PGP, Top
+@node Acknowledgments, Concept Index, PGP, Top
+@chapter \e$B<U<-\e(B
+
+\e$B:G=i$K!"\e(Btm-edit \e$B$NA0?H$H$J$C$?\e(B @file{mime.el} \e$B$r=q$-!"$=$NG[I[$H2~B$$r$*\e(B
+\e$B5v$72<$5$C$?!"G_ED@/?.$5$s$K46<U$7$^$9!#\e(Btm-edit \e$B$N\e(B user interface \e$B$N4pK\\e(B
+\e$BE*$J@_7W$OG_ED$5$s$N<j$K$h$k$b$N$G!"$H$F$bNI$$@_7W$G$"$C$?$H;W$$$^$9!#\e(B
+@refill
+
+\e$B<!$K!"\e(Bbeta test \e$B$K6(NO$7$F2<$5$C$?F|K\8lHG!"1Q8lHGAPJ}$N\e(B tm mailing
+list \e$B$N\e(B member \e$B$K46<U$7$^$9!#\e(B
+
+
+@node Concept Index, Function Index, Acknowledgments, Top
@chapter \e$B35G0:w0z\e(B
@printindex cp
-Info file: tm-en.info, -*-Text-*-
-produced by `texinfo-format-buffer'
-from file `tm-en.texi'
-using `texinfmt.el' version 2.32 of 19 November 1993.
-
+This is Info file tm-en.info, produced by Makeinfo-1.63 from the input
+file tm-en.texi.
\1f
-File: tm-en.info, Node: Top, Next: Introduction, Prev: (dir), Up: (dir)
-
-tm 7.98 Manual (English Version)
-********************************
+File: tm-en.info, Node: Top, Next: Introduction, Prev: (dir), Up: (dir)
+tm 7.100 Manual (English Version)
+*********************************
-This file documents tm, a MIME package for GNU Emacs.
+ This file documents tm, a MIME package for GNU Emacs.
* Menu:
* Introduction:: What is tm?
-* Setting::
+* Setting::
* Bug report:: How to report bug and about mailing list of tm
-* Concept Index::
-* Variable Index::
-
+* Acknowledgments::
+* Concept Index::
+* Variable Index::
\1f
-File: tm-en.info, Node: Introduction, Next: Setting, Prev: Top, Up: Top
+File: tm-en.info, Node: Introduction, Next: Setting, Prev: Top, Up: Top
What is tm?
***********
-The tm package is a set of modules to enjoy MIME on GNU Emacs. Using
+ The tm package is a set of modules to enjoy MIME on GNU Emacs. Using
tm, you can
* playback or view the MIME messages using tm-view
+
* compose MIME message using tm-edit
+
* use the enhanced MIME features with mh-e, GNUS, Gnus, RMAIL and VM
and more.
-Please read following about each topics:
+ Please read following about each topics:
* tm-MUA for Gnus (*Note (gnus-mime-en)::)
+
* tm-MUA for GNUS (*Note (tm-gnus-en)::)
+
* tm-MUA for mh-e (*Note (tm-mh-e-en)::)
- * mime/viewer-mode (*Note (tm-view-en)::)
- * mime/editor-mode (*Note (tm-edit-en)::)
+ * mime/viewer-mode (*Note (tm-view-en)::)
+ * mime/editor-mode (*Note (tm-edit-en)::)
* Menu:
-* Glossary::
-
+* Glossary::
\1f
-File: tm-en.info, Node: Glossary, Prev: Introduction, Up: Introduction
+File: tm-en.info, Node: Glossary, Prev: Introduction, Up: Introduction
Glossary
========
-
* Menu:
-* 7bit::
-* 8bit::
-* 94-character set::
-* 96-character set::
-* 94x94-character set::
-* ASCII::
-* Base64::
-* binary::
+* 7bit::
+* 8bit::
+* 94-character set::
+* 96-character set::
+* 94x94-character set::
+* ASCII::
+* Base64::
+* binary::
* cn-gb:: cn-gb, gb2312
* cn-big5:: cn-big5, big5
* CNS 11643:: CNS 11643-1992
* coded character set:: Coded character set, Character code
* code extension:: Code extension
* Content-Disposition:: Content-Disposition field
-* Content-Type field::
-* Emacs::
-* encoded-word::
-* encapsulation::
-* euc-kr::
-* FTP:: FTP
+* Content-Type field::
+* Emacs::
+* encoded-word::
+* encapsulation::
+* entity:: Entity
+* euc-kr::
+* FTP:: FTP
* GB 2312:: GB 2312-1980
* GB 8565.2:: GB 8565.2-1988
* graphic character set:: Graphic Character Set
-* hz-gb2312::
-* ISO 2022::
-* iso-2022-cn::
-* iso-2022-cn-ext::
-* iso-2022-jp::
-* iso-2022-jp-2::
-* iso-2022-kr::
-* ISO 646::
-* ISO 8859-1::
-* iso-8859-1::
-* ISO 8859-2::
-* iso-8859-2::
-* ISO 8859-3::
-* ISO 8859-4::
-* ISO 8859-5::
-* iso-8859-5::
-* ISO 8859-6::
-* ISO 8859-7::
-* iso-8859-7::
-* ISO 8859-8::
-* ISO 8859-9::
-* ISO-IR-165:: ISO-IR-165, CCITT Extended GB
-* JIS X0201::
+* hz-gb2312::
+* ISO 2022::
+* iso-2022-cn::
+* iso-2022-cn-ext::
+* iso-2022-jp::
+* iso-2022-jp-2::
+* iso-2022-kr::
+* ISO 646::
+* ISO 8859-1::
+* iso-8859-1::
+* ISO 8859-2::
+* iso-8859-2::
+* ISO 8859-3::
+* ISO 8859-4::
+* ISO 8859-5::
+* iso-8859-5::
+* ISO 8859-6::
+* ISO 8859-7::
+* iso-8859-7::
+* ISO 8859-8::
+* ISO 8859-9::
+* ISO-IR-165:: ISO-IR-165, CCITT Extended GB
+* JIS X0201::
* JIS C6226:: JIS C6226-1978
-* JIS X0208::
+* JIS X0208::
* JIS X0212:: JIS X0212-1990
-* koi8-r::
+* koi8-r::
* KS C5601:: KS C5601-1987
-* media type::
-* message::
-* message/rfc822::
-* method::
-* MIME::
-* MIME charset::
-* MTA::
-* MUA::
-* MULE::
+* media type::
+* message::
+* message/rfc822::
+* method::
+* MIME::
+* MIME charset::
+* MTA::
+* MUA::
+* MULE::
* multipart:: Multipart
-* multipart/alternative::
-* multipart/digest::
-* multipart/encrypted::
-* multipart/mixed::
-* multipart/parallel::
-* multipart/signed::
-* PGP::
-* PGP-kazu::
-* PGP/MIME::
-* Quoted-Printable::
-* RFC 821::
-* RFC 822::
-* RFC 934::
-* RFC 1036::
-* RFC 1153::
-* RFC 1557::
-* RFC 1922::
-* RFC 2045::
-* RFC 2046::
-* RFC 2048::
-* RFC 2049::
-* plain text::
-* Security multipart::
-* text/enriched::
-* text/plain::
+* multipart/alternative::
+* multipart/digest::
+* multipart/encrypted::
+* multipart/mixed::
+* multipart/parallel::
+* multipart/signed::
+* PGP::
+* PGP-kazu::
+* PGP/MIME::
+* Quoted-Printable::
+* RFC 821::
+* RFC 822::
+* RFC 934::
+* RFC 1036::
+* RFC 1153::
+* RFC 1557::
+* RFC 1922::
+* RFC 2045::
+* RFC 2046::
+* RFC 2048::
+* RFC 2049::
+* plain text::
+* Security multipart::
+* text/enriched::
+* text/plain::
* tm-kernel:: tm-kernel, tm
-* tm-MUA::
-* us-ascii::
-
+* tm-MUA::
+* us-ascii::
\1f
-File: tm-en.info, Node: 7bit, Next: 8bit, Prev: Glossary, Up: Glossary
+File: tm-en.info, Node: 7bit, Next: 8bit, Prev: Glossary, Up: Glossary
7bit
----
-*7bit* means any integer between 0 .. 127.
+ *7bit* means any integer between 0 .. 127.
-Any data represented by 7bit integers is called *7bit data*.
+ Any data represented by 7bit integers is called *7bit data*.
-Textual string consisted of Control characters between 0 .. 31 and 127,
-and space represented by 32, and graphic characters between 33 .. 236
-are called *7bit (textual) string*.
+ Textual string consisted of Control characters between 0 .. 31 and
+127, and space represented by 32, and graphic characters between 33 ..
+236 are called *7bit (textual) string*.
-Traditional Internet MTA (*Note MTA::) can translate 7bit data, so it is
-no need to translate by Quoted-Printable (*Note Quoted-Printable::) or
-Base64 (*Note Base64::) for 7bit data.
+ Traditional Internet MTA (*Note MTA::) can translate 7bit data, so
+it is no need to translate by Quoted-Printable (*Note
+Quoted-Printable::) or Base64 (*Note Base64::) for 7bit data.
-However if there are too long lines, it can not translate by 7bit MTA
+ However if there are too long lines, it can not translate by 7bit MTA
even if it is 7bit data. RFC 821 (*Note RFC 821::) and RFC 2045 (*Note
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 (*Note binary::). For example, Postscript file should be encoded
-by Quoted-Printable.
-
-
+binary (*Note binary::). For example, Postscript file should be
+encoded by Quoted-Printable.
\1f
-File: tm-en.info, Node: 8bit, Next: 94-character set, Prev: 7bit, Up: Glossary
+File: tm-en.info, Node: 8bit, Next: 94-character set, Prev: 7bit, Up: Glossary
8bit
----
-*8bit* means any integer between 0 .. 255.
+ *8bit* means any integer between 0 .. 255.
-Any data represented by 8bit integers is called *8bit data*.
+ Any data represented by 8bit integers is called *8bit data*.
-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 *8bit (textual) string*.
+ 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 *8bit (textual) string*.
-For example, iso-8859-1 (*Note iso-8859-1::) or euc-kr (*Note euc-kr::)
-are coded-character-set represented by 8bit textual string.
+ For example, iso-8859-1 (*Note iso-8859-1::) or euc-kr (*Note
+euc-kr::) are coded-character-set represented by 8bit textual string.
-Traditional Internet MTA (*Note MTA::) can translate only 7bit (*Note
-7bit::) data, so if a 8bit data will be translated such MTA, it must be
-encoded by Quoted-Printable (*Note Quoted-Printable::) or Base64 (*Note
-Base64::).
+ Traditional Internet MTA (*Note MTA::) can translate only 7bit
+(*Note 7bit::) data, so if a 8bit data will be translated such MTA, it
+must be encoded by Quoted-Printable (*Note Quoted-Printable::) or Base64
+(*Note Base64::).
-However 8bit MTA are increasing today.
+ However 8bit MTA are increasing today.
-However if there are too long lines, it can not translate by 8bit MTA
+ However if there are too long lines, it can not translate by 8bit MTA
even if it is 8bit data. RFC 2045 (*Note RFC 2045::) require lines in
8bit data must be less than 998 bytes. So if a "8bit data" has a line
more than 999 bytes, it is regarded as binary (*Note binary::), so it
must be encoded by Base64 or Quoted-Printable.
-
-
\1f
-File: tm-en.info, Node: 94-character set, Next: 96-character set, Prev: 8bit, Up: Glossary
+File: tm-en.info, Node: 94-character set, Next: 96-character set, Prev: 8bit, Up: Glossary
94-character set
----------------
-*94-character set* is a kind of 1 byte
-graphic character set (*Note 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 (*Note ASCII::), JIS X0201-Latin)
-
-
+ *94-character set* is a kind of 1 byte graphic character set (*Note
+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 (*Note
+ASCII::), JIS X0201-Latin)
\1f
-File: tm-en.info, Node: 96-character set, Next: 94x94-character set, Prev: 94-character set, Up: Glossary
+File: tm-en.info, Node: 96-character set, Next: 94x94-character set, Prev: 94-character set, Up: Glossary
96-character set
----------------
-*96-character set* is a kind of 1 byte
-graphic character set (*Note 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)
-
-
+ *96-character set* is a kind of 1 byte graphic character set (*Note
+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)
\1f
-File: tm-en.info, Node: 94x94-character set, Next: ASCII, Prev: 96-character set, Up: Glossary
+File: tm-en.info, Node: 94x94-character set, Next: ASCII, Prev: 96-character set, Up: Glossary
94x94-character set
-------------------
-*94x94-character set* is a kind of 2
-byte graphic character set (*Note 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 (*Note JIS X0208::), GB 2312 (*Note GB 2312::))
-
-
+ *94x94-character set* is a kind of 2 byte graphic character set
+(*Note 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 (*Note
+JIS X0208::), GB 2312 (*Note GB 2312::))
\1f
-File: tm-en.info, Node: ASCII, Next: Base64, Prev: 94x94-character set, Up: Glossary
+File: tm-en.info, Node: ASCII, Next: Base64, Prev: 94x94-character set, Up: Glossary
ASCII
-----
-*ASCII* is a 94-character set (*Note 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 (*Note ISO 646::).
-
-
-[ASCII] "Coded Character Set -- 7-Bit American Standard Code for
- Information Interchange", ANSI X3.4:1986.
-
-
+ *ASCII* is a 94-character set (*Note 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
+(*Note ISO 646::).
+[ASCII]
+ "Coded Character Set - 7-Bit American Standard Code for Information
+ Interchange", ANSI X3.4:1986.
\1f
-File: tm-en.info, Node: Base64, Next: binary, Prev: ASCII, Up: Glossary
+File: tm-en.info, Node: Base64, Next: binary, Prev: ASCII, Up: Glossary
Base64
------
-*Base64* is a transfer encoding method of MIME
-(*Note MIME::) defined in RFC 2045 (*Note RFC 2045::).
+ *Base64* is a transfer encoding method of MIME (*Note MIME::)
+defined in RFC 2045 (*Note RFC 2045::).
-The encoding process represents 24-bit groups of input bits as output
+ The encoding process represents 24-bit groups of input bits as output
strings of 4 encoded characters. Encoded characters represent integer 0
-.. 63 or *pad*. Base64 data must be 4 * n bytes, so
-pad is used to adjust size.
+.. 63 or *pad*. Base64 data must be 4 * n bytes, so pad is used to
+adjust size.
-These 65 characters are subset of all versions of ISO 646, including
+ These 65 characters are subset of all versions of ISO 646, including
US-ASCII, and all versions of EBCDIC. So it is safe even if it is
translated by non-Internet gateways.
-
-
\1f
-File: tm-en.info, Node: binary, Next: cn-gb, Prev: Base64, Up: Glossary
+File: tm-en.info, Node: binary, Next: cn-gb, Prev: Base64, Up: Glossary
binary
------
-Any byte stream is called *binary*.
+ Any byte stream is called *binary*.
-It does not require structureof lines. It differs from from 8bit (*Note
-8bit::).
+ It does not require structureof lines. It differs from from 8bit
+(*Note 8bit::).
-In addition, if line structured data contain too long line (more than
+ In addition, if line structured data contain too long line (more than
998 bytes), it is regarded as binary.
-
-
\1f
-File: tm-en.info, Node: cn-gb, Next: cn-big5, Prev: binary, Up: Glossary
+File: tm-en.info, Node: cn-gb, Next: cn-big5, Prev: binary, Up: Glossary
cn-gb, gb2312
-------------
-A MIME charset (*Note MIME charset::) for simplified Chinese mainly used
-in the Chinese mainland.
-
-It is a 8bit (*Note 8bit::) coded character set (*Note coded character
-set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII (*Note
-ASCII::) to combine GB 2312 (*Note GB 2312::).
-
-It is defined in RFC 1922 (*Note RFC 1922::).
+ A MIME charset (*Note MIME charset::) for simplified Chinese mainly
+used in the Chinese mainland.
+ It is a 8bit (*Note 8bit::) coded character set (*Note coded
+character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
+(*Note ASCII::) to combine GB 2312 (*Note GB 2312::).
+ It is defined in RFC 1922 (*Note RFC 1922::).
\1f
-File: tm-en.info, Node: cn-big5, Next: CNS 11643, Prev: cn-gb, Up: Glossary
+File: tm-en.info, Node: cn-big5, Next: CNS 11643, Prev: cn-gb, Up: Glossary
cn-big5, big5
-------------
-A MIME charset (*Note MIME charset::) for traditional Chinese mainly
+ A MIME charset (*Note MIME charset::) for traditional Chinese mainly
used in Taiwan and Hon Kong.
-It is a 8bit (*Note 8bit::) coded character set (*Note coded character
-set::) not based on ISO 2022 (*Note ISO 2022::). It is a de-fact
-standard.
-
-It is defined in RFC 1922 (*Note RFC 1922::).
+ It is a 8bit (*Note 8bit::) coded character set (*Note coded
+character set::) not based on ISO 2022 (*Note ISO 2022::). It is a
+de-fact standard.
-cf. [BIG5] Institute for Information Industry, "Chinese Coded
- Character Set in Computer", March 1984.
+ It is defined in RFC 1922 (*Note RFC 1922::).
-It corresponds to CNS 11643 (*Note CNS 11643::).
+ cf.
+[BIG5]
+ Institute for Information Industry, "Chinese Coded Character Set in
+ Computer", March 1984.
+ It corresponds to CNS 11643 (*Note CNS 11643::).
\1f
-File: tm-en.info, Node: CNS 11643, Next: coded character set, Prev: cn-big5, Up: Glossary
+File: tm-en.info, Node: CNS 11643, Next: coded character set, Prev: cn-big5, Up: Glossary
CNS 11643-1992
--------------
-Graphic character set (*Note Graphic character set::)s for Chinese
+ Graphic character sets (*Note 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 (*Note 94x94 character set::).
+Kong. It is a standard of Taiwan. Currently there are seven
+94x94-character set (*Note 94x94-character set::).
-Final byte of ISO 2022 (*Note ISO 2022::) are following:
+ Final byte of ISO 2022 (*Note ISO 2022::) are following:
`plane 1'
04/07 (`G')
`plane 7'
04/13 (`M')
-
-
-
-[CNS 11643-1992] "Standard Interchange Code for Generally-Used
- Chinese Characters", CNS 11643:1992.
-
-
-
+[CNS 11643-1992]
+ "Standard Interchange Code for Generally-Used Chinese Characters",
+ CNS 11643:1992.
\1f
-File: tm-en.info, Node: coded character set, Next: code extension, Prev: CNS 11643, Up: Glossary
+File: tm-en.info, Node: coded character set, Next: code extension, Prev: CNS 11643, Up: Glossary
Coded character set, Character code
-----------------------------------
-A set of unambiguous rules that establishes a character set and the
+ A set of unambiguous rules that establishes a character set and the
one-to-one relationship between the characters of the set and their bit
combinations.
-
-
\1f
-File: tm-en.info, Node: code extension, Next: Content-Disposition, Prev: coded character set, Up: Glossary
+File: tm-en.info, Node: code extension, Next: Content-Disposition, Prev: coded character set, Up: Glossary
Code extension
--------------
-The techniques for the encoding of characters that are not included in
-the character set of a given code. (ex. ISO 2022 (*Note ISO 2022::))
-
-
+ The techniques for the encoding of characters that are not included
+in the character set of a given code. (ex. ISO 2022 (*Note ISO 2022::))
\1f
-File: tm-en.info, Node: Content-Disposition, Next: Content-Type field, Prev: code extension, Up: Glossary
+File: tm-en.info, Node: Content-Disposition, Next: Content-Type field, Prev: code extension, Up: Glossary
Content-Disposition field
-------------------------
-A field to specify presentation of entity or file name. It is an
+ A field to specify presentation of entity or file name. It is an
extension for MIME (*Note MIME::).
-
-[RFC 1806] E R. Troost and S. Dorner, "Communicating Presentation
- Information in Internet Messages: The Content-Disposition Header",
- June 1995, Experimental.
-
-
-
+[RFC 1806]
+ E R. Troost and S. Dorner, "Communicating Presentation Information
+ in Internet Messages: The Content-Disposition Header", June 1995,
+ Experimental.
\1f
-File: tm-en.info, Node: Content-Type field, Next: Emacs, Prev: Content-Disposition, Up: Glossary
+File: tm-en.info, Node: Content-Type field, Next: Emacs, Prev: Content-Disposition, Up: Glossary
Content-Type field
------------------
-Header field to represent information about body, such as media type
+ Header field to represent information about body, such as media type
(*Note media type::), MIME charset (*Note MIME charset::). It is
defined in RFC 2045 (*Note RFC 2045::).
*[Memo]*
-
Historically, Content-Type field was proposed in RFC 1049. In it,
Content-Type did not distinguish type and subtype. However MIME
- parser may be able to accept RFC 1049 based Content-Type as unknown
- type.
-
-
-Content-Type field is defined as following:
+ parser may be able to accept RFC 1049 based Content-Type as
+ unknown type.
- "Content-Type" ":" *type* "/"
- *subtype* *( ";" *parameter* )
+ Content-Type field is defined as following:
+ "Content-Type" ":" *type* "/" *subtype* *( ";" *parameter* )
-For example:
+ For example:
Content-Type: image/jpeg
-
Content-Type: text/plain; charset=iso-2022-jp
-
*[Memo]*
-
A part does not have content-type field is regarded as
Content-Type: text/plain; charset=us-ascii
(cf. *Note us-ascii::)
-
And a part has unknown type/subtype is regarded as
Content-Type: application/octet-stream
-
-
-
\1f
-File: tm-en.info, Node: Emacs, Next: encoded-word, Prev: Content-Type field, Up: Glossary
+File: tm-en.info, Node: Emacs, Next: encoded-word, Prev: Content-Type field, Up: Glossary
Emacs
-----
-In this document, `Emacs' means GNU Emacs released by FSF, and `emacs'
-means any variants of GNU Emacs.
-
-
+ In this document, `Emacs' means GNU Emacs released by FSF, and
+`emacs' means any variants of GNU Emacs.
\1f
-File: tm-en.info, Node: encoded-word, Next: encapsulation, Prev: Emacs, Up: Glossary
+File: tm-en.info, Node: encoded-word, Next: encapsulation, Prev: Emacs, Up: Glossary
encoded-word
------------
-Representation non ASCII (*Note ASCII::) characters in header. It is
+ Representation non ASCII (*Note ASCII::) characters in header. It is
defined in *RFC 2047*.
-
-[RFC 2047] K. Moore, "MIME (Multipurpose Internet Mail Extensions)
- Part Three: Message Header Extensions for Non-ASCII Text", November
- 1996, Standards Track (obsolete RFC 1521,1522,1590).
-
-
-
+[RFC 2047]
+ K. Moore, "MIME (Multipurpose Internet Mail Extensions) Part Three:
+ Message Header Extensions for Non-ASCII Text", November 1996,
+ Standards Track (obsolete RFC 1521,1522,1590).
\1f
-File: tm-en.info, Node: encapsulation, Next: euc-kr, Prev: encoded-word, Up: Glossary
+File: tm-en.info, Node: encapsulation, Next: entity, Prev: encoded-word, Up: Glossary
encapsulation
-------------
-Method to insert whole Internet message (*Note RFC 822::) into another
-Internet message.
+ Method to insert whole Internet message (*Note RFC 822::) into
+another Internet message.
+
+ For example, it is used to forward a message.
-For example, it is used to forward a message.
+ (cf. *Note message/rfc822::)
-(cf. *Note message/rfc822::)
+\1f
+File: tm-en.info, Node: entity, Next: euc-kr, Prev: encapsulation, Up: Glossary
+Entity
+------
+ Header fields and contents of a message or one of the parts in the
+body of a multipart (*Note multipart::) entity.
+*[Memo]*
+ In this document, `entity' might be called "part".
\1f
-File: tm-en.info, Node: euc-kr, Next: FTP, Prev: encapsulation, Up: Glossary
+File: tm-en.info, Node: euc-kr, Next: FTP, Prev: entity, Up: Glossary
euc-kr
------
-A MIME charset (*Note MIME charset::) for Korean.
-
-It is a 8bit (*Note 8bit::) coded character set (*Note coded character
-set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII (*Note
-ASCII::) to combine KS C5601 (*Note KS C5601::).
+ A MIME charset (*Note MIME charset::) for Korean.
-It is defined in RFC 1557 (*Note RFC 1557::).
-
-cf. [euc-kr] Korea Industrial Standards Association, "Hangul Unix
- Environment", KS C 5861:1992.
+ It is a 8bit (*Note 8bit::) coded character set (*Note coded
+character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
+(*Note ASCII::) to combine KS C5601 (*Note KS C5601::).
+ It is defined in RFC 1557 (*Note RFC 1557::).
+ cf.
+[euc-kr]
+ Korea Industrial Standards Association, "Hangul Unix Environment",
+ KS C 5861:1992.
\1f
-File: tm-en.info, Node: FTP, Next: GB 2312, Prev: euc-kr, Up: Glossary
+File: tm-en.info, Node: FTP, Next: GB 2312, Prev: euc-kr, Up: Glossary
FTP
---
-
-[FTP: RFC 959] Postel, J. and J. Reynolds, "File Transfer
- Protocol", October 1985, STD 9.
-
-
-
+[FTP: RFC 959]
+ Postel, J. and J. Reynolds, "File Transfer Protocol", October 1985,
+ STD 9.
\1f
-File: tm-en.info, Node: GB 2312, Next: GB 8565.2, Prev: FTP, Up: Glossary
+File: tm-en.info, Node: GB 2312, Next: GB 8565.2, Prev: FTP, Up: Glossary
GB 2312-1980
------------
-A 94x94 character set (*Note 94x94 character set::) for Chinese mainly
-written by simplified Chinese mainly used in the Chinese mainland. It
-is a standard of China.
-
-Final byte of ISO 2022 (*Note ISO 2022::) is 04/01 (`A').
-
-
-[GB 2312] "Code of Chinese Graphic Character Set for Information
- Interchange - Primary Set", GB 2312:1980.
-
+ A 94x94-character set (*Note 94x94-character set::) for Chinese
+mainly written by simplified Chinese mainly used in the Chinese
+mainland. It is a standard of China.
+ Final byte of ISO 2022 (*Note ISO 2022::) is 04/01 (`A').
+[GB 2312]
+ "Code of Chinese Graphic Character Set for Information Interchange
+ - Primary Set", GB 2312:1980.
\1f
-File: tm-en.info, Node: GB 8565.2, Next: graphic character set, Prev: GB 2312, Up: Glossary
+File: tm-en.info, Node: GB 8565.2, Next: graphic character set, Prev: GB 2312, Up: Glossary
GB 8565.2-1988
--------------
-A 94x94 character set (*Note 94x94 character set::) for Chinese as
+ A 94x94-character set (*Note 94x94-character set::) for Chinese as
supplement to GB 2312 (*Note GB 2312::). It is a standard of China.
-
-[GB 8565.2] "Information Processing - Coded Character Sets for Text
+[GB 8565.2]
+ "Information Processing - Coded Character Sets for Text
Communication - Part 2: Graphic Characters used with Primary Set",
GB 8565.2:1988.
-
-
-
\1f
-File: tm-en.info, Node: graphic character set, Next: hz-gb2312, Prev: GB 8565.2, Up: Glossary
+File: tm-en.info, Node: graphic character set, Next: hz-gb2312, Prev: GB 8565.2, Up: Glossary
Graphic Character Set
---------------------
-Coded character set (*Note Coded character set::) for graphic
+ Coded character set (*Note coded character set::) for graphic
characters.
-
-
\1f
-File: tm-en.info, Node: hz-gb2312, Next: ISO 2022, Prev: graphic character set, Up: Glossary
+File: tm-en.info, Node: hz-gb2312, Next: ISO 2022, Prev: graphic character set, Up: Glossary
hz-gb2312
---------
-A MIME charset (*Note MIME charset::) for simplified Chinese mainly used
-in the Chinese mainland.
-
-It extends ASCII (*Note ASCII::) to combine GB 2312 (*Note GB 2312::),
-its technique is like iso-2022-jp (*Note iso-2022-jp::), but it is
-designed to be ASCII printable to use special form for ESC sequence to
-designate GB 2312 to G0.
+ A MIME charset (*Note MIME charset::) for simplified Chinese mainly
+used in the Chinese mainland.
-It is defined in RFC 1842 and 1843.
-
-
-[RFC 1842] Y. Wei, Y. Zhang, J. Li, J. Ding and Y. Jiang, "ASCII
- Printable Characters-Based Chinese Character Encoding for Internet
- Messages", August 1995, Informational.
-
-
-[RFC 1843] F. Lee, "HZ - A Data Format for Exchanging Files of
- Arbitrarily Mixed Chinese and ASCII characters", August 1995,
- Informational.
+ It extends ASCII (*Note ASCII::) to combine GB 2312 (*Note GB
+2312::), its technique is like iso-2022-jp (*Note iso-2022-jp::), but
+it is designed to be ASCII printable to use special form for ESC
+sequence to designate GB 2312 to G0.
+ It is defined in RFC 1842 and 1843.
+[RFC 1842]
+ Y. Wei, Y. Zhang, J. Li, J. Ding and Y. Jiang, "ASCII Printable
+ Characters-Based Chinese Character Encoding for Internet Messages",
+ August 1995, Informational.
+[RFC 1843]
+ F. Lee, "HZ - A Data Format for Exchanging Files of Arbitrarily
+ Mixed Chinese and ASCII characters", August 1995, Informational.
\1f
-File: tm-en.info, Node: ISO 2022, Next: iso-2022-cn, Prev: hz-gb2312, Up: Glossary
+File: tm-en.info, Node: ISO 2022, Next: iso-2022-cn, Prev: hz-gb2312, Up: Glossary
ISO 2022
--------
-It is a standard for character code structure and code extension (*Note
-code extension::) technique.
-
-
-[ISO 2022] International Organization for Standardization (ISO),
- "Information Processing: ISO 7-bit and 8-bit coded character sets:
- Code extension techniques", ISO/IEC 2022:1994.
-
-
+ It is a standard for character code structure and code extension
+(*Note code extension::) technique.
+[ISO 2022]
+ International Organization for Standardization (ISO), "Information
+ Processing: ISO 7-bit and 8-bit coded character sets: Code
+ extension techniques", ISO/IEC 2022:1994.
\1f
-File: tm-en.info, Node: iso-2022-cn, Next: iso-2022-cn-ext, Prev: ISO 2022, Up: Glossary
+File: tm-en.info, Node: iso-2022-cn, Next: iso-2022-cn-ext, Prev: ISO 2022, Up: Glossary
iso-2022-cn
-----------
-A MIME charset (*Note MIME charset::) for Chinese.
-
-It is a 7bit (*Note 7bit::) coded character set (*Note coded character
-set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII (*Note
-ASCII::) to combine GB 2312 (*Note GB 2312::) and/or CNS 11643 plain 1,
-plain 2 (*Note CNS 11643::).
-
-It is defined in RFC 1922 (*Note RFC 1922::).
+ A MIME charset (*Note MIME charset::) for Chinese.
+ It is a 7bit (*Note 7bit::) coded character set (*Note coded
+character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
+(*Note ASCII::) to combine GB 2312 (*Note GB 2312::) and/or CNS 11643
+plain 1, plain 2 (*Note CNS 11643::).
+ It is defined in RFC 1922 (*Note RFC 1922::).
\1f
-File: tm-en.info, Node: iso-2022-cn-ext, Next: iso-2022-jp, Prev: iso-2022-cn, Up: Glossary
+File: tm-en.info, Node: iso-2022-cn-ext, Next: iso-2022-jp, Prev: iso-2022-cn, Up: Glossary
iso-2022-cn-ext
---------------
-A MIME charset (*Note MIME charset::) for Chinese.
+ A MIME charset (*Note MIME charset::) for Chinese.
-It is a 7bit (*Note 7bit::) coded character set (*Note coded character
-set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII (*Note
-ASCII::) to combine GB 2312 (*Note GB 2312::), CNS 11643 plain 1 .. 7
-(*Note CNS 11643::), ISO-IR-165 (*Note ISO-IR-165::) and other Chinese
-graphic character sets.
+ It is a 7bit (*Note 7bit::) coded character set (*Note coded
+character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
+(*Note ASCII::) to combine GB 2312 (*Note GB 2312::), CNS 11643 plain 1
+.. 7 (*Note CNS 11643::), ISO-IR-165 (*Note ISO-IR-165::) and other
+Chinese graphic character sets.
-It is defined in RFC 1922 (*Note RFC 1922::).
+ It is defined in RFC 1922 (*Note RFC 1922::).
*[Memo]*
MULE 2.3 and current XEmacs/mule can not use it correctly.
Emacs/mule can use it.
-
-
-
\1f
-File: tm-en.info, Node: iso-2022-jp, Next: iso-2022-jp-2, Prev: iso-2022-cn-ext, Up: Glossary
+File: tm-en.info, Node: iso-2022-jp, Next: iso-2022-jp-2, Prev: iso-2022-cn-ext, Up: Glossary
iso-2022-jp
-----------
-A MIME charset (*Note MIME charset::) for Japanese.
+ A MIME charset (*Note MIME charset::) for Japanese.
-It is a 7bit (*Note 7bit::) coded character set (*Note coded character
-set::) based on old ISO 2022 (*Note ISO 2022::). It switches ASCII
-(*Note ASCII::), JIS X0201-Latin, JIS X0208-1978 (*Note JIS
-C6226-1978::) and JIS X0208-1983 (*Note JIS X0208::).
+ It is a 7bit (*Note 7bit::) coded character set (*Note coded
+character set::) based on old ISO 2022 (*Note ISO 2022::). It switches
+ASCII (*Note ASCII::), JIS X0201-Latin, JIS X0208-1978 (*Note JIS
+C6226::) and JIS X0208-1983 (*Note JIS X0208::).
-It is defined in RFC 1468.
+ It is defined in RFC 1468.
*[Memo]*
JIS X0208-1997? will define it in annex as non-ISO 2022 (*Note ISO
2022::) encoding.
-
-
-[iso-2022-jp: RFC 1468] Murai J., M. Crispin, and E. van der Poel,
- "Japanese Character Encoding for Internet Messages", June 1993.
-
-
-
+[iso-2022-jp: RFC 1468]
+ Murai J., M. Crispin, and E. van der Poel, "Japanese Character
+ Encoding for Internet Messages", June 1993.
\1f
-File: tm-en.info, Node: iso-2022-jp-2, Next: iso-2022-kr, Prev: iso-2022-jp, Up: Glossary
+File: tm-en.info, Node: iso-2022-jp-2, Next: iso-2022-kr, Prev: iso-2022-jp, Up: Glossary
iso-2022-jp-2
-------------
-A MIME charset (*Note MIME charset::), which is a multilingual extension
-of iso-2022-jp (*Note iso-2022-jp::).
-
-It is defined in RFC 1554.
-
-
-[iso-2022-jp-2: RFC 1554] Ohta M. and Handa K., "ISO-2022-JP-2:
- Multilingual Extension of ISO-2022-JP", December 1993,
- Informational.
-
+ A MIME charset (*Note MIME charset::), which is a multilingual
+extension of iso-2022-jp (*Note iso-2022-jp::).
+ It is defined in RFC 1554.
+[iso-2022-jp-2: RFC 1554]
+ Ohta M. and Handa K., "ISO-2022-JP-2: Multilingual Extension of
+ ISO-2022-JP", December 1993, Informational.
\1f
-File: tm-en.info, Node: iso-2022-kr, Next: ISO 646, Prev: iso-2022-jp-2, Up: Glossary
+File: tm-en.info, Node: iso-2022-kr, Next: ISO 646, Prev: iso-2022-jp-2, Up: Glossary
iso-2022-kr
-----------
-A MIME charset (*Note MIME charset::) for Korean language (Hangul
+ A MIME charset (*Note MIME charset::) for Korean language (Hangul
script).
-It is based on ISO 2022 (*Note ISO 2022::) code extension (*Note code
-extension::) technique to extend ASCII (*Note ASCII::) to use KS C5601
-(*Note KS C5601::) as 7bit (*Note 7bit::) text.
-
-It is defined in RFC 1557 (*Note RFC 1557::).
-
+ It is based on ISO 2022 (*Note ISO 2022::) code extension (*Note
+code extension::) technique to extend ASCII (*Note ASCII::) to use KS
+C5601 (*Note KS C5601::) as 7bit (*Note 7bit::) text.
+ It is defined in RFC 1557 (*Note RFC 1557::).
\1f
-File: tm-en.info, Node: ISO 646, Next: ISO 8859-1, Prev: iso-2022-kr, Up: Glossary
+File: tm-en.info, Node: ISO 646, Next: ISO 8859-1, Prev: iso-2022-kr, Up: Glossary
ISO 646
-------
-
-[ISO 646] International Organization for Standardization (ISO),
- "Information technology: ISO 7-bit coded character set for
- information interchange", ISO/IEC 646:1991.
-
-
-
+[ISO 646]
+ International Organization for Standardization (ISO), "Information
+ technology: ISO 7-bit coded character set for information
+ interchange", ISO/IEC 646:1991.
\1f
-File: tm-en.info, Node: ISO 8859-1, Next: iso-8859-1, Prev: ISO 646, Up: Glossary
+File: tm-en.info, Node: ISO 8859-1, Next: iso-8859-1, Prev: ISO 646, Up: Glossary
ISO 8859-1
----------
-
-[ISO 8859-1] International Organization for Standardization (ISO),
- "Information Processing -- 8-bit Single-Byte Coded Graphic
- Character Sets -- Part 1: Latin Alphabet No.1", ISO 8859-1:1987.
-
-
-
+[ISO 8859-1]
+ International Organization for Standardization (ISO), "Information
+ Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
+ 1: Latin Alphabet No.1", ISO 8859-1:1987.
\1f
-File: tm-en.info, Node: iso-8859-1, Next: ISO 8859-2, Prev: ISO 8859-1, Up: Glossary
+File: tm-en.info, Node: iso-8859-1, Next: ISO 8859-2, Prev: ISO 8859-1, Up: Glossary
iso-8859-1
----------
-*iso-8859-1* is a MIME charset (*Note MIME charset::) for west-European languages written by Latin script.
-
-It is a 8bit (*Note 8bit::) coded character set (*Note coded character
-set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII (*Note
-ASCII::) to combine ISO 8859-1 (*Note ISO 8859-1::).
-
-It is defined in RFC 2046 (*Note RFC 2046::).
+ *iso-8859-1* is a MIME charset (*Note MIME charset::) for
+west-European languages written by Latin script.
+ It is a 8bit (*Note 8bit::) coded character set (*Note coded
+character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
+(*Note ASCII::) to combine ISO 8859-1 (*Note ISO 8859-1::).
+ It is defined in RFC 2046 (*Note RFC 2046::).
\1f
-File: tm-en.info, Node: ISO 8859-2, Next: iso-8859-2, Prev: iso-8859-1, Up: Glossary
+File: tm-en.info, Node: ISO 8859-2, Next: iso-8859-2, Prev: iso-8859-1, Up: Glossary
ISO 8859-2
----------
-
-[ISO 8859-2] International Organization for Standardization (ISO),
- "Information Processing -- 8-bit Single-Byte Coded Graphic
- Character Sets -- Part 2: Latin alphabet No.2", ISO 8859-2:1987.
-
-
-
+[ISO 8859-2]
+ International Organization for Standardization (ISO), "Information
+ Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
+ 2: Latin alphabet No.2", ISO 8859-2:1987.
\1f
-File: tm-en.info, Node: iso-8859-2, Next: ISO 8859-3, Prev: ISO 8859-2, Up: Glossary
+File: tm-en.info, Node: iso-8859-2, Next: ISO 8859-3, Prev: ISO 8859-2, Up: Glossary
iso-8859-2
----------
-*iso-8859-2* is a MIME charset (*Note MIME charset::) for east-European languages written by Latin script.
-
-It is a 8bit (*Note 8bit::) coded character set (*Note coded character
-set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII (*Note
-ASCII::) to combine ISO 8859-2 (*Note ISO 8859-2::).
-
-It is defined in RFC 2046 (*Note RFC 2046::).
+ *iso-8859-2* is a MIME charset (*Note MIME charset::) for
+east-European languages written by Latin script.
+ It is a 8bit (*Note 8bit::) coded character set (*Note coded
+character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
+(*Note ASCII::) to combine ISO 8859-2 (*Note ISO 8859-2::).
+ It is defined in RFC 2046 (*Note RFC 2046::).
\1f
-File: tm-en.info, Node: ISO 8859-3, Next: ISO 8859-4, Prev: iso-8859-2, Up: Glossary
+File: tm-en.info, Node: ISO 8859-3, Next: ISO 8859-4, Prev: iso-8859-2, Up: Glossary
ISO 8859-3
----------
-
-[ISO 8859-3] International Organization for Standardization (ISO),
- "Information Processing -- 8-bit Single-Byte Coded Graphic
- Character Sets -- Part 3: Latin alphabet No.3", ISO 8859-3:1988.
-
-
-
+[ISO 8859-3]
+ International Organization for Standardization (ISO), "Information
+ Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
+ 3: Latin alphabet No.3", ISO 8859-3:1988.
\1f
-File: tm-en.info, Node: ISO 8859-4, Next: ISO 8859-5, Prev: ISO 8859-3, Up: Glossary
+File: tm-en.info, Node: ISO 8859-4, Next: ISO 8859-5, Prev: ISO 8859-3, Up: Glossary
ISO 8859-4
----------
-
-[ISO 8859-4] International Organization for Standardization (ISO),
- "Information Processing -- 8-bit Single-Byte Coded Graphic
- Character Sets -- Part 4: Latin alphabet No.4", ISO 8859-4:1988.
-
-
-
+[ISO 8859-4]
+ International Organization for Standardization (ISO), "Information
+ Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
+ 4: Latin alphabet No.4", ISO 8859-4:1988.
\1f
-File: tm-en.info, Node: ISO 8859-5, Next: iso-8859-5, Prev: ISO 8859-4, Up: Glossary
+File: tm-en.info, Node: ISO 8859-5, Next: iso-8859-5, Prev: ISO 8859-4, Up: Glossary
ISO 8859-5
----------
-
-[ISO 8859-5] International Organization for Standardization (ISO),
- "Information Processing -- 8-bit Single-Byte Coded Graphic
- Character Sets -- Part 5: Latin/Cyrillic alphabet", ISO
- 8859-5:1988.
-
-
-
+[ISO 8859-5]
+ International Organization for Standardization (ISO), "Information
+ Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
+ 5: Latin/Cyrillic alphabet", ISO 8859-5:1988.
\1f
-File: tm-en.info, Node: iso-8859-5, Next: ISO 8859-6, Prev: ISO 8859-5, Up: Glossary
+File: tm-en.info, Node: iso-8859-5, Next: ISO 8859-6, Prev: ISO 8859-5, Up: Glossary
iso-8859-5
----------
-*iso-8859-5* is a MIME charset (*Note MIME charset::) for Cyrillic script.
-
-It is a 8bit (*Note 8bit::) coded character set (*Note coded character
-set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII (*Note
-ASCII::) to combine ISO 8859-5 (*Note ISO 8859-5::).
-
-It is defined in RFC 2046 (*Note RFC 2046::).
+ *iso-8859-5* is a MIME charset (*Note MIME charset::) for Cyrillic
+script.
+ It is a 8bit (*Note 8bit::) coded character set (*Note coded
+character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
+(*Note ASCII::) to combine ISO 8859-5 (*Note ISO 8859-5::).
+ It is defined in RFC 2046 (*Note RFC 2046::).
\1f
-File: tm-en.info, Node: ISO 8859-6, Next: ISO 8859-7, Prev: iso-8859-5, Up: Glossary
+File: tm-en.info, Node: ISO 8859-6, Next: ISO 8859-7, Prev: iso-8859-5, Up: Glossary
ISO 8859-6
----------
-
-[ISO 8859-6] International Organization for Standardization (ISO),
- "Information Processing -- 8-bit Single-Byte Coded Graphic
- Character Sets -- Part 6: Latin/Arabic alphabet", ISO 8859-6:1987.
-
-
-
+[ISO 8859-6]
+ International Organization for Standardization (ISO), "Information
+ Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
+ 6: Latin/Arabic alphabet", ISO 8859-6:1987.
\1f
-File: tm-en.info, Node: ISO 8859-7, Next: iso-8859-7, Prev: ISO 8859-6, Up: Glossary
+File: tm-en.info, Node: ISO 8859-7, Next: iso-8859-7, Prev: ISO 8859-6, Up: Glossary
ISO 8859-7
----------
-
-[ISO 8859-7] International Organization for Standardization (ISO),
- "Information Processing -- 8-bit Single-Byte Coded Graphic
- Character Sets -- Part 7: Latin/Greek alphabet", ISO 8859-7:1987.
-
-
-
+[ISO 8859-7]
+ International Organization for Standardization (ISO), "Information
+ Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
+ 7: Latin/Greek alphabet", ISO 8859-7:1987.
\1f
-File: tm-en.info, Node: iso-8859-7, Next: ISO 8859-8, Prev: ISO 8859-7, Up: Glossary
+File: tm-en.info, Node: iso-8859-7, Next: ISO 8859-8, Prev: ISO 8859-7, Up: Glossary
iso-8859-7
----------
-*iso-8859-7* is a MIME charset (*Note MIME charset::) for Greek script.
-
-It is a 8bit (*Note 8bit::) coded character set (*Note coded character
-set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII (*Note
-ASCII::) to combine ISO 8859-7 (*Note ISO 8859-7::).
-
-It is defined in RFC 1947.
-
-
-[iso-8859-7: RFC 1947] D. Spinellis, "Greek Character Encoding for
- Electronic Mail Messages", May 1996, Informational.
+ *iso-8859-7* is a MIME charset (*Note MIME charset::) for Greek
+script.
+ It is a 8bit (*Note 8bit::) coded character set (*Note coded
+character set::) based on ISO 2022 (*Note ISO 2022::). It extends ASCII
+(*Note ASCII::) to combine ISO 8859-7 (*Note ISO 8859-7::).
+ It is defined in RFC 1947.
+[iso-8859-7: RFC 1947]
+ D. Spinellis, "Greek Character Encoding for Electronic Mail
+ Messages", May 1996, Informational.
\1f
-File: tm-en.info, Node: ISO 8859-8, Next: ISO 8859-9, Prev: iso-8859-7, Up: Glossary
+File: tm-en.info, Node: ISO 8859-8, Next: ISO 8859-9, Prev: iso-8859-7, Up: Glossary
ISO 8859-8
----------
-
-[ISO 8859-8] International Organization for Standardization (ISO),
- "Information Processing -- 8-bit Single-Byte Coded Graphic
- Character Sets -- Part 8: Latin/Hebrew alphabet", ISO 8859-8:1988.
-
-
-
+[ISO 8859-8]
+ International Organization for Standardization (ISO), "Information
+ Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
+ 8: Latin/Hebrew alphabet", ISO 8859-8:1988.
\1f
-File: tm-en.info, Node: ISO 8859-9, Next: ISO-IR-165, Prev: ISO 8859-8, Up: Glossary
+File: tm-en.info, Node: ISO 8859-9, Next: ISO-IR-165, Prev: ISO 8859-8, Up: Glossary
ISO 8859-9
----------
-
-[ISO 8859-9] International Organization for Standardization (ISO),
- "Information Processing -- 8-bit Single-Byte Coded Graphic
- Character Sets -- Part 9: Latin alphabet No.5", ISO 8859-9:1990.
-
-
-
+[ISO 8859-9]
+ International Organization for Standardization (ISO), "Information
+ Processing - 8-bit Single-Byte Coded Graphic Character Sets - Part
+ 9: Latin alphabet No.5", ISO 8859-9:1990.
\1f
-File: tm-en.info, Node: ISO-IR-165, Next: JIS X0201, Prev: ISO 8859-9, Up: Glossary
+File: tm-en.info, Node: ISO-IR-165, Next: JIS X0201, Prev: ISO 8859-9, Up: Glossary
ISO-IR-165, CCITT Extended GB
-----------------------------
-A 94x94-character set (*Note 94x94-character set::) for Chinese mainly
-written by simplified Chinese mainly used in the Chinese mainland
+ A 94x94-character set (*Note 94x94-character set::) for Chinese
+mainly written by simplified Chinese mainly used in the Chinese mainland
registered by CCITT.
-It consists of GB 2312 (*Note GB 2312::), GB 8865.2 (*Note GB 8865.2::)
-and additional 150 characters.
-
-Final byte of ISO 2022 (*Note ISO 2022::) is 04/05 (`E').
-
+ It consists of GB 2312 (*Note GB 2312::), GB 8565.2 (*Note GB
+8565.2::) and additional 150 characters.
+ Final byte of ISO 2022 (*Note ISO 2022::) is 04/05 (`E').
\1f
-File: tm-en.info, Node: JIS X0201, Next: JIS C6226, Prev: ISO-IR-165, Up: Glossary
+File: tm-en.info, Node: JIS X0201, Next: JIS C6226, Prev: ISO-IR-165, Up: Glossary
JIS X0201
---------
-It defines two 94-character set (*Note 94-character set::), for Latin
+ It defines two 94-character set (*Note 94-character set::), for Latin
script (a variant of ISO 646 (*Note ISO 646::)) and Katakana script, and
7bit and 8bit coded character set (*Note coded character set::)s.
-It was renamed from *JIS C6220-1976*.
-
-
-[JIS X0201-1976] Japanese Standards Association, "Code for
- Information Interchange", JIS X 0201-1976:.
-
-
-In addition, revised version will be published in 1997.
-
-
-[JIS X0201-1997?] Japanese Standards Association, "7-bit and 8-bit
- coded character sets for information interchange", JIS X 0201:1997?
- draft.
+ It was renamed from *JIS C6220-1976*.
+[JIS X0201-1976]
+ Japanese Standards Association, "Code for Information Interchange",
+ JIS X 0201-1976:.
+ In addition, revised version will be published in 1997.
+[JIS X0201-1997?]
+ Japanese Standards Association, "7-bit and 8-bit coded character
+ sets for information interchange", JIS X 0201:1997? draft.
\1f
-File: tm-en.info, Node: JIS C6226, Next: JIS X0208, Prev: JIS X0201, Up: Glossary
+File: tm-en.info, Node: JIS C6226, Next: JIS X0208, Prev: JIS X0201, Up: Glossary
JIS C6226-1978
--------------
-A 94x94-character set (*Note 94x94-character set::) for Japanese. It
-was renamed to JIS X0208-1978.
-
-(cf. *Note JIS X0208::)
-
-
+ A 94x94-character set (*Note 94x94-character set::) for Japanese.
+It was renamed to JIS X0208-1978.
+ (cf. *Note JIS X0208::)
\1f
-File: tm-en.info, Node: JIS X0208, Next: JIS X0212, Prev: JIS C6226, Up: Glossary
+File: tm-en.info, Node: JIS X0208, Next: JIS X0212, Prev: JIS C6226, Up: Glossary
JIS X0208
---------
-A 94x94-character set (*Note 94x94-character set::) for Japanese.
+ A 94x94-character set (*Note 94x94-character set::) for Japanese.
Japanese standard. It was published in 1978, and revised in 1983 and
1990. In the Internet message, 1983 edition is major.
-JIS X0208 contains some symbols, numbers, primary Latin script, Hiragana
-script, Katakana script, Greek script, Cyrillic script, box drawing
-parts, Kanji (Ideographic characters used in Japanese). Notice that
-some symbols and box drawing parts were added in 1983 and some Kanjis
-were changed or swapped code points. So 1978 edition and 1983 edition
-are regarded as different graphic character set.
+ JIS X0208 contains some symbols, numbers, primary Latin script,
+Hiragana script, Katakana script, Greek script, Cyrillic script, box
+drawing parts, Kanji (Ideographic characters used in Japanese). Notice
+that some symbols and box drawing parts were added in 1983 and some
+Kanjis were changed or swapped code points. So 1978 edition and 1983
+edition are regarded as different graphic character set.
-1990 edition added some characters, so designation of 1990 edition
+ 1990 edition added some characters, so designation of 1990 edition
requires `identify revised registration' sequence, ESC 02/06 4/0 as
prefix of designation sequence.
+[JIS X0208-1978]
+ Japanese Standards Association, "Code of the Japanese graphic
+ character set for information interchange", JIS C6226:1978.
-[JIS X0208-1978] Japanese Standards Association, "Code of the
- Japanese graphic character set for information interchange", JIS
- C6226:1978.
-
-
-[JIS X0208-1983,1990] Japanese Standards Association, "Code of the
- Japanese graphic character set for information interchange", JIS
- X0208:1983,1990.
-
+[JIS X0208-1983,1990]
+ Japanese Standards Association, "Code of the Japanese graphic
+ character set for information interchange", JIS X0208:1983,1990.
-In addition, revised version will be published in 1997. (It does not
+ In addition, revised version will be published in 1997. (It does not
change graphic character set)
-
-[JIS X0208-1997?] Japanese Standards Association, "7-bit and 8-bit
- double byte coded Kanji sets for information interchange", JIS X
- 0208:1997? draft.
-
-
-
+[JIS X0208-1997?]
+ Japanese Standards Association, "7-bit and 8-bit double byte coded
+ Kanji sets for information interchange", JIS X 0208:1997? draft.
\1f
-File: tm-en.info, Node: JIS X0212, Next: koi8-r, Prev: JIS X0208, Up: Glossary
+File: tm-en.info, Node: JIS X0212, Next: koi8-r, Prev: JIS X0208, Up: Glossary
JIS X0212-1990
--------------
-A 94x94 character set (*Note 94x94 character set::) for Japanese as
+ A 94x94-character set (*Note 94x94-character set::) for Japanese as
supplement to JIS X0208 (*Note JIS X0208::). It is a standard of Japan.
-Final byte of ISO 2022 (*Note ISO 2022::) is 04/04 (`D').
-
-
+ Final byte of ISO 2022 (*Note ISO 2022::) is 04/04 (`D').
\1f
-File: tm-en.info, Node: koi8-r, Next: KS C5601, Prev: JIS X0212, Up: Glossary
+File: tm-en.info, Node: koi8-r, Next: KS C5601, Prev: JIS X0212, Up: Glossary
koi8-r
------
-A MIME charset (*Note MIME charset::) for Cyrillic script for Russian or
-other languages.
+ A MIME charset (*Note MIME charset::) for Cyrillic script for
+Russian or other languages.
-It is a 1 byte 8bit (*Note 8bit::) coded character set (*Note coded
+ It is a 1 byte 8bit (*Note 8bit::) coded character set (*Note coded
character set::), not based on ISO 2022 (*Note ISO 2022::). It is a
de-fact standard.
-It is defined in RFC 1489.
-
-
-[RFC 1489] A. Chernov, "Registration of a Cyrillic Character Set",
- July 1993.
-
-
+ It is defined in RFC 1489.
+[RFC 1489]
+ A. Chernov, "Registration of a Cyrillic Character Set", July 1993.
\1f
-File: tm-en.info, Node: KS C5601, Next: media type, Prev: koi8-r, Up: Glossary
+File: tm-en.info, Node: KS C5601, Next: media type, Prev: koi8-r, Up: Glossary
KS C5601-1987
-------------
-A 94x94-character set (*Note 94x94-character set::) for Korean language
-(Hangul script). Korean Standard. Final byte of ISO 2022 (*Note ISO
-2022::) is 04/03 (`C').
-
-
-[KS C5601] Korea Industrial Standards Association, "Code for
- Information Interchange (Hangul and Hanja)", KS C 5601:1987.
-
-
+ A 94x94-character set (*Note 94x94-character set::) for Korean
+language (Hangul script). Korean Standard. Final byte of ISO 2022
+(*Note ISO 2022::) is 04/03 (`C').
+[KS C5601]
+ Korea Industrial Standards Association, "Code for Information
+ Interchange (Hangul and Hanja)", KS C 5601:1987.
\1f
-File: tm-en.info, Node: media type, Next: message, Prev: KS C5601, Up: Glossary
+File: tm-en.info, Node: media type, Next: message, Prev: KS C5601, Up: Glossary
media type
----------
-*media type* specifies the nature of the data
-in the body of MIME (*Note MIME::) entity (*Note entity::). It consists of
-*type* and *subtype*. It is
-defined in RFC 2046 (*Note RFC 2046::).
+ *media type* specifies the nature of the data in the body of MIME
+(*Note MIME::) entity (*Note entity::). It consists of *type* and
+*subtype*. It is defined in RFC 2046 (*Note RFC 2046::).
-Currently there are following types:
+ Currently there are following types:
* *text*
+
* *image*
+
* *audio*
+
* *video*
+
* *application*
+
* *multipart* (*Note multipart::)
- * *message*
+ * *message*
-And there are various subtypes, for example, application/octet-stream,
-audio/basic, image/jpeg, multipart/mixed (*Note multipart/mixed::),
-text/plain (*Note text/plain::), video/mpeg...
+ And there are various subtypes, for example,
+application/octet-stream, audio/basic, image/jpeg, multipart/mixed
+(*Note multipart/mixed::), text/plain (*Note text/plain::),
+video/mpeg...
-You can refer registered media types at MEDIA TYPES
+ You can refer registered media types at MEDIA TYPES
(ftp://ftp.isi.edu/in-notes/iana/assignments/media-types).
-In addition, you can use private type or subtype using
-*x-token*, which as the prefix `x-'. However you
-can not use them in public.
-
-(cf. *Note Content-Type field::)
-
-
+ In addition, you can use private type or subtype using *x-token*,
+which as the prefix `x-'. However you can not use them in public.
+ (cf. *Note Content-Type field::)
\1f
-File: tm-en.info, Node: message, Next: message/rfc822, Prev: media type, Up: Glossary
+File: tm-en.info, Node: message, Next: message/rfc822, Prev: media type, Up: Glossary
message
-------
-In this document, it means mail defined in RFC 822 (*Note RFC 822::) and
-news message defined in RFC 1036 (*Note RFC 1036::).
-
-
+ In this document, it means mail defined in RFC 822 (*Note RFC 822::)
+and news message defined in RFC 1036 (*Note RFC 1036::).
\1f
-File: tm-en.info, Node: message/rfc822, Next: method, Prev: message, Up: Glossary
+File: tm-en.info, Node: message/rfc822, Next: method, Prev: message, Up: Glossary
message/rfc822
--------------
-*message/rfc822* indicates that the body
-contains an encapsulated message, with the syntax of an RFC 822 (*Note
-RFC 822::) message. It is the replacement of traditional RFC 934 (*Note
-RFC 934::) encapsulation. It is defined in RFC 2046 (*Note RFC 2046::).
-
-
+ *message/rfc822* indicates that the body contains an encapsulated
+message, with the syntax of an RFC 822 (*Note RFC 822::) message. It is
+the replacement of traditional RFC 934 (*Note RFC 934::) encapsulation.
+It is defined in RFC 2046 (*Note RFC 2046::).
\1f
-File: tm-en.info, Node: method, Next: MIME, Prev: message/rfc822, Up: Glossary
+File: tm-en.info, Node: method, Next: MIME, Prev: message/rfc822, Up: Glossary
method
------
-Application program of tm-view to process for specified media type
+ Application program of tm-view to process for specified media type
(*Note media type::) when user plays an entity.
-There are two kinds of methods, *internal method* and *external method*.
-Internal method is written by Emacs Lisp. External method is written by
-C or script languages and called by asynchronous process call.
-
-(cf. *Note (tm-view-en)method::)
-
-
+ There are two kinds of methods, *internal method* and *external
+method*. Internal method is written by Emacs Lisp. External method is
+written by C or script languages and called by asynchronous process
+call.
+ (cf. *Note (tm-view-en)method::)
\1f
-File: tm-en.info, Node: MIME, Next: MIME charset, Prev: method, Up: Glossary
+File: tm-en.info, Node: MIME, Next: MIME charset, Prev: method, Up: Glossary
MIME
----
-MIME stands for *Multipurpose Internet Mail Extensions*, it is an
+ MIME stands for *Multipurpose Internet Mail Extensions*, it is an
extension for RFC 822 (*Note RFC 822::).
-According to RFC 2045:
+ According to RFC 2045:
-STD 11, RFC 822, defines a message representation protocol specifying
+ STD 11, RFC 822, defines a message representation protocol specifying
considerable detail about US-ASCII message headers, and leaves the
message content, or message body, as flat US-ASCII text. This set of
documents, collectively called the Multipurpose Internet Mail
Extensions, or MIME, redefines the format of messages to allow for
1. textual message bodies in character sets other than US-ASCII,
+
2. an extensible set of different formats for non-textual message
bodies,
+
3. multi-part message bodies, and
- 4. textual header information in character sets other than US-ASCII.
+ 4. textual header information in character sets other than US-ASCII.
-It is defined in RFC 2045 (*Note RFC 2045::), RFC 2046 (*Note RFC
+ It is defined in RFC 2045 (*Note RFC 2045::), RFC 2046 (*Note RFC
2046::), RFC 2047 (*Note encoded-word::), RFC 2048 (*Note RFC 2048::)
and RFC 2049 (*Note RFC 2049::).
-
-
\1f
-File: tm-en.info, Node: MIME charset, Next: MTA, Prev: MIME, Up: Glossary
+File: tm-en.info, Node: MIME charset, Next: MTA, Prev: MIME, Up: Glossary
MIME charset
------------
-Coded character set (*Note Coded character set::) used in Content-Type
-field (*Note Content-Type field::) or charset parameter of encoded-word
-(*Note encoded-word::).
-
-It is defined in RFC 2045 (*Note RFC 2045::).
-
-iso-2022-jp (*Note iso-2022-jp::) or euc-kr (*Note euc-kr::) are kinds
-of it. (In this document, MIME charsets are written by small letters to
-distinguish graphic character set (*Note graphic character set::). For
-example, ISO 8859-1 is a graphic character set, and iso-8859-1 is a MIME
-charset)
+ Coded character set (*Note coded character set::) used in
+Content-Type field (*Note Content-Type field::) or charset parameter of
+encoded-word (*Note encoded-word::).
+ It is defined in RFC 2045 (*Note RFC 2045::).
+ iso-2022-jp (*Note iso-2022-jp::) or euc-kr (*Note euc-kr::) are
+kinds of it. (In this document, MIME charsets are written by small
+letters to distinguish graphic character set (*Note graphic character
+set::). For example, ISO 8859-1 is a graphic character set, and
+iso-8859-1 is a MIME charset)
\1f
-File: tm-en.info, Node: MTA, Next: MUA, Prev: MIME charset, Up: Glossary
+File: tm-en.info, Node: MTA, Next: MUA, Prev: MIME charset, Up: Glossary
MTA
---
-*Message Transfer Agent*. It
-means mail transfer programs (ex. sendmail) and news servers.
-
-(cf. *Note MUA::)
-
-
+ *Message Transfer Agent*. It means mail transfer programs (ex.
+sendmail) and news servers.
+ (cf. *Note MUA::)
\1f
-File: tm-en.info, Node: MUA, Next: MULE, Prev: MTA, Up: Glossary
+File: tm-en.info, Node: MUA, Next: MULE, Prev: MTA, Up: Glossary
MUA
---
-*Message User Agent*. It means mail
-readers and news readers.
-
-(cf. *Note MTA::)
-
-
+ *Message User Agent*. It means mail readers and news readers.
+ (cf. *Note MTA::)
\1f
-File: tm-en.info, Node: MULE, Next: multipart, Prev: MUA, Up: Glossary
+File: tm-en.info, Node: MULE, Next: multipart, Prev: MUA, Up: Glossary
MULE
----
-Multilingual extension of GNU Emacs (*Note Emacs::) by HANDA Ken'ichi et
-al.
-
+ Multilingual extension of GNU Emacs (*Note Emacs::) by HANDA
+Ken'ichi et al.
-[MULE] Nishikimi M., Handa K. and Tomura S., "Mule: MULtilingual
+[MULE]
+ Nishikimi M., Handa K. and Tomura S., "Mule: MULtilingual
Enhancement to GNU Emacs", Proc. of INET'93, August, 1993.
-Now, FSF and HANDA Ken'ichi et al. are working to merge MULE feature
+ Now, FSF and HANDA Ken'ichi et al. are working to merge MULE feature
into Emacs, there is alpha version of mule merged emacs
(ftp://etlport.etl.go.jp/pub/mule/mule-19.33-delta.taz).
-In addition, there is XEmacs with mule feature.
+ In addition, there is XEmacs with mule feature.
-So now, there are 3 kinds of mule variants.
+ So now, there are 3 kinds of mule variants.
-In this document, *mule* means any mule variants,
-*MULE* means original MULE (..2.3),
-*Emacs/mule* means mule merged Emacs,
+ In this document, *mule* means any mule variants, *MULE* means
+original MULE (..2.3), *Emacs/mule* means mule merged Emacs,
*XEmacs/mule* means XEmacs with mule feature.
-
-
\1f
-File: tm-en.info, Node: multipart, Next: multipart/alternative, Prev: MULE, Up: Glossary
+File: tm-en.info, Node: multipart, Next: multipart/alternative, Prev: MULE, Up: Glossary
Multipart
---------
-*multipart* means media type (*Note media type::)
-to insert multiple entities (*Note entities::) in a single body. Or it
-also indicates a message consists of multiple entities.
+ *multipart* means media type (*Note media type::) to insert multiple
+entities (*Note entity::) in a single body. Or it also indicates a
+message consists of multiple entities.
-There are following subtypes registered in RFC 2046 (*Note RFC 2046::):
+ There are following subtypes registered in RFC 2046 (*Note RFC
+2046::):
* multipart/mixed (*Note multipart/mixed::)
+
* multipart/alternative (*Note multipart/alternative::)
+
* multipart/digest (*Note multipart/digest::)
+
* multipart/parallel (*Note multipart/parallel::)
and registered in RFC 1847 (*Note Security multipart::):
* multipart/signed (*Note multipart/signed::)
- * multipart/encrypted (*Note multipart/encrypted::)
-
-
+ * multipart/encrypted (*Note multipart/encrypted::)
\1f
-File: tm-en.info, Node: multipart/alternative, Next: multipart/digest, Prev: multipart, Up: Glossary
+File: tm-en.info, Node: multipart/alternative, Next: multipart/digest, Prev: multipart, Up: Glossary
multipart/alternative
---------------------
-*multipart/digest* is one of multipart
-(*Note multipart::) media types. This type is syntactically identical
-to multipart/mixed (*Note multipart/mixed::), but the semantics are
-different. In particular, each of the body parts is an "alternative"
-version of the same information.
-
-(cf. *Note RFC 2046::)
-
-
+ *multipart/digest* is one of multipart (*Note multipart::) media
+types. This type is syntactically identical to multipart/mixed (*Note
+multipart/mixed::), but the semantics are different. In particular,
+each of the body parts is an "alternative" version of the same
+information.
+ (cf. *Note RFC 2046::)
\1f
-File: tm-en.info, Node: multipart/digest, Next: multipart/encrypted, Prev: multipart/alternative, Up: Glossary
+File: tm-en.info, Node: multipart/digest, Next: multipart/encrypted, Prev: multipart/alternative, Up: Glossary
multipart/digest
----------------
-*multipart/digest* is one of multipart
-(*Note multipart::) media types. This type is syntactically identical
-to multipart/mixed (*Note 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 (*Note text/plain::) to
-message/rfc822 (*Note message/rfc822::).
-
-This is the replacement of traditional RFC 1153 (*Note RFC 1153::) based
-encapsulation (*Note encapsulation::).
-
-(cf. *Note RFC 2046::)
-
+ *multipart/digest* is one of multipart (*Note multipart::) media
+types. This type is syntactically identical to multipart/mixed (*Note
+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 (*Note text/plain::) to message/rfc822 (*Note
+message/rfc822::).
+ This is the replacement of traditional RFC 1153 (*Note RFC 1153::)
+based encapsulation (*Note encapsulation::).
+ (cf. *Note RFC 2046::)
\1f
-File: tm-en.info, Node: multipart/encrypted, Next: multipart/mixed, Prev: multipart/digest, Up: Glossary
+File: tm-en.info, Node: multipart/encrypted, Next: multipart/mixed, Prev: multipart/digest, Up: Glossary
multipart/encrypted
-------------------
-It is a Security multipart (*Note Security multipart::) defined in RFC
-1847, used to represent encrypted message.
-
-(cf. *Note PGP/MIME::)
-
-
+ It is a Security multipart (*Note Security multipart::) defined in
+RFC 1847, used to represent encrypted message.
+ (cf. *Note PGP/MIME::)
\1f
-File: tm-en.info, Node: multipart/mixed, Next: multipart/parallel, Prev: multipart/encrypted, Up: Glossary
+File: tm-en.info, Node: multipart/mixed, Next: multipart/parallel, Prev: multipart/encrypted, Up: Glossary
multipart/mixed
---------------
-Primary and default subtype of multipart (*Note multipart::), it is used
-when the body parts are independent and need to be bundled in a
+ Primary and default subtype of multipart (*Note multipart::), it is
+used when the body parts are independent and need to be bundled in a
particular order.
-(cf. *Note RFC 2046::)
-
-
-
+ (cf. *Note RFC 2046::)
\1f
-File: tm-en.info, Node: multipart/parallel, Next: multipart/signed, Prev: multipart/mixed, Up: Glossary
+File: tm-en.info, Node: multipart/parallel, Next: multipart/signed, Prev: multipart/mixed, Up: Glossary
multipart/parallel
------------------
-*multipart/parallel* is a subtype of
-multipart (*Note multipart::). This type is syntactically identical to
-multipart/mixed (*Note multipart/mixed::), but the semantics are
-different. In particular, in a parallel entity, the order of body parts
-is not significant.
-
-(cf. *Note RFC 2046::)
-
-
+ *multipart/parallel* is a subtype of multipart (*Note multipart::).
+This type is syntactically identical to multipart/mixed (*Note
+multipart/mixed::), but the semantics are different. In particular, in
+a parallel entity, the order of body parts is not significant.
+ (cf. *Note RFC 2046::)
\1f
-File: tm-en.info, Node: multipart/signed, Next: PGP, Prev: multipart/parallel, Up: Glossary
+File: tm-en.info, Node: multipart/signed, Next: PGP, Prev: multipart/parallel, Up: Glossary
multipart/signed
----------------
-It is a Security multipart (*Note Security multipart::) defined in RFC
-1847, used to represent signed message.
-
-(cf. *Note PGP/MIME::)
-
-
+ It is a Security multipart (*Note Security multipart::) defined in
+RFC 1847, used to represent signed message.
+ (cf. *Note PGP/MIME::)
\1f
-File: tm-en.info, Node: PGP, Next: PGP-kazu, Prev: multipart/signed, Up: Glossary
+File: tm-en.info, Node: PGP, Next: PGP-kazu, Prev: multipart/signed, Up: Glossary
PGP
---
-A public key encryption program by Phil Zimmermann. It provides
+ A public key encryption program by Phil Zimmermann. It provides
encryption and signature for message (*Note message::). PGP stands for
*Pretty Good Privacy*.
-Traditional PGP uses RFC 934 (*Note RFC 934::) encapsulation (*Note
-encapsulation::). It is conflict with MIME (*Note MIME::). So PGP/MIME
-(*Note PGP/MIME::) is defined. On the other hand, PGP-kazu (*Note
-PGP-kazu::) was proposed to use PGP encapsulation in MIME. But it is
-obsoleted.
-
-
-[PGP: RFC 1991] D. Atkins, W. Stallings and P. Zimmermann, "PGP
- Message Exchange Formats", August 1996, Informational.
-
-
-
+ Traditional PGP uses RFC 934 (*Note RFC 934::) encapsulation (*Note
+encapsulation::). It is conflict with MIME (*Note MIME::). So
+PGP/MIME (*Note PGP/MIME::) is defined. On the other hand, PGP-kazu
+(*Note PGP-kazu::) was proposed to use PGP encapsulation in MIME. But
+it is obsoleted.
+[PGP: RFC 1991]
+ D. Atkins, W. Stallings and P. Zimmermann, "PGP Message Exchange
+ Formats", August 1996, Informational.
\1f
-File: tm-en.info, Node: PGP-kazu, Next: PGP/MIME, Prev: PGP, Up: Glossary
+File: tm-en.info, Node: PGP-kazu, Next: PGP/MIME, Prev: PGP, Up: Glossary
PGP-kazu
--------
-In this document, *PGP-kazu* means a method to use traditional PGP
+ In this document, *PGP-kazu* means a method to use traditional PGP
encapsulation in MIME (*Note MIME::), proposed by YAMAMOTO Kazuhiko.
-PGP-kazu defines a media type (*Note media type::),
+ PGP-kazu defines a media type (*Note media type::),
*application/pgp*.
-In application/pgp entity, PGP encapsulation (*Note encapsulation::) is
-used. PGP encapsulation conflicts with MIME, so it requires
+ In application/pgp entity, PGP encapsulation (*Note encapsulation::)
+is used. PGP encapsulation conflicts with MIME, so it requires
PGP-processing to read as MIME message.
-It was obsoleted, so you should use PGP/MIME (*Note PGP/MIME::).
+ It was obsoleted, so you should use PGP/MIME (*Note PGP/MIME::).
However if you want to use traditional PGP message, it might be
available.
-
-
\1f
-File: tm-en.info, Node: PGP/MIME, Next: Quoted-Printable, Prev: PGP-kazu, Up: Glossary
+File: tm-en.info, Node: PGP/MIME, Next: Quoted-Printable, Prev: PGP-kazu, Up: Glossary
PGP/MIME
--------
-PGP (*Note PGP::) and MIME (*Note MIME::) integration proposed by
+ PGP (*Note PGP::) and MIME (*Note MIME::) integration proposed by
Michael Elkins.
-It is based on RFC 1847 (*Note Security multipart::), so it is
+ It is based on RFC 1847 (*Note Security multipart::), so it is
harmonious with MIME, but it is not compatible with traditional PGP
encapsulation. However MIME MUA can read PGP/MIME signed message even
if it does not support PGP/MIME.
-PGP/MIME (*Note PGP/MIME::) will be standard of PGP message.
-
-
-[PGP/MIME: RFC 2015] M. Elkins, "MIME Security with Pretty Good
- Privacy (PGP)", October 1996, Standards Track.
-
-
+ PGP/MIME (*Note PGP/MIME::) will be standard of PGP message.
+[PGP/MIME: RFC 2015]
+ M. Elkins, "MIME Security with Pretty Good Privacy (PGP)", October
+ 1996, Standards Track.
\1f
-File: tm-en.info, Node: Quoted-Printable, Next: RFC 821, Prev: PGP/MIME, Up: Glossary
+File: tm-en.info, Node: Quoted-Printable, Next: RFC 821, Prev: PGP/MIME, Up: Glossary
Quoted-Printable
----------------
-*Quoted-Printable* is a transfer
-encoding method of MIME (*Note MIME::) defined in RFC 2045 (*Note RFC
-2045::).
-
-If the data being encoded are mostly US-ASCII text, the encoded form of
-the data remains largely recognizable by humans.
-
-(cf. *Note Base64::)
-
+ *Quoted-Printable* is a transfer encoding method of MIME (*Note
+MIME::) defined in RFC 2045 (*Note RFC 2045::).
+ If the data being encoded are mostly US-ASCII text, the encoded form
+of the data remains largely recognizable by humans.
+ (cf. *Note Base64::)
\1f
-File: tm-en.info, Node: RFC 821, Next: RFC 822, Prev: Quoted-Printable, Up: Glossary
+File: tm-en.info, Node: RFC 821, Next: RFC 822, Prev: Quoted-Printable, Up: Glossary
RFC 821
-------
-
-[SMTP: RFC 821] J. Postel, "Simple Mail Transfer Protocol", August
- 1982, STD 10.
-
-
-
+[SMTP: RFC 821]
+ J. Postel, "Simple Mail Transfer Protocol", August 1982, STD 10.
\1f
-File: tm-en.info, Node: RFC 822, Next: RFC 934, Prev: RFC 821, Up: Glossary
+File: tm-en.info, Node: RFC 822, Next: RFC 934, Prev: RFC 821, Up: Glossary
RFC 822
-------
-A RFC defines format of Internet mail message, mainly *message header*.
+ A RFC defines format of Internet mail message, mainly *message
+header*.
*[Memo]*
+ news message is based on RFC 822, so *Internet message* may be
+ more suitable than *Internet mail* .
- news message is based on RFC 822, so *Internet message* may be more suitable than
- *Internet mail* .
-
-
-
-[RFC 822] D. Crocker, "Standard for the Format of ARPA Internet
- Text Messages", August 1982, STD 11.
-
-
-
+[RFC 822]
+ D. Crocker, "Standard for the Format of ARPA Internet Text
+ Messages", August 1982, STD 11.
\1f
-File: tm-en.info, Node: RFC 934, Next: RFC 1036, Prev: RFC 822, Up: Glossary
+File: tm-en.info, Node: RFC 934, Next: RFC 1036, Prev: RFC 822, Up: Glossary
RFC 934
-------
-A RFC defines an *encapsulation* (*Note encapsulation::) method for
+ A RFC defines an *encapsulation* (*Note encapsulation::) method for
Internet mail (*Note RFC 822::).
-It conflicts with MIME (*Note MIME::), so you should use message/rfc822
-(*Note message/rfc822::).
-
-
-[RFC 934] Marshall T. Rose and Einar A. Stefferud, "Proposed
- Standard for Message Encapsulation", January 1985.
-
-
+ It conflicts with MIME (*Note MIME::), so you should use
+message/rfc822 (*Note message/rfc822::).
+[RFC 934]
+ Marshall T. Rose and Einar A. Stefferud, "Proposed Standard for
+ Message Encapsulation", January 1985.
\1f
-File: tm-en.info, Node: RFC 1036, Next: RFC 1153, Prev: RFC 934, Up: Glossary
+File: tm-en.info, Node: RFC 1036, Next: RFC 1153, Prev: RFC 934, Up: Glossary
RFC 1036
--------
-A RFC defines format of USENET message. It is a subset of RFC 822
+ A RFC defines format of USENET message. It is a subset of RFC 822
(*Note RFC 822::). It is not Internet standard, but a lot of netnews
excepting Usenet uses it.
-
-[USENET: RFC 1036] M. Horton and R. Adams, "Standard for
- Interchange of USENET Messages", December 1987, (obsolete RFC 850).
-
-
-
+[USENET: RFC 1036]
+ M. Horton and R. Adams, "Standard for Interchange of USENET
+ Messages", December 1987, (obsolete RFC 850).
\1f
-File: tm-en.info, Node: RFC 1153, Next: RFC 1557, Prev: RFC 1036, Up: Glossary
+File: tm-en.info, Node: RFC 1153, Next: RFC 1557, Prev: RFC 1036, Up: Glossary
RFC 1153
--------
-
-[RFC 1153] F. Wancho, "Digest Message Format", April 1990.
-
-
-
+[RFC 1153]
+ F. Wancho, "Digest Message Format", April 1990.
\1f
-File: tm-en.info, Node: RFC 1557, Next: RFC 1922, Prev: RFC 1153, Up: Glossary
+File: tm-en.info, Node: RFC 1557, Next: RFC 1922, Prev: RFC 1153, Up: Glossary
RFC 1557
--------
-A RFC defines MIME charset (*Note MIME charset::)s for Korean, euc-kr
+ A RFC defines MIME charset (*Note MIME charset::)s for Korean, euc-kr
(*Note euc-kr::) and iso-2022-kr (*Note iso-2022-kr::).
-
-[RFC 1557] U. Choi, K. Chon and H. Park, "Korean Character Encoding
- for Internet Messages", December 1993, Informational.
-
-
-
+[RFC 1557]
+ U. Choi, K. Chon and H. Park, "Korean Character Encoding for
+ Internet Messages", December 1993, Informational.
\1f
-File: tm-en.info, Node: RFC 1922, Next: RFC 2045, Prev: RFC 1557, Up: Glossary
+File: tm-en.info, Node: RFC 1922, Next: RFC 2045, Prev: RFC 1557, Up: Glossary
RFC 1922
--------
-A RFC defines MIME charset (*Note MIME charset::)s for Chinese,
+ A RFC defines MIME charset (*Note MIME charset::)s for Chinese,
iso-2022-cn (*Note iso-2022-cn::), iso-2022-cn-ext (*Note
iso-2022-cn-ext::), cn-gb (*Note cn-gb::), cn-big5 (*Note cn-big5::),
etc.
-In addition, it defines additional parameters of Content-Type field
-(*Note Content-Type field::) field,
-*charset-edition* and
+ In addition, it defines additional parameters of Content-Type field
+(*Note Content-Type field::) field, *charset-edition* and
*charset-extension*.
-
-[RFC 1922] Zhu, HF., Hu, DY., Wang, ZG., Kao, TC., Chang, WCH. and
- Crispin, M., "Chinese Character Encoding for Internet Messages",
- March 1996, Informational.
-
-
-
+[RFC 1922]
+ Zhu, HF., Hu, DY., Wang, ZG., Kao, TC., Chang, WCH. and Crispin,
+ M., "Chinese Character Encoding for Internet Messages", March 1996,
+ Informational.
\1f
-File: tm-en.info, Node: RFC 2045, Next: RFC 2046, Prev: RFC 1922, Up: Glossary
+File: tm-en.info, Node: RFC 2045, Next: RFC 2046, Prev: RFC 1922, Up: Glossary
RFC 2045
--------
-
-[RFC 2045] N. Freed and N. Borenstein, "Multipurpose Internet Mail
- Extensions (MIME) Part One: Format of Internet Message Bodies",
- November 1996, Standards Track (obsolete RFC 1521, 1522, 1590).
-
-
-
+[RFC 2045]
+ N. Freed and N. Borenstein, "Multipurpose Internet Mail Extensions
+ (MIME) Part One: Format of Internet Message Bodies", November 1996,
+ Standards Track (obsolete RFC 1521, 1522, 1590).
\1f
-File: tm-en.info, Node: RFC 2046, Next: RFC 2048, Prev: RFC 2045, Up: Glossary
+File: tm-en.info, Node: RFC 2046, Next: RFC 2048, Prev: RFC 2045, Up: Glossary
RFC 2046
--------
-
-[RFC 2046] N. Freed and N. Borenstein, "Multipurpose Internet Mail
- Extensions (MIME) Part Two: Media Types", November 1996, Standards
- Track (obsolete RFC 1521, 1522, 1590).
-
-
-
+[RFC 2046]
+ N. Freed and N. Borenstein, "Multipurpose Internet Mail Extensions
+ (MIME) Part Two: Media Types", November 1996, Standards Track
+ (obsolete RFC 1521, 1522, 1590).
\1f
-File: tm-en.info, Node: RFC 2048, Next: RFC 2049, Prev: RFC 2046, Up: Glossary
+File: tm-en.info, Node: RFC 2048, Next: RFC 2049, Prev: RFC 2046, Up: Glossary
RFC 2048
--------
-
-[RFC 2048] N. Freed, J. Klensin and J. Postel, "Multipurpose
- Internet Mail Extensions (MIME) Part Four: Registration
- Procedures", November 1996, Standards Track (obsolete RFC 1521,
- 1522, 1590).
-
-
-
+[RFC 2048]
+ N. Freed, J. Klensin and J. Postel, "Multipurpose Internet Mail
+ Extensions (MIME) Part Four: Registration Procedures", November
+ 1996, Standards Track (obsolete RFC 1521, 1522, 1590).
\1f
-File: tm-en.info, Node: RFC 2049, Next: plain text, Prev: RFC 2048, Up: Glossary
+File: tm-en.info, Node: RFC 2049, Next: plain text, Prev: RFC 2048, Up: Glossary
RFC 2049
--------
-
-[RFC 2049] N. Freed and N. Borenstein, "Multipurpose Internet Mail
- Extensions (MIME) Part Five: Conformance Criteria and Examples",
- November 1996, Standards Track (obsolete RFC 1521, 1522, 1590).
-
-
-
+[RFC 2049]
+ N. Freed and N. Borenstein, "Multipurpose Internet Mail Extensions
+ (MIME) Part Five: Conformance Criteria and Examples", November
+ 1996, Standards Track (obsolete RFC 1521, 1522, 1590).
\1f
-File: tm-en.info, Node: plain text, Next: Security multipart, Prev: RFC 2049, Up: Glossary
+File: tm-en.info, Node: plain text, Next: Security multipart, Prev: RFC 2049, Up: Glossary
plain text
----------
-A textual data represented by only coded character set (*Note coded
+ A textual data represented by only coded character set (*Note coded
character set::). It does not have information about font or
typesetting. (cf. *Note text/plain::)
-
-
-
\1f
-File: tm-en.info, Node: Security multipart, Next: text/enriched, Prev: plain text, Up: Glossary
+File: tm-en.info, Node: Security multipart, Next: text/enriched, Prev: plain text, Up: Glossary
Security multipart
------------------
-A format to represent signed/encrypted message in MIME (*Note MIME::).
-
-It defines two multipart media types,
-*multipart/signed*
-(*Note multipart/signed::) and
-*multipart/encrypted*
-(*Note multipart/encrypted::).
-
-MOSS and PGP/MIME (*Note PGP/MIME::) are based on it.
-
-
-[Security multipart: RFC 1847] James Galvin, Gale Murphy, Steve
- Crocker and Ned Freed, "Security Multiparts for MIME:
- Multipart/Signed and Multipart/Encrypted", October 1995, Standards
- Track.
+ A format to represent signed/encrypted message in MIME (*Note
+MIME::).
+ It defines two multipart media types, *multipart/signed* (*Note
+multipart/signed::) and *multipart/encrypted* (*Note
+multipart/encrypted::).
+ MOSS and PGP/MIME (*Note PGP/MIME::) are based on it.
+[Security multipart: RFC 1847]
+ James Galvin, Gale Murphy, Steve Crocker and Ned Freed, "Security
+ Multiparts for MIME: Multipart/Signed and Multipart/Encrypted",
+ October 1995, Standards Track.
\1f
-File: tm-en.info, Node: text/enriched, Next: text/plain, Prev: Security multipart, Up: Glossary
+File: tm-en.info, Node: text/enriched, Next: text/plain, Prev: Security multipart, Up: Glossary
text/enriched
-------------
-
-[text/enriched: RFC 1896] P. Resnick and A. Walker, "The
- text/enriched MIME Content-type", February 1996, (obsolete RFC
- 1563).
-
-
-
+[text/enriched: RFC 1896]
+ P. Resnick and A. Walker, "The text/enriched MIME Content-type",
+ February 1996, (obsolete RFC 1563).
\1f
-File: tm-en.info, Node: text/plain, Next: tm-kernel, Prev: text/enriched, Up: Glossary
+File: tm-en.info, Node: text/plain, Next: tm-kernel, Prev: text/enriched, Up: Glossary
text/plain
----------
-*text/plain* is a media type (*Note media type::) for plain text (*Note plain text::), defined in RFC 2046 (*Note RFC 2046::).
+ *text/plain* is a media type (*Note media type::) for plain text
+(*Note plain text::), defined in RFC 2046 (*Note RFC 2046::).
-The default media type of "text/plain; charset=us-ascii" for Internet
+ The default media type of "text/plain; charset=us-ascii" for Internet
mail describes existing Internet practice. That is, it is the type of
body defined by RFC 822 (*Note RFC 822::).
-(cf. *Note MIME charset::) (cf. *Note us-ascii::)
-
-
-
+ (cf. *Note MIME charset::) (cf. *Note us-ascii::)
\1f
-File: tm-en.info, Node: tm-kernel, Next: tm-MUA, Prev: text/plain, Up: Glossary
+File: tm-en.info, Node: tm-kernel, Next: tm-MUA, Prev: text/plain, Up: Glossary
tm-kernel, tm
-------------
-A libraries to provide user interface about MIME (*Note MIME::) for
+ A libraries to provide user interface about MIME (*Note MIME::) for
emacs. tm stands for `tools for MIME'.
*[Unimportant notice(^-^;]*
-
* tm may not stand for "tiny-mime"(^-^;
-
- * tm may not stand for initial of an author (^-^;
-
- * "Tools for MIME" may be strained (^-^;
-
+ * tm may not stand for initial of an author (^-^;
+ * "Tools for MIME" may be strained (^-^;
\1f
-File: tm-en.info, Node: tm-MUA, Next: us-ascii, Prev: tm-kernel, Up: Glossary
+File: tm-en.info, Node: tm-MUA, Next: us-ascii, Prev: tm-kernel, Up: Glossary
tm-MUA
------
-MUA (*Note MUA::) or MUA extender using tm (*Note tm-kernel::).
+ MUA (*Note MUA::) or MUA extender using tm (*Note tm-kernel::).
+
+ *tm oomori package* has following extenders:
-*tm oomori package* has following extenders:
+ * *tm-mh-e* (*Note (tm-mh-e-en)::) for mh-e (*Note (mh-e)::)
- * *tm-mh-e* (*Note (tm-mh-e-en)::)
- for mh-e (*Note (mh-e)::)
* *tm-gnus* (*Note (tm-gnus_en)::) for GNUS
- * *gnus-mime* (*Note (gnus-mime-en)::) for Gnus
- * *tm-vm* (*Note (tm-vm_en)::) for VM
- * *tm-rmail* for RMAIL
+ * *gnus-mime* (*Note (gnus-mime-en)::) for Gnus
+ * *tm-vm* (*Note (tm-vm_en)::) for VM
+ * *tm-rmail* for RMAIL
\1f
-File: tm-en.info, Node: us-ascii, Prev: tm-MUA, Up: Glossary
+File: tm-en.info, Node: us-ascii, Prev: tm-MUA, Up: Glossary
us-ascii
--------
-A MIME charset (*Note MIME charset::) for primary Latin script mainly
+ A MIME charset (*Note MIME charset::) for primary Latin script mainly
written by English or other languages.
-It is a 7bit coded character set (*Note coded character set::) based on
-ISO 2022 (*Note ISO 2022::), it contains only ASCII (*Note ASCII::) and
-code extension (*Note code extension::) is not allowed.
-
-It is standard coded character set of Internet mail. If MIME charset is
-not specified, *us-ascii* is used as default.
-
-In addition, *ASCII* of RFC 822 (*Note RFC 822::) should be interpreted
-as us-ascii.
+ It is a 7bit coded character set (*Note coded character set::) based
+on ISO 2022 (*Note ISO 2022::), it contains only ASCII (*Note ASCII::)
+and code extension (*Note code extension::) is not allowed.
+ It is standard coded character set of Internet mail. If MIME
+charset is not specified, *us-ascii* is used as default.
+ In addition, *ASCII* of RFC 822 (*Note RFC 822::) should be
+interpreted as us-ascii.
\1f
-File: tm-en.info, Node: Setting, Next: Bug report, Prev: Introduction, Up: Top
+File: tm-en.info, Node: Setting, Next: Bug report, Prev: Introduction, Up: Top
Setting
*******
-In the tm package, two files, `mime-setup.el' and `tm-setup.el', are
+ In the tm package, two files, `mime-setup.el' and `tm-setup.el', are
provided to ease the setup.
-The `mime-setup.el' is used for the whole MIME related setup including
-MIME encoding using `tm-edit.el', while `tm-setup.el' is used to set up
-tm-MUA only.
-
+ The `mime-setup.el' is used for the whole MIME related setup
+including MIME encoding using `tm-edit.el', while `tm-setup.el' is used
+to set up tm-MUA only.
* Menu:
* setting for VM:: Setting for VM
* manual setting:: Setting up without loading provided setup files
-
\1f
-File: tm-en.info, Node: mime-setup, Next: tm-setup, Prev: Setting, Up: Setting
+File: tm-en.info, Node: mime-setup, Next: tm-setup, Prev: Setting, Up: Setting
Normal setting
==============
-If you want normal setting, please use *mime-setup*. For example,
+ If you want normal setting, please use *mime-setup*. For example,
please insert following into `~/.emacs':
(load "mime-setup")
-
-As `mime-setup.el' loads `tm-setup.el', you don't need to load
+ As `mime-setup.el' loads `tm-setup.el', you don't need to load
`tm-setup.el' when you use `mime-setup.el' (Description of old version
of Gnus FAQ is wrong!)
-
* Menu:
-* signature::
+* signature::
* Notice about GNUS:: Notices for GNUS
-
\1f
-File: tm-en.info, Node: signature, Next: Notice about GNUS, Prev: mime-setup, Up: mime-setup
+File: tm-en.info, Node: signature, Next: Notice about GNUS, Prev: mime-setup, Up: mime-setup
signature
---------
-You can set up the *automatic signature selection tool* using
+ You can set up the *automatic signature selection tool* using
`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 `signature.el' for more
-details).
+depending on how the message headers show, add lines like shown below
+to your .emacs (Refer to the reference manual of `signature.el' for
+more details).
(setq signature-file-alist
'((("Newsgroups" . "jokes") . "~/.signature-jokes")
(("To" . ("sim" "oku" "takuo")) . "~/.signature-formal")
))
-
-
- -- Variable: mime-setup-use-signature
-
+ - Variable: mime-setup-use-signature
If it is not `nil', `mime-setup.el' sets up for `signature.el'.
Its default value is `t'.
-
-
- -- Variable: mime-setup-signature-key-alist
-
+ - Variable: mime-setup-signature-key-alist
It defines key to bind signature inserting command for each
major-mode. Its default value is following:
((mail-mode . "\C-c\C-w"))
-
If you want to change, please rewrite it. For example:
(set-alist 'mime-setup-signature-key-alist
'news-reply-mode "\C-c\C-w")
-
-
- -- Variable: mime-setup-default-signature-key
-
+ - Variable: mime-setup-default-signature-key
If key to bind signature inserting command for a major-mode is not
found from `mime-setup-signature-key-alist', its value is used as
key. Its default value is `"\C-c\C-s"'.
-
-
-
\1f
-File: tm-en.info, Node: Notice about GNUS, Prev: signature, Up: mime-setup
+File: tm-en.info, Node: Notice about GNUS, Prev: signature, Up: mime-setup
Notices for GNUS
----------------
-When `mime-setup.el' sets up for `signature.el', it sets variable
+ When `mime-setup.el' sets up for `signature.el', it sets variable
`gnus-signature-file' to `nil'. Therefore GNUS does not insert
signature automatically when it is sending a message. Reason of this
setting is following:
-GNUS inserts signature after `tm-edit.el' composed as MIME message.
+ GNUS inserts signature after `tm-edit.el' composed as MIME message.
Therefore signature inserted by GNUS is not processed as a valid MIME
part. In particular, for multipart message, signature places in outside
of MIME part. So MIME MUA might not display it.
-Other notice is key bind. In historical reason, key bind to insert
+ Other notice is key bind. In historical reason, key bind to insert
signature is `C-c C-s' (like mh-e (*Note (mh-e)::)) instead of `C-c
C-w'. If you change to GNUS's default, please set following:
(set-alist 'mime-setup-signature-key-alist 'news-reply-mode "\C-c\C-w")
-
-
-
\1f
-File: tm-en.info, Node: tm-setup, Next: setting for VM, Prev: mime-setup, Up: Setting
+File: tm-en.info, Node: tm-setup, Next: setting for VM, Prev: mime-setup, Up: Setting
Setting not to use tm-edit
==========================
-*tm-setup* only sets up tm-MUA (*Note 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 `mime-setup.el'.
+ *tm-setup* only sets up tm-MUA (*Note 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 `mime-setup.el'.
-For example, please insert following into `~/.emacs':
+ For example, please insert following into `~/.emacs':
(load "tm-setup")
-
-
*[Memo]*
-
If you use `mime-setup.el', you you don't need to load
`tm-setup.el'.
-
-
-
\1f
-File: tm-en.info, Node: setting for VM, Next: manual setting, Prev: tm-setup, Up: Setting
+File: tm-en.info, Node: setting for VM, Next: manual setting, Prev: tm-setup, Up: Setting
Setting for VM
==============
-If you use *vm*, please insert following in `~/.vm':
+ If you use *vm*, please insert following in `~/.vm':
(require 'tm-vm)
-
-
*[Notice]*
-
If you use *BBDB*, please insert `(require 'tm-vm)' *after*
`(bbdb-insinuate-vm)'.
-
-
-
\1f
-File: tm-en.info, Node: manual setting, Prev: setting for VM, Up: Setting
+File: tm-en.info, Node: manual setting, Prev: setting for VM, Up: Setting
Setting up without loading provided setup files
===============================================
-You may find the valuable hints in `mime-setup.el' or `tm-setup.el' if
-you want to set up MIME environment without loading the tm-provided
+ You may find the valuable hints in `mime-setup.el' or `tm-setup.el'
+if you want to set up MIME environment without loading the tm-provided
setup files.
*[Memo]*
-
Current tm provides some convenient features to expect tm-edit, and
they can not use if `mime-setup.el' is not used. If you want to
set up original setting to use tm-edit, please declare following
(provide 'mime-setup)
-
-
-
\1f
-File: tm-en.info, Node: Bug report, Next: Concept Index, Prev: Setting, Up: Top
+File: tm-en.info, Node: Bug report, Next: Acknowledgments, Prev: Setting, Up: Top
How to report bug and about mailing list of tm
**********************************************
-If you write bug-reports and/or suggestions for improvement, please send
-them to the tm Mailing List:
+ If you write bug-reports and/or suggestions for improvement, please
+send them to the tm Mailing List:
* Japanese <bug-tm-ja@chamonix.jaist.ac.jp>
- * English <bug-tm-en@chamonix.jaist.ac.jp>
+ * English <bug-tm-en@chamonix.jaist.ac.jp>
-Notice that, we does not welcome bug reports about too old version.
+ Notice that, we does not welcome bug reports about too old version.
Bugs in old version might be fixed. So please try latest version at
first.
-You should write *good bug report*. If you write only "tm does not
+ You should write *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. *Note (emacs)Bugs::)
+In addition, if error occurs, to send backtrace is very important. (cf.
+*Note (emacs)Bugs::)
-Bug may not appear only your environment, but also in a lot of
+ 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
author directly, we must write a lot of mails. So please send mail to
address for tm bugs instead of author.
-Via the tm ML, you can report tm bugs, obtain the latest release of tm,
-and discuss future enhancements to tm. To join the tm ML, send e-mail
-to:
+ Via the tm ML, you can report tm bugs, obtain the latest release of
+tm, and discuss future enhancements to tm. To join the tm ML, send
+e-mail to:
* Japanese <tm-ja-admin@chamonix.jaist.ac.jp>
- * English <tm-en-admin@chamonix.jaist.ac.jp>
-Since the user registration is done manually, please write the mail body
-in human-recognizable language (^_^).
+ * English <tm-en-admin@chamonix.jaist.ac.jp>
+
+Since the user registration is done manually, please write the mail
+body in human-recognizable language (^_^).
+
+\1f
+File: tm-en.info, Node: Acknowledgments, Next: Concept Index, Prev: Bug report, Up: Top
+
+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.
+ I thank ENAMI Tsugutomo for work of `mime.el', which is an origin of
+`tm-ew-d.el' and `mel-b.el', and permission to rewrite for tm.
+ 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.
+
+ I thank UMEDA Masanobu for his work of `mime.el', which is the
+origin of tm-edit, and permission to rewrite his work as tm-edit.
+
+ I thank KOBAYASHI Shuhei for his work as a tm maintainer. In
+addition, he often points out or suggests about conformity with RFCs.
+
+ 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.
+
+ Last of all, I thank members of two tm mailing lists, Japanese and
+English version.
\1f
-File: tm-en.info, Node: Concept Index, Next: Variable Index, Prev: Bug report, Up: Top
+File: tm-en.info, Node: Concept Index, Next: Variable Index, Prev: Acknowledgments, Up: Top
Concept Index
*************
-
* Menu:
-* 7bit
-* 7bit: 7bit. 5.
-* 7bit (textual) string: 7bit. 12.
-* 8bit
-* 8bit: 8bit. 5.
-* 8bit (textual)
-* 94-character set: 94-character set. 5.
-* 94x94-character set: 94x94-character set. 5.
-* 96-character set: 96-character set. 5.
-* ANSI X3.4:1986: ASCII. 9.
-* application: media type. 21.
-* application/pgp: PGP-kazu. 9.
-* ASCII: ASCII. 5.
-* ASCII: ASCII. 9.
-* ASCII: us-ascii. 16.
-* audio: media type. 17.
-* automatic signature selection
-* Base64: Base64. 5.
-* BBDB: setting for VM. 14.
-* BIG5: cn-big5. 15.
-* binary: binary. 6.
-* charset-edition: RFC 1922. 12.
-* charset-extension: RFC 1922. 13.
-* CNS 11643:1992: CNS 11643. 35.
-* CNS 11643-1992: CNS 11643. 35.
-* Emacs/mule: MULE. 22.
-* encapsulation: RFC 934. 6.
-* euc-kr: euc-kr. 14.
-* Experimental: Content-Disposition. 8.
-* external method: method. 10.
-* FTP: FTP. 5.
-* GB 2312: GB 2312. 11.
-* GB 2312:1980: GB 2312. 11.
-* GB 8565.2: GB 8565.2. 8.
-* GB 8565.2:1988: GB 8565.2. 8.
-* gnus-mime: tm-MUA. 15.
-* good bug report: Bug report. 17.
-* image: media type. 15.
-* Informational: hz-gb2312. 15.
-* Informational: hz-gb2312. 20.
-* Informational: iso-2022-jp-2. 10.
-* Informational: iso-8859-7. 13.
-* Informational: PGP. 15.
-* Informational: RFC 1557. 8.
-* Informational: RFC 1922. 15.
-* internal method: method. 9.
-* Internet
-* Internet mail: RFC 822. 10.
-* ISO 2022: ISO 2022. 8.
-* ISO 646: ISO 646. 5.
-* ISO 8859-1: ISO 8859-1. 5.
-* ISO 8859-1:1987: ISO 8859-1. 5.
-* ISO 8859-2: ISO 8859-2. 5.
-* ISO 8859-2:1987: ISO 8859-2. 5.
-* ISO 8859-3: ISO 8859-3. 5.
-* ISO 8859-3:1988: ISO 8859-3. 5.
-* ISO 8859-4: ISO 8859-4. 5.
-* ISO 8859-4:1988: ISO 8859-4. 5.
-* ISO 8859-5: ISO 8859-5. 5.
-* ISO 8859-5:1988: ISO 8859-5. 5.
-* ISO 8859-6: ISO 8859-6. 5.
-* ISO 8859-6:1987: ISO 8859-6. 5.
-* ISO 8859-7: ISO 8859-7. 5.
-* ISO 8859-7:1987: ISO 8859-7. 5.
-* ISO 8859-8: ISO 8859-8. 5.
-* ISO 8859-8:1988: ISO 8859-8. 5.
-* ISO 8859-9: ISO 8859-9. 5.
-* ISO 8859-9:1990: ISO 8859-9. 5.
-* iso-2022-jp: iso-2022-jp. 19.
-* iso-2022-jp-2: iso-2022-jp-2. 10.
-* iso-8859-1: iso-8859-1. 5.
-* iso-8859-2: iso-8859-2. 5.
-* iso-8859-5: iso-8859-5. 5.
-* iso-8859-7: iso-8859-7. 13.
-* iso-8859-7: iso-8859-7. 5.
-* ISO/IEC 2022:1994: ISO 2022. 8.
-* ISO/IEC 646:1991: ISO 646. 5.
-* JIS X 0201-1976:: JIS X0201. 11.
-* JIS X0208:1983,1990: JIS X0208. 25.
-* JIS C6220-1976: JIS X0201. 10.
-* JIS C6226:1978: JIS X0208. 20.
-* JIS X 0208:1997? draft: JIS X0208. 34.
-* JIS X 0201:1997? draft: JIS X0201. 18.
-* JIS X0201-1976: JIS X0201. 11.
-* JIS X0201-1997?: JIS X0201. 18.
-* JIS X0208-1978: JIS X0208. 20.
-* JIS X0208-1983,1990: JIS X0208. 25.
-* JIS X0208-1997?: JIS X0208. 34.
-* KS C 5601:1987: KS C5601. 9.
-* KS C 5861:1992: euc-kr. 14.
-* KS C5601: KS C5601. 9.
-* media type: media type. 5.
-* message
-* message: media type. 25.
-* Message Transfer Agent: MTA. 5.
-* Message User Agent: MUA. 5.
-* message/rfc822: message/rfc822. 5.
-* mime-setup: mime-setup. 6.
-* MULE: MULE. 21.
-* mule: MULE. 21.
-* MULE: MULE. 8.
-* multipart: media type. 23.
-* multipart: multipart. 5.
-* multipart/digest: multipart/alternative. 5.
-* multipart/digest: multipart/digest. 5.
-* multipart/encrypted: Security multipart. 10.
-* multipart/parallel: multipart/parallel. 5.
-* multipart/signed: Security multipart. 8.
-* Multipurpose Internet Mail
-* pad: Base64. 11.
-* parameter: Content-Type field. 21.
-* PGP: PGP. 15.
-* PGP-kazu: PGP-kazu. 6.
-* PGP/MIME: PGP/MIME. 15.
-* Pretty Good Privacy: PGP. 7.
-* Quoted-Printable: Quoted-Printable. 5.
-* RFC 1036: RFC 1036. 9.
-* RFC 1153: RFC 1153. 5.
-* RFC 1468: iso-2022-jp. 19.
-* RFC 1489: koi8-r. 14.
-* RFC 1554: iso-2022-jp-2. 10.
-* RFC 1557: RFC 1557. 8.
-* RFC 1806: Content-Disposition. 8.
-* RFC 1842: hz-gb2312. 15.
-* RFC 1843: hz-gb2312. 20.
-* RFC 1847: Security multipart. 15.
-* RFC 1896: text/enriched. 5.
-* RFC 1922: RFC 1922. 15.
-* RFC 1947: iso-8859-7. 13.
-* RFC 1991: PGP. 15.
-* RFC 2015: PGP/MIME. 15.
-* RFC 2045: RFC 2045. 5.
-* RFC 2046: RFC 2046. 5.
-* RFC 2047: encoded-word. 7.
-* RFC 2047: encoded-word. 8.
-* RFC 2048: RFC 2048. 5.
-* RFC 2049: RFC 2049. 5.
-* RFC 821: RFC 821. 5.
-* RFC 822: RFC 822. 13.
-* RFC 934: RFC 934. 11.
-* RFC 959: FTP. 5.
-* Security multipart: Security multipart. 15.
-* SMTP: RFC 821. 5.
-* Standards Track: encoded-word. 8.
-* Standards Track: PGP/MIME. 15.
-* Standards Track: RFC 2045. 5.
-* Standards Track: RFC 2046. 5.
-* Standards Track: RFC 2048. 5.
-* Standards Track: RFC 2049. 5.
-* Standards Track: Security multipart. 15.
-* STD 10: RFC 821. 5.
-* STD 11: RFC 822. 13.
-* STD 9: FTP. 5.
-* subtype: Content-Type field. 20.
-* subtype: media type. 8.
-* text: media type. 13.
-* text/enriched: text/enriched. 5.
-* text/plain: text/plain. 5.
-* tm oomori package: tm-MUA. 7.
-* tm-gnus: tm-MUA. 13.
-* tm-mh-e: tm-MUA. 10.
-* tm-rmail: tm-MUA. 19.
-* tm-setup: tm-setup. 5.
-* tm-vm: tm-MUA. 17.
-* type: Content-Type field. 20.
-* type: media type. 7.
-* us-ascii: us-ascii. 14.
-* USENET: RFC 1036. 9.
-* video: media type. 19.
-* vm: setting for VM. 6.
-* XEmacs/mule: MULE. 23.
-* x-token: media type. 29.
-data: 7bit. 8.
-data: 8bit. 8.
-Extensions: MIME. 6.
-header: RFC 822. 6.
-message: RFC 822. 10.
-string: 8bit. 12.
-tool: signature. 6.
-
-
-\1f
-File: tm-en.info, Node: Variable Index, Prev: Concept Index, Up: Top
+* 7bit: 7bit.
+* 7bit (textual) string: 7bit.
+* 7bit data: 7bit.
+* 8bit: 8bit.
+* 8bit (textual) string: 8bit.
+* 8bit data: 8bit.
+* 94-character set: 94-character set.
+* 94x94-character set: 94x94-character set.
+* 96-character set: 96-character set.
+* ANSI X3.4:1986: ASCII.
+* application: media type.
+* application/pgp: PGP-kazu.
+* ASCII <1>: ASCII.
+* ASCII <1>: us-ascii.
+* ASCII: ASCII.
+* audio: media type.
+* automatic signature selection tool: signature.
+* Base64: Base64.
+* BBDB: setting for VM.
+* BIG5: cn-big5.
+* binary: binary.
+* charset-edition: RFC 1922.
+* charset-extension: RFC 1922.
+* CNS 11643:1992: CNS 11643.
+* CNS 11643-1992: CNS 11643.
+* Emacs/mule: MULE.
+* encapsulation: RFC 934.
+* euc-kr: euc-kr.
+* Experimental: Content-Disposition.
+* external method: method.
+* FTP: FTP.
+* GB 2312: GB 2312.
+* GB 2312:1980: GB 2312.
+* GB 8565.2: GB 8565.2.
+* GB 8565.2:1988: GB 8565.2.
+* gnus-mime: tm-MUA.
+* good bug report: Bug report.
+* image: media type.
+* Informational <1>: hz-gb2312.
+* Informational <1>: RFC 1557.
+* Informational <1>: RFC 1922.
+* Informational <1>: hz-gb2312.
+* Informational <1>: iso-2022-jp-2.
+* Informational <1>: iso-8859-7.
+* Informational: PGP.
+* internal method: method.
+* Internet mail: RFC 822.
+* Internet message: RFC 822.
+* ISO 2022: ISO 2022.
+* ISO 646: ISO 646.
+* ISO 8859-1: ISO 8859-1.
+* ISO 8859-1:1987: ISO 8859-1.
+* ISO 8859-2: ISO 8859-2.
+* ISO 8859-2:1987: ISO 8859-2.
+* ISO 8859-3: ISO 8859-3.
+* ISO 8859-3:1988: ISO 8859-3.
+* ISO 8859-4: ISO 8859-4.
+* ISO 8859-4:1988: ISO 8859-4.
+* ISO 8859-5: ISO 8859-5.
+* ISO 8859-5:1988: ISO 8859-5.
+* ISO 8859-6: ISO 8859-6.
+* ISO 8859-6:1987: ISO 8859-6.
+* ISO 8859-7: ISO 8859-7.
+* ISO 8859-7:1987: ISO 8859-7.
+* ISO 8859-8: ISO 8859-8.
+* ISO 8859-8:1988: ISO 8859-8.
+* ISO 8859-9: ISO 8859-9.
+* ISO 8859-9:1990: ISO 8859-9.
+* iso-2022-jp: iso-2022-jp.
+* iso-2022-jp-2: iso-2022-jp-2.
+* iso-8859-1: iso-8859-1.
+* iso-8859-2: iso-8859-2.
+* iso-8859-5: iso-8859-5.
+* iso-8859-7: iso-8859-7.
+* ISO/IEC 2022:1994: ISO 2022.
+* ISO/IEC 646:1991: ISO 646.
+* JIS X 0201-1976:: JIS X0201.
+* JIS X0208:1983,1990: JIS X0208.
+* JIS C6220-1976: JIS X0201.
+* JIS C6226:1978: JIS X0208.
+* JIS X 0208:1997? draft: JIS X0208.
+* JIS X 0201:1997? draft: JIS X0201.
+* JIS X0201-1976: JIS X0201.
+* JIS X0201-1997?: JIS X0201.
+* JIS X0208-1978: JIS X0208.
+* JIS X0208-1983,1990: JIS X0208.
+* JIS X0208-1997?: JIS X0208.
+* KS C 5601:1987: KS C5601.
+* KS C 5861:1992: euc-kr.
+* KS C5601: KS C5601.
+* media type: media type.
+* message: media type.
+* message header: RFC 822.
+* Message Transfer Agent: MTA.
+* Message User Agent: MUA.
+* message/rfc822: message/rfc822.
+* mime-setup: mime-setup.
+* MULE: MULE.
+* multipart <1>: media type.
+* multipart: multipart.
+* multipart/digest <1>: multipart/alternative.
+* multipart/digest: multipart/digest.
+* multipart/encrypted: Security multipart.
+* multipart/parallel: multipart/parallel.
+* multipart/signed: Security multipart.
+* Multipurpose Internet Mail Extensions: MIME.
+* pad: Base64.
+* parameter: Content-Type field.
+* PGP: PGP.
+* PGP-kazu: PGP-kazu.
+* PGP/MIME: PGP/MIME.
+* Pretty Good Privacy: PGP.
+* Quoted-Printable: Quoted-Printable.
+* RFC 1036: RFC 1036.
+* RFC 1153: RFC 1153.
+* RFC 1468: iso-2022-jp.
+* RFC 1489: koi8-r.
+* RFC 1554: iso-2022-jp-2.
+* RFC 1557: RFC 1557.
+* RFC 1806: Content-Disposition.
+* RFC 1842: hz-gb2312.
+* RFC 1843: hz-gb2312.
+* RFC 1847: Security multipart.
+* RFC 1896: text/enriched.
+* RFC 1922: RFC 1922.
+* RFC 1947: iso-8859-7.
+* RFC 1991: PGP.
+* RFC 2015: PGP/MIME.
+* RFC 2045: RFC 2045.
+* RFC 2046: RFC 2046.
+* RFC 2047: encoded-word.
+* RFC 2048: RFC 2048.
+* RFC 2049: RFC 2049.
+* RFC 821: RFC 821.
+* RFC 822: RFC 822.
+* RFC 934: RFC 934.
+* RFC 959: FTP.
+* Security multipart: Security multipart.
+* SMTP: RFC 821.
+* Standards Track <1>: PGP/MIME.
+* Standards Track <1>: RFC 2046.
+* Standards Track <1>: RFC 2049.
+* Standards Track <1>: Security multipart.
+* Standards Track <1>: encoded-word.
+* Standards Track <1>: RFC 2045.
+* Standards Track: RFC 2048.
+* STD 10: RFC 821.
+* STD 11: RFC 822.
+* STD 9: FTP.
+* subtype <1>: Content-Type field.
+* subtype: media type.
+* text: media type.
+* text/enriched: text/enriched.
+* text/plain: text/plain.
+* tm oomori package: tm-MUA.
+* tm-gnus: tm-MUA.
+* tm-mh-e: tm-MUA.
+* tm-rmail: tm-MUA.
+* tm-setup: tm-setup.
+* tm-vm: tm-MUA.
+* type <1>: media type.
+* type: Content-Type field.
+* us-ascii: us-ascii.
+* USENET: RFC 1036.
+* video: media type.
+* vm: setting for VM.
+* x-token: media type.
+* XEmacs/mule: MULE.
+
+\1f
+File: tm-en.info, Node: Variable Index, Prev: Concept Index, Up: Top
Variable Index
**************
-
* Menu:
-* mime-setup-default-signature-key: signature. 46.
-* mime-setup-signature-key-alist: signature. 30.
-* mime-setup-use-signature: signature. 23.
-\1f\f
-Tag table:
-Node: Top\7f152
-Node: Introduction\7f583
-Node: Glossary\7f1260
-Node: 7bit\7f4560
-Node: 8bit\7f5492
-Node: 94-character set\7f6629
-Node: 96-character set\7f6991
-Node: 94x94-character set\7f7337
-Node: ASCII\7f7725
-Node: Base64\7f8174
-Node: binary\7f8768
-Node: cn-gb\7f9089
-Node: cn-big5\7f9531
-Node: CNS 11643\7f10094
-Node: coded character set\7f10834
-Node: code extension\7f11164
-Node: Content-Disposition\7f11448
-Node: Content-Type field\7f11885
-Node: Emacs\7f12941
-Node: encoded-word\7f13154
-Node: encapsulation\7f13566
-Node: euc-kr\7f13854
-Node: FTP\7f14344
-Node: GB 2312\7f14527
-Node: GB 8565.2\7f14974
-Node: graphic character set\7f15403
-Node: hz-gb2312\7f15622
-Node: ISO 2022\7f16448
-Node: iso-2022-cn\7f16849
-Node: iso-2022-cn-ext\7f17310
-Node: iso-2022-jp\7f17950
-Node: iso-2022-jp-2\7f18654
-Node: iso-2022-kr\7f19065
-Node: ISO 646\7f19494
-Node: ISO 8859-1\7f19779
-Node: iso-8859-1\7f20093
-Node: ISO 8859-2\7f20556
-Node: iso-8859-2\7f20873
-Node: ISO 8859-3\7f21336
-Node: ISO 8859-4\7f21653
-Node: ISO 8859-5\7f21970
-Node: iso-8859-5\7f22296
-Node: ISO 8859-6\7f22727
-Node: ISO 8859-7\7f23046
-Node: iso-8859-7\7f23364
-Node: ISO 8859-8\7f23900
-Node: ISO 8859-9\7f24219
-Node: ISO-IR-165\7f24536
-Node: JIS X0201\7f25008
-Node: JIS C6226\7f25690
-Node: JIS X0208\7f25936
-Node: JIS X0212\7f27382
-Node: koi8-r\7f27698
-Node: KS C5601\7f28157
-Node: media type\7f28567
-Node: message\7f29497
-Node: message/rfc822\7f29732
-Node: method\7f30109
-Node: MIME\7f30569
-Node: MIME charset\7f31558
-Node: MTA\7f32178
-Node: MUA\7f32378
-Node: MULE\7f32541
-Node: multipart\7f33285
-Node: multipart/alternative\7f34025
-Node: multipart/digest\7f34483
-Node: multipart/encrypted\7f35130
-Node: multipart/mixed\7f35421
-Node: multipart/parallel\7f35747
-Node: multipart/signed\7f36188
-Node: PGP\7f36457
-Node: PGP-kazu\7f37132
-Node: PGP/MIME\7f37754
-Node: Quoted-Printable\7f38365
-Node: RFC 821\7f38749
-Node: RFC 822\7f38945
-Node: RFC 934\7f39347
-Node: RFC 1036\7f39767
-Node: RFC 1153\7f40166
-Node: RFC 1557\7f40331
-Node: RFC 1922\7f40691
-Node: RFC 2045\7f41312
-Node: RFC 2046\7f41623
-Node: RFC 2048\7f41912
-Node: RFC 2049\7f42227
-Node: plain text\7f42541
-Node: Security multipart\7f42831
-Node: text/enriched\7f43450
-Node: text/plain\7f43720
-Node: tm-kernel\7f44200
-Node: tm-MUA\7f44618
-Node: us-ascii\7f45064
-Node: Setting\7f45666
-Node: mime-setup\7f46265
-Node: signature\7f46766
-Node: Notice about GNUS\7f48311
-Node: tm-setup\7f49187
-Node: setting for VM\7f49735
-Node: manual setting\7f50047
-Node: Bug report\7f50649
-Node: Concept Index\7f52082
-Node: Variable Index\7f62552
-\1f
-End tag table
+* mime-setup-default-signature-key: signature.
+* mime-setup-signature-key-alist: signature.
+* mime-setup-use-signature: signature.
+
+
+\1f
+Tag Table:
+Node: Top\7f89
+Node: Introduction\7f497
+Node: Glossary\7f1167
+Node: 7bit\7f3183
+Node: 8bit\7f4132
+Node: 94-character set\7f5292
+Node: 96-character set\7f5659
+Node: 94x94-character set\7f6010
+Node: ASCII\7f6403
+Node: Base64\7f6859
+Node: binary\7f7464
+Node: cn-gb\7f7796
+Node: cn-big5\7f8249
+Node: CNS 11643\7f8834
+Node: coded character set\7f9583
+Node: code extension\7f9918
+Node: Content-Disposition\7f10207
+Node: Content-Type field\7f10652
+Node: Emacs\7f11706
+Node: encoded-word\7f11924
+Node: encapsulation\7f12344
+Node: entity\7f12642
+Node: euc-kr\7f12929
+Node: FTP\7f13430
+Node: GB 2312\7f13618
+Node: GB 8565.2\7f14076
+Node: graphic character set\7f14513
+Node: hz-gb2312\7f14737
+Node: ISO 2022\7f15576
+Node: iso-2022-cn\7f15985
+Node: iso-2022-cn-ext\7f16457
+Node: iso-2022-jp\7f17107
+Node: iso-2022-jp-2\7f17819
+Node: iso-2022-kr\7f18236
+Node: ISO 646\7f18676
+Node: ISO 8859-1\7f18966
+Node: iso-8859-1\7f19283
+Node: ISO 8859-2\7f19757
+Node: iso-8859-2\7f20077
+Node: ISO 8859-3\7f20551
+Node: ISO 8859-4\7f20871
+Node: ISO 8859-5\7f21191
+Node: iso-8859-5\7f21515
+Node: ISO 8859-6\7f21957
+Node: ISO 8859-7\7f22279
+Node: iso-8859-7\7f22600
+Node: ISO 8859-8\7f23150
+Node: ISO 8859-9\7f23472
+Node: ISO-IR-165\7f23792
+Node: JIS X0201\7f24275
+Node: JIS C6226\7f24969
+Node: JIS X0208\7f25221
+Node: JIS X0212\7f26675
+Node: koi8-r\7f26999
+Node: KS C5601\7f27467
+Node: media type\7f27885
+Node: message\7f28839
+Node: message/rfc822\7f29079
+Node: method\7f29460
+Node: MIME\7f29931
+Node: MIME charset\7f30936
+Node: MTA\7f31567
+Node: MUA\7f31774
+Node: MULE\7f31944
+Node: multipart\7f32709
+Node: multipart/alternative\7f33458
+Node: multipart/digest\7f33923
+Node: multipart/encrypted\7f34580
+Node: multipart/mixed\7f34878
+Node: multipart/parallel\7f35211
+Node: multipart/signed\7f35658
+Node: PGP\7f35934
+Node: PGP-kazu\7f36619
+Node: PGP/MIME\7f37255
+Node: Quoted-Printable\7f37880
+Node: RFC 821\7f38274
+Node: RFC 822\7f38470
+Node: RFC 934\7f38878
+Node: RFC 1036\7f39309
+Node: RFC 1153\7f39716
+Node: RFC 1557\7f39886
+Node: RFC 1922\7f40254
+Node: RFC 2045\7f40886
+Node: RFC 2046\7f41202
+Node: RFC 2048\7f41496
+Node: RFC 2049\7f41811
+Node: plain text\7f42130
+Node: Security multipart\7f42424
+Node: text/enriched\7f43052
+Node: text/plain\7f43322
+Node: tm-kernel\7f43812
+Node: tm-MUA\7f44229
+Node: us-ascii\7f44681
+Node: Setting\7f45296
+Node: mime-setup\7f45903
+Node: signature\7f46392
+Node: Notice about GNUS\7f47928
+Node: tm-setup\7f48813
+Node: setting for VM\7f49366
+Node: manual setting\7f49679
+Node: Bug report\7f50283
+Node: Acknowledgments\7f51737
+Node: Concept Index\7f52830
+Node: Variable Index\7f61554
+\1f
+End Tag Table
<!doctype sinfo system>
-<!-- $Id: tm-en.sgml,v 1.2 1996/12/23 21:17:11 morioka Exp $ -->
+<!-- $Id: tm-en.sgml,v 3.1 1996/12/25 18:56:14 morioka Exp $ -->
<head>
-<title>tm 7.98 Manual (English Version)
+<title>tm 7.100 Manual (English Version)
<author>MORIOKA Tomohiko <mail>morioka@jaist.ac.jp</mail>
-<date>1996/12/24
+<date>1996/12/25
<toc>
</head>
<h3> CNS 11643-1992
<node> CNS 11643
<p>
-<dref>Graphic character set</dref>s for Chinese mainly written by
-traditional Chinese mainly used in Taiwan and Hong Kong. It is a
-standard of Taiwan. Currently there are seven <dref>94x94
-character set</dref>.
+<a node="graphic character set">Graphic character sets</a> for Chinese
+mainly written by traditional Chinese mainly used in Taiwan and Hong
+Kong. It is a standard of Taiwan. Currently there are seven
+<dref>94x94-character set</dref>.
<p>
Final byte of <dref>ISO 2022</dref> are following:
<cf node="message/rfc822">
+<h3> Entity
+<node> entity
+<p>
+Header fields and contents of a message or one of the parts in the
+body of a <dref>multipart</dref> entity.
+
+<memo>
+<p>
+In this document, `entity' might be called ``part''.
+</memo>
+
+
<h3> euc-kr
<node> euc-kr
<p>
<h3> GB 2312-1980
<node> GB 2312
<p>
-A <dref>94x94 character set</dref> for Chinese mainly written by
+A <dref>94x94-character set</dref> for Chinese mainly written by
simplified Chinese mainly used in the Chinese mainland. It is a
standard of China.
<p>
<h3> GB 8565.2-1988
<node> GB 8565.2
<p>
-A <dref>94x94 character set</dref> for Chinese as supplement to
+A <dref>94x94-character set</dref> for Chinese as supplement to
<dref>GB 2312</dref>. It is a standard of China.
<standard abbrev="GB 8565.2" title-en="Information Processing - Coded
<h3> Graphic Character Set
<node> graphic character set
<p>
-<dref>Coded character set</dref> for graphic characters.
+<a node="coded character set">Coded character set</a> for graphic
+characters.
<h3> hz-gb2312
<p>
It is a <dref>7bit</dref> <dref>coded character set</dref> based on
old <dref>ISO 2022</dref>. It switches <dref>ASCII</dref>, JIS
-X0201-Latin, <a node="JIS C6226-1978">JIS X0208-1978</a> and <a
-node="JIS X0208">JIS X0208-1983</a>.
+X0201-Latin, <a node="JIS C6226">JIS X0208-1978</a> and <a node="JIS
+X0208">JIS X0208-1983</a>.
<p>
It is defined in RFC 1468.
<p>
simplified Chinese mainly used in the Chinese mainland registered by
CCITT.
<p>
-It consists of <dref>GB 2312</dref>, <dref>GB 8865.2</dref> and
+It consists of <dref>GB 2312</dref>, <dref>GB 8565.2</dref> and
additional 150 characters.
<p>
Final byte of <dref>ISO 2022</dref> is 04/05 (`E').
<h3> JIS X0212-1990
<node> JIS X0212
<p>
-A <dref>94x94 character set</dref> for Japanese as supplement to
+A <dref>94x94-character set</dref> for Japanese as supplement to
<dref>JIS X0208</dref>. It is a standard of Japan.
<p>
Final byte of <dref>ISO 2022</dref> is 04/04 (`D').
<h3> MIME charset
<node> MIME charset
<p>
-<dref>Coded character set</dref> used in <dref>Content-Type
-field</dref> or charset parameter of <a
+<a node="coded character set">Coded character set</a> used in
+<dref>Content-Type field</dref> or charset parameter of <a
node="encoded-word">encoded-word</a>.
<p>
It is defined in <dref>RFC 2045</dref>.
<node> multipart
<p>
<concept>multipart</concept> means <dref>media type</dref> to insert
-multiple <dref>entities</dref> in a single body. Or it also indicates
-a message consists of multiple entities.
+multiple <a node="entity">entities</a> in a single body. Or it also
+indicates a message consists of multiple entities.
<p>
There are following subtypes registered in <dref>RFC 2046</dref>:
body in human-recognizable language (^_^).
+<h1> Acknowledgments
+<node> Acknowledgments
+<p>
+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.
+<p>
+I thank ENAMI Tsugutomo for work of <file>mime.el</file>, which is an
+origin of <file>tm-ew-d.el</file> and <file>mel-b.el</file>, and
+permission to rewrite for tm.
+<p>
+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.
+<p>
+I thank UMEDA Masanobu for his work of <file>mime.el</file>, which is
+the origin of tm-edit, and permission to rewrite his work as tm-edit.
+<p>
+I thank KOBAYASHI Shuhei for his work as a tm maintainer. In
+addition, he often points out or suggests about conformity with RFCs.
+<p>
+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.
+<p>
+Last of all, I thank members of two tm mailing lists, Japanese and
+English version.
+
+
<h1> Concept Index
<node> Concept Index
\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
\1f
File: tm-ja.info, Node: Top, Next: Introduction, Prev: (dir), Up: (dir)
-tm 7.98 Manual\e$B!JF|K\8lHG!K\e(B
-**************************
+tm 7.100 Manual\e$B!JF|K\8lHG!K\e(B
+***************************
This file documents tm, a MIME package for GNU Emacs.
* Introduction:: tm \e$B$C$F2?!)\e(B
* Setting:: \e$B@_Dj\e(B
* Bug report:: bug \e$BJs9p$N;EJ}\e(B
+* Acknowledgments:: \e$B<U<-\e(B
* Concept Index:: \e$B35G0:w0z\e(B
* Variable Index:: \e$BJQ?t:w0z\e(B
* Emacs::
* encoded-word::
* encapsulation::
+* entity:: Entity
* euc-kr::
* FTP:: FTP
* GB 2312:: GB 2312-1980
* iso-8859-7::
* ISO 8859-8::
* ISO 8859-9::
-* ISO-IR-165:: ISO-IR-165, CCITT Extended GB
+* ISO-IR-165:: ISO-IR-165, CCITT Extended GB
* JIS X0201::
* JIS C6226:: JIS C6226-1978
* JIS X0208::
\1f
-File: tm-ja.info, Node: encapsulation, Next: euc-kr, Prev: encoded-word, Up: Glossary
+File: tm-ja.info, Node: encapsulation, Next: entity, Prev: encoded-word, Up: Glossary
encapsulation
-------------
\1f
-File: tm-ja.info, Node: euc-kr, Next: FTP, Prev: encapsulation, Up: Glossary
+File: tm-ja.info, Node: entity, Next: euc-kr, Prev: encapsulation, Up: Glossary
+
+Entity
+------
+
+\e$B$"$k\e(B message \e$B$b$7$/$O\e(B multipart (*Note multipart::) message \e$B$N#1$D$N\e(B
+part \e$B$N\e(B header \e$B$H\e(B body \e$B$rJ;$;$?$b$N!#\e(B
+
+*[Memo]*
+
+ \e$B$3$3$G$O\e(B part \e$B$H8F$V$3$H$b$"$k!#\e(B
+
+
+
+
+\1f
+File: tm-ja.info, Node: euc-kr, Next: FTP, Prev: entity, Up: Glossary
euc-kr
------
\e$BF|K\8l$rI=8=$9$k$?$a$N\e(B MIME charset (*Note MIME charset::) \e$B$N0l$D!#\e(B
\e$B8E$$\e(B ISO 2022 (*Note ISO 2022::) \e$B$K4p$$$F\e(B ASCII (*Note ASCII::), JIS
-X0201-Latin, JIS X0208-1978 (*Note JIS C6226-1978::), JIS X0208-1983
-(*Note JIS X0208::) \e$B$r@Z$jBX$($k\e(B 7bit (*Note 7bit::) \e$BJ8;zId9f!#\e(B
+X0201-Latin, JIS X0208-1978 (*Note JIS C6226::), JIS X0208-1983 (*Note
+JIS X0208::) \e$B$r@Z$jBX$($k\e(B 7bit (*Note 7bit::) \e$BJ8;zId9f!#\e(B
RFC 1468 \e$B$GDj5A$5$l$F$$$k!#\e(B
CCITT \e$B$,EPO?$7$?!"Cf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=\e(B
\e$B$9$k$?$a$N\e(B94\e$B!_\e(B94 \e$BJ8;z=89g\e(B(*Note 94x94-character set::)\e$B!#\e(B
-GB 2312 (*Note GB 2312::) \e$B$H\e(B GB 8565 \e$BI=#2\e(B (*Note GB 8865.2::) \e$B$K\e(B 150 \e$BJ8\e(B
+GB 2312 (*Note GB 2312::) \e$B$H\e(B GB 8565 \e$BI=#2\e(B (*Note GB 8565.2::) \e$B$K\e(B 150 \e$BJ8\e(B
\e$B;z$[$I$rDI2C$7$?$b$N$i$7$$!#\e(B
ISO 2022 (*Note ISO 2022::) \e$B$G$N=*C<\e(B byte \e$B$O\e(B 04/05 (`E') \e$B$G$"$k!#\e(B
media type
----------
-MIME (*Note MIME::) \e$B$K$*$1$k\e(B entity (*Note entity::) \e$B$N<oN`!#\e(B
-*type* \e$B$H\e(B *subtype* \e$B$+$i$J$k!#\e(B
-RFC 2046 (*Note RFC 2046::) \e$B$GDj5A$5$l$F$$$k!#\e(B
+MIME (*Note MIME::) \e$B$K$*$1$k\e(B entity (*Note entity::) \e$B$N<oN`!#\e(B*type* \e$B$H\e(B
+*subtype* \e$B$+$i$J$k!#\e(BRFC 2046 (*Note RFC 2046::) \e$B$GDj5A$5$l$F$$$k!#\e(B
type \e$B$OI8=`$G$O\e(B
\e$B$k!#8=:_!"EPO?$5$l$F$$$k$b$N$O\e(B MEDIA TYPES
(ftp://ftp.isi.edu/in-notes/iana/assignments/media-types) \e$B$G;2>H$G$-$k!#\e(B
-\e$B$^$?!"\e(Btype \e$B$b$7$/$O\e(B subtype \e$B$K!"A0$K\e(B `x-' \e$B$rIU$1$?\e(B
-*x-token* \e$B$rMQ$$$k$3$H$K$h$j!"EPO?$5$l$F$$$J$$$b\e(B
-\e$B$N$r;dE*$KMQ$$$k$3$H$b$G$-$k!#$7$+$7!"EvA3$N$3$H$J$,$i!"$3$&$7$?;dE*$J\e(B
-content-type
\e$B$ONJ2r$rF@$?<T$N4V$G$7$+2r<a$G$-$J$$$N$GMxMQ$K$OCm0U$9$k$3
\e(B
-\e$B$H!#\e(B
+\e$B$^$?!"\e(Btype \e$B$b$7$/$O\e(B subtype \e$B$K!"A0$K\e(B `x-' \e$B$rIU$1$?\e(B *x-token* \e$B$rMQ$$$k$3\e(B
+\e$B$H$K$h$j!"EPO?$5$l$F$$$J$$$b$N$r;dE*$KMQ$$$k$3$H$b$G$-$k!#$7$+$7!"EvA3$N\e(B
+
\e$B$3$H$J$,$i!"$3$&$7$?;dE*$J
\e(B content-type
\e$B$ONJ2r$rF@$?<T$N4V$G$7$+2r<a$G$-
\e(B
+\e$B$J$$$N$GMxMQ$K$OCm0U$9$k$3$H!#\e(B
(cf. *Note Content-Type field::)
MIME
----
-*Multipurpose
-Internet Mail Extensions* \e$B$NN,$G!"\e(BInternet \e$B$N\e(B mail \e$B$d\e(B news \e$B$G\e(B us-ascii
-plain text (*Note us-ascii::) \e$B0J30$NJ8;z$r;H$&$?$a$N\e(B RFC 822 (*Note RFC
-822::) \e$B$KBP$9$k3HD%!#\e(B
+*Multipurpose Internet Mail Extensions* \e$B$NN,$G!"\e(BInternet \e$B$N\e(B mail
+\e$B$d\e(B news \e$B$G\e(B us-ascii plain text (*Note us-ascii::) \e$B0J30$NJ8;z$r;H$&$?$a$N\e(B
+RFC 822 (*Note RFC 822::) \e$B$KBP$9$k3HD%!#\e(B
RFC 2045 \e$B$OKAF,$G<!$N$h$&$K=R$Y$F$$$k!'\e(B
MTA
---
-*Message Transfer Agent* \e$B$NN,$G!"\e(B
-sendmail \e$B$J$I$N\e(B mail \e$BG[Aw\e(B program \e$B$H\e(B news server \e$B$NAm>N!#\e(B
+*Message Transfer Agent* \e$B$NN,$G!"\e(Bsendmail \e$B$J$I$N\e(B mail \e$BG[Aw\e(B
+program \e$B$H\e(B news server \e$B$NAm>N!#\e(B
(cf. *Note MUA::)
MUA
---
-*Message User Agent* \e$B$NN,$G!"\e(Bmail
-reader \e$B$H\e(B news reader \e$B$NAm>N!#\e(B
+*Message User Agent* \e$B$NN,$G!"\e(Bmail reader \e$B$H\e(B news reader \e$B$NAm>N!#\e(B
+
(cf. *Note MTA::)
RFC 934
-------
-Internet mail (*Note RFC 822::) \e$B$N\e(B
-*encapsulation* (*Note encapsulation::) \e$B$NJ}\e(B
-\e$BK!$rDj$a$?\e(B RFC.
+Internet mail (*Note RFC 822::) \e$B$N\e(B *encapsulation* (*Note
+encapsulation::) \e$B$NJ}K!$rDj$a$?\e(B RFC.
MIME (*Note MIME::) \e$B$HL7=b$9$k$N$G!"8=:_$G$O\e(B message/rfc822 (*Note
message/rfc822::) \e$B$rMQ$$$k$Y$-$G$"$k!#\e(B
RFC 1153
--------
-\e$BJ#?t$N\e(B Internet mail (*Note RFC 822::) \e$B$r\e(B
-*encapsulation* (*Note encapsulation::) \e$B$9$k\e(B
-\e$B$?$a$NJ}K!$rDj$a$?\e(B RFC.
+\e$BJ#?t$N\e(B Internet mail (*Note RFC 822::) \e$B$r\e(B *encapsulation* (*Note
+encapsulation::) \e$B$9$k$?$a$NJ}K!$rDj$a$?\e(B RFC.
MIME (*Note MIME::) \e$B$HL7=b$9$k$N$G!"8=:_$G$O\e(B message/rfc822 (*Note
message/rfc822::) \e$B$rMQ$$$?\e(B multipart (*Note multipart::) \e$B$rMQ$$$k$Y$-$G\e(B
\e$B$$$C$?Cf9q8l$N$?$a$N\e(B MIME charset (*Note MIME charset::) \e$B$rDj5A$7$F$$$k\e(B
RFC.
-\e$B$3$l$K2C$($F!"\e(B*charset-edition* \e$B$H\e(B
-*charset-extension* \e$B$H$$$&\e(B Content-Type
-field (*Note Content-Type field::) \e$B$N\e(B parameter \e$B$rDj5A$7$F$$$k!#\e(B
+\e$B$3$l$K2C$($F!"\e(B*charset-edition* \e$B$H\e(B *charset-extension* \e$B$H$$$&\e(B
+Content-Type field (*Note Content-Type field::) \e$B$N\e(B parameter \e$B$rDj5A$7$F\e(B
+\e$B$$$k!#\e(B
[RFC 1922] Zhu, HF., Hu, DY., Wang, ZG., Kao, TC., Chang, WCH. and
MIME (*Note MIME::) \e$B$G0E9f$dEE;R=qL>$rMQ$$$k$?$a$N7A<0!#\e(B
-*multipart/signed*
-(*Note multipart/signed::) \e$B$H\e(B
-*multipart/encrypted*
-(*Note multipart/encrypted::) \e$B$H$$$&\e(B multipart \e$B$rMQ$$$k!#\e(B
+*multipart/signed* (*Note multipart/signed::) \e$B$H\e(B
+*multipart/encrypted* (*Note multipart/encrypted::) \e$B$H$$$&\e(B
+multipart \e$B$rMQ$$$k!#\e(B
MOSS \e$B$d\e(B PGP/MIME (*Note PGP/MIME::) \e$B$O$3$l$K4p$$$F$$$k!#\e(B
RFC 2046 (*Note RFC 2046::) \e$B$GDj5A$5$l$?!"\e(Bplain text (*Note plain
text::) \e$B$rI=8=$9$k$?$a$N\e(B media type (*Note media type::).
-\e$BHs\e(B MIME message \e$B$J$I$N\e(B content-type \e$B$,Dj5A$5$l$J$$\e(B entity \e$B$O\e(B MIME
-charset (*Note MIME charset::) \e$B$,\e(B us-ascii (*Note us-ascii::) \e$B$G$"$k\e(B
-*text/plain* \e$B$N\e(B entity \e$B$G$"$k$H8+Pv$5$l$k$3$H\e(B
-\e$B$K$J$C$F$$$k!#\e(B
+\e$BHs\e(B MIME message \e$B$J$I$N\e(B content-type \e$B$,Dj5A$5$l$J$$\e(B entity (*Note entity::)
+\e$B$O\e(B MIME charset (*Note MIME charset::) \e$B$,\e(B us-ascii (*Note us-ascii::) \e$B$G$"$k\e(B
+*text/plain* \e$B$N\e(B entity \e$B$G$"$k$H8+Pv$5$l$k$3$H$K$J$C$F$$$k!#\e(B
\e$BI8=`E*$J@_Dj\e(B
============
-tm \e$B$N0lHLE*$J@_Dj$r9T$$$?$$>l9g$O!"\e(B
-*mime-setup* \e$B$H$$$&I8=`@_Dj\e(B file \e$B$r;H$C$F$/$@\e(B
-\e$B$5$$!#Nc$($P!"\e(B`~/.emacs' \e$BEy$G!"\e(B
+tm \e$B$N0lHLE*$J@_Dj$r9T$$$?$$>l9g$O!"\e(B*mime-setup* \e$B$H$$$&I8=`@_Dj\e(B file \e$B$r;H$C\e(B
+\e$B$F$/$@$5$$!#Nc$($P!"\e(B`~/.emacs' \e$BEy$G!"\e(B
(load "mime-setup")
======================
-*tm-setup* \e$B$O\e(B tm-MUA (*Note tm-MUA::) \e$B$N@_Dj$N$_$r\e(B
-\e$B9T$J$&\e(B module \e$B$G$9!#$3$N@_Dj\e(B file \e$B$G$O\e(B tm-edit (*Note (tm-edit-ja)::) \e$B$r\e(B
-\e$B;H$C$?\e(B MIME message \e$B$N:n@.$K4X$9$k@_Dj$O9T$o$l$:!"\e(BMIME message \e$B$N1\Mw$K\e(B
-\e$B4X$9$k@_Dj$N$_$,9T$o$l$^$9!#\e(BMIME message \e$B$rFI$_$?$$$,<+J,$G$O:n@.$7$J$$\e(B
-\e$B$H$+!"\e(Btm-edit \e$B0J30$N\e(B MIME composer \e$B$r;H$$$?$$>l9g$K$O\e(B mime-setup.el \e$B$NBe\e(B
-\e$B$o$j$K$3$N@_Dj\e(B file \e$B$r;H$C$F$/$@$5$$!#\e(B
+*tm-setup* \e$B$O\e(B tm-MUA (*Note tm-MUA::) \e$B$N@_Dj$N$_$r9T$J$&\e(B module \e$B$G\e(B
+\e$B$9!#$3$N@_Dj\e(B file \e$B$G$O\e(B tm-edit (*Note (tm-edit-ja)::) \e$B$r;H$C$?\e(B MIME
+message \e$B$N:n@.$K4X$9$k@_Dj$O9T$o$l$:!"\e(BMIME message \e$B$N1\Mw$K4X$9$k@_Dj$N\e(B
+\e$B$_$,9T$o$l$^$9!#\e(BMIME message \e$B$rFI$_$?$$$,<+J,$G$O:n@.$7$J$$$H$+!"\e(Btm-edit
+\e$B0J30$N\e(B MIME composer \e$B$r;H$$$?$$>l9g$K$O\e(B mime-setup.el \e$B$NBe$o$j$K$3$N@_Dj\e(B
+file \e$B$r;H$C$F$/$@$5$$!#\e(B
\e$BNc$($P!"\e(B`~/.emacs' \e$BEy$K\e(B
*[\e$BCm0U\e(B]*
- *BBDB* \e$B$r;H$&>l9g$O\e(B `(bbdb-insinuate-vm)' \e$B$N\e(B
- *\e$B8e\e(B* \e$B$K\e(B `(require 'tm-vm)' \e$B$rF~$l$F$/$@$5$$!#\e(B
+ *BBDB* \e$B$r;H$&>l9g$O\e(B `(bbdb-insinuate-vm)' \e$B$N\e(B *\e$B8e\e(B* \e$B$K\e(B
+ `(require 'tm-vm)' \e$B$rF~$l$F$/$@$5$$!#\e(B
\1f
-File: tm-ja.info, Node: Bug report, Next: Concept Index, Prev: Setting, Up: Top
+File: tm-ja.info, Node: Bug report, Next: Acknowledgments, Prev: Setting, Up: Top
bug \e$BJs9p$N;EJ}\e(B
**************
\1f
-File: tm-ja.info, Node: Concept Index, Next: Variable Index, Prev: Bug report, Up: Top
+File: tm-ja.info, Node: Acknowledgments, Next: Concept Index, Prev: Bug report, Up: Top
+
+\e$B<U<-\e(B
+****
+
+\e$B;d$,\e(B tm-view \e$B$r:G=i$K:n$C$?;~$K!"87$7$$CmJ8$HM-1W$J=u8@$r2<$5$j!"$=$N@_\e(B
+\e$B7W$KB?Bg$JM?$($i$l$?>#C+J]Gn$5$s$K46<U$7$^$9!#\e(B
+
+`tm-ew-d.el' \e$B$H\e(B `mel-b.el' \e$B$NA0?H$KEv$?$k\e(B`mime.el' \e$B$r=q$-!"$=$NG[I[$H2~\e(B
+\e$BB$$r$*5v$72<$5$C$?1]JB;LCR$5$s$K46<U$7$^$9!#\e(B
+
+\e$B$^$?!"\e(BLaTeX \e$BMQ$NFbIt\e(B method \e$B$H\e(B message/partial \e$BMQ$N<+F07k9g\e(B method \e$B$rDs\e(B
+\e$B6!$7$F2<$5$C$?2,It<wCK$5$s!"\e(Btar archive \e$BMQ$NFbIt\e(B method \e$B$rDs6!$7$F2<$5$C\e(B
+\e$B$?>eLnGn$5$s$K46<U$7$^$9!#\e(B
+
+tm-edit \e$B$NA0?H$H$J$C$?\e(B `mime.el' \e$B$r=q$-!"$=$NG[I[$H2~B$$r$*5v$72<$5$C$?!"\e(B
+\e$BG_ED@/?.$5$s$K46<U$7$^$9!#\e(Btm-edit \e$B$N\e(B user interface \e$B$N4pK\E*$J@_7W$OG_ED\e(B
+\e$B$5$s$N<j$K$h$k$b$N$G!"$H$F$bNI$$@_7W$G$"$C$?$H;W$$$^$9!#\e(B
+
+tm \e$B$N4v$D$+$N\e(B module \e$B$N\e(B maintainer \e$B$r0z$-<u$1$F2<$5$C$?>.NS=$J?$5$s!"H`\e(B
+\e$B$O$^$?!"\e(BRFC \e$B$KBP$9$kE,9g@-$KBP$7$F1T$$;XE&$rB?!99T$&$3$H$G\e(B tm \e$B$NF0:n$N5,\e(B
+\e$B3J$KBP$9$kCi<BEY$r>e$2$k$N$KHs>o$J9W8%$r9T$$$^$7$?!#\e(B
+
+\e$B$^$?!"\e(Btm-vm \e$B$N\e(B maintainer \e$B$r0z$-<u$1$F2<$5$C$?\e(B Oscar Figueiredo \e$B$5$s$K46\e(B
+\e$B<U$7$^$9!#@:NOE*$K\e(B tm-vm \e$B$r2~NI$7!"$^$?!"N)GI$J@bL@=q$r=q$$$F2<$5$$$^$7\e(B
+\e$B$?!#\e(B
+
+\e$B:G8e$K!"\e(Bbeta test \e$B$K6(NO$7$F2<$5$C$?F|K\8lHG!"1Q8lHGAPJ}$N\e(B tm mailing
+list \e$B$N\e(B member \e$B$K46<U$7$^$9!#$^$?!"\e(Bpatch \e$B$rAw$C$F2<$5$C$?A4$F$NJ}$K46<U\e(B
+\e$B$7$^$9!#\e(B
+
+
+
+\1f
+File: tm-ja.info, Node: Concept Index, Next: Variable Index, Prev: Acknowledgments, Up: Top
\e$B35G0:w0z\e(B
********
* Menu:
-* ANSI X3.4:1986: ASCII. 9.
-* application: media type. 20.
-* application/pgp: PGP-kazu. 9.
-* ASCII: ASCII. 9.
-* ASCII: us-ascii. 16.
-* audio: media type. 16.
-* BBDB: setting for VM. 15.
-* BIG5: cn-big5. 13.
-* binary: 8bit. 35.
-* binary: binary. 6.
-* binary data: binary. 14.
-* charset-edition: RFC 1922. 11.
-* charset-extension: RFC 1922. 11.
-* CNS 11643:1992: CNS 11643. 35.
-* CNS 11643-1992: CNS 11643. 35.
-* content-type/subtype: media type. 26.
-* Emacs/mule: MULE. 21.
-* encapsulation: RFC 1153. 6.
-* encapsulation: RFC 934. 6.
-* euc-kr: euc-kr. 14.
-* Experimental: Content-Disposition. 8.
-* external
-* FTP: FTP. 8.
-* GB 2312: GB 2312. 11.
-* GB 2312:1980: GB 2312. 11.
-* GB 8565.2: GB 8565.2. 9.
-* GB 8565.2:1988: GB 8565.2. 9.
-* gnus-mime: tm-MUA. 16.
-* image: media type. 14.
-* Informational: hz-gb2312. 14.
-* Informational: hz-gb2312. 19.
-* Informational: iso-2022-jp-2. 10.
-* Informational: iso-8859-7. 13.
-* Informational: PGP. 16.
-* Informational: RFC 1557. 8.
-* Informational: RFC 1922. 14.
-* internal method: method. 7.
-* Internet
-* Internet
-* ISO 2022: ISO 2022. 11.
-* ISO 646: ISO 646. 11.
-* ISO 8859-1: ISO 8859-1. 8.
-* ISO 8859-1:1987: ISO 8859-1. 8.
-* ISO 8859-2: ISO 8859-2. 8.
-* ISO 8859-2:1987: ISO 8859-2. 8.
-* ISO 8859-3: ISO 8859-3. 5.
-* ISO 8859-3:1988: ISO 8859-3. 5.
-* ISO 8859-4: ISO 8859-4. 5.
-* ISO 8859-4:1988: ISO 8859-4. 5.
-* ISO 8859-5: ISO 8859-5. 7.
-* ISO 8859-5:1988: ISO 8859-5. 7.
-* ISO 8859-6: ISO 8859-6. 5.
-* ISO 8859-6:1987: ISO 8859-6. 5.
-* ISO 8859-7: ISO 8859-7. 7.
-* ISO 8859-7:1987: ISO 8859-7. 7.
-* ISO 8859-8: ISO 8859-8. 5.
-* ISO 8859-8:1988: ISO 8859-8. 5.
-* ISO 8859-9: ISO 8859-9. 5.
-* ISO 8859-9:1990: ISO 8859-9. 5.
-* iso-2022-jp: iso-2022-jp. 18.
-* iso-2022-jp-2: iso-2022-jp-2. 10.
-* iso-8859-7: iso-8859-7. 13.
-* ISO/IEC 2022:1994: ISO 2022. 11.
-* ISO/IEC 646:1991: ISO 646. 11.
-* JIS
-* JIS X 0201-1976:: JIS X0201. 11.
-* JIS C6220-1976: JIS X0201. 10.
-* JIS C6226:1978: JIS X0208. 18.
-* JIS X 0201:1997? draft: JIS X0201. 19.
-* JIS X 0208:1997? draft: JIS X0208. 32.
-* JIS X0201-1976: JIS X0201. 11.
-* JIS X0201-1997?: JIS X0201. 19.
-* JIS X0208-1978: JIS X0208. 18.
-* JIS X0208-1983,1990: JIS X0208. 23.
-* JIS X0208:1983,1990: JIS X0208. 23.
-* JIS X0208-1997?: JIS X0208. 32.
-* KS C 5601:1987: KS C5601. 8.
-* KS C 5861:1992: euc-kr. 14.
-* KS C5601: KS C5601. 8.
-* message: media type. 24.
-* message header: RFC 822. 6.
-* Message Transfer Agent: MTA. 5.
-* Message User Agent: MUA. 5.
-* mime-setup: mime-setup. 6.
-* mule: MULE. 20.
-* MULE: MULE. 21.
-* MULE: MULE. 7.
-* multipart: media type. 22.
-* multipart: multipart. 10.
-* multipart/digest: multipart/digest. 9.
-* multipart/encrypted: Security multipart. 9.
-* multipart/signed: Security multipart. 7.
-* Multipurpose Internet Mail Extensions: MIME. 5.
-* pad: Base64. 10.
-* parameter: Content-Type field. 21.
-* PGP: PGP. 16.
-* PGP-kazu: PGP-kazu. 7.
-* PGP/MIME: PGP/MIME. 20.
-* RFC
-* RFC 1036: RFC 1036. 9.
-* RFC 1153: RFC 1153. 16.
-* RFC 1468: iso-2022-jp. 18.
-* RFC 1489: koi8-r. 13.
-* RFC 1554: iso-2022-jp-2. 10.
-* RFC 1557: RFC 1557. 8.
-* RFC 1806: Content-Disposition. 8.
-* RFC 1842: hz-gb2312. 14.
-* RFC 1843: hz-gb2312. 19.
-* RFC 1847: Security multipart. 14.
-* RFC 1896: text/enriched. 8.
-* RFC 1922: RFC 1922. 14.
-* RFC 1947: iso-8859-7. 13.
-* RFC 1991: PGP. 16.
-* RFC 2015: PGP/MIME. 20.
-* RFC 2045: RFC 2045. 5.
-* RFC 2046: RFC 2046. 5.
-* RFC 2047: encoded-word. 8.
-* RFC 2048: RFC 2048. 5.
-* RFC 2049: RFC 2049. 5.
-* RFC 821: RFC 821. 8.
-* RFC 822: RFC 822. 14.
-* RFC 934: RFC 934. 13.
-* RFC 959: FTP. 8.
-* Security multipart: Security multipart. 14.
-* signature: signature. 6.
-* SMTP: RFC 821. 5.
-* SMTP: RFC 821. 8.
-* Standards Track: encoded-word. 8.
-* Standards Track: PGP/MIME. 20.
-* Standards Track: RFC 2045. 5.
-* Standards Track: RFC 2046. 5.
-* Standards Track: RFC 2048. 5.
-* Standards Track: RFC 2049. 5.
-* Standards Track: Security multipart. 14.
-* STD 10: RFC 821. 8.
-* STD 11: RFC 822. 14.
-* STD 9: FTP. 8.
-* subtype: Content-Type field. 20.
-* subtype: media type. 7.
-* text: media type. 12.
-* text/enriched: text/enriched. 8.
-* text/plain: text/plain. 10.
-* text/richtext: text/enriched. 6.
-* tm \e$BBg@9$j\e(B package: tm-MUA. 8.
-* tm-gnus: tm-MUA. 14.
-* tm-mh-e: tm-MUA. 12.
-* tm-rmail: tm-MUA. 20.
-* tm-setup: tm-setup. 6.
-* tm-vm: tm-MUA. 18.
-* type: Content-Type field. 20.
-* type: media type. 6.
-* us-ascii: us-ascii. 13.
-* USENET: RFC 1036. 9.
-* video: media type. 18.
-* vm: setting for VM. 6.
-* XEmacs/mule: MULE. 22.
-* x-token: media type. 34.
-2047: encoded-word. 6.
-mail: RFC 822. 11.
-message: RFC 822. 11.
-method: method. 8.
-X0201: JIS X0201. 10.
+* ANSI X3.4:1986: ASCII. 4.
+* application: media type. 4.
+* application/pgp: PGP-kazu. 4.
+* ASCII: ASCII. 4.
+* ASCII: us-ascii. 4.
+* audio: media type. 4.
+* BBDB: setting for VM. 4.
+* BIG5: cn-big5. 4.
+* binary: 8bit. 4.
+* binary: binary. 4.
+* binary data: binary. 4.
+* charset-edition: RFC 1922. 4.
+* charset-extension: RFC 1922. 4.
+* CNS 11643:1992: CNS 11643. 4.
+* CNS 11643-1992: CNS 11643. 4.
+* content-type/subtype: media type. 4.
+* Emacs/mule: MULE. 4.
+* encapsulation: RFC 1153. 4.
+* encapsulation: RFC 934. 4.
+* euc-kr: euc-kr. 4.
+* Experimental: Content-Disposition. 4.
+* external method: method. 4.
+* FTP: FTP. 4.
+* GB 2312: GB 2312. 4.
+* GB 2312:1980: GB 2312. 4.
+* GB 8565.2: GB 8565.2. 4.
+* GB 8565.2:1988: GB 8565.2. 4.
+* gnus-mime: tm-MUA. 4.
+* image: media type. 4.
+* Informational: hz-gb2312. 4.
+* Informational: hz-gb2312. 4.
+* Informational: iso-2022-jp-2. 4.
+* Informational: iso-8859-7. 4.
+* Informational: PGP. 4.
+* Informational: RFC 1557. 4.
+* Informational: RFC 1922. 4.
+* internal method: method. 4.
+* Internet mail: RFC 822. 4.
+* Internet message: RFC 822. 4.
+* ISO 2022: ISO 2022. 4.
+* ISO 646: ISO 646. 4.
+* ISO 8859-1: ISO 8859-1. 4.
+* ISO 8859-1:1987: ISO 8859-1. 4.
+* ISO 8859-2: ISO 8859-2. 4.
+* ISO 8859-2:1987: ISO 8859-2. 4.
+* ISO 8859-3: ISO 8859-3. 4.
+* ISO 8859-3:1988: ISO 8859-3. 4.
+* ISO 8859-4: ISO 8859-4. 4.
+* ISO 8859-4:1988: ISO 8859-4. 4.
+* ISO 8859-5: ISO 8859-5. 4.
+* ISO 8859-5:1988: ISO 8859-5. 4.
+* ISO 8859-6: ISO 8859-6. 4.
+* ISO 8859-6:1987: ISO 8859-6. 4.
+* ISO 8859-7: ISO 8859-7. 4.
+* ISO 8859-7:1987: ISO 8859-7. 4.
+* ISO 8859-8: ISO 8859-8. 4.
+* ISO 8859-8:1988: ISO 8859-8. 4.
+* ISO 8859-9: ISO 8859-9. 4.
+* ISO 8859-9:1990: ISO 8859-9. 4.
+* iso-2022-jp: iso-2022-jp. 4.
+* iso-2022-jp-2: iso-2022-jp-2. 4.
+* iso-8859-7: iso-8859-7. 4.
+* ISO/IEC 2022:1994: ISO 2022. 4.
+* ISO/IEC 646:1991: ISO 646. 4.
+* JIS X 0201-1976:: JIS X0201. 4.
+* JIS C6220-1976: JIS X0201. 4.
+* JIS C6226:1978: JIS X0208. 4.
+* JIS X 0201:1997? draft: JIS X0201. 4.
+* JIS X 0208:1997? draft: JIS X0208. 4.
+* JIS X0201: JIS X0201. 4.
+* JIS X0201-1976: JIS X0201. 4.
+* JIS X0201-1997?: JIS X0201. 4.
+* JIS X0208-1978: JIS X0208. 4.
+* JIS X0208-1983,1990: JIS X0208. 4.
+* JIS X0208:1983,1990: JIS X0208. 4.
+* JIS X0208-1997?: JIS X0208. 4.
+* KS C 5601:1987: KS C5601. 4.
+* KS C 5861:1992: euc-kr. 4.
+* KS C5601: KS C5601. 4.
+* message: media type. 4.
+* message header: RFC 822. 4.
+* Message Transfer Agent: MTA. 4.
+* Message User Agent: MUA. 4.
+* mime-setup: mime-setup. 4.
+* MULE: MULE. 4.
+* MULE: MULE. 4.
+* mule: MULE. 4.
+* multipart: media type. 4.
+* multipart: multipart. 4.
+* multipart/digest: multipart/digest. 4.
+* multipart/encrypted: Security multipart. 4.
+* multipart/signed: Security multipart. 4.
+* Multipurpose Internet Mail Extensions: MIME. 4.
+* pad: Base64. 4.
+* parameter: Content-Type field. 4.
+* PGP: PGP. 4.
+* PGP-kazu: PGP-kazu. 4.
+* PGP/MIME: PGP/MIME. 4.
+* RFC 1036: RFC 1036. 4.
+* RFC 1153: RFC 1153. 4.
+* RFC 1468: iso-2022-jp. 4.
+* RFC 1489: koi8-r. 4.
+* RFC 1554: iso-2022-jp-2. 4.
+* RFC 1557: RFC 1557. 4.
+* RFC 1806: Content-Disposition. 4.
+* RFC 1842: hz-gb2312. 4.
+* RFC 1843: hz-gb2312. 4.
+* RFC 1847: Security multipart. 4.
+* RFC 1896: text/enriched. 4.
+* RFC 1922: RFC 1922. 4.
+* RFC 1947: iso-8859-7. 4.
+* RFC 1991: PGP. 4.
+* RFC 2015: PGP/MIME. 4.
+* RFC 2045: RFC 2045. 4.
+* RFC 2046: RFC 2046. 4.
+* RFC 2047: encoded-word. 4.
+* RFC 2047: encoded-word. 4.
+* RFC 2048: RFC 2048. 4.
+* RFC 2049: RFC 2049. 4.
+* RFC 821: RFC 821. 4.
+* RFC 822: RFC 822. 4.
+* RFC 934: RFC 934. 4.
+* RFC 959: FTP. 4.
+* Security multipart: Security multipart. 4.
+* signature: signature. 4.
+* SMTP: RFC 821. 4.
+* SMTP: RFC 821. 4.
+* Standards Track: encoded-word. 4.
+* Standards Track: PGP/MIME. 4.
+* Standards Track: RFC 2045. 4.
+* Standards Track: RFC 2046. 4.
+* Standards Track: RFC 2048. 4.
+* Standards Track: RFC 2049. 4.
+* Standards Track: Security multipart. 4.
+* STD 10: RFC 821. 4.
+* STD 11: RFC 822. 4.
+* STD 9: FTP. 4.
+* subtype: Content-Type field. 4.
+* subtype: media type. 4.
+* text: media type. 4.
+* text/enriched: text/enriched. 4.
+* text/plain: text/plain. 4.
+* text/richtext: text/enriched. 4.
+* tm \e$BBg@9$j\e(B package: tm-MUA. 4.
+* tm-gnus: tm-MUA. 4.
+* tm-mh-e: tm-MUA. 4.
+* tm-rmail: tm-MUA. 4.
+* tm-setup: tm-setup. 4.
+* tm-vm: tm-MUA. 4.
+* type: Content-Type field. 4.
+* type: media type. 4.
+* us-ascii: us-ascii. 4.
+* USENET: RFC 1036. 4.
+* video: media type. 4.
+* vm: setting for VM. 4.
+* XEmacs/mule: MULE. 4.
+* x-token: media type. 4.
\1f
\1f\f
Tag table:
Node: Top\7f152
-Node: Introduction\7f680
-Node: Glossary\7f1421
-Node: 7bit\7f4913
-Node: 8bit\7f6194
-Node: 94-character set\7f8214
-Node: 96-character set\7f8500
-Node: 94x94-character set\7f8780
-Node: ASCII\7f9097
-Node: Base64\7f9527
-Node: binary\7f10225
-Node: cn-gb\7f10780
-Node: cn-big5\7f11259
-Node: CNS 11643\7f11902
-Node: Coded character set\7f12672
-Node: Code extension\7f13005
-Node: Content-Disposition\7f13363
-Node: Content-Type field\7f13812
-Node: Emacs\7f14907
-Node: encoded-word\7f15141
-Node: encapsulation\7f15563
-Node: euc-kr\7f15858
-Node: FTP\7f16375
-Node: GB 2312\7f16660
-Node: GB 8565.2\7f17222
-Node: Graphic character set\7f17713
-Node: hz-gb2312\7f17977
-Node: ISO 2022\7f18798
-Node: iso-2022-cn\7f19428
-Node: iso-2022-cn-ext\7f19911
-Node: iso-2022-jp\7f20590
-Node: iso-2022-jp-2\7f21305
-Node: iso-2022-kr\7f21714
-Node: ISO 646\7f22147
-Node: ISO 8859-1\7f22822
-Node: iso-8859-1\7f23253
-Node: ISO 8859-2\7f23698
-Node: iso-8859-2\7f24132
-Node: ISO 8859-3\7f24571
-Node: ISO 8859-4\7f24888
-Node: ISO 8859-5\7f25205
-Node: iso-8859-5\7f25614
-Node: ISO 8859-6\7f26056
-Node: ISO 8859-7\7f26375
-Node: iso-8859-7\7f26779
-Node: ISO 8859-8\7f27329
-Node: ISO 8859-9\7f27648
-Node: ISO-IR-165\7f27965
-Node: JIS X0201\7f28487
-Node: JIS C6226\7f29390
-Node: JIS X0208\7f29682
-Node: JIS X0212\7f31581
-Node: koi8-r\7f31940
-Node: KS C5601\7f32438
-Node: media type\7f32850
-Node: message\7f34260
-Node: message/rfc822\7f34525
-Node: method\7f34833
-Node: MIME\7f35184
-Node: MIME charset\7f36406
-Node: MTA\7f36982
-Node: MUA\7f37196
-Node: MULE\7f37370
-Node: multipart\7f38233
-Node: multipart/alternative\7f39098
-Node: multipart/digest\7f39403
-Node: multipart/encrypted\7f40065
-Node: multipart/mixed\7f40395
-Node: multipart/parallel\7f40688
-Node: multipart/signed\7f40975
-Node: PGP\7f41271
-Node: PGP-kazu\7f42107
-Node: PGP/MIME\7f43513
-Node: Quoted-Printable\7f44546
-Node: RFC 821\7f45312
-Node: RFC 822\7f45592
-Node: RFC 934\7f46076
-Node: RFC 1036\7f46531
-Node: RFC 1153\7f46987
-Node: RFC 1557\7f47486
-Node: RFC 1922\7f47877
-Node: RFC 2045\7f48541
-Node: RFC 2046\7f48852
-Node: RFC 2048\7f49141
-Node: RFC 2049\7f49456
-Node: plain text\7f49770
-Node: Security multipart\7f50045
-Node: text/enriched\7f50680
-Node: text/plain\7f51122
-Node: tm-kernel\7f51610
-Node: tm-MUA\7f52115
-Node: us-ascii\7f52634
-Node: Setting\7f53300
-Node: mime-setup\7f53980
-Node: signature\7f54602
-Node: Notice about GNUS\7f56360
-Node: tm-setup\7f57512
-Node: setting for VM\7f58353
-Node: manual setting\7f58719
-Node: Bug report\7f59274
-Node: Concept Index\7f60884
-Node: Variable Index\7f70407
+Node: Introduction\7f721
+Node: Glossary\7f1462
+Node: 7bit\7f4992
+Node: 8bit\7f6273
+Node: 94-character set\7f8293
+Node: 96-character set\7f8579
+Node: 94x94-character set\7f8859
+Node: ASCII\7f9176
+Node: Base64\7f9606
+Node: binary\7f10304
+Node: cn-gb\7f10859
+Node: cn-big5\7f11338
+Node: CNS 11643\7f11981
+Node: Coded character set\7f12751
+Node: Code extension\7f13084
+Node: Content-Disposition\7f13442
+Node: Content-Type field\7f13891
+Node: Emacs\7f14986
+Node: encoded-word\7f15220
+Node: encapsulation\7f15642
+Node: entity\7f15937
+Node: euc-kr\7f16228
+Node: FTP\7f16738
+Node: GB 2312\7f17023
+Node: GB 8565.2\7f17585
+Node: Graphic character set\7f18076
+Node: hz-gb2312\7f18340
+Node: ISO 2022\7f19161
+Node: iso-2022-cn\7f19791
+Node: iso-2022-cn-ext\7f20274
+Node: iso-2022-jp\7f20953
+Node: iso-2022-jp-2\7f21663
+Node: iso-2022-kr\7f22072
+Node: ISO 646\7f22505
+Node: ISO 8859-1\7f23180
+Node: iso-8859-1\7f23611
+Node: ISO 8859-2\7f24056
+Node: iso-8859-2\7f24490
+Node: ISO 8859-3\7f24929
+Node: ISO 8859-4\7f25246
+Node: ISO 8859-5\7f25563
+Node: iso-8859-5\7f25972
+Node: ISO 8859-6\7f26414
+Node: ISO 8859-7\7f26733
+Node: iso-8859-7\7f27137
+Node: ISO 8859-8\7f27687
+Node: ISO 8859-9\7f28006
+Node: ISO-IR-165\7f28323
+Node: JIS X0201\7f28845
+Node: JIS C6226\7f29748
+Node: JIS X0208\7f30040
+Node: JIS X0212\7f31939
+Node: koi8-r\7f32298
+Node: KS C5601\7f32796
+Node: media type\7f33208
+Node: message\7f34616
+Node: message/rfc822\7f34881
+Node: method\7f35189
+Node: MIME\7f35540
+Node: MIME charset\7f36764
+Node: MTA\7f37340
+Node: MUA\7f37554
+Node: MULE\7f37729
+Node: multipart\7f38592
+Node: multipart/alternative\7f39457
+Node: multipart/digest\7f39762
+Node: multipart/encrypted\7f40424
+Node: multipart/mixed\7f40754
+Node: multipart/parallel\7f41047
+Node: multipart/signed\7f41334
+Node: PGP\7f41630
+Node: PGP-kazu\7f42466
+Node: PGP/MIME\7f43872
+Node: Quoted-Printable\7f44905
+Node: RFC 821\7f45671
+Node: RFC 822\7f45951
+Node: RFC 934\7f46435
+Node: RFC 1036\7f46888
+Node: RFC 1153\7f47344
+Node: RFC 1557\7f47841
+Node: RFC 1922\7f48232
+Node: RFC 2045\7f48897
+Node: RFC 2046\7f49208
+Node: RFC 2048\7f49497
+Node: RFC 2049\7f49812
+Node: plain text\7f50126
+Node: Security multipart\7f50401
+Node: text/enriched\7f51037
+Node: text/plain\7f51479
+Node: tm-kernel\7f51984
+Node: tm-MUA\7f52489
+Node: us-ascii\7f53008
+Node: Setting\7f53674
+Node: mime-setup\7f54354
+Node: signature\7f54975
+Node: Notice about GNUS\7f56733
+Node: tm-setup\7f57885
+Node: setting for VM\7f58725
+Node: manual setting\7f59091
+Node: Bug report\7f59646
+Node: Acknowledgments\7f61258
+Node: Concept Index\7f62898
+Node: Variable Index\7f72297
\1f
End tag table
<!doctype sinfo system>
-<!-- $Id: tm-ja.sgml,v 7.1 1996/12/23 21:25:12 morioka Exp $ -->
+<!-- $Id: tm-ja.sgml,v 7.5 1996/12/25 18:38:38 morioka Exp $ -->
<head>
-<title>tm 7.98 Manual\e$B!JF|K\8lHG!K\e(B
+<title>tm 7.100 Manual\e$B!JF|K\8lHG!K\e(B
<author>\e$B<i2,\e(B \e$BCNI'\e(B <mail>morioka@jaist.ac.jp</mail>
-<date>1996/12/24
+<date>1996/12/25
<toc>
</head>
<cf node="message/rfc822">
+<h3> Entity
+<node> entity
+<p>
+\e$B$"$k\e(B message \e$B$b$7$/$O\e(B <dref>multipart</dref> message \e$B$N#1$D$N\e(B part \e$B$N\e(B
+header \e$B$H\e(B body \e$B$rJ;$;$?$b$N!#\e(B
+
+<memo>
+<p>
+\e$B$3$3$G$O\e(B part \e$B$H8F$V$3$H$b$"$k!#\e(B
+</memo>
+
+
<h3> euc-kr
<node> euc-kr
<p>
\e$BF|K\8l$rI=8=$9$k$?$a$N\e(B <dref>MIME charset</dref> \e$B$N0l$D!#\e(B
<p>
\e$B8E$$\e(B <dref>ISO 2022</dref> \e$B$K4p$$$F\e(B <dref>ASCII</dref>, JIS
-X0201-Latin, <a node="JIS C6226-1978">JIS X0208-1978</a>, <a node="JIS
+X0201-Latin, <a node="JIS C6226">JIS X0208-1978</a>, <a node="JIS
X0208">JIS X0208-1983</a> \e$B$r@Z$jBX$($k\e(B <dref>7bit</dref> \e$BJ8;zId9f!#\e(B
<p>
RFC 1468 \e$B$GDj5A$5$l$F$$$k!#\e(B
number="ISO 8859-9" year="1990">
-<h3> ISO-IR-165, CCITT Extended GB <node> ISO-IR-165
+<h3> ISO-IR-165, CCITT Extended GB
+<node> ISO-IR-165
<p>
CCITT \e$B$,EPO?$7$?!"Cf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=\e(B
\e$B8=$9$k$?$a$N
\e(B<a node="94x94-character set">94
\e$B!_
\e(B94
\e$BJ8;z=89g
\e(B</a>
\e$B!#
\e(B
<p>
-<dref>GB 2312</dref>
\e$B$H
\e(B <a node="GB 8865.2">GB 8565
\e$BI=#2
\e(B</a>
\e$B$K
\e(B 150
\e$BJ8
\e(B
+<dref>GB 2312</dref>
\e$B$H
\e(B <a node="GB 8565.2">GB 8565
\e$BI=#2
\e(B</a>
\e$B$K
\e(B 150
\e$BJ8
\e(B
\e$B;z$[$I$rDI2C$7$?$b$N$i$7$$!#\e(B
<p>
<dref>ISO 2022</dref> \e$B$G$N=*C<\e(B byte \e$B$O\e(B 04/05 (`E') \e$B$G$"$k!#\e(B
<dref>RFC 2046</dref> \e$B$GDj5A$5$l$?!"\e(B<dref>plain text</dref> \e$B$rI=8=$9$k\e(B
\e$B$?$a$N\e(B <dref>media type</dref>.
<p>
-\e$BHs\e(B MIME message \e$B$J$I$N\e(B content-type \e$B$,Dj5A$5$l$J$$\e(B entity \e$B$O\e(B
-<dref>MIME charset</dref> \e$B$,\e(B <dref>us-ascii</dref> \e$B$G$"$k\e(B
+\e$BHs\e(B MIME message \e$B$J$I$N\e(B content-type \e$B$,Dj5A$5$l$J$$\e(B <dref>entity</dref>
+\e$B$O\e(B <dref>MIME charset</dref> \e$B$,\e(B <dref>us-ascii</dref> \e$B$G$"$k\e(B
<concept>text/plain</concept> \e$B$N\e(B entity \e$B$G$"$k$H8+Pv$5$l$k$3$H$K$J$C$F\e(B
\e$B$$$k!#\e(B
\e$B$F2<$5$$!#\e(B(^_^)
+<h1> \e$B<U<-\e(B
+<node> Acknowledgments
+<p>
+\e$B;d$,\e(B tm-view \e$B$r:G=i$K:n$C$?;~$K!"87$7$$CmJ8$HM-1W$J=u8@$r2<$5$j!"$=$N\e(B
+\e$B@_7W$KB?Bg$JM?$($i$l$?>#C+J]Gn$5$s$K46<U$7$^$9!#\e(B
+<p>
+<file>tm-ew-d.el</file> \e$B$H\e(B <file>mel-b.el</file> \e$B$NA0?H$KEv$?$k\e(B
+<file>mime.el</file> \e$B$r=q$-!"$=$NG[I[$H2~B$$r$*5v$72<$5$C$?1]JB;LCR$5\e(B
+\e$B$s$K46<U$7$^$9!#\e(B
+<p>
+\e$B$^$?!"\e(BLaTeX \e$BMQ$NFbIt\e(B method \e$B$H\e(B message/partial \e$BMQ$N<+F07k9g\e(B method \e$B$r\e(B
+\e$BDs6!$7$F2<$5$C$?2,It<wCK$5$s!"\e(Btar archive \e$BMQ$NFbIt\e(B method \e$B$rDs6!$7$F2<\e(B
+\e$B$5$C$?>eLnGn$5$s$K46<U$7$^$9!#\e(B
+<p>
+tm-edit \e$B$NA0?H$H$J$C$?\e(B <file>mime.el</file> \e$B$r=q$-!"$=$NG[I[$H2~B$$r$*\e(B
+\e$B5v$72<$5$C$?!"G_ED@/?.$5$s$K46<U$7$^$9!#\e(Btm-edit \e$B$N\e(B user interface \e$B$N4p\e(B
+\e$BK\E*$J@_7W$OG_ED$5$s$N<j$K$h$k$b$N$G!"$H$F$bNI$$@_7W$G$"$C$?$H;W$$$^$9!#\e(B
+<p>
+tm \e$B$N4v$D$+$N\e(B module \e$B$N\e(B maintainer \e$B$r0z$-<u$1$F2<$5$C$?>.NS=$J?$5$s!"\e(B
+\e$BH`$O$^$?!"\e(BRFC \e$B$KBP$9$kE,9g@-$KBP$7$F1T$$;XE&$rB?!99T$&$3$H$G\e(B tm \e$B$NF0:n\e(B
+\e$B$N5,3J$KBP$9$kCi<BEY$r>e$2$k$N$KHs>o$J9W8%$r9T$$$^$7$?!#\e(B
+<p>
+\e$B$^$?!"\e(Btm-vm \e$B$N\e(B maintainer \e$B$r0z$-<u$1$F2<$5$C$?\e(B Oscar Figueiredo \e$B$5$s$K\e(B
+\e$B46<U$7$^$9!#@:NOE*$K\e(B tm-vm \e$B$r2~NI$7!"$^$?!"N)GI$J@bL@=q$r=q$$$F2<$5$$\e(B
+\e$B$^$7$?!#\e(B
+<p>
+\e$B:G8e$K!"\e(Bbeta test \e$B$K6(NO$7$F2<$5$C$?F|K\8lHG!"1Q8lHGAPJ}$N\e(B tm mailing
+list \e$B$N\e(B member \e$B$K46<U$7$^$9!#$^$?!"\e(Bpatch \e$B$rAw$C$F2<$5$C$?A4$F$NJ}$K46\e(B
+\e$B<U$7$^$9!#\e(B
+
+
<h1> \e$B35G0:w0z\e(B
<node> Concept Index
\input texinfo.tex
@setfilename tm-ja.info
-@settitle{tm 7.98 Manual\e$B!JF|K\8lHG!K\e(B}
+@settitle{tm 7.100 Manual\e$B!JF|K\8lHG!K\e(B}
@titlepage
-@title tm 7.98 Manual\e$B!JF|K\8lHG!K\e(B
+@title tm 7.100 Manual\e$B!JF|K\8lHG!K\e(B
@author \e$B<i2,\e(B \e$BCNI'\e(B <morioka@@jaist.ac.jp>
-@subtitle 1996/12/24
+@subtitle 1996/12/25
@end titlepage
@node Top, Introduction, (dir), (dir)
-@top tm 7.98 Manual\e$B!JF|K\8lHG!K\e(B
+@top tm 7.100 Manual\e$B!JF|K\8lHG!K\e(B
@ifinfo
* Introduction:: tm \e$B$C$F2?!)\e(B
* Setting:: \e$B@_Dj\e(B
* Bug report:: bug \e$BJs9p$N;EJ}\e(B
+* Acknowledgments:: \e$B<U<-\e(B
* Concept Index:: \e$B35G0:w0z\e(B
* Variable Index:: \e$BJQ?t:w0z\e(B
@end menu
* Emacs::
* encoded-word::
* encapsulation::
+* entity:: Entity
* euc-kr::
* FTP:: FTP
* GB 2312:: GB 2312-1980
* iso-8859-7::
* ISO 8859-8::
* ISO 8859-9::
-* ISO-IR-165:: ISO-IR-165, CCITT Extended GB
+* ISO-IR-165:: ISO-IR-165, CCITT Extended GB
* JIS X0201::
* JIS C6226:: JIS C6226-1978
* JIS X0208::
@node 8bit, 94-character set, 7bit, Glossary
@subsection 8bit
+@cindex binary
\e$B$3$3$G$O\e(B 0 \e$B$+$i\e(B 255 \e$B$N@0?t$r;X$9!#\e(B@refill
\e$B$^$?!"\e(B0 \e$B$+$i\e(B 31, 127 \e$B$*$h$S\e(B 128 \e$B$+$i\e(B 159 \e$B$GI=8=$5$l$k@)8fJ8;z$H\e(B 32 \e$B$GI=\e(B
\e$B8=$5$l$k6uGr$H\e(B 33 \e$B$+$i\e(B 126 \e$B$H\e(B 160 \e$B$+$i\e(B 255 \e$B$GI=8=$5$l$k?^7AJ8;z$+$i$J$k\e(B
-\e$BJ8;zNs$N$3$H$r\e(B ``8bit \e$B$NJ8;zNs\e(B'' \e$B$H8F$V!J$3$l$O\e(B ISO 2022 (@ref{ISO
-2022}) \e$B$N!V\e(B8 \e$BC10L7O!W$HF1MM!K!#\e(B@refill
+\e$BJ8;zNs$N$3$H$r\e(B ``8bit \e$B$NJ8;zNs\e(B'' \e$B$H8F$V!J$3$l$O\e(B ISO 2022 (@ref{ISO 2022}) \e$B$N!V\e(B8 \e$BC10L7O!W$HF1MM!K!#\e(B@refill
iso-8859-1 (@ref{iso-8859-1}) \e$B$d\e(B euc-kr (@ref{euc-kr}) \e$B$H$$$C$?Id9f2=J8\e(B
\e$B;z=89g$O\e(B 8bit \e$B$NJ8;zNs$G$"$k!#\e(B@refill
encode\e$B$9$kI,MQ$,$"$k!#\e(B@refill
\e$B$^$?!"$3$&$7$?M}M3$+$i!"#19T$,\e(B 999 byte \e$B0J>e$N9T$,B8:_$9$k2DG=@-$N$"$k\e(B
-data \e$B$O\e(B @cindex{binary}@strong{binary} (@ref{binary}) \e$B$H8F$V$3$H$K$9$k!#\e(B
+data \e$B$O\e(B @strong{binary} (@ref{binary}) \e$B$H8F$V$3$H$K$9$k!#\e(B@refill
\e$B$A$J$_$K!"\e(B7bit \e$B$GI=8=$G$-$k\e(B data \e$B$O\e(B 8bit \e$B$G$bI=8=$G$-$k!#$h$C$F!"\e(B
``8bit'' \e$B$H8@$C$?>l9g!"#19T$,\e(B 998 byte \e$B0J2<$NG$0U$N\e(B data \e$B$r;X$9$3$H$,\e(B
@node 94-character set, 96-character set, 8bit, Glossary
@subsection 94 \e$BJ8;z=89g\e(B
-33 \e$B$+$i\e(B 126 \e$B$NHO0O$N\e(B 1 byte \e$B$+$i$J$k\e(B \e$B?^7AJ8;z=89g\e(B(@ref{Graphic character
-set})\e$B!#\e(BASCII (@ref{ASCII}) \e$B$d\e(B JIS X0201-Latin \e$B$O$=$N0l<o!#\e(B
+33 \e$B$+$i\e(B 126 \e$B$NHO0O$N\e(B 1 byte \e$B$+$i$J$k\e(B \e$B?^7AJ8;z=89g\e(B(@ref{Graphic character set})\e$B!#\e(BASCII (@ref{ASCII}) \e$B$d\e(B JIS X0201-Latin \e$B$O$=$N0l<o!#\e(B
@node 96-character set, 94x94-character set, 94-character set, Glossary
@subsection 96 \e$BJ8;z=89g\e(B
-32 \e$B$+$i\e(B 127 \e$B$NHO0O$N\e(B 1 byte \e$B$+$i$J$k\e(B \e$B?^7AJ8;z=89g\e(B(@ref{Graphic character
-set})\e$B!#\e(BISO 8859 \e$B%7%j!<%:$O$=$N0l<o!#\e(B
+32 \e$B$+$i\e(B 127 \e$B$NHO0O$N\e(B 1 byte \e$B$+$i$J$k\e(B \e$B?^7AJ8;z=89g\e(B(@ref{Graphic character set})\e$B!#\e(BISO 8859 \e$B%7%j!<%:$O$=$N0l<o!#\e(B
@node 94x94-character set, ASCII, 96-character set, Glossary
@subsection 94\e$B!_\e(B94 \e$BJ8;z=89g\e(B
-33 \e$B$+$i\e(B 126 \e$B$NHO0O$N\e(B 2 byte \e$B$+$i$J$k\e(B \e$B?^7AJ8;z=89g\e(B(@ref{Graphic character
-set})\e$B!#\e(BJIS X0208 (@ref{JIS X0208}) \e$B$d\e(B GB 2312 (@ref{GB 2312}) \e$B$O$=$N0l<o!#\e(B
+33 \e$B$+$i\e(B 126 \e$B$NHO0O$N\e(B 2 byte \e$B$+$i$J$k\e(B \e$B?^7AJ8;z=89g\e(B(@ref{Graphic character set})\e$B!#\e(BJIS X0208 (@ref{JIS X0208}) \e$B$d\e(B GB 2312 (@ref{GB 2312}) \e$B$O$=$N0l<o!#\e(B
@node ASCII, Base64, 94x94-character set, Glossary
@subsection ASCII
+@cindex ANSI X3.4:1986
+@cindex ASCII
-\e$B%"%a%j%+O"K.$G;H$o$l$kJ8;z$rId9f2=$7$?\e(B 94 \e$BJ8;z=89g\e(B(@ref{94-character
-set})\e$B!#\e(BA-Z, a-z \e$B$N\e(B Latin \e$BJ8;z$H?t;z!"4v$D$+$N5-9f$+$i$J$k!#\e(BISO 646
+\e$B%"%a%j%+O"K.$G;H$o$l$kJ8;z$rId9f2=$7$?\e(B 94 \e$BJ8;z=89g\e(B(@ref{94-character set})\e$B!#\e(BA-Z, a-z \e$B$N\e(B Latin \e$BJ8;z$H?t;z!"4v$D$+$N5-9f$+$i$J$k!#\e(BISO 646
(@ref{ISO 646}) \e$B$N0l$D!#\e(B
-@cindex{ASCII}@cindex{ANSI X3.4:1986}
+
@noindent
[ASCII]
@quotation
@node Base64, binary, ASCII, Glossary
@subsection Base64
+@cindex pad
RFC 2045 (@ref{RFC 2045}) \e$B$GDj5A$5$l$F$$$k\e(B MIME (@ref{MIME}) \e$B$K$*$1$k\e(B
binary data (@ref{binary}) \e$B$N\e(B network \e$B$G$NJQ49K!$N#1$D!#\e(B@refill
\e$B!X\e(B64 \e$B?J?t!Y$H$$$&0UL#$G!"\e(B3 byte \e$B$N\e(B data \e$B$r\e(B 0 \e$B$+$i\e(B 63 \e$B$N?t$rI=$9\e(B ASCII
(@ref{ASCII}) 4 \e$BJ8;z$KJQ49$9$kJ}K!!#!J$b$7!"\e(B4 \e$BJ8;z$K$J$i$J$1$l$P\e(B
-@cindex{pad}@strong{pad} \e$B$H8F$P$l$k5M$aJ*$r$7$FD9$5$rD4@0$9$k!K\e(B@refill
+@strong{pad} \e$B$H8F$P$l$k5M$aJ*$r$7$FD9$5$rD4@0$9$k!K\e(B@refill
\e$B$3$N\e(B 65 \e$B<oN`$NJ8;z$O\e(B ASCII \e$B$H\e(B EBCDIC \e$B$N6&DLItJ,$+$iA*$P$l$F$*$j!"\e(B
Internet \e$B0J30$N\e(B network \e$B$r7PM3$9$k>l9g$G$b0BA4$KE>Aw$G$-$k$h$&$K@_7W$5\e(B
@node binary, cn-gb, Base64, Glossary
@subsection binary
+@cindex binary data
+@cindex binary
-\e$BG$0U$N\e(B byte \e$BNs$r\e(B @cindex{binary}@strong{binary} \e$B$H8F$V!#\e(B@refill
+\e$BG$0U$N\e(B byte \e$BNs$r\e(B @strong{binary} \e$B$H8F$V!#\e(B@refill
8bit (@ref{8bit}) \e$B$H0[$J$k$N$O\e(B data \e$B$K9T$N9=B$$r2>Dj$7$J$$$3$H$G$"$k!#\e(B
\e$B8F$V$3$H$K$9$k!#\e(B@refill
\e$B$A$J$_$K!"\e(B7bit (@ref{7bit}) \e$B$d\e(B 8bit \e$B$GI=8=$G$-$k\e(B data \e$B$O\e(B binary \e$B$G$bI=8=\e(B
-\e$B$G$-$k!#$h$C$F!"\e(B@cindex{binary data}@strong{binary data} \e$B$H8@$C$?>l9g!"\e(B
-\e$BG$0U$N\e(B data \e$B$r;X$9$3$H$,$"$k!#\e(B
+\e$B$G$-$k!#$h$C$F!"\e(B@strong{binary data} \e$B$H8@$C$?>l9g!"G$0U$N\e(B data \e$B$r;X$9$3\e(B
+\e$B$H$,$"$k!#\e(B
@node cn-gb, cn-big5, binary, Glossary
@node cn-big5, CNS 11643, cn-gb, Glossary
@subsection cn-big5, big5
+@cindex BIG5
\e$BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N\e(B
MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B@refill
(@ref{Coded character set})\e$B$G\e(B de-fact standard \e$B$G$"$k!#\e(BRFC 1922
(@ref{RFC 1922}) \e$B$GDj5A$5$l$F$$$k!#\e(B@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
\e$BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N\e(B
\e$B?^7AJ8;z=89g\e(B(@ref{Graphic character set})\e$B!#BfOQ$NI8=`!#8=:_!"\e(B94\e$B!_\e(B94
@noindent
\e$B$G$"$k!#\e(B
-@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
Content \e$B$NI=<($N;EJ}$d\e(B file \e$BL>$rI=8=$9$k$?$a$N\e(B field. MIME (@ref{MIME})
\e$B$N3HD%$N#1$D!#\e(B
-@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
media type (@ref{media type}) \e$B$d\e(B MIME charset (@ref{MIME charset}) \e$B$J$I\e(B
\e$B$N\e(B body \e$B$K4X$9$k>pJs$rI=8=$9$k$?$a$N\e(B field. RFC 2045 (@ref{RFC 2045})
Content-Type field \e$B$O\e(B
@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
@noindent
@node encoded-word, encapsulation, Emacs, Glossary
@subsection encoded-word
+@cindex RFC 2047
+@cindex Standards Track
+@cindex RFC 2047
+
+header \e$B$K$*$1$kHs\e(B ASCII (@ref{ASCII}) \e$BJ8;z$NI=8=!#\e(B@strong{RFC 2047} \e$B$GDj\e(B
+\e$B5A$5$l$F$$$k!#\e(B@refill
-header \e$B$K$*$1$kHs\e(B ASCII (@ref{ASCII}) \e$BJ8;z$NI=8=!#\e(B@cindex{RFC
-2047}@strong{RFC 2047} \e$B$GDj5A$5$l$F$$$k!#\e(B@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
Internet mail (@ref{RFC 822}) \e$B$rB>$N5-;v$K$^$k$4$HF~$l$kJ}K!!#\e(B@refill
-@node euc-kr, FTP, encapsulation, Glossary
+@node entity, euc-kr, encapsulation, Glossary
+@subsection Entity
+
+\e$B$"$k\e(B message \e$B$b$7$/$O\e(B multipart (@ref{multipart}) message \e$B$N#1$D$N\e(B part
+\e$B$N\e(B header \e$B$H\e(B body \e$B$rJ;$;$?$b$N!#\e(B
+
+@noindent
+@strong{[Memo]}
+@quotation
+
+\e$B$3$3$G$O\e(B part \e$B$H8F$V$3$H$b$"$k!#\e(B
+@end quotation
+
+
+
+@node euc-kr, FTP, entity, Glossary
@subsection euc-kr
+@cindex KS C 5861:1992
+@cindex euc-kr
\e$B4Z9q8l$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
RFC 1557 (@ref{RFC 1557}) \e$B$GDj5A$5$l$F$$$k!#\e(B@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
Internet \e$B$G\e(B file \e$B$rE>Aw$9$k$?$a$N\e(B protocol \e$B$N#1$D!#\e(BRFC 959 \e$B$GDj5A$5$l$F\e(B
\e$B$$$k!#\e(B@refill
-@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
\e$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=$9$?$a$N\e(B 94\e$B!_\e(B94 \e$BJ8;z\e(B
-\e$B=89g\e(B(@ref{94x94-character set})\e$B!#Cf9q$N9q2HI8=`!#\e(BISO 2022 (@ref{ISO
-2022}) \e$B$G$N=*C<\e(B byte \e$B$O\e(B 04/01 (`A').@refill
+\e$B=89g\e(B(@ref{94x94-character set})\e$B!#Cf9q$N9q2HI8=`!#\e(BISO 2022 (@ref{ISO 2022}) \e$B$G$N=*C<\e(B byte \e$B$O\e(B 04/01 (`A').@refill
\e$B$3$l$O\e(B GB \e$B$K$*$1$k4pK\=8$G$"$k!#\e(B
-@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
\e$BCf9q8l$N$?$a$NJd=u?^7AJ8;z=89g\e(B(@ref{Graphic character set})\e$B!#Cf9q$N9q2H\e(B
\e$BI8=`!#\e(BGB 2312 (@ref{GB 2312}) \e$B$N6u$-ItJ,$KJd=<$9$k$h$&$KDj5A$5$l$?$i$7$$!#\e(B
-@cindex{GB 8565.2}@cindex{GB 8565.2:1988}
+
@noindent
[GB 8565.2]
@quotation
@node hz-gb2312, ISO 2022, Graphic character set, Glossary
@subsection hz-gb2312
+@cindex RFC 1843
+@cindex Informational
+@cindex RFC 1842
+@cindex Informational
\e$BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N\e(B MIME
charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B@refill
RFC 1842, 1843 \e$B$GDj5A$5$l$F$$$k!#\e(B
-@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
\e$BId9f2=J8;z=89g$N9=B$$HId9f3HD%\e(B(@ref{Code extension})\e$BK!$rDj$a$?9q:]I8=`!#\e(B
\e$B$3$l$rMQ$$$FJ#?t$N?^7AJ8;z=89g\e(B(@ref{Graphic character set})\e$B$rAH9g$;$F\e(B
-7bit (@ref{7bit}) \e$B$J$$$7\e(B 8bit (@ref{8bit}) \e$B$N\e(B \e$BId9f2=J8;z=89g\e(B(@ref{Coded
-character set}) \e$B$r:n$k$3$H$,$G$-$k!#\e(B
+7bit (@ref{7bit}) \e$B$J$$$7\e(B 8bit (@ref{8bit}) \e$B$N\e(B \e$BId9f2=J8;z=89g\e(B(@ref{Coded character set}) \e$B$r:n$k$3$H$,$G$-$k!#\e(B
+
-@cindex{ISO 2022}@cindex{ISO/IEC 2022:1994}
@noindent
[ISO 2022]
@quotation
ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F\e(B ASCII (@ref{ASCII}) \e$B$K\e(B GB 2312
(@ref{GB 2312}), CNS 11643 plain 1 .. 7 (@ref{CNS 11643}), ISO-IR-165
-(@ref{ISO-IR-165}) \e$BEy$r\e(B 7bit (@ref{7bit}) \e$B$GId9f3HD%\e(B (@ref{Code
-extension})\e$B$7$F$$$k!#\e(B@refill
+(@ref{ISO-IR-165}) \e$BEy$r\e(B 7bit (@ref{7bit}) \e$B$GId9f3HD%\e(B (@ref{Code extension})\e$B$7$F$$$k!#\e(B@refill
RFC 1922 (@ref{RFC 1922}) \e$B$GDj5A$5$l$F$$$k!#\e(B@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
\e$BF|K\8l$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N0l$D!#\e(B
\e$B8E$$\e(B ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F\e(B ASCII (@ref{ASCII}), JIS
-X0201-Latin, JIS X0208-1978 (@ref{JIS C6226-1978}), JIS X0208-1983
-(@ref{JIS X0208}) \e$B$r@Z$jBX$($k\e(B 7bit (@ref{7bit}) \e$BJ8;zId9f!#\e(B@refill
+X0201-Latin, JIS X0208-1978 (@ref{JIS C6226}), JIS X0208-1983 (@ref{JIS X0208}) \e$B$r@Z$jBX$($k\e(B 7bit (@ref{7bit}) \e$BJ8;zId9f!#\e(B@refill
RFC 1468 \e$B$GDj5A$5$l$F$$$k!#\e(B@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
-iso-2022-jp (@ref{iso-2022-jp}) \e$B$r3HD%$7$?\e(B MIME charset (@ref{MIME
-charset}) \e$B$N0l$D!#\e(B@refill
+iso-2022-jp (@ref{iso-2022-jp}) \e$B$r3HD%$7$?\e(B MIME charset (@ref{MIME charset}) \e$B$N0l$D!#\e(B@refill
RFC 1554 \e$B$GDj5A$5$l$F$$$k!#\e(B
-@cindex{iso-2022-jp-2}@cindex{Informational}@cindex{RFC 1554}
+
@noindent
[iso-2022-jp-2: RFC 1554]
@quotation
@node ISO 646, ISO 8859-1, iso-2022-kr, Glossary
@subsection ISO 646
+@cindex ISO/IEC 646:1991
+@cindex ISO 646
\e$B3F9q$G6&DL$K;H$($k:G>.8BEY$N?^7AJ8;z=89g\e(B(@ref{Graphic character set})\e$B$r\e(B
\e$BDj$a$?$b$N!#\e(B94 \e$BJ8;z=89g\e(B (@ref{94-character set})\e$B$N#1$D!#\e(BISO 646 IRV\e$B!J9q\e(B
\e$B:]4p=`HG!K$r85$K4v$D$+$NJ8;z$O3F9q$G0c$&J8;z$r3dEv$k$3$H$r5v$7$F$$$F!"4v\e(B
\e$B$D$+$NJQ<o$,B8:_$9$k!#\e(BASCII (@ref{ASCII}) \e$B$d\e(B JIS X0201-Latin \e$B$O$=$N0l<o!#\e(B
-@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
\e$B@>2$=t8l$GMQ$$$i$l$k3HD%\e(B Latin \e$BJ8;z$d5-9f$+$i$J$k\e(B 96 \e$BJ8;z=89g\e(B
(@ref{96-character set})\e$B!#\e(B
-@cindex{ISO 8859-1}@cindex{ISO 8859-1:1987}
+
@noindent
[ISO 8859-1]
@quotation
\e$B@>2$=t8l$J$I$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F!"\e(BASCII (@ref{ASCII}) \e$B$K\e(B ISO 8859-1
-(@ref{ISO 8859-1}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code
-extension})\e$B$7$F$$$k!#\e(B@refill
+(@ref{ISO 8859-1}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code extension})\e$B$7$F$$$k!#\e(B@refill
RFC 2046 (@ref{RFC 2046}) \e$B$GDj5A$5$l$F$$$k!#\e(B
@node ISO 8859-2, iso-8859-2, iso-8859-1, Glossary
@subsection ISO 8859-2
+@cindex ISO 8859-2:1987
+@cindex ISO 8859-2
\e$BEl2$=t8l$GMQ$$$i$l$k3HD%\e(B Latin \e$BJ8;z$d5-9f$+$i$J$k\e(B 96 \e$BJ8;z=89g\e(B
(@ref{96-character set})\e$B!#\e(B
-@cindex{ISO 8859-2}@cindex{ISO 8859-2:1987}
+
@noindent
[ISO 8859-2]
@quotation
\e$BEl2$=t8l$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F!"\e(BASCII (@ref{ASCII}) \e$B$K\e(B ISO 8859-2
-(@ref{ISO 8859-2}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code
-extension})\e$B$7$F$$$k!#\e(B@refill
+(@ref{ISO 8859-2}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code extension})\e$B$7$F$$$k!#\e(B@refill
RFC 2046 (@ref{RFC 2046}) \e$B$GDj5A$5$l$F$$$k!#\e(B
@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
\e$B%-%j%kJ8;z$d5-9f$+$i$J$k\e(B 96 \e$BJ8;z=89g\e(B(@ref{96-character set})\e$B!#\e(B
-@cindex{ISO 8859-5}@cindex{ISO 8859-5:1988}
+
@noindent
[ISO 8859-5]
@quotation
\e$B%-%j%kJ8;z$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F!"\e(BASCII (@ref{ASCII}) \e$B$K\e(B ISO 8859-5
-(@ref{ISO 8859-5}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code
-extension})\e$B$7$F$$$k!#\e(B@refill
+(@ref{ISO 8859-5}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code extension})\e$B$7$F$$$k!#\e(B@refill
RFC 2046 (@ref{RFC 2046}) \e$B$GDj5A$5$l$F$$$k!#\e(B
@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
\e$B%.%j%7%"J8;z$d5-9f$+$i$J$k\e(B 96 \e$BJ8;z=89g\e(B(@ref{96-character set})\e$B!#\e(B
-@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
\e$B%.%j%7%"8l$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F!"\e(BASCII (@ref{ASCII}) \e$B$K\e(B ISO 8859-7
-(@ref{ISO 8859-7}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code
-extension})\e$B$7$F$$$k!#\e(B@refill
+(@ref{ISO 8859-7}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code extension})\e$B$7$F$$$k!#\e(B@refill
RFC 1947 \e$B$GDj5A$5$l$F$$$k!#\e(B
-@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
@node ISO-IR-165, JIS X0201, ISO 8859-9, Glossary
-@subsection ISO-IR-165, CCITT Extended GB
+@subsection ISO-IR-165, CCITT Extended GB
CCITT \e$B$,EPO?$7$?!"Cf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=\e(B
\e$B$9$k$?$a$N\e(B94\e$B!_\e(B94 \e$BJ8;z=89g\e(B(@ref{94x94-character set})\e$B!#\e(B@refill
-GB 2312 (@ref{GB 2312}) \e$B$H\e(B GB 8565 \e$BI=#2\e(B (@ref{GB 8865.2}) \e$B$K\e(B 150 \e$BJ8;z$[\e(B
+GB 2312 (@ref{GB 2312}) \e$B$H\e(B GB 8565 \e$BI=#2\e(B (@ref{GB 8565.2}) \e$B$K\e(B 150 \e$BJ8;z$[\e(B
\e$B$I$rDI2C$7$?$b$N$i$7$$!#\e(B@refill
ISO 2022 (@ref{ISO 2022}) \e$B$G$N=*C<\e(B byte \e$B$O\e(B 04/05 (`E') \e$B$G$"$k!#\e(B
@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 X0201
+@cindex JIS C6220-1976
ISO 646 (@ref{ISO 646}) \e$B$NJQ<o$N#1$D$G$"$k\e(B Latin \e$BJ8;z=89g$H\e(B 1 byte \e$B$N%+\e(B
\e$B%?%+%JJ8;z=89g$H!"$3$l$i$+$i$J$k\e(B 7bit \e$B$*$h$S\e(B 8bit \e$BId9f2=J8;z=89g\e(B
(@ref{Coded character set}) \e$B$rDj5A$7$F$$$k!#\e(B@refill
-\e$B85$O\e(B @cindex{JIS C6220-1976}@strong{JIS C6220-1976} \e$B$H8@$C$?$,\e(B @cindex{JIS
-X0201}@strong{JIS
-X0201} \e$B$KHV9f$,JQ99$5$l$?!#\e(B
+\e$B85$O\e(B @strong{JIS C6220-1976} \e$B$H8@$C$?$,\e(B @strong{JIS X0201} \e$B$KHV9f$,JQ99$5$l$?!#\e(B
+
-@cindex{JIS X0201-1976}@cindex{JIS X 0201-1976:}
@noindent
[JIS X0201-1976]
@quotation
\e$B$^$?!"\e(B1997 \e$BG/$K2~DjHG$,=P$kM=Dj!#\e(B
-@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
\e$BF|K\8l$rI=$9$?$a$K:n$i$l$?\e(B94\e$B!_\e(B94 \e$BJ8;z=89g\e(B(@ref{94x94-character set})\e$B!#F|\e(B
\e$BK\$N9q2HI8=`!#\e(B1978 \e$BG/HG!"\e(B1983 \e$BG/HG!"\e(B1990 \e$BG/HG$,$"$k$,!"\e(BInternet \e$B$G$O\e(B
1990 \e$BG/$N2~Dj$G$O\e(B 1983 \e$BG/HG$KBP$9$kDI2C$,9T$o$l$?!#$3$N$?$a!"\e(B1990 \e$BG/HG\e(B
\e$B$r;X<($9$k>l9g$OA0$K99?7%7!<%1%s%9\e(B (ESC 02/06 4/0) \e$B$rMQ$$$k!#\e(B
-@cindex{JIS X0208-1978}@cindex{JIS C6226:1978}
+
@noindent
[JIS X0208-1978]
@quotation
interchange'', JIS C6226:1978.
@end quotation
-@cindex{JIS X0208-1983,1990}@cindex{JIS X0208:1983,1990}
+
@noindent
[JIS X0208-1983,1990]
@quotation
\e$B$^$?!"\e(B1997 \e$BG/$K2~DjHG$,=PHG$5$l$kM=Dj!#!J;z7A$NJQ99$O9T$o$l$J$$$N$GJ8\e(B
\e$B;z=89g$H$7$F$O\e(B 1990 \e$BG/HG$HF10l$G$"$k!K\e(B
-@cindex{JIS X0208-1997?}@cindex{JIS X 0208:1997? draft}
+
@noindent
[JIS X0208-1997?]
@quotation
@node koi8-r, KS C5601, JIS X0212, Glossary
@subsection koi8-r
+@cindex RFC 1489
-\e$B%m%7%d8lEy$GMQ$$$i$l$k%-%j%kJ8;z$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME
-charset}) \e$B$N#1$D!#\e(B@refill
+\e$B%m%7%d8lEy$GMQ$$$i$l$k%-%j%kJ8;z$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B@refill
ISO 2022 (@ref{ISO 2022}) \e$B$K4p$+$J$$\e(B 8bit (@ref{8bit}) \e$B$NId9f2=J8;z=89g\e(B
(@ref{Coded character set})\e$B$G\e(B de-fact standard \e$B$G$"$k!#\e(B
RFC 1489 \e$B$GDj5A$5$l$F$$$k!#\e(B@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
\e$B4Z9q8l$rI=$9$?$a$N\e(B 94\e$B!_\e(B94 \e$BJ8;z=89g\e(B(@ref{94x94-character set})\e$B!#4Z9q$N9q\e(B
\e$B2HI8=`!#\e(BISO 2022 (@ref{ISO 2022}) \e$B$G$N=*C<\e(B byte \e$B$O\e(B 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
-
-MIME (@ref{MIME}) \e$B$K$*$1$k\e(B entity (@ref{entity}) \e$B$N<oN`!#\e(B
-@cindex{type}@strong{type} \e$B$H\e(B @cindex{subtype}@strong{subtype} \e$B$+$i$J$k!#\e(B
-RFC 2046 (@ref{RFC 2046}) \e$B$GDj5A$5$l$F$$$k!#\e(B@refill
+@cindex x-token
+@cindex content-type/subtype
+@cindex message
+@cindex multipart
+@cindex application
+@cindex video
+@cindex audio
+@cindex image
+@cindex text
+@cindex subtype
+@cindex type
+
+MIME (@ref{MIME}) \e$B$K$*$1$k\e(B entity (@ref{entity}) \e$B$N<oN`!#\e(B@strong{type}
+\e$B$H\e(B @strong{subtype} \e$B$+$i$J$k!#\e(BRFC 2046 (@ref{RFC 2046}) \e$B$GDj5A$5$l$F$$$k!#\e(B
type \e$B$OI8=`$G$O\e(B
@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
@noindent
@quotation
\e$B$3$3$G$O!"\e(Btext/plain \e$B$J$I$N\e(B type/subtype \e$B$NAH$r$7$P$7$P\e(B
-@cindex{content-type/subtype}@strong{content-type/subtype} \e$B$H=q$/!#\e(B
+@strong{content-type/subtype} \e$B$H=q$/!#\e(B
@end quotation
\e$B$k!#8=:_!"EPO?$5$l$F$$$k$b$N$O\e(B MEDIA TYPES
(ftp://ftp.isi.edu/in-notes/iana/assignments/media-types) \e$B$G;2>H$G$-$k!#\e(B
-\e$B$^$?!"\e(Btype \e$B$b$7$/$O\e(B subtype \e$B$K!"A0$K\e(B `x-' \e$B$rIU$1$?\e(B
-@cindex{x-token}@strong{x-token} \e$B$rMQ$$$k$3$H$K$h$j!"EPO?$5$l$F$$$J$$$b\e(B
-\e$B$N$r;dE*$KMQ$$$k$3$H$b$G$-$k!#$7$+$7!"EvA3$N$3$H$J$,$i!"$3$&$7$?;dE*$J\e(B
-content-type
\e$B$ONJ2r$rF@$?<T$N4V$G$7$+2r<a$G$-$J$$$N$GMxMQ$K$OCm0U$9$k$3
\e(B
-\e$B$H!#\e(B@refill
+\e$B$^$?!"\e(Btype \e$B$b$7$/$O\e(B subtype \e$B$K!"A0$K\e(B `x-' \e$B$rIU$1$?\e(B @strong{x-token} \e$B$rMQ\e(B
+\e$B$$$k$3$H$K$h$j!"EPO?$5$l$F$$$J$$$b$N$r;dE*$KMQ$$$k$3$H$b$G$-$k!#$7$+$7!"\e(B
+\e$BEvA3$N$3$H$J$,$i!"$3$&$7$?;dE*$J\e(B content-type \e$B$ONJ2r$rF@$?<T$N4V$G$7$+2r\e(B
+
\e$B<a$G$-$J$$$N$GMxMQ$K$OCm0U$9$k$3$H!#
\e(B@refill
(cf. @ref{Content-Type field})
@node message, message/rfc822, media type, Glossary
@subsection message
-\e$B$3$3$G$O\e(B RFC 822 (@ref{RFC 822}) \e$B$GDj5A$5$l$k\e(B mail \e$B$H\e(B RFC 1036 (@ref{RFC
-1036}) \e$B$GDj5A$5$l$k\e(B news \e$B5-;v$NAm>N$H$7$FMQ$$$k!#\e(B
+\e$B$3$3$G$O\e(B RFC 822 (@ref{RFC 822}) \e$B$GDj5A$5$l$k\e(B mail \e$B$H\e(B RFC 1036 (@ref{RFC 1036}) \e$B$GDj5A$5$l$k\e(B news \e$B5-;v$NAm>N$H$7$FMQ$$$k!#\e(B
@node message/rfc822, method, message, Glossary
@node method, MIME, message/rfc822, Glossary
@subsection method
+@cindex external method
+@cindex internal method
tm \e$B$GFCDj$N<oN`$N\e(B data \e$B$r:F@8$7$?$H$-<B:]$K$=$N=hM}$r9T$J$&\e(B program.
-Emacs Lisp \e$B$G=q$+$l$?\e(B @cindex{internal method}@strong{internal method}
-\e$B$H\e(B C \e$B$d\e(B script \e$B8@8l$J$I$G=q$+$l$?\e(B @cindex{external
-method}@strong{external method} \e$B$,$"$k!#\e(B@refill
+Emacs Lisp \e$B$G=q$+$l$?\e(B @strong{internal method} \e$B$H\e(B C \e$B$d\e(B script \e$B8@8l$J$I$G\e(B
+\e$B=q$+$l$?\e(B @strong{external method} \e$B$,$"$k!#\e(B@refill
(cf. @ref{(tm-view-ja)method})
@node MIME, MIME charset, method, Glossary
@subsection MIME
+@cindex Multipurpose Internet Mail Extensions
-@cindex{Multipurpose Internet Mail Extensions}@strong{Multipurpose
-Internet Mail Extensions} \e$B$NN,$G!"\e(BInternet \e$B$N\e(B mail \e$B$d\e(B news \e$B$G\e(B us-ascii
-plain text (@ref{us-ascii}) \e$B0J30$NJ8;z$r;H$&$?$a$N\e(B RFC 822 (@ref{RFC
-822}) \e$B$KBP$9$k3HD%!#\e(B@refill
+@strong{Multipurpose Internet Mail Extensions} \e$B$NN,$G!"\e(BInternet \e$B$N\e(B mail
+\e$B$d\e(B news \e$B$G\e(B us-ascii plain text (@ref{us-ascii}) \e$B0J30$NJ8;z$r;H$&$?$a$N\e(B
+RFC 822 (@ref{RFC 822}) \e$B$KBP$9$k3HD%!#\e(B@refill
RFC 2045 \e$B$OKAF,$G<!$N$h$&$K=R$Y$F$$$k!'\e(B@refill
RFC 2045 (@ref{RFC 2045}), RFC 2046 (@ref{RFC 2046}), RFC 2047
-(@ref{encoded-word}), RFC 2048 (@ref{RFC 2048}), RFC 2049 (@ref{RFC
-2049}) \e$B$GDj5A$5$l$F$$$k!#\e(B
+(@ref{encoded-word}), RFC 2048 (@ref{RFC 2048}), RFC 2049 (@ref{RFC 2049}) \e$B$GDj5A$5$l$F$$$k!#\e(B
@node MIME charset, MTA, MIME, Glossary
@node MTA, MUA, MIME charset, Glossary
@subsection MTA
+@cindex Message Transfer Agent
-@cindex{Message Transfer Agent}@strong{Message Transfer Agent} \e$B$NN,$G!"\e(B
-sendmail \e$B$J$I$N\e(B mail \e$BG[Aw\e(B program \e$B$H\e(B news server \e$B$NAm>N!#\e(B@refill
+@strong{Message Transfer Agent} \e$B$NN,$G!"\e(Bsendmail \e$B$J$I$N\e(B mail \e$BG[Aw\e(B
+program \e$B$H\e(B news server \e$B$NAm>N!#\e(B@refill
(cf. @ref{MUA})
@node MUA, MULE, MTA, Glossary
@subsection MUA
+@cindex Message User Agent
-@cindex{Message User Agent}@strong{Message User Agent} \e$B$NN,$G!"\e(Bmail
-reader \e$B$H\e(B news reader \e$B$NAm>N!#\e(B@refill
+@strong{Message User Agent} \e$B$NN,$G!"\e(Bmail reader \e$B$H\e(B news reader \e$B$NAm>N!#\e(B
+@refill
(cf. @ref{MTA})
@node MULE, multipart, MUA, Glossary
@subsection MULE
+@cindex XEmacs/mule
+@cindex Emacs/mule
+@cindex MULE
+@cindex mule
+@cindex MULE
\e$BH>ED\e(B \e$B7u0l;a$i$,:n$C$?!"B?8@8l$5$l$?\e(B GNU Emacs (@ref{Emacs}).
-@cindex{MULE}
+
@noindent
[MULE]
@quotation
\e$B$3$N$?$a!"8=:_$G$OB?8@8l\e(B Emacs \e$B$O!"85!9$N\e(B MULE \e$B$r4^$a$F#3<oN`$"$k$3$H$K\e(B
\e$B$J$k!#\e(B@refill
-\e$B$=$3$G!"$3$3$G$O!"B?8@8l\e(B Emacs \e$B$NAm>N$r\e(B @cindex{mule}@strong{mule}, \e$B85!9\e(B
-\e$B$N\e(B MULE \e$B$r\e(B @cindex{MULE}@strong{MULE}, mule \e$B5!G=$r\e(B merge \e$B$7$?\e(B Emacs \e$B$r\e(B
-@cindex{Emacs/mule}@strong{Emacs/mule}, mule \e$B5!G=$r\e(B merge \e$B$7$?\e(B XEmacs \e$B$r\e(B
-@cindex{XEmacs/mule}@strong{XEmacs/mule} \e$B$H8F$V$3$H$K$9$k!#\e(B
+\e$B$=$3$G!"$3$3$G$O!"B?8@8l\e(B Emacs \e$B$NAm>N$r\e(B @strong{mule}, \e$B85!9\e(B
+\e$B$N\e(B MULE \e$B$r\e(B @strong{MULE}, mule \e$B5!G=$r\e(B merge \e$B$7$?\e(B Emacs \e$B$r\e(B
+@strong{Emacs/mule}, mule \e$B5!G=$r\e(B merge \e$B$7$?\e(B XEmacs \e$B$r\e(B
+@strong{XEmacs/mule} \e$B$H8F$V$3$H$K$9$k!#\e(B
@node multipart, multipart/alternative, MULE, Glossary
@subsection Multipart
+@cindex multipart
\e$B#1$D$N\e(B message (@ref{message}) \e$B$KJ#?t$N\e(B entity (@ref{entity}) \e$B$rF~$l$k$?\e(B
\e$B$a$N\e(B MIME (@ref{MIME}) \e$B$K$*$1$k\e(B media type (@ref{media type}) \e$B$N#1$D!"$b\e(B
\e$B$7$/$O!"J#?t$N\e(B entity \e$B$+$i$J$k\e(B message \e$B$r;X$9!#\e(B@refill
-\e$B8=:_!"Dj5A$5$l$F$$$k\e(B @cindex{multipart}@strong{multipart} \e$B$H$7$F$O!"\e(BRFC
-2046 (@ref{RFC 2046}) \e$B$GDj5A$5$l$?\e(B
+\e$B8=:_!"Dj5A$5$l$F$$$k\e(B @strong{multipart} \e$B$H$7$F$O!"\e(BRFC 2046 (@ref{RFC 2046}) \e$B$GDj5A$5$l$?\e(B
@itemize @bullet
@item
@node multipart/digest, multipart/encrypted, multipart/alternative, Glossary
@subsection multipart/digest
+@cindex multipart/digest
multipart (@ref{multipart}) \e$B$N#1$D$G!"4^$^$l$k\e(B entity (@ref{entity}) \e$B$N\e(B
default \e$B$N\e(Bmedia type (@ref{media type}) \e$B$,\e(B multipart/mixed
(@ref{multipart/mixed}) \e$B$J$I$N>l9g\e(B text/plain (@ref{text/plain}) \e$B$G$"$k\e(B
-\e$B$N$KBP$7!"\e(B@cindex{multipart/digest}@strong{multipart/digest}\e$B$G$O\e(B
-message/rfc822 (@ref{message/rfc822}) \e$B$,MQ$$$i$l$kE@$,0[$J$k!#\e(B@refill
+\e$B$N$KBP$7!"\e(B@strong{multipart/digest}\e$B$G$O\e(B message/rfc822
+(@ref{message/rfc822}) \e$B$,MQ$$$i$l$kE@$,0[$J$k!#\e(B@refill
\e$B$3$l$OEAE}E*$J\e(B RFC 1153 (@ref{RFC 1153}) \e$B$K4p$E$/\e(B encapsulation
(@ref{encapsulation}) \e$B$KBe$o$k$b$N$G$"$k!#\e(B@refill
@node PGP, PGP-kazu, multipart/signed, Glossary
@subsection PGP
+@cindex RFC 1991
+@cindex Informational
+@cindex PGP
Phil Zimmermann \e$B;a$,:n@.$7$?8x3+800E9f=hM}7O$N#1$D!#\e(Bmessage
(@ref{message}) \e$B$N0E9f2=$dEE;R=pL>$r9T$&$3$H$,$G$-$k!#\e(BPretty Good
\e$B$bMxMQ$5$l$F$-$?!#$7$+$7!":#8e$O\e(B PGP/MIME \e$B$KE}0l$7$F$$$/J}$,K>$^$7$$!#\e(B
@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
\e$B;3K\\e(B \e$BOBI'\e(B \e$B;a$,Ds0F$7$?\e(B MIME (@ref{MIME}) \e$B$G\e(B PGP (@ref{PGP}) \e$B$rMxMQ$9$k$?\e(B
-\e$B$a$NJ}K!$r$3$3$G$O\e(B @cindex{PGP-kazu}@strong{PGP-kazu} \e$B$H8F$V$3$H$K$9$k!#\e(B
+\e$B$a$NJ}K!$r$3$3$G$O\e(B @strong{PGP-kazu} \e$B$H8F$V$3$H$K$9$k!#\e(B@refill
-PGP-kazu \e$B$O\e(B @cindex{application/pgp}@strong{application/pgp} \e$B$H$$$&\e(B
-content-type (@ref{content-type}) \e$B$rDj5A$9$k!#\e(B@refill
+PGP-kazu \e$B$O\e(B @strong{application/pgp} \e$B$H$$$&\e(B content-type
+(@ref{content-type}) \e$B$rDj5A$9$k!#\e(B@refill
application/pgp \e$B$N\e(B part \e$B$G$O\e(B PGP \e$B$N\e(B encapsulation (@ref{encapsulation})
\e$B$,MQ$$$i$l$k!#\e(BPGP \e$B$N\e(B encapsulation (cf. @ref{RFC 934})
@node PGP/MIME, Quoted-Printable, PGP-kazu, Glossary
@subsection PGP/MIME
+@cindex RFC 2015
+@cindex Standards Track
+@cindex PGP/MIME
Michael Elkins \e$B;a$,Ds0F$7$?\e(B MIME (@ref{MIME}) \e$B$G\e(B PGP (@ref{PGP}) \e$B$rMxMQ\e(B
\e$B$9$k$?$a$NJ}K!!#\e(B@refill
\e$B$&$3$H$G9g0U$,<h$l$F$$$k!#$h$C$F!":#8e$O\e(B PGP \e$B$rMQ$$$k>l9g$O\e(B PGP/MIME\e$B$rMQ\e(B
\e$B$$$k$N$,K>$^$7$$!#\e(B
-@cindex{PGP/MIME}@cindex{Standards Track}@cindex{RFC 2015}
+
@noindent
[PGP/MIME: RFC 2015]
@quotation
@node RFC 821, RFC 822, Quoted-Printable, Glossary
@subsection RFC 821
+@cindex RFC 821
+@cindex STD 10
+@cindex SMTP
+@cindex SMTP
-@cindex{SMTP}@strong{SMTP} \e$B$H8F$P$l$k\e(B Internet mail \e$B$NG[AwK!$NI8=`$rDj$a\e(B
+@strong{SMTP} \e$B$H8F$P$l$k\e(B Internet mail \e$B$NG[AwK!$NI8=`$rDj$a\e(B
\e$B$F$$$k\e(B RFC.
-@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 message
+@cindex Internet mail
+@cindex message header
-Internet mail \e$B$N<g$K\e(B @cindex{message header}@strong{message header} \e$B$K4X$9$k7A<0$K\e(B
+Internet mail \e$B$N<g$K\e(B @strong{message header} \e$B$K4X$9$k7A<0$K\e(B
\e$B4X$9$kI8=`$rDj$a$F$$$k\e(B RFC.
@noindent
@strong{[Memo]}
@quotation
-news message \e$B$b$3$l$K=`$8$F$$$k$N$G!"\e(B@cindex{Internet
-mail}@strong{Internet mail} \e$B$H=q$/$h$j$b!"\e(B@cindex{Internet
-message}@strong{Internet message} \e$B$H=q$$$?J}$,NI$$$+$b$7$l$J$$!#\e(B
+news message \e$B$b$3$l$K=`$8$F$$$k$N$G!"\e(B@strong{Internet mail} \e$B$H=q$/$h$j$b!"\e(B
+@strong{Internet message} \e$B$H=q$$$?J}$,NI$$$+$b$7$l$J$$!#\e(B
@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
-Internet mail (@ref{RFC 822}) \e$B$N\e(B
-@cindex{encapsulation}@strong{encapsulation} (@ref{encapsulation}) \e$B$NJ}\e(B
-\e$BK!$rDj$a$?\e(B RFC.@refill
+Internet mail (@ref{RFC 822}) \e$B$N\e(B @strong{encapsulation}
+(@ref{encapsulation}) \e$B$NJ}K!$rDj$a$?\e(B RFC.@refill
MIME (@ref{MIME}) \e$B$HL7=b$9$k$N$G!"8=:_$G$O\e(B message/rfc822
(@ref{message/rfc822}) \e$B$rMQ$$$k$Y$-$G$"$k!#\e(B
-@cindex{RFC 934}
+
@noindent
[RFC 934]
@quotation
@node RFC 1036, RFC 1153, RFC 934, Glossary
@subsection RFC 1036
+@cindex RFC 1036
+@cindex USENET
USENET \e$B$G$N\e(B message \e$B$N7A<0$rDj$a$?\e(B RFC. RFC 822 (@ref{RFC 822}) \e$B$N\e(B
subset \e$B$K$J$C$F$$$k!#\e(BInternet \e$B$NI8=`$G$O$J$$$,!"\e(BUSENET \e$B0J30$N\e(B netnews \e$B$G\e(B
\e$B$b$3$l$K=`$8$F$$$k$b$N$,B?$$!#\e(B
-@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 encapsulation
-\e$BJ#?t$N\e(B Internet mail (@ref{RFC 822}) \e$B$r\e(B
-@cindex{encapsulation}@strong{encapsulation} (@ref{encapsulation}) \e$B$9$k\e(B
-\e$B$?$a$NJ}K!$rDj$a$?\e(B RFC.@refill
+\e$BJ#?t$N\e(B Internet mail (@ref{RFC 822}) \e$B$r\e(B @strong{encapsulation}
+(@ref{encapsulation}) \e$B$9$k$?$a$NJ}K!$rDj$a$?\e(B RFC.@refill
MIME (@ref{MIME}) \e$B$HL7=b$9$k$N$G!"8=:_$G$O\e(B message/rfc822
(@ref{message/rfc822}) \e$B$rMQ$$$?\e(B multipart (@ref{multipart}) \e$B$rMQ$$$k$Y$-\e(B
(cf. @ref{multipart/digest})
-@cindex{RFC 1153}
+
@noindent
[RFC 1153]
@quotation
@node RFC 1557, RFC 1922, RFC 1153, Glossary
@subsection RFC 1557
+@cindex RFC 1557
+@cindex Informational
euc-kr (@ref{euc-kr}) \e$B$H\e(B iso-2022-kr (@ref{iso-2022-kr}) \e$B$H$$$&4Z9q8l$N\e(B
\e$B$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$rDj5A$7$F$$$k\e(B RFC.
-@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
iso-2022-cn (@ref{iso-2022-cn}), iso-2022-cn-ext
(@ref{iso-2022-cn-ext}), cn-gb (@ref{cn-gb}), cn-big5 (@ref{cn-big5}) \e$B$H\e(B
\e$B$$$C$?Cf9q8l$N$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$rDj5A$7$F$$$k\e(B
RFC.@refill
-\e$B$3$l$K2C$($F!"\e(B@cindex{charset-edition}@strong{charset-edition} \e$B$H\e(B
-@cindex{charset-extension}@strong{charset-extension} \e$B$H$$$&\e(B Content-Type
-field (@ref{Content-Type field}) \e$B$N\e(B parameter \e$B$rDj5A$7$F$$$k!#\e(B
+\e$B$3$l$K2C$($F!"\e(B@strong{charset-edition} \e$B$H\e(B @strong{charset-extension} \e$B$H\e(B
+\e$B$$$&\e(B Content-Type field (@ref{Content-Type field}) \e$B$N\e(B parameter \e$B$rDj5A$7\e(B
+\e$B$F$$$k!#\e(B
+
-@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 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
MIME (@ref{MIME}) \e$B$G0E9f$dEE;R=qL>$rMQ$$$k$?$a$N7A<0!#\e(B@refill
-@cindex{multipart/signed}@strong{multipart/signed}
-(@ref{multipart/signed}) \e$B$H\e(B
-@cindex{multipart/encrypted}@strong{multipart/encrypted}
-(@ref{multipart/encrypted}) \e$B$H$$$&\e(B multipart \e$B$rMQ$$$k!#\e(B@refill
+@strong{multipart/signed} (@ref{multipart/signed}) \e$B$H\e(B
+@strong{multipart/encrypted} (@ref{multipart/encrypted}) \e$B$H$$$&\e(B
+multipart \e$B$rMQ$$$k!#\e(B@refill
MOSS \e$B$d\e(B PGP/MIME (@ref{PGP/MIME}) \e$B$O$3$l$K4p$$$F$$$k!#\e(B
-@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/richtext
+
+RFC 1521 \e$B$GDj5A$5$l$?\e(B @strong{text/richtext} \e$B$KBe$o$C$F!"=qBN$dAHHG$K4X\e(B
+\e$B$9$k>pJs$r;}$C$?\e(B text\e$B$rI=8=$9$k$?$a$N\e(B media type (@ref{media type}).
-RFC 1521 \e$B$GDj5A$5$l$?\e(B @cindex{text/richtext}@strong{text/richtext} \e$B$KBe\e(B
-\e$B$o$C$F!"=qBN$dAHHG$K4X$9$k>pJs$r;}$C$?\e(B text\e$B$rI=8=$9$k$?$a$N\e(B media type
-(@ref{media type}).
-@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
RFC 2046 (@ref{RFC 2046}) \e$B$GDj5A$5$l$?!"\e(Bplain text (@ref{plain text}) \e$B$r\e(B
\e$BI=8=$9$k$?$a$N\e(B media type (@ref{media type}).@refill
-\e$BHs\e(B MIME message \e$B$J$I$N\e(B content-type \e$B$,Dj5A$5$l$J$$\e(B entity \e$B$O\e(B MIME
-charset (@ref{MIME charset}) \e$B$,\e(B us-ascii (@ref{us-ascii}) \e$B$G$"$k\e(B
-@cindex{text/plain}@strong{text/plain} \e$B$N\e(B entity \e$B$G$"$k$H8+Pv$5$l$k$3$H\e(B
-\e$B$K$J$C$F$$$k!#\e(B
+\e$BHs\e(B MIME message \e$B$J$I$N\e(B content-type \e$B$,Dj5A$5$l$J$$\e(B entity (@ref{entity})
+\e$B$O\e(B MIME charset (@ref{MIME charset}) \e$B$,\e(B us-ascii (@ref{us-ascii}) \e$B$G$"$k\e(B
+@strong{text/plain} \e$B$N\e(B entity \e$B$G$"$k$H8+Pv$5$l$k$3$H$K$J$C$F$$$k!#\e(B
@node tm-kernel, tm-MUA, text/plain, Glossary
@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 \e$BBg@9$j\e(B package
tm (@ref{tm-kernel}) \e$B$rMQ$$$?\e(B MUA (@ref{MUA}) \e$B$b$7$/$O\e(B MUA \e$B$KBP$9$k\e(B
extender.@refill
-@cindex{tm \e$BBg@9$j\e(B package}@strong{tm \e$BBg@9$j\e(B package} \e$B$K$O\e(B
+@strong{tm \e$BBg@9$j\e(B package} \e$B$K$O\e(B
@itemize @bullet
@item
-mh-e (@ref{(mh-e)}) \e$BMQ$N\e(B @cindex{tm-mh-e}@strong{tm-mh-e}
+mh-e (@ref{(mh-e)}) \e$BMQ$N\e(B @strong{tm-mh-e}
@item
-GNUS \e$BMQ$N\e(B @cindex{tm-gnus}@strong{tm-gnus}
+GNUS \e$BMQ$N\e(B @strong{tm-gnus}
@item
-Gnus \e$BMQ$N\e(B @cindex{gnus-mime}@strong{gnus-mime} (@ref{(gnus-mime-ja)})
+Gnus \e$BMQ$N\e(B @strong{gnus-mime} (@ref{(gnus-mime-ja)})
@item
-VM \e$BMQ$N\e(B @cindex{tm-vm}@strong{tm-vm}
+VM \e$BMQ$N\e(B @strong{tm-vm}
@item
-RMAIL \e$BMQ$N\e(B @cindex{tm-rmail}@strong{tm-rmail}
+RMAIL \e$BMQ$N\e(B @strong{tm-rmail}
@end itemize
@noindent
@node us-ascii, , tm-MUA, Glossary
@subsection us-ascii
+@cindex ASCII
+@cindex us-ascii
\e$B%"%a%j%+O"K.$J$I$G;H$o$l$k1Q8l$J$I$rI=8=$9$k$?$a$N\e(B MIME charset
(@ref{MIME charset}) \e$B$N#1$D!#\e(B@refill
Internet mail \e$B$K$*$1$kI8=`$NId9f2=J8;z=89g\e(B(@ref{Coded character set})\e$B$G\e(B
\e$B$"$j!"L@<(E*$K\e(B MIME charset \e$B$,<($5$l$J$$>l9g$O86B'$H$7$F\e(B
-@cindex{us-ascii}@strong{us-ascii} \e$B$,;H$o$l$k!#\e(B@refill
+@strong{us-ascii} \e$B$,;H$o$l$k!#\e(B@refill
-\e$B$^$?!"\e(BRFC 822 (@ref{RFC 822}) \e$B$K$*$1$k\e(B @cindex{ASCII}@strong{ASCII} \e$B$O\e(B
-us-ascii
\e$B$r;X$9$b$N$H2r<a$9$Y$-$G$"$k!#
\e(B
+\e$B$^$?!"\e(BRFC 822 (@ref{RFC 822}) \e$B$K$*$1$k\e(B @strong{ASCII} \e$B$O\e(B us-ascii \e$B$r;X$9\e(B
+
\e$B$b$N$H2r<a$9$Y$-$G$"$k!#
\e(B
@node Setting, Bug report, Introduction, Top
@node mime-setup, tm-setup, Setting, Setting
@section \e$BI8=`E*$J@_Dj\e(B
+@cindex mime-setup
-tm \e$B$N0lHLE*$J@_Dj$r9T$$$?$$>l9g$O!"\e(B
-@cindex{mime-setup}@strong{mime-setup} \e$B$H$$$&I8=`@_Dj\e(B file \e$B$r;H$C$F$/$@\e(B
-\e$B$5$$!#Nc$($P!"\e(B@file{~/.emacs} \e$BEy$G!"\e(B@refill
+tm \e$B$N0lHLE*$J@_Dj$r9T$$$?$$>l9g$O!"\e(B@strong{mime-setup} \e$B$H$$$&I8=`@_Dj\e(B
+file \e$B$r;H$C$F$/$@$5$$!#Nc$($P!"\e(B@file{~/.emacs} \e$BEy$G!"\e(B@refill
@lisp
(load "mime-setup")
@node signature, Notice about GNUS, mime-setup, mime-setup
@subsection signature.el
+@cindex signature
-tm \e$B$K$O\e(B @cindex{signature}@strong{signature} \e$B$H$$$&\e(B signature \e$B$N<+F0@ZBX$(\e(B
+tm \e$B$K$O\e(B @strong{signature} \e$B$H$$$&\e(B signature \e$B$N<+F0@ZBX$(\e(B
tool \e$B$,ImB0$7$F$*$j!"\e(B@file{mime-setup.el} \e$B$O$3$N@_Dj$b9T$J$$$^$9!#\e(B
message header \e$B$N\e(B field \e$B$K9g$o$;$F\e(B signature \e$B$N<+F0@ZBX$r9T$J$$$?$$>l\e(B
\e$B9g$O\e(B @file{~/.emacs} \e$B$K0J2<$N$h$&$J$b$N$rF~$l$F2<$5$$!#!J>\$7$/\e(B
@node tm-setup, setting for VM, mime-setup, Setting
@section tm-edit \e$B$r;H$o$J$$@_Dj\e(B
+@cindex tm-setup
-@cindex{tm-setup}@strong{tm-setup} \e$B$O\e(B tm-MUA (@ref{tm-MUA}) \e$B$N@_Dj$N$_$r\e(B
-\e$B9T$J$&\e(B module \e$B$G$9!#$3$N@_Dj\e(B file \e$B$G$O\e(B tm-edit (@ref{(tm-edit-ja)}) \e$B$r;H$C\e(B
-\e$B$?\e(B MIME message \e$B$N:n@.$K4X$9$k@_Dj$O9T$o$l$:!"\e(BMIME message \e$B$N1\Mw$K4X$9\e(B
-\e$B$k@_Dj$N$_$,9T$o$l$^$9!#\e(BMIME message \e$B$rFI$_$?$$$,<+J,$G$O:n@.$7$J$$$H$+!"\e(B
-tm-edit \e$B0J30$N\e(B MIME composer \e$B$r;H$$$?$$>l9g$K$O\e(B mime-setup.el \e$B$NBe$o$j$K\e(B
-\e$B$3$N@_Dj\e(B file \e$B$r;H$C$F$/$@$5$$!#\e(B@refill
+@strong{tm-setup} \e$B$O\e(B tm-MUA (@ref{tm-MUA}) \e$B$N@_Dj$N$_$r9T$J$&\e(B module \e$B$G\e(B
+\e$B$9!#$3$N@_Dj\e(B file \e$B$G$O\e(B tm-edit (@ref{(tm-edit-ja)}) \e$B$r;H$C$?\e(B MIME
+message \e$B$N:n@.$K4X$9$k@_Dj$O9T$o$l$:!"\e(BMIME message \e$B$N1\Mw$K4X$9$k@_Dj$N\e(B
+\e$B$_$,9T$o$l$^$9!#\e(BMIME message \e$B$rFI$_$?$$$,<+J,$G$O:n@.$7$J$$$H$+!"\e(Btm-edit
+\e$B0J30$N\e(B MIME composer \e$B$r;H$$$?$$>l9g$K$O\e(B mime-setup.el \e$B$NBe$o$j$K$3$N@_Dj\e(B
+file \e$B$r;H$C$F$/$@$5$$!#\e(B@refill
\e$BNc$($P!"\e(B@file{~/.emacs} \e$BEy$K\e(B
@node setting for VM, manual setting, tm-setup, Setting
@section VM \e$B$r;H$&>l9g$N@_Dj\e(B
+@cindex BBDB
+@cindex vm
-@cindex{vm}@strong{vm} \e$B$r;H$&>l9g$O\e(B @file{~/.vm} \e$B$K\e(B
+@strong{vm} \e$B$r;H$&>l9g$O\e(B @file{~/.vm} \e$B$K\e(B
@lisp
(require 'tm-vm)
@strong{[\e$BCm0U\e(B]}
@quotation
-@cindex{BBDB}@strong{BBDB} \e$B$r;H$&>l9g$O\e(B @code{(bbdb-insinuate-vm)} \e$B$N\e(B
-@strong{\e$B8e\e(B} \e$B$K\e(B @code{(require 'tm-vm)} \e$B$rF~$l$F$/$@$5$$!#\e(B
+@strong{BBDB} \e$B$r;H$&>l9g$O\e(B @code{(bbdb-insinuate-vm)} \e$B$N\e(B @strong{\e$B8e\e(B} \e$B$K\e(B
+@code{(require 'tm-vm)} \e$B$rF~$l$F$/$@$5$$!#\e(B
@end quotation
-@node Bug report, Concept Index, Setting, Top
+@node Bug report, Acknowledgments, Setting, Top
@chapter bug \e$BJs9p$N;EJ}\e(B
tm \e$B$N%P%0$r8+$D$1$?$i!"0J2<$N\e(B address \e$B$K\e(B mail \e$B$rAw$C$F$/$@$5$$!'\e(B
\e$B$F2<$5$$!#\e(B(^_^)
-@node Concept Index, Variable Index, Bug report, Top
+@node Acknowledgments, Concept Index, Bug report, Top
+@chapter \e$B<U<-\e(B
+
+\e$B;d$,\e(B tm-view \e$B$r:G=i$K:n$C$?;~$K!"87$7$$CmJ8$HM-1W$J=u8@$r2<$5$j!"$=$N@_\e(B
+\e$B7W$KB?Bg$JM?$($i$l$?>#C+J]Gn$5$s$K46<U$7$^$9!#\e(B@refill
+
+@file{tm-ew-d.el} \e$B$H\e(B @file{mel-b.el} \e$B$NA0?H$KEv$?$k\e(B@file{mime.el} \e$B$r=q$-!"\e(B
+\e$B$=$NG[I[$H2~B$$r$*5v$72<$5$C$?1]JB;LCR$5$s$K46<U$7$^$9!#\e(B@refill
+
+\e$B$^$?!"\e(BLaTeX \e$BMQ$NFbIt\e(B method \e$B$H\e(B message/partial \e$BMQ$N<+F07k9g\e(B method \e$B$rDs\e(B
+\e$B6!$7$F2<$5$C$?2,It<wCK$5$s!"\e(Btar archive \e$BMQ$NFbIt\e(B method \e$B$rDs6!$7$F2<$5$C\e(B
+\e$B$?>eLnGn$5$s$K46<U$7$^$9!#\e(B@refill
+
+tm-edit \e$B$NA0?H$H$J$C$?\e(B @file{mime.el} \e$B$r=q$-!"$=$NG[I[$H2~B$$r$*5v$72<$5$C\e(B
+\e$B$?!"G_ED@/?.$5$s$K46<U$7$^$9!#\e(Btm-edit \e$B$N\e(B user interface \e$B$N4pK\E*$J@_7W$O\e(B
+\e$BG_ED$5$s$N<j$K$h$k$b$N$G!"$H$F$bNI$$@_7W$G$"$C$?$H;W$$$^$9!#\e(B@refill
+
+tm \e$B$N4v$D$+$N\e(B module \e$B$N\e(B maintainer \e$B$r0z$-<u$1$F2<$5$C$?>.NS=$J?$5$s!"H`\e(B
+\e$B$O$^$?!"\e(BRFC \e$B$KBP$9$kE,9g@-$KBP$7$F1T$$;XE&$rB?!99T$&$3$H$G\e(B tm \e$B$NF0:n$N5,\e(B
+\e$B3J$KBP$9$kCi<BEY$r>e$2$k$N$KHs>o$J9W8%$r9T$$$^$7$?!#\e(B@refill
+
+\e$B$^$?!"\e(Btm-vm \e$B$N\e(B maintainer \e$B$r0z$-<u$1$F2<$5$C$?\e(B Oscar Figueiredo \e$B$5$s$K46\e(B
+\e$B<U$7$^$9!#@:NOE*$K\e(B tm-vm \e$B$r2~NI$7!"$^$?!"N)GI$J@bL@=q$r=q$$$F2<$5$$$^$7\e(B
+\e$B$?!#\e(B@refill
+
+\e$B:G8e$K!"\e(Bbeta test \e$B$K6(NO$7$F2<$5$C$?F|K\8lHG!"1Q8lHGAPJ}$N\e(B tm mailing
+list \e$B$N\e(B member \e$B$K46<U$7$^$9!#$^$?!"\e(Bpatch \e$B$rAw$C$F2<$5$C$?A4$F$NJ}$K46\e(B
+\e$B<U$7$^$9!#\e(B
+
+
+@node Concept Index, Variable Index, Acknowledgments, Top
@chapter \e$B35G0:w0z\e(B
@printindex cp
-Info file: tm-view-en.info, -*-Text-*-
-produced by `texinfo-format-buffer'
-from file `tm-view-en.texi'
-using `texinfmt.el' version 2.32 of 19 November 1993.
-
+This is Info file tm-view-en.info, produced by Makeinfo-1.63 from the
+input file tm-view-en.texi.
\1f
-File: tm-view-en.info, Node: Top, Next: Introduction, Prev: (dir), Up: (dir)
+File: tm-view-en.info, Node: Top, Next: Introduction, Prev: (dir), Up: (dir)
-tm-view 7.77 Reference Manual (English Version)
+tm-view 7.79 Reference Manual (English Version)
***********************************************
-
-This file documents tm-view, a MIME Viewer for GNU Emacs.
+ This file documents tm-view, a MIME Viewer for GNU Emacs.
* Menu:
* method:: Mechanism of decoding
* Two buffers for an article:: raw-article-buffer and preview-buffer
* API:: Functions to decode MIME message
-* Concept Index::
-* Function Index::
-* Variable Index::
-
+* Acknowledgments::
+* Concept Index::
+* Function Index::
+* Variable Index::
\1f
-File: tm-view-en.info, Node: Introduction, Next: MIME display, Prev: Top, Up: Top
+File: tm-view-en.info, Node: Introduction, Next: MIME display, Prev: Top, Up: Top
What is tm-view?
****************
-The tm-view is a general MIME viewer running on GNU Emacs.
+ The tm-view is a general MIME viewer running on GNU Emacs.
-tm-view provides the major-mode called `mime/viewer-mode' (*Note
+ tm-view provides the major-mode called `mime/viewer-mode' (*Note
mime/viewer-mode::) to read MIME message for MUA. MUA (*Note
(tm-en)MUA::) implementer can use it to add MIME function.
-tm-view is a user interface kernel to view and navigate MIME message.
-tm-view drives some programs to navigate each content-type
-(*Note (tm-en)content-type::)s, they are called
-*method* (*Note method::). tm-view calls some
-programs to display each contents and headers in preview buffer, they
-are called *filter* (*Note Two buffers for an article::). Method and
-filters are tm-view application program. They expand tm-view to treat
-various kinds of MIME types.
-
-
+ tm-view is a user interface kernel to view and navigate MIME message.
+tm-view drives some programs to navigate each content-type (*Note
+(tm-en)content-type::)s, they are called *method* (*Note method::).
+tm-view calls some programs to display each contents and headers in
+preview buffer, they are called *filter* (*Note Two buffers for an
+article::). Method and filters are tm-view application program. They
+expand tm-view to treat various kinds of MIME types.
\1f
-File: tm-view-en.info, Node: MIME display, Next: mime/viewer-mode, Prev: Introduction, Up: Top
+File: tm-view-en.info, Node: MIME display, Next: mime/viewer-mode, Prev: Introduction, Up: Top
Structure of display in mime/viewer-mode
****************************************
-In mime/viewer-mode (*Note mime/viewer-mode::), following are displayed
-for each parts:
+ In mime/viewer-mode (*Note mime/viewer-mode::), following are
+displayed for each parts:
[content-button]
(content-header)
-
+
(content-body)
(content-separator)
-You can change design or stop to display if you specify for each
+ You can change design or stop to display if you specify for each
conditions, such as content-types.
-Example:
+ Example:
From: morioka@jaist.ac.jp (MORIOKA Tomohiko)
Subject: Re: Question
Mime-Version: 1.0
Organization: Japan Advanced Institute of Science and Technology,
Ishikawa, Japan
-
+
[1 (text/plain)]
How to compose MIME message in MIME-Edit mode.
-
+
Press `C-c C-x ?' then help message will be displayed:
-
+
C-c C-x C-t insert a text message.
C-c C-x TAB insert a (binary) file.
C-c C-x C-e insert a reference to external body.
C-c C-x C-k insert PGP public key.
C-c C-x C-p preview editing MIME message.
...
-
+
So press `C-c C-x C-i' and specify file name you want to include.
-
+
MIME encoding for binary file is normally Base64.
-
+
[2 (image/gif)]
-
+
[3 (text/plain)]
-
+
In this way, it is finish a message attaching a picture.
-
+
======================== A cup of Russian tea ========================
============ * not by jam, not by marmalade, by honey * ============
============ MORIOKA Tomohiko ============
=============== Internet E-mail: <morioka@jaist.ac.jp> ===============
-
-
* Menu:
-* content-button::
-* content-header::
-* content-body::
-* content-separator::
-
+* content-button::
+* content-header::
+* content-body::
+* content-separator::
\1f
-File: tm-view-en.info, Node: content-button, Next: content-header, Prev: MIME display, Up: MIME display
+File: tm-view-en.info, Node: content-button, Next: content-header, Prev: MIME display, Up: MIME display
content-button
==============
-content-subject displays abstract for the part. It is placed in top of
-the part.
+ content-subject displays abstract for the part. It is placed in top
+of the part.
-In default, it is displayed following design:
+ In default, it is displayed following design:
[1.3 test (text/plain)]
+ First number field represents position of a content in the part. It
+is called *content-number*. It can be considered as the chapter number
+in the message.
-First number field represents position of a content in the part. It is
-called *content-number*. It can be considered as the chapter number in
-the message.
-
-Second string part represents title. It is created by following:
+ Second string part represents title. It is created by following:
1. name paramater or x-name parameter in Content-Type field (*Note
(tm-en)Content-Type field::)
+
2. Content-Description field (*Note (tm-en)Content-Description
field::) or Subject field
- 3. filename of uuencode
+ 3. filename of uuencode
-If they are not exists, space is displayed.
+ If they are not exists, space is displayed.
-Third parenthesis part represents content-type/subtype of the part. If
-it is non-MIME part, `nil' is displayed.
+ Third parenthesis part represents content-type/subtype of the part.
+If it is non-MIME part, `nil' is displayed.
-Content-button is used like icon when content-header (*Note
+ Content-button is used like icon when content-header (*Note
content-header::) and content-body (*Note content-body::) are hidden.
For example:
if you press `v' key, GIF image is displayed.
-If mouse operations are available, you can press content-button by mouse
-button-2 (center button of 3 button-mouse) to play, similarly to press
-`v' key. (cf. *Note mime/viewer-mode::)
-
-By the way, it is annoying to display content-button if content-header
-is displayed. So tm-view provides a mechanism to specify conditions to
-display content-button.
-
+ If mouse operations are available, you can press content-button by
+mouse button-2 (center button of 3 button-mouse) to play, similarly to
+press `v' key. (cf. *Note mime/viewer-mode::)
- -- Variable: mime-viewer/content-button-ignored-ctype-list
+ By the way, it is annoying to display content-button if
+content-header is displayed. So tm-view provides a mechanism to
+specify conditions to display content-button.
+ - Variable: mime-viewer/content-button-ignored-ctype-list
List of content-types.
If content-type of a part is a member of this list, its
content-button is not displayed.
-
-
-
\1f
-File: tm-view-en.info, Node: content-header, Next: content-body, Prev: content-button, Up: MIME display
+File: tm-view-en.info, Node: content-header, Next: content-body, Prev: content-button, Up: MIME display
content-header
==============
-A content header displays the header portion of a part in the
+ A content header displays the header portion of a part in the
preview-buffer. However it is annoying to display header for every
parts, so tm-view provides a mechanism to specify its condition.
-When the function `mime-viewer/header-visible-p' returns `t' for
+ When the function `mime-viewer/header-visible-p' returns `t' for
reversed-content-number of a part, content-header is displayed.
-This judge function returns `t' when a part is root or content-type of
-its parent is a member of the variable
+ This judge function returns `t' when a part is root or content-type
+of its parent is a member of the variable
`mime-viewer/childrens-header-showing-Content-Type-list'.
-If you want to change this condition, please redefine it. Notice that
-it refers variable
-`mime-viewer/childrens-header-showing-Content-Type-list', however if you
-redefine function `mime-viewer/header-visible-p', it may not work. So
-if you want to redefine it, it should be refer variable
+ If you want to change this condition, please redefine it. Notice
+that it refers variable
+`mime-viewer/childrens-header-showing-Content-Type-list', however if
+you redefine function `mime-viewer/header-visible-p', it may not work.
+So if you want to redefine it, it should be refer variable
`mime-viewer/childrens-header-showing-Content-Type-list'.
-When content-header is displayed, content-header are formated by the
-program called by
-*content-header-filter*.
-Content-header-filter is searched from variable
-`mime-viewer/content-header-filter-alist'. Its key is major-mode of the
-raw-article-buffer (*Note raw-article-buffer::). If not found, function
+ When content-header is displayed, content-header are formated by the
+program called by *content-header-filter*. Content-header-filter is
+searched from variable `mime-viewer/content-header-filter-alist'. Its
+key is major-mode of the raw-article-buffer (*Note
+raw-article-buffer::). If not found, function
`mime-viewer/default-content-header-filter' is called.
-
- -- Variable: mime-viewer/childrens-header-showing-Content-Type-list
-
+ - Variable: mime-viewer/childrens-header-showing-Content-Type-list
List of content-types. If content-type of parent of a part is a
member of this variable, its content-header is displayed. Default
value is `'("message/rfc822" "message/news")'.
This variable is referred by the function
`mime-viewer/header-visible-p'.
-
-
- -- Function: mime-viewer/header-visible-p RCNUM CINFO &optional CTYPE
-
+ - Function: mime-viewer/header-visible-p RCNUM CINFO &optional CTYPE
Returns `t' if a part which reversed-content-number is RCNUM in
content-info CINFO is displayed.
If you know content-type, you can specify by CTYPE.
-
-
- -- Variable: mime-viewer/content-header-filter-alist
-
+ - Variable: mime-viewer/content-header-filter-alist
Association-list whose key is major-mode of a raw-article-buffer,
value is content-header-filter.
-
-
- -- Function: mime-viewer/default-content-header-filter
-
+ - Function: mime-viewer/default-content-header-filter
It is called when content-header-filter is not found in variable
`mime-viewer/content-header-filter-alist'.
It refers `mime-viewer/ignored-field-regexp'.
-
-
- -- Variable: mime-viewer/ignored-field-list
-
+ - Variable: mime-viewer/ignored-field-list
List of regular expression to represent invisible fields even if
content-header is displayed.
Please use function `tm:add-fields' or `tm:delete-fields' to set
it.
-
-
-
\1f
-File: tm-view-en.info, Node: content-body, Next: content-separator, Prev: content-header, Up: MIME display
+File: tm-view-en.info, Node: content-body, Next: content-separator, Prev: content-header, Up: MIME display
content-body
============
-*content-body* represents content of the
-part.
+ *content-body* represents content of the part.
-tm-view does not display raw content body. For example, if a content
+ tm-view does not display raw content body. For example, if a content
has binary, it is hidden. If a content has text/enriched, it is
formated. Namely content body is hidden or formated.
-Function `mime-viewer/body-visible-p' is a judge function whether
+ Function `mime-viewer/body-visible-p' is a judge function whether
content-body of a content is displayed. If it returns `nil',
content-body is hidden. In default, it returns non-`nil' when
content-type of a part is a member of variable
`mime-viewer/default-showing-Content-Type-list'.
-When content-body of a content is displayed, content-body is formated by
-*content-filter*. Content-filter is
-searched from variable `mime-viewer/content-filter-alist'. At this
-time, major-mode of the raw-article-buffer (*Note raw-article-buffer::)
-is used as the key.
+ When content-body of a content is displayed, content-body is
+formated by *content-filter*. Content-filter is searched from variable
+`mime-viewer/content-filter-alist'. At this time, major-mode of the
+raw-article-buffer (*Note raw-article-buffer::) is used as the key.
-If it is not found, function `mime-viewer/default-content-filter' is
+ If it is not found, function `mime-viewer/default-content-filter' is
called.
-
- -- Variable: mime-viewer/default-showing-Content-Type-list
-
+ - Variable: mime-viewer/default-showing-Content-Type-list
List of content-type. If content-type of a part is a member of
this variable, its body is displayed.
+ - Function: mime-viewer/body-visible-p RCNUM CINFO &optional CTYPE
+ Return non-`nil', if content-type of a part is displayed. RCNUM
+ is reversed-content-number of a part. CINFO is content-info of
+ the message. If you know content-type of a part, you can specify
+ it as argument CTYPE.
-
- -- Function: mime-viewer/body-visible-p RCNUM CINFO &optional CTYPE
-
- Return non-`nil', if content-type of a part is displayed. RCNUM is
- reversed-content-number of a part. CINFO is content-info of the
- message. If you know content-type of a part, you can specify it as
- argument CTYPE.
-
-
-
- -- Variable: mime-viewer/content-filter-alist
-
+ - Variable: mime-viewer/content-filter-alist
Association-list whose key is major-mode of a raw-article-buffer,
value is content-filter.
-
-
- -- Function: mime-viewer/default-content-filter RCNUM CINFO CTYPE PARAMS SUBJ
-
+ - Function: mime-viewer/default-content-filter RCNUM CINFO CTYPE
+ PARAMS SUBJ
It is called when content-body of a part should be displayed and
content-filter is not found in `mime-viewer/content-filter-alist'.
In default, it does nothing.
-
-
-
\1f
-File: tm-view-en.info, Node: content-separator, Prev: content-body, Up: MIME display
+File: tm-view-en.info, Node: content-separator, Prev: content-body, Up: MIME display
content-separator
=================
-*content-separator* is displayed to
-represent boundary of contents.
+ *content-separator* is displayed to represent boundary of contents.
-Content-separator is displayed by function
+ Content-separator is displayed by function
`mime-viewer/default-content-separator'. In default, it displays
line-break when content-header and content-body are not displayed.
-If you want to change this condition, please redefine this function.
-
-
- -- Function: mime-viewer/default-content-separator RCNUM CINFO CTYPE PARAMS SUBJ
+ If you want to change this condition, please redefine this function.
+ - Function: mime-viewer/default-content-separator RCNUM CINFO CTYPE
+ PARAMS SUBJ
Display content-separator. CNUM is content-number of a content.
CINFO is content-info of the message. CTYPE is content-type of a
content. PARAMS is Content-Type field parameters of a content.
In default, it displays line-break when content-header and
content-body are not displayed.
-
-
-
\1f
-File: tm-view-en.info, Node: mime/viewer-mode, Next: method, Prev: MIME display, Up: Top
+File: tm-view-en.info, Node: mime/viewer-mode, Next: method, Prev: MIME display, Up: Top
Navigation in mime/viewer-mode
******************************
-`mime/viewer-mode' has following functions:
+ `mime/viewer-mode' has following functions:
`u'
goes to the upper content (returns to the Summary mode if the
For URL-button, it drives WWW browser
-
*[Notice]*
-
(*1) Not return to the Summary mode unless tm-view has been setup
using tm-mh-e, tm-vm, gnus-mime, tm-gnus, tm-rmail etc.
(*2) Actual playback/extract/print will be performed by a method.
-
-
-
\1f
-File: tm-view-en.info, Node: method, Next: Two buffers for an article, Prev: mime/viewer-mode, Up: Top
+File: tm-view-en.info, Node: method, Next: Two buffers for an article, Prev: mime/viewer-mode, Up: Top
Mechanism of decoding
*********************
-In `mime/viewer-mode', you can do play (`v'), extract
-(`e'), or print (`C-c C-p') for each parts. These operations
-are called *decoding
-operation(s) (for a part)*. And kind of decoding operations are called
-*decoding-mode*.
+ In `mime/viewer-mode', you can do play (`v'), extract (`e'), or
+print (`C-c C-p') for each parts. These operations are called
+*decoding operation(s) (for a part)*. And kind of decoding operations
+are called *decoding-mode*.
-When decoding operation is driven, tm-view calls a procedure matched for
-the condition, such as content-type (*Note (tm-en)content-type::) of the
-part or its environment. This procedure is called
-*method*.
+ When decoding operation is driven, tm-view calls a procedure matched
+for the condition, such as content-type (*Note (tm-en)content-type::)
+of the part or its environment. This procedure is called *method*.
-There are two kinds of methods. One is Emacs Lisp function, called
-*internal method*. Another one is
-external program, called *external method*.
+ There are two kinds of methods. One is Emacs Lisp function, called
+*internal method*. Another one is external program, called *external
+method*.
-Internal method operates in Emacs, so it can do carefully.
+ Internal method operates in Emacs, so it can do carefully.
-External method is called as asynchronous process, so Emacs does not
+ External method is called as asynchronous process, so Emacs does not
wait while method is running. So it is good for big data, such as
audio, image or video.
-
* Menu:
* decoding-condition:: Setting decoding condition for parts
* environment variables:: Environment variables
-
\1f
-File: tm-view-en.info, Node: decoding-condition, Next: environment variables, Prev: method, Up: method
+File: tm-view-en.info, Node: decoding-condition, Next: environment variables, Prev: method, Up: method
Setting decoding condition for parts
====================================
-When decoding operation is driven, tm-view calls a method matched for
+ When decoding operation is driven, tm-view calls a method matched for
the condition searched from the variable
`mime/content-decoding-condition'.
-Variable `mime/content-decoding-condition' is defined as a list with the
-following syntax:
+ Variable `mime/content-decoding-condition' is defined as a list with
+the following syntax:
(condition_1 condition_2 ...)
-Each condition are association-list with the following syntax:
+ Each condition are association-list with the following syntax:
((field-type_1 . value_1)
(field-type_2 . value_2)
...)
-For example, if you want to call the external method named tm-plain to
-decode every text/plain (*Note (tm-en)text/plain::) type parts, you can
-define the condition like:
+ For example, if you want to call the external method named tm-plain
+to decode every text/plain (*Note (tm-en)text/plain::) type parts, you
+can define the condition like:
((type . "text/plain")
(method "tm-plain" nil 'file 'type 'encoding 'mode 'name))
-This condition definition will match all parts whose content-type (*Note
-(tm-en)content-type::) are text/plain. Here is an another example:
+ This condition definition will match all parts whose content-type
+(*Note (tm-en)content-type::) are text/plain. Here is an another
+example:
((type . "text/plain")
(method "tm-plain" nil 'file 'type 'encoding 'mode 'name)
(mode . "play"))
-This will match the part whose type is text/plain and the mode is play.
+ This will match the part whose type is text/plain and the mode is
+play.
-Here is an another example:
+ Here is an another example:
((method "metamail" t "-m" "tm" "-x" "-d" "-z" "-e" 'file)
(mode . "play"))
-This will match all parts which have a mode of play.
-
-The conditions defined in a variable `mime/content-decoding-condition'
-are examined from top to bottom. The first matching condition becomes
-valid and the method specified in that condition definition will be
-executed.
+ This will match all parts which have a mode of play.
+ The conditions defined in a variable
+`mime/content-decoding-condition' are examined from top to bottom. The
+first matching condition becomes valid and the method specified in that
+condition definition will be executed.
* Menu:
* method value:: Format of method value
-* Example of decoding-condition::
-
+* Example of decoding-condition::
\1f
-File: tm-view-en.info, Node: method value, Next: Example of decoding-condition, Prev: decoding-condition, Up: decoding-condition
+File: tm-view-en.info, Node: method value, Next: Example of decoding-condition, Prev: decoding-condition, Up: decoding-condition
Format of method value
----------------------
-You can specify the method field of the decoding-condition definition in
-two different ways,
+ You can specify the method field of the decoding-condition
+definition in two different ways,
(method . SYMBOL)
can be accepted.
-When a symbol is specified in the method field, a function whose name is
-SYMBOL will be called as an internal method.
+ When a symbol is specified in the method field, a function whose
+name is SYMBOL will be called as an internal method.
-When a list is specified in the method field, it will be called as an
+ When a list is specified in the method field, it will be called as an
external method.
-The list below shows the meaning of the parameters when the external
+ The list below shows the meaning of the parameters when the external
method is specified in the method field.
`STRING'
`ARGUMENTs'
list of arguments passed to an external method
-
-An argument passed to an external method can be in one of the following
-formats:
+ An argument passed to an external method can be in one of the
+following formats:
`STRING'
string itself
`'STRING'
value gotten using STRING as a key from decoding-condition
-
-`'SYMBOL' can be one of the following:
+ `'SYMBOL' can be one of the following:
`'file'
name of a file holding the original content
`'name'
name of a file created by decode operation
-
-
-`'STRING' is used to search a parameter of the Content-Type field whose
-name matches with it, and pass the value of that parameter to the
+ `'STRING' is used to search a parameter of the Content-Type field
+whose name matches with it, and pass the value of that parameter to the
external method.
-
-
\1f
-File: tm-view-en.info, Node: Example of decoding-condition, Prev: method value, Up: decoding-condition
+File: tm-view-en.info, Node: Example of decoding-condition, Prev: method value, Up: decoding-condition
Example of decoding-condition
-----------------------------
-Following is an example of decoding-condition:
+ Following is an example of decoding-condition:
(defvar mime/content-decoding-condition
'(((type . "text/plain")
"-m" "tm" "-x" "-d" "-z" "-e" 'file)(mode . "play"))
))
-
-For example, if you want to use metamail to decode any contents,
+ For example, if you want to use metamail to decode any contents,
(setq mime/content-decoding-condition
'(
will work.
-Variable `mime/content-decoding-condition' provides you of very flexible
-way to define the conditions of decoding. It can be simple if you only
-need the a few decoding methods, while it can be very complicated if you
-want to use the separate decoding method for each type/mode combination.
+ Variable `mime/content-decoding-condition' provides you of very
+flexible way to define the conditions of decoding. It can be simple if
+you only need the a few decoding methods, while it can be very
+complicated if you want to use the separate decoding method for each
+type/mode combination.
-Following function may be useful to set decoding-condition. It is a
+ Following function may be useful to set decoding-condition. It is a
function of `tl-atype.el'.
-
- -- Function: set-atype SYMBOL ALIST
-
+ - Function: set-atype SYMBOL ALIST
Add condition ALIST to SYMBOL.
*[Example]*
-
(set-atype 'mime/content-decoding-condition
'((type . "message/external-body")
("access-type" . "anon-ftp")
(method . mime/decode-message/external-ftp)
))
-
-
-
\1f
-File: tm-view-en.info, Node: environment variables, Prev: decoding-condition, Up: method
+File: tm-view-en.info, Node: environment variables, Prev: decoding-condition, Up: method
Environment variables
=====================
-Standard methods of tm-view reference some environment variables. You
-can specify them to customize.
+ Standard methods of tm-view reference some environment variables.
+You can specify them to customize.
TM_TMP_DIR
Directory for temporary files or extracted files. If it is
TM_WWW_BROWSER
WWW browser name. If it is omitted, `netscape' is used.
-
-
-
-
\1f
-File: tm-view-en.info, Node: Two buffers for an article, Next: API, Prev: method, Up: Top
+File: tm-view-en.info, Node: Two buffers for an article, Next: API, Prev: method, Up: Top
raw-article-buffer and preview-buffer
*************************************
-tm-view managements two buffers, one is for raw message called
-*raw-article-buffer*, another one is
-to preview for user called
-*preview-buffer*. major-mode of
-raw-article-buffer is same as major-mode for article of original MUA,
-major-mode of preview-buffer is `mime/viewer-mode' (*Note
-mime/viewer-mode::).
+ tm-view managements two buffers, one is for raw message called
+*raw-article-buffer*, another one is to preview for user called
+*preview-buffer*. major-mode of raw-article-buffer is same as
+major-mode for article of original MUA, major-mode of preview-buffer is
+`mime/viewer-mode' (*Note mime/viewer-mode::).
-When called `mime/viewer-mode', tm-view analyzes raw-article-buffer, and
-sets its result to the variable `mime::article/content-info'.
+ When called `mime/viewer-mode', tm-view analyzes raw-article-buffer,
+and sets its result to the variable `mime::article/content-info'.
-After that, tm-view create a preview-buffer corresponded to the
+ After that, tm-view create a preview-buffer corresponded to the
raw-article-buffer. As this time, tm-view modifies header and body of
each parts of the message by specified conditions. Filter program for
-header is called *header-filter*
-(*Note content-header::), filter program for body is called
-*content-filter* (*Note content-body::), and
+header is called *header-filter* (*Note content-header::), filter
+program for body is called *content-filter* (*Note content-body::), and
they are called *filter*.
-When preview-buffer is made, buffer local variable of preview-buffer
+ When preview-buffer is made, buffer local variable of preview-buffer
`mime::preview/content-list' is made to register structure of
-preview-buffer. tm-view manages message by `mime::article/content-info'
-in raw-article-buffer and `mime::preview/content-list' in
-preview-buffer.
+preview-buffer. tm-view manages message by
+`mime::article/content-info' in raw-article-buffer and
+`mime::preview/content-list' in preview-buffer.
*[Notice]*
In this document, I call "content-type" as content-type/subtype of
Content-Type field.
-
-
* Menu:
* raw-article-buffer:: buffer local variables of raw-article-buffer
* preview-buffer:: Buffer local variables of preview-buffer
-
\1f
-File: tm-view-en.info, Node: raw-article-buffer, Next: preview-buffer, Prev: Two buffers for an article, Up: Two buffers for an article
+File: tm-view-en.info, Node: raw-article-buffer, Next: preview-buffer, Prev: Two buffers for an article, Up: Two buffers for an article
buffer local variables of raw-article-buffer
============================================
- -- Structure: mime::content-info RCNUM POINT-MIN POINT-MAX TYPE PARAMETERS ENCODING CHILDREN
-
+ - Structure: mime::content-info RCNUM POINT-MIN POINT-MAX TYPE
+ PARAMETERS ENCODING CHILDREN
structure to represent MIME content in raw-article-buffer. It is
called by *content-info*.
Following is a list of slots of the structure:
- RCNUM
+ RCNUM
"reversed content-number" (list)
- POINT-MIN
+ POINT-MIN
beginning point of region in raw-article-buffer
- POINT-MAX
+ POINT-MAX
end point of region in raw-article-buffer
- TYPE
+ TYPE
content-type/sub-type (string or nil)
- PARAMETERS
+ PARAMETERS
parameter of Content-Type field (association list)
- ENCODING
+ ENCODING
Content-Transfer-Encoding (string or nil)
- CHILDREN
+ CHILDREN
parts included in this part (list of content-infos)
-
If a part includes other parts in its contents, such as multipart
or message/rfc822, content-infos of other parts are included in
CHILDREN, so content-info become a tree.
-
- -- Variable: mime::article/content-info
-
+ - Variable: mime::article/content-info
result of MIME parsing of raw-article-buffer (content-info)
-
- -- Variable: mime::article/preview-buffer
-
+ - Variable: mime::article/preview-buffer
preview-buffer corresponded by this buffer
-
- -- Function: mime-article/point-content-number POINT &optional CINFO
-
+ - Function: mime-article/point-content-number POINT &optional CINFO
In a region managed by content-info CINFO, it returns
content-number corresponded by POINT.
If CINFO is omitted, `mime::article/content-info' is used as
default value.
-
- -- Function: mime-article/rcnum-to-cinfo RCNUM &optional CINFO
-
+ - Function: mime-article/rcnum-to-cinfo RCNUM &optional CINFO
In a region managed by content-info CINFO, it returns content-info
corresponded by reversed-content-number RCNUM.
If CINFO is omitted, `mime::article/content-info' is used as
default value.
-
- -- Function: mime-article/cnum-to-cinfo RCNUM &optional CINFO
-
+ - Function: mime-article/cnum-to-cinfo RCNUM &optional CINFO
In a region managed by content-info CINFO, it returns content-info
corresponded by content-number RCNUM.
If CINFO is omitted, `mime::article/content-info' is used as
default value.
-
- -- Function: mime/flatten-content-info &optional CINFO
-
+ - Function: mime/flatten-content-info &optional CINFO
It returns flatten list of content-info from content-info CINFO
tree.
If CINFO is omitted, `mime::article/content-info' is used as
default value.
-
-
-
\1f
-File: tm-view-en.info, Node: preview-buffer, Prev: raw-article-buffer, Up: Two buffers for an article
+File: tm-view-en.info, Node: preview-buffer, Prev: raw-article-buffer, Up: Two buffers for an article
Buffer local variables of preview-buffer
========================================
- -- Variable: mime::preview/mother-buffer
-
+ - Variable: mime::preview/mother-buffer
Mother buffer of this preview-buffer.
-
- -- Structure: mime::preview-content-info POINT-MIN POINT-MAX BUFFER CONTENT-INFO
-
- structure to represent MIME content in preview-buffer. It is called by
- *preview-content-info*.
+ - Structure: mime::preview-content-info POINT-MIN POINT-MAX BUFFER
+ CONTENT-INFO
+ structure to represent MIME content in preview-buffer. It is
+ called by *preview-content-info*.
Please use reference function
`mime::preview-content-info/SLOT-NAME' to reference slot of
Following is a list of slots of the structure:
- POINT-MIN
+ POINT-MIN
beginning point of region in preview-buffer
- POINT-MAX
+ POINT-MAX
end point of region in preview-buffer
- BUFFER
+ BUFFER
raw-article-buffer corresponding a part
- CONTENT-INFO
+ CONTENT-INFO
content-info corresponding a part
-
-
- -- Variable: mime::preview/content-list
-
+ - Variable: mime::preview/content-list
List of preview-content-info to represent structure of this
preview-buffer.
-
-
- -- Variable: mime::preview/article-buffer
-
+ - Variable: mime::preview/article-buffer
raw-article-buffer corresponded by this preview-buffer.
-
-
- -- Variable: mime::preview/original-major-mode
-
+ - Variable: mime::preview/original-major-mode
major-mode of original buffer.
-
-
- -- Variable: mime::preview/original-window-configuration
-
+ - Variable: mime::preview/original-window-configuration
window-configuration just before made this preview-buffer.
-
-
- -- Function: mime-preview/point-pcinfo POINT &optional PCL
-
+ - Function: mime-preview/point-pcinfo POINT &optional PCL
In a region of preview-buffer managed by preview-content-info PCL,
it returns preview-content-info corresponded by POINT.
If CINFO is omitted, `mime::preview/content-list' is used.
-
-
-
\1f
-File: tm-view-en.info, Node: API, Next: Concept Index, Prev: Two buffers for an article, Up: Top
+File: tm-view-en.info, Node: API, Next: Acknowledgments, Prev: Two buffers for an article, Up: Top
Functions to decode MIME message
********************************
-tm-view provides some available functions to decode and navigate MIME
+ tm-view provides some available functions to decode and navigate MIME
message to each MUA (*Note (tm-en)MUA::)s.
-There are 2 kinds of functions, one is for MIME preview, another one is
-to decode RFC 1522 encoded-word (*Note (tm-en)encoded-word::).
-
+ There are 2 kinds of functions, one is for MIME preview, another one
+is to decode RFC 1522 encoded-word (*Note (tm-en)encoded-word::).
* Menu:
* API about MIME preview:: Function to preview MIME message
* encoded-word decoding:: encoded-word decoder
-
\1f
-File: tm-view-en.info, Node: API about MIME preview, Next: encoded-word decoding, Prev: API, Up: API
+File: tm-view-en.info, Node: API about MIME preview, Next: encoded-word decoding, Prev: API, Up: API
Function to preview MIME message
================================
-
- -- Command: mime/viewer-mode &optional MOTHER CTL ENCODING IBUF OBUF MOTHER-KEYMAP
-
+ - Command: mime/viewer-mode &optional MOTHER CTL ENCODING IBUF OBUF
+ MOTHER-KEYMAP
Parse IBUF as a MIME message, and create preview-buffer into OBUF
to display to user, then enter `mime/viewer-mode' (*Note
mime/viewer-mode::).
CTL is used to specify Content-Type field (*Note
(tm-en)Content-Type field::) information. Its format is output
- format of `mime/Content-Type'. When CTL is specified, tm-view uses
- it instead of Content-Type field of the raw-article-buffer.
+ format of `mime/Content-Type'. When CTL is specified, tm-view
+ uses it instead of Content-Type field of the raw-article-buffer.
- ENCODING is used to specify field-body of Content-Transfer-Encoding
- field. When is is specified, tm-view uses it instead of
- Content-Type field of the raw-article-buffer.
+ ENCODING is used to specify field-body of
+ Content-Transfer-Encoding field. When is is specified, tm-view
+ uses it instead of Content-Type field of the raw-article-buffer.
If MOTHER-KEYMAP is specified, keymap of `mime/viewer-mode'
includes it.
-
-
-
\1f
-File: tm-view-en.info, Node: encoded-word decoding, Prev: API about MIME preview, Up: API
+File: tm-view-en.info, Node: encoded-word decoding, Prev: API about MIME preview, Up: API
encoded-word decoder
====================
-tm-view has functions to decode RFC 1522 encoded-word (*Note
+ tm-view has functions to decode RFC 1522 encoded-word (*Note
(tm-en)encoded-word::).
-
- -- Command: mime/decode-message-header
-
+ - Command: mime/decode-message-header
It decodes encoded-words in message header of current buffer.
If an encoded-word is broken or invalid, or it has non supported
MIME charset (*Note (tm-en)MIME charset::), it is not decoded.
-
-
- -- Command: mime-eword/decode-region START END &optional UNFOLDING MUST-UNFOLD
-
+ - Command: mime-eword/decode-region START END &optional UNFOLDING
+ MUST-UNFOLD
It decodes encoded-words in region START to END.
If an encoded-word is broken or invalid, or it has non supported
If MUST-FOLD is non-nil and decoded result of an encoded-word has
folding or raw CR or LF, it unfolds or delete raw CR or LF.
-
-
- -- Function: mime-eword/decode-string STRING &optional MUST-UNFOLD
-
+ - Function: mime-eword/decode-string STRING &optional MUST-UNFOLD
It decodes encoded-words in STRING and returns decoded string.
If an encoded-word is broken or invalid, or it has non supported
If MUST-FOLD is non-nil and decoded result of an encoded-word has
folding or raw CR or LF, it unfolds or delete raw CR or LF.
+\1f
+File: tm-view-en.info, Node: Acknowledgments, Next: Concept Index, Prev: API, Up: Top
+
+Acknowledgments
+***************
+
+ First of all, 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.
+ I thank ENAMI Tsugutomo for work of `mime.el', which is an origin of
+`tm-ew-d.el' and `mel-b.el', and permission to rewrite for tm.
+ 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.
+
+ Last of all, I thank members of two tm mailing lists, Japanese and
+English version.
\1f
-File: tm-view-en.info, Node: Concept Index, Next: Function Index, Prev: API, Up: Top
+File: tm-view-en.info, Node: Concept Index, Next: Function Index, Prev: Acknowledgments, Up: Top
Concept Index
*************
-
* Menu:
-* content-body: content-body. 5.
-* content-filter: content-body. 19.
-* content-filter: Two buffers for an article. 21.
-* content-header-filter: content-header. 25.
-* content-info: raw-article-buffer. 10.
-* content-number: content-button. 15.
-* content-separator: content-separator. 5.
-* decoding operation(s) (for a part): method. 8.
-* decoding-mode: method. 9.
-* external method: method. 19.
-* filter: Introduction. 17.
-* filter: Two buffers for an article. 23.
-* header-filter: Two buffers for an article. 20.
-* internal method: method. 17.
-* method: Introduction. 14.
-* method: method. 14.
-* preview-buffer: Two buffers for an article. 8.
-* preview-content-info: preview-buffer. 14.
-* raw-article-buffer: Two buffers for an article. 6.
-
+* content-body: content-body.
+* content-filter <1>: content-body.
+* content-filter: Two buffers for an article.
+* content-header-filter: content-header.
+* content-info: raw-article-buffer.
+* content-number: content-button.
+* content-separator: content-separator.
+* decoding operation(s) (for a part): method.
+* decoding-mode: method.
+* external method: method.
+* filter <1>: Introduction.
+* filter: Two buffers for an article.
+* header-filter: Two buffers for an article.
+* internal method: method.
+* method <1>: method.
+* method: Introduction.
+* preview-buffer: Two buffers for an article.
+* preview-content-info: preview-buffer.
+* raw-article-buffer: Two buffers for an article.
\1f
-File: tm-view-en.info, Node: Function Index, Next: Variable Index, Prev: Concept Index, Up: Top
+File: tm-view-en.info, Node: Function Index, Next: Variable Index, Prev: Concept Index, Up: Top
Function Index
**************
-
* Menu:
-* mime-article/cnum-to-cinfo: raw-article-buffer. 73.
-* mime-article/point-content-number: raw-article-buffer. 55.
-* mime-article/rcnum-to-cinfo: raw-article-buffer. 64.
-* mime::content-info: raw-article-buffer. 7.
-* mime/decode-message-header: encoded-word decoding. 11.
-* mime-eword/decode-region: encoded-word decoding. 20.
-* mime-eword/decode-string: encoded-word decoding. 34.
-* mime/flatten-content-info: raw-article-buffer. 82.
-* mime::preview-content-info: preview-buffer. 12.
-* mime-preview/point-pcinfo: preview-buffer. 63.
-* mime-viewer/body-visible-p: content-body. 37.
-* mime-viewer/default-content-filter: content-body. 53.
-* mime-viewer/default-content-header-filter: content-header. 61.
-* mime-viewer/default-content-separator: content-separator. 17.
-* mime-viewer/header-visible-p: content-header. 45.
-* mime/viewer-mode: API about MIME preview. 8.
-* set-atype: Example of decoding-condition. 57.
-
+* mime-article/cnum-to-cinfo: raw-article-buffer.
+* mime-article/point-content-number: raw-article-buffer.
+* mime-article/rcnum-to-cinfo: raw-article-buffer.
+* mime-eword/decode-region: encoded-word decoding.
+* mime-eword/decode-string: encoded-word decoding.
+* mime-preview/point-pcinfo: preview-buffer.
+* mime-viewer/body-visible-p: content-body.
+* mime-viewer/default-content-filter: content-body.
+* mime-viewer/default-content-header-filter: content-header.
+* mime-viewer/default-content-separator: content-separator.
+* mime-viewer/header-visible-p: content-header.
+* mime/decode-message-header: encoded-word decoding.
+* mime/flatten-content-info: raw-article-buffer.
+* mime/viewer-mode: API about MIME preview.
+* mime::content-info: raw-article-buffer.
+* mime::preview-content-info: preview-buffer.
+* set-atype: Example of decoding-condition.
\1f
-File: tm-view-en.info, Node: Variable Index, Prev: Function Index, Up: Top
+File: tm-view-en.info, Node: Variable Index, Prev: Function Index, Up: Top
Variable Index
**************
-
* Menu:
-* mime::article/content-info: raw-article-buffer. 45.
-* mime::article/preview-buffer: raw-article-buffer. 50.
-* mime::preview/article-buffer: preview-buffer. 45.
-* mime::preview/content-list: preview-buffer. 38.
-* mime::preview/mother-buffer: preview-buffer. 7.
-* mime::preview/original-major-mode: preview-buffer. 51.
-* mime::preview/original-window-configuration: preview-buffer. 57.
-* mime-viewer/childrens-header-showing-Content-Type-list: content-header. 34.
-* mime-viewer/content-button-ignored-ctype-list: content-button. 50.
-* mime-viewer/content-filter-alist: content-body. 46.
-* mime-viewer/content-header-filter-alist: content-header. 54.
-* mime-viewer/default-showing-Content-Type-list: content-body. 30.
-* mime-viewer/ignored-field-list: content-header. 70.
-\1f\f
-Tag table:
-Node: Top\7f162
-Node: Introduction\7f883
-Node: MIME display\7f1717
-Node: content-button\7f4001
-Node: content-header\7f5689
-Node: content-body\7f8326
-Node: content-separator\7f10238
-Node: mime/viewer-mode\7f11101
-Node: method\7f12253
+* mime-viewer/childrens-header-showing-Content-Type-list: content-header.
+* mime-viewer/content-button-ignored-ctype-list: content-button.
+* mime-viewer/content-filter-alist: content-body.
+* mime-viewer/content-header-filter-alist: content-header.
+* mime-viewer/default-showing-Content-Type-list: content-body.
+* mime-viewer/ignored-field-list: content-header.
+* mime::article/content-info: raw-article-buffer.
+* mime::article/preview-buffer: raw-article-buffer.
+* mime::preview/article-buffer: preview-buffer.
+* mime::preview/content-list: preview-buffer.
+* mime::preview/mother-buffer: preview-buffer.
+* mime::preview/original-major-mode: preview-buffer.
+* mime::preview/original-window-configuration: preview-buffer.
+
+
+\1f
+Tag Table:
+Node: Top\7f99
+Node: Introduction\7f802
+Node: MIME display\7f1646
+Node: content-button\7f3934
+Node: content-header\7f5646
+Node: content-body\7f8280
+Node: content-separator\7f10203
+Node: mime/viewer-mode\7f11082
+Node: method\7f12236
Node: decoding-condition\7f13342
-Node: method value\7f15115
-Node: Example of decoding-condition\7f16825
-Node: environment variables\7f19390
-Node: Two buffers for an article\7f19896
-Node: raw-article-buffer\7f21434
-Node: preview-buffer\7f23971
-Node: API\7f25642
-Node: API about MIME preview\7f26189
-Node: encoded-word decoding\7f27351
-Node: Concept Index\7f28774
-Node: Function Index\7f30062
-Node: Variable Index\7f31244
+Node: method value\7f15142
+Node: Example of decoding-condition\7f16871
+Node: environment variables\7f19443
+Node: Two buffers for an article\7f19950
+Node: raw-article-buffer\7f21501
+Node: preview-buffer\7f24021
+Node: API\7f25673
+Node: API about MIME preview\7f26230
+Node: encoded-word decoding\7f27400
+Node: Acknowledgments\7f28825
+Node: Concept Index\7f29539
+Node: Function Index\7f30765
+Node: Variable Index\7f31930
\1f
-End tag table
+End Tag Table
<!doctype sinfo system>
-<!-- $Id: tm-view-en.sgml,v 1.1 1996/11/29 19:09:27 morioka Exp $ -->
+<!-- $Id: tm-view-en.sgml,v 3.0 1996/12/25 19:07:20 morioka Exp $ -->
<head>
-<title>tm-view 7.77 Reference Manual (English Version)
+<title>tm-view 7.79 Reference Manual (English Version)
<author>MORIOKA Tomohiko <mail>morioka@jaist.ac.jp</mail>
-<date>1996/10/11
+<date>1996/12/25
<toc>
</head>
</defun>
+<h1> Acknowledgments
+<node> Acknowledgments
+<p>
+First of all, 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.
+<p>
+I thank ENAMI Tsugutomo for work of <file>mime.el</file>, which is an
+origin of <file>tm-ew-d.el</file> and <file>mel-b.el</file>, and
+permission to rewrite for tm.
+<p>
+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.
+<p>
+Last of all, I thank members of two tm mailing lists, Japanese and
+English version.
+
+
<h1> Concept Index
<node> Concept Index
\input texinfo.tex
@setfilename tm-view-en.info
-@settitle{tm-view 7.77 Reference Manual (English Version)}
+@settitle{tm-view 7.79 Reference Manual (English Version)}
@titlepage
-@title tm-view 7.77 Reference Manual (English Version)
+@title tm-view 7.79 Reference Manual (English Version)
@author MORIOKA Tomohiko <morioka@@jaist.ac.jp>
-@subtitle 1996/10/11
+@subtitle 1996/12/25
@end titlepage
@node Top, Introduction, (dir), (dir)
-@top tm-view 7.77 Reference Manual (English Version)
+@top tm-view 7.79 Reference Manual (English Version)
@ifinfo
* method:: Mechanism of decoding
* Two buffers for an article:: raw-article-buffer and preview-buffer
* API:: Functions to decode MIME message
+* Acknowledgments::
* Concept Index::
* Function Index::
* Variable Index::
@node Introduction, MIME display, Top, Top
@chapter What is tm-view?
+@cindex filter
+@cindex method
The tm-view is a general MIME viewer running on GNU Emacs.@refill
tm-view is a user interface kernel to view and navigate MIME message.
tm-view drives some programs to navigate each content-type
-(@ref{(tm-en)content-type})s, they are called
-@cindex{method}@strong{method} (@ref{method}). tm-view calls some
-programs to display each contents and headers in preview buffer, they
-are called @cindex{filter}@strong{filter} (@ref{Two buffers for an
-article}). Method and filters are tm-view application program. They
-expand tm-view to treat various kinds of MIME types.
+(@ref{(tm-en)content-type})s, they are called @strong{method}
+(@ref{method}). tm-view calls some programs to display each contents
+and headers in preview buffer, they are called @strong{filter} (@ref{Two buffers for an article}). Method and filters are tm-view application
+program. They expand tm-view to treat various kinds of MIME types.
@node MIME display, mime/viewer-mode, Introduction, Top
@node content-button, content-header, MIME display, MIME display
@section content-button
+@cindex content-number
content-subject displays abstract for the part. It is placed in top of
the part.@refill
First number field represents position of a content in the part. It is
-called @cindex{content-number}@strong{content-number}. It can be
-considered as the chapter number in the message.@refill
+called @strong{content-number}. It can be considered as the chapter
+number in the message.@refill
Second string part represents title. It is created by following:
@node content-header, content-body, content-button, MIME display
@section content-header
+@cindex content-header-filter
A content header displays the header portion of a part in the
preview-buffer. However it is annoying to display header for every
@code{mime-viewer/childrens-header-showing-Content-Type-list}.@refill
When content-header is displayed, content-header are formated by the
-program called by
-@cindex{content-header-filter}@strong{content-header-filter}.
-Content-header-filter is searched from variable
+program called by @strong{content-header-filter}. Content-header-filter
+is searched from variable
@code{mime-viewer/content-header-filter-alist}. Its key is major-mode
of the raw-article-buffer (@ref{raw-article-buffer}). If not found,
function @code{mime-viewer/default-content-header-filter} is
@node content-body, content-separator, content-header, MIME display
@section content-body
+@cindex content-filter
+@cindex content-body
-@cindex{content-body}@strong{content-body} represents content of the
-part.@refill
+@strong{content-body} represents content of the part.@refill
tm-view does not display raw content body. For example, if a content
has binary, it is hidden. If a content has text/enriched, it is
@code{mime-viewer/default-showing-Content-Type-list}.@refill
When content-body of a content is displayed, content-body is formated by
-@cindex{content-filter}@strong{content-filter}. Content-filter is
-searched from variable @code{mime-viewer/content-filter-alist}. At this
-time, major-mode of the raw-article-buffer (@ref{raw-article-buffer}) is
-used as the key.
+@strong{content-filter}. Content-filter is searched from variable
+@code{mime-viewer/content-filter-alist}. At this time, major-mode of
+the raw-article-buffer (@ref{raw-article-buffer}) is used as the key.
If it is not found, function
@code{mime-viewer/default-content-filter} is called.
@node content-separator, , content-body, MIME display
@section content-separator
+@cindex content-separator
-@cindex{content-separator}@strong{content-separator} is displayed to
-represent boundary of contents.@refill
+@strong{content-separator} is displayed to represent boundary of
+contents.@refill
Content-separator is displayed by function
@code{mime-viewer/default-content-separator}. In default, it displays
@node method, Two buffers for an article, mime/viewer-mode, Top
@chapter Mechanism of decoding
+@cindex external method
+@cindex internal method
+@cindex method
+@cindex decoding-mode
+@cindex decoding operation(s) (for a part)
In @code{mime/viewer-mode}, you can do play (@kbd{v}), extract
(@kbd{e}), or print (@kbd{C-c C-p}) for each parts. These operations
-are called @cindex{decoding operation(s) (for a part)}@strong{decoding
-operation(s) (for a part)}. And kind of decoding operations are called
-@cindex{decoding-mode}@strong{decoding-mode}.@refill
+are called @strong{decoding operation(s) (for a part)}. And kind of
+decoding operations are called @strong{decoding-mode}.@refill
When decoding operation is driven, tm-view calls a procedure matched for
the condition, such as content-type (@ref{(tm-en)content-type}) of the
part or its environment. This procedure is called
-@cindex{method}@strong{method}.@refill
+@strong{method}.@refill
There are two kinds of methods. One is Emacs Lisp function, called
-@cindex{internal method}@strong{internal method}. Another one is
-external program, called @cindex{external method}@strong{external
-method}.@refill
+@strong{internal method}. Another one is external program, called
+@strong{external method}.@refill
Internal method operates in Emacs, so it can do carefully.@refill
@node Two buffers for an article, API, method, Top
@chapter raw-article-buffer and preview-buffer
+@cindex filter
+@cindex content-filter
+@cindex header-filter
+@cindex preview-buffer
+@cindex raw-article-buffer
tm-view managements two buffers, one is for raw message called
-@cindex{raw-article-buffer}@strong{raw-article-buffer}, another one is
-to preview for user called
-@cindex{preview-buffer}@strong{preview-buffer}. major-mode of
-raw-article-buffer is same as major-mode for article of original MUA,
-major-mode of preview-buffer is @code{mime/viewer-mode}
-(@ref{mime/viewer-mode}).@refill
+@strong{raw-article-buffer}, another one is to preview for user called
+@strong{preview-buffer}. major-mode of raw-article-buffer is same as
+major-mode for article of original MUA, major-mode of preview-buffer is
+@code{mime/viewer-mode} (@ref{mime/viewer-mode}).@refill
When called @code{mime/viewer-mode}, tm-view analyzes
raw-article-buffer, and sets its result to the variable
After that, tm-view create a preview-buffer corresponded to the
raw-article-buffer. As this time, tm-view modifies header and body of
each parts of the message by specified conditions. Filter program for
-header is called @cindex{header-filter}@strong{header-filter}
-(@ref{content-header}), filter program for body is called
-@cindex{content-filter}@strong{content-filter} (@ref{content-body}), and
-they are called @cindex{filter}@strong{filter}.@refill
+header is called @strong{header-filter} (@ref{content-header}), filter
+program for body is called @strong{content-filter} (@ref{content-body}),
+and they are called @strong{filter}.@refill
When preview-buffer is made, buffer local variable of preview-buffer
@code{mime::preview/content-list} is made to register structure of
@node raw-article-buffer, preview-buffer, Two buffers for an article, Two buffers for an article
@section buffer local variables of raw-article-buffer
+@cindex content-info
@deffn{Structure} mime::content-info rcnum point-min point-max type parameters encoding children
structure to represent MIME content in raw-article-buffer. It is called
-by @cindex{content-info}@strong{content-info}.@refill
+by @strong{content-info}.@refill
Please use reference function @code{mime::content-info/SLOT-NAME} to
reference slot of content-info. Their argument is only
@node preview-buffer, , raw-article-buffer, Two buffers for an article
@section Buffer local variables of preview-buffer
+@cindex preview-content-info
@defvar mime::preview/mother-buffer
@deffn{Structure} mime::preview-content-info point-min point-max buffer content-info
structure to represent MIME content in preview-buffer. It is called by
-@cindex{preview-content-info}@strong{preview-content-info}.@refill
+@strong{preview-content-info}.@refill
Please use reference function
@code{mime::preview-content-info/SLOT-NAME} to reference slot of
-@node API, Concept Index, Two buffers for an article, Top
+@node API, Acknowledgments, Two buffers for an article, Top
@chapter Functions to decode MIME message
tm-view provides some available functions to decode and navigate MIME
-@node Concept Index, Function Index, API, Top
+@node Acknowledgments, Concept Index, API, Top
+@chapter Acknowledgments
+
+First of all, 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
+
+Last of all, I thank members of two tm mailing lists, Japanese and
+English version.
+
+
+@node Concept Index, Function Index, Acknowledgments, Top
@chapter Concept Index
@printindex cp
\1f
File: tm-view-ja.info, Node: Top, Next: Introduction, Prev: (dir), Up: (dir)
-tm-view 7.77 Reference Manual\e$B!JF|K\8lHG!K\e(B
+tm-view 7.79 Reference Manual\e$B!JF|K\8lHG!K\e(B
*****************************************
* method:: \e$B:F@8=hM}$N<B8=\e(B
* Two buffers for an article:: raw-article-buffer \e$B$H\e(B preview-buffer
* API:: MIME message \e$B$N\e(B decode \e$B$K4X$9$k4X?t\e(B
+* Acknowledgments:: \e$B<U<-\e(B
* Concept Index:: \e$B35G0:w0z\e(B
* Function Index:: \e$B4X?t:w0z\e(B
* Variable Index:: \e$BJQ?t:w0z\e(B
tm-view \e$B$O\e(B MIME message \e$B$r1\Mw$9$k$?$a$N\e(B user interface \e$B$N3K$G$"$j!"$=$N\e(B
\e$B>e$G3F\e(B content-type (*Note (tm-ja)content-type::) \e$B$r07$&$?$a$N\e(B
-*method* (*Note method::) \e$B$H8F$P$l$k%W%m%0%i%`$rF0:n\e(B
-\e$B$5$;$^$9!#$^$?!"\e(BMIME message \e$B$NI=<($N;EJ}$r7h$a$k\e(B
-*filter* (*Note Two buffers for an article::) \e$B$H8F$P\e(B
-\e$B$l$k%W%m%0%i%`$r5/F0;~$K8F$S=P$7$^$9!#\e(Bmethod \e$B$H\e(B filter \e$B$r\e(B tm-view \e$B$KAH$_\e(B
-\e$B9~$`;v$K$h$C$F!"\e(B`mime/viewer-mode' \e$B$G$5$^$6$^$J\e(B MIME content-type \e$B$r07$&\e(B
-\e$B;v$,$G$-$^$9!#\e(B
+*method* (*Note method::) \e$B$H8F$P$l$k%W%m%0%i%`$rF0:n$5$;$^$9!#$^$?!"\e(B
+MIME message \e$B$NI=<($N;EJ}$r7h$a$k\e(B *filter* (*Note Two buffers for an
+article::) \e$B$H8F$P$l$k%W%m%0%i%`$r5/F0;~$K8F$S=P$7$^$9!#\e(Bmethod \e$B$H\e(B filter
+\e$B$r\e(B tm-view \e$B$KAH$_9~$`;v$K$h$C$F!"\e(B`mime/viewer-mode' \e$B$G$5$^$6$^$J\e(B MIME
+content-type \e$B$r07$&;v$,$G$-$^$9!#\e(B
content-button
==============
-*content-button* \e$B$O\e(B part \e$B$N@hF,$K$"$C$F!"\e(B
-\e$B$=$N\e(B part \e$B$K4X$9$kBg$^$+$J>pJs$rI=<($9$kItJ,$G$9!#\e(B
+*content-button* \e$B$O\e(B part \e$B$N@hF,$K$"$C$F!"$=$N\e(B part \e$B$K4X$9$kBg$^$+\e(B
+\e$B$J>pJs$rI=<($9$kItJ,$G$9!#\e(B
\e$BI8=`$G$O\e(B
content-header
==============
-*content-header* \e$B$O$"$k\e(B part \e$B$N\e(B header \e$B$r\e(B
-\e$BI=<($9$kItJ,$G$9!#$7$+$7!"A4$F$N\e(B part \e$B$N\e(B content-header \e$B$rI=<($9$k$N$O]5\e(B
-\e$BF+$7$$$N$G!"0J2<$N$h$&$J\e(B mechanism \e$B$K$h$C$FI=<($9$k$+$7$J$$$+$r7h$a$F$$\e(B
-\e$B$^$9!#\e(B
+*content-header* \e$B$O$"$k\e(B part \e$B$N\e(B header \e$B$rI=<($9$kItJ,$G$9!#$7$+$7!"\e(B
+\e$BA4$F$N\e(B part \e$B$N\e(B content-header \e$B$rI=<($9$k$N$O]5F+$7$$$N$G!"0J2<$N$h$&$J\e(B
+mechanism \e$B$K$h$C$FI=<($9$k$+$7$J$$$+$r7h$a$F$$$^$9!#\e(B
\e$B$"$k\e(B part \e$B$N\e(B reversed-content-number \e$B$r4X?t\e(B
`mime-viewer/header-visible-p' \e$B$KM?$($?;~$NJV$jCM$,\e(B `t' \e$B$K$J$k>l9g!"$=$N\e(B
\e$B$,!":FDj5A$7$?>l9g!"$3$NJQ?t$NM-8z@-$OJ]>Z$5$l$J$$$N$GCm0U$7$F2<$5$$!#\e(B
content-header \e$B$,I=<($5$l$k>l9g!"\e(Bcontent-header \e$B$O\e(B
-*content-header-filter* \e$B$H8F$P$l$k\e(B
-program \e$B$K$h$C$F@07A$5$l$^$9!#\e(Bcontent-header-filter \e$B$O\e(B
-raw-article-buffer (*Note raw-article-buffer::) \e$B$N\e(B major-mode \e$B$r\e(B key \e$B$H\e(B
-\e$B$7$FJQ?t\e(B `mime-viewer/content-header-filter-alist' \e$B$+$iC5$5$l$^$9!#$b$7!"\e(B
+*content-header-filter* \e$B$H8F$P$l$k\e(B program \e$B$K$h$C$F@07A$5$l$^$9!#\e(B
+content-header-filter \e$B$O\e(B raw-article-buffer (*Note raw-article-buffer::)
+\e$B$N\e(B major-mode \e$B$r\e(B key \e$B$H$7$FJQ?t\e(B
+`mime-viewer/content-header-filter-alist' \e$B$+$iC5$5$l$^$9!#$b$7!"\e(B
content-header-filter \e$B$,8+$D$+$i$J$+$C$?>l9g!"4X?t\e(B
`mime-viewer/default-content-header-filter' \e$B$,8F$P$l$^$9!#\e(B
content-body
============
-*content-body* \e$B$O\e(B part \e$B$NFbMF$rI=<($9$kItJ,\e(B
-\e$B$G$9!#\e(B
+*content-body* \e$B$O\e(B part \e$B$NFbMF$rI=<($9$kItJ,$G$9!#\e(B
\e$BA4$F$N\e(B part \e$B$NFbMF$rI=<($G$-$k$H$O8B$i$J$$$7!"$^$?!"I=<($7$?$/$J$$\e(B part
\e$B$bB8:_$9$k$N$G!"0J2<$N$h$&$JJ}K!$GI=<($9$k$+$7$J$$$+$r7h$a$F$$$^$9!#\e(B
+
\e$B$"$k\e(B part \e$B$N\e(B content-body \e$B$rI=<($9$k$+$I$&$+$O!"4X?t\e(B
`mime-viewer/body-visible-p' \e$B$,\e(B `t' \e$B$K$J$k$+$I$&$+$G7h$^$j$^$9!#I8=`$G$O!"\e(B
\e$B$"$k\e(B part \e$B$N\e(B content-type \e$B$,JQ?t\e(B
content-separator
=================
-*content-separator* \e$B$O\e(B part \e$B$N0lHV:G8e\e(B
-\e$B$K\e(B part \e$B4V$N6-L\$rL@$i$+$K$9$k$?$a$KI=<($5$l$^$9!#\e(B
+*content-separator* \e$B$O\e(B part \e$B$N0lHV:G8e$K\e(B part \e$B4V$N6-L\$rL@$i$+$K\e(B
+\e$B$9$k$?$a$KI=<($5$l$^$9!#\e(B
content-separator \e$B$O4X?t\e(B `mime-viewer/default-content-separator'\e$B$K$h$C$F\e(B
\e$BI=<($5$l$^$9!#I8=`$G$O!"\e(Bcontent-header \e$B$b\e(B content-body \e$B$bI=<($5$l$J$$>l\e(B
play, extract, print \e$B$H$$$&\e(B decode \e$BA`:n$N<oN`$N$3$H$r\e(B
*decoding-mode* \e$B$H8F$V$3$H$K$7$^$9!#\e(B
-decode \e$BA`:n$,9T$J$o$l$?;~!"$=$N\e(B part \e$B$N\e(B content-type
-(*Note (tm-ja)content-type::) \e$B$J$I$N>r7o$d$=$N>l$N4D6-$K1~$8$F<B:]$K$=$NA`\e(B
-\e$B:n$r<B9T$9$k<jB3$-$,8F$P$l$^$9!#$3$N<jB3$-$N$3$H$r\e(B
-*method* \e$B$H8F$S$^$9!#\e(B
+decode \e$BA`:n$,9T$J$o$l$?;~!"$=$N\e(B part \e$B$N\e(B content-type (*Note
+(tm-ja)content-type::) \e$B$J$I$N>r7o$d$=$N>l$N4D6-$K1~$8$F<B:]$K$=$NA`:n$r\e(B
+\e$B<B9T$9$k<jB3$-$,8F$P$l$^$9!#$3$N<jB3$-$N$3$H$r\e(B *method* \e$B$H8F$S$^$9!#\e(B
method \e$B$K$O!"\e(BEmacs Lisp \e$B$G=q$+$l$?\e(B *\e$BFbIt\e(B method* \e$B$H!"30It\e(B program \e$B$G<B8=\e(B
\e$B$5$l$?\e(B *\e$B30It\e(B method* \e$B$,$"$j$^$9!#FbIt\e(B method \e$B$O\e(B Emacs \e$B$N5!G=$r;H$C$F$-$a\e(B
************************************
tm-view \e$B$O!"\e(BMIME \e$B=hM}$r9T$J$&A0$N@8$N\e(B message \e$B$,F~$C$F$$$k\e(B
-*raw-article-buffer* \e$B$H$=$NFbMF$r\e(B user
-\e$B$K4J7i$KI=<($7!"\e(Buser \e$B$,A`:n$9$k$?$a$N\e(B
-*preview-buffer* \e$B$H$$$$D$N\e(B buffer \e$B$r4I\e(B
-\e$BM}$7$^$9!#\e(Braw-article-buffer \e$B$N\e(B major-mode \e$B$O$b$H$b$H$N\e(B MUA \e$B$N\e(B article
-\e$BI=<(MQ$N\e(B major-mode \e$B$G$"$j!"\e(Bpreview-buffer \e$B$N\e(B major-mode \e$B$O\e(B
-`mime/viewer-mode' (*Note mime/viewer-mode::) \e$B$H$J$j$^$9!#\e(B
+*raw-article-buffer* \e$B$H$=$NFbMF$r\e(B user \e$B$K4J7i$KI=<($7!"\e(Buser \e$B$,A`\e(B
+\e$B:n$9$k$?$a$N\e(B *preview-buffer* \e$B$H$$$$D$N\e(B buffer \e$B$r4IM}$7$^$9!#\e(B
+raw-article-buffer \e$B$N\e(B major-mode \e$B$O$b$H$b$H$N\e(B MUA \e$B$N\e(B article \e$BI=<(MQ$N\e(B
+major-mode \e$B$G$"$j!"\e(Bpreview-buffer \e$B$N\e(B major-mode \e$B$O\e(B `mime/viewer-mode'
+(*Note mime/viewer-mode::) \e$B$H$J$j$^$9!#\e(B
`mime/viewer-mode' \e$B$r<B9T$9$k$H!"\e(Btm-view \e$B$O$^$:\e(B raw-article-buffer \e$B$NFb\e(B
\e$BMF$r2r@O$7!"$=$N\e(B message \e$B$N9=B$$r\e(B raw-article-buffer \e$B$N\e(B buffer local \e$BJQ\e(B
\e$B<!$K!"$3$N7k2L$r85$K\e(B raw-article-buffer \e$B$KBP1~$9$k\e(B preview-buffer \e$B$r:n$j\e(B
\e$B$^$9!#$3$N:]!"\e(Bcontent-type \e$B$K1~$8$F!"\e(Bpart \e$BC10L$G\e(B header \e$B$d\e(B body \e$B$r2C9)$9\e(B
\e$B$k$3$H$,$G$-$^$9!#$3$N\e(B header \e$B$r2C9)$9$k%W%m%0%i%`$r\e(B
-*header-filter* (*Note content-header::),
-body \e$B$r2C9)$9$k%W%m%0%i%`$r\e(B
-*content-filter* (*Note content-body::) \e$B$H8F\e(B
-\e$B$S!"$3$l$i$rAm>N$7$F\e(B *filter* \e$B$H8F$S$^$9!#\e(B
+*header-filter* (*Note content-header::), body \e$B$r2C9)$9$k%W%m%0%i%`\e(B
+\e$B$r\e(B *content-filter* (*Note content-body::) \e$B$H8F$S!"$3$l$i$rAm>N$7$F\e(B
+*filter* \e$B$H8F$S$^$9!#\e(B
preview-buffer \e$B$r:n@.$9$k;~$K!"\e(Bmessage \e$B$NI=<(>e$N9=B$$r5-O?$7$?\e(B
preview-buffer \e$B$N\e(B buffer local \e$BJQ?t\e(B `mime::preview/content-list' \e$B$,:n$i\e(B
preview-buffer \e$B$K$*$1$k\e(B MIME content \e$B$K4X$9$k>pJs$r3JG<$9$k$?$a$N9=\e(B
\e$BB$BN!#C1$K\e(B *preview-content-info* \e$B$H$b8F$V!#\e(B
-
\e$B$3$N9=B$BN$r;2>H$9$k$K$O!"\e(B`mime::content-info/\e$B%9%m%C%HL>\e(B' \e$B$H$$$&\e(B
content-info \e$B$r0z?t$K$H$k4X?t$rMQ$$$k!#\e(B
\1f
-File: tm-view-ja.info, Node: API, Next: Concept Index, Prev: Two buffers for an article, Up: Top
+File: tm-view-ja.info, Node: API, Next: Acknowledgments, Prev: Two buffers for an article, Up: Top
MIME message \e$B$N\e(B decode \e$B$K4X$9$k4X?t\e(B
***********************************
\1f
-File: tm-view-ja.info, Node: Concept Index, Next: Function Index, Prev: API, Up: Top
+File: tm-view-ja.info, Node: Acknowledgments, Next: Concept Index, Prev: API, Up: Top
+
+\e$B<U<-\e(B
+****
+
+\e$B:G=i$K!";d$,\e(B tm-view \e$B$r:G=i$K:n$C$?;~$K!"87$7$$CmJ8$HM-1W$J=u8@$r2<$5$j!"\e(B
+\e$B$=$N@_7W$KB?Bg$JM?$($i$l$?>#C+J]Gn$5$s$K46<U$7$^$9!#\e(B
+
+\e$B<!$K!"\e(B`tm-ew-d.el' \e$B$H\e(B `mel-b.el' \e$B$NA0?H$KEv$?$k\e(B`mime.el' \e$B$r=q$-!"$=$NG[\e(B
+\e$BI[$H2~B$$r$*5v$72<$5$C$?1]JB;LCR$5$s$K46<U$7$^$9!#\e(B
+
+\e$B$^$?!"\e(BLaTeX \e$BMQ$NFbIt\e(B method \e$B$H\e(B message/partial \e$BMQ$N<+F07k9g\e(B method \e$B$rDs\e(B
+\e$B6!$7$F2<$5$C$?2,It<wCK$5$s!"\e(Btar archive \e$BMQ$NFbIt\e(B method \e$B$rDs6!$7$F2<$5$C\e(B
+\e$B$?>eLnGn$5$s$K46<U$7$^$9!#\e(B
+
+\e$B:G8e$K!"\e(Bbeta test \e$B$K6(NO$7$F2<$5$C$?F|K\8lHG!"1Q8lHGAPJ}$N\e(B tm mailing
+list \e$B$N\e(B member \e$B$K46<U$7$^$9!#\e(B
+
+
+
+\1f
+File: tm-view-ja.info, Node: Concept Index, Next: Function Index, Prev: Acknowledgments, Up: Top
\e$B35G0:w0z\e(B
********
* Menu:
-* \e$B30It\e(B method: method. 18.
-* \e$BFbIt\e(B method: method. 17.
-* content-body: content-body. 5.
-* content-button: content-button. 5.
-* content-filter: content-body. 20.
-* content-filter: Two buffers for an article. 22.
-* content-header: content-header. 5.
-* content-header-filter: content-header. 24.
-* content-info: raw-article-buffer. 10.
-* content-number: content-button. 15.
-* content-separator: content-separator. 5.
-* decoding-mode: method. 9.
-* filter: Introduction. 16.
-* filter: Two buffers for an article. 24.
-* header-filter: Two buffers for an article. 20.
-* method: Introduction. 14.
-* method: method. 14.
-* preview-buffer: Two buffers for an article. 8.
-* preview-content-info: preview-buffer. 15.
-* raw-article-buffer: Two buffers for an article. 6.
+* \e$B30It\e(B method: method. 4.
+* \e$BFbIt\e(B method: method. 4.
+* content-body: content-body. 4.
+* content-button: content-button. 4.
+* content-filter: content-body. 4.
+* content-filter: Two buffers for an article. 4.
+* content-header: content-header. 4.
+* content-header-filter: content-header. 4.
+* content-info: raw-article-buffer. 4.
+* content-number: content-button. 4.
+* content-separator: content-separator. 4.
+* decoding-mode: method. 4.
+* filter: Introduction. 4.
+* filter: Two buffers for an article. 4.
+* header-filter: Two buffers for an article. 4.
+* method: Introduction. 4.
+* method: method. 4.
+* preview-buffer: Two buffers for an article. 4.
+* preview-content-info: preview-buffer. 4.
+* raw-article-buffer: Two buffers for an article. 4.
\1f
* mime-eword/decode-string: encoded-word decoding. 42.
* mime/flatten-content-info: raw-article-buffer. 80.
* mime::preview-content-info: preview-buffer. 12.
-* mime-preview/point-pcinfo: preview-buffer. 57.
+* mime-preview/point-pcinfo: preview-buffer. 56.
* mime-viewer/body-visible-p: content-body. 35.
* mime-viewer/default-content-filter: content-body. 50.
-* mime-viewer/default-content-header-filter: content-header. 60.
+* mime-viewer/default-content-header-filter: content-header. 59.
* mime-viewer/default-content-separator: content-separator. 18.
-* mime-viewer/header-visible-p: content-header. 44.
+* mime-viewer/header-visible-p: content-header. 43.
* mime/viewer-mode: API about MIME preview. 8.
* set-atype: Example of decoding-condition. 53.
* mime::article/content-info: raw-article-buffer. 44.
* mime::article/preview-buffer: raw-article-buffer. 50.
-* mime::preview/article-buffer: preview-buffer. 41.
-* mime::preview/content-list: preview-buffer. 37.
+* mime::preview/article-buffer: preview-buffer. 40.
+* mime::preview/content-list: preview-buffer. 36.
* mime::preview/mother-buffer: preview-buffer. 7.
-* mime::preview/original-major-mode: preview-buffer. 46.
-* mime::preview/original-window-configuration: preview-buffer. 51.
-* mime-viewer/childrens-header-showing-Content-Type-list: content-header. 34.
+* mime::preview/original-major-mode: preview-buffer. 45.
+* mime::preview/original-window-configuration: preview-buffer. 50.
+* mime-viewer/childrens-header-showing-Content-Type-list: content-header. 33.
* mime-viewer/content-button-ignored-ctype-list: content-button. 48.
* mime-viewer/content-filter-alist: content-body. 43.
-* mime-viewer/content-header-filter-alist: content-header. 53.
+* mime-viewer/content-header-filter-alist: content-header. 52.
* mime-viewer/default-showing-Content-Type-list: content-body. 29.
-* mime-viewer/ignored-field-list: content-header. 70.
+* mime-viewer/ignored-field-list: content-header. 69.
\1f\f
Tag table:
Node: Top\7f162
-Node: Introduction\7f999
-Node: MIME display\7f2056
-Node: content-button\7f4557
-Node: content-header\7f6486
-Node: content-body\7f9693
-Node: content-separator\7f11864
-Node: mime/viewer-mode\7f12716
-Node: method\7f14000
-Node: decoding-condition\7f15394
-Node: method value\7f17145
-Node: Example of decoding-condition\7f18914
-Node: environment variables\7f21282
-Node: Two buffers for an article\7f21873
-Node: raw-article-buffer\7f23817
-Node: preview-buffer\7f26635
-Node: API\7f28494
-Node: API about MIME preview\7f29165
-Node: encoded-word decoding\7f30575
-Node: Concept Index\7f32714
-Node: Function Index\7f34067
-Node: Variable Index\7f35241
+Node: Introduction\7f1038
+Node: MIME display\7f2092
+Node: content-button\7f4593
+Node: content-header\7f6522
+Node: content-body\7f9728
+Node: content-separator\7f11899
+Node: mime/viewer-mode\7f12751
+Node: method\7f14035
+Node: decoding-condition\7f15428
+Node: method value\7f17179
+Node: Example of decoding-condition\7f18948
+Node: environment variables\7f21316
+Node: Two buffers for an article\7f21907
+Node: raw-article-buffer\7f23849
+Node: preview-buffer\7f26667
+Node: API\7f28525
+Node: API about MIME preview\7f29198
+Node: encoded-word decoding\7f30608
+Node: Acknowledgments\7f32747
+Node: Concept Index\7f33565
+Node: Function Index\7f34917
+Node: Variable Index\7f36091
\1f
End tag table
<!doctype sinfo system>
-<!-- $Id: tm-view-ja.sgml,v 4.1 1996/10/21 02:38:17 morioka Exp $ -->
+<!-- $Id: tm-view-ja.sgml,v 5.0 1996/12/25 19:05:15 morioka Exp $ -->
<head>
-<title>tm-view 7.77 Reference Manual\e$B!JF|K\8lHG!K\e(B
+<title>tm-view 7.79 Reference Manual\e$B!JF|K\8lHG!K\e(B
<author>\e$B<i2,\e(B \e$BCNI'\e(B <mail>morioka@jaist.ac.jp</mail>
-<date>1996/10/11
+<date>1996/12/25
<toc>
</head>
</defun>
+<h1> \e$B<U<-\e(B
+<node> Acknowledgments
+<p>
+\e$B:G=i$K!";d$,\e(B tm-view \e$B$r:G=i$K:n$C$?;~$K!"87$7$$CmJ8$HM-1W$J=u8@$r2<$5\e(B
+\e$B$j!"$=$N@_7W$KB?Bg$JM?$($i$l$?>#C+J]Gn$5$s$K46<U$7$^$9!#\e(B
+<p>
+\e$B<!$K!"\e(B<file>tm-ew-d.el</file> \e$B$H\e(B <file>mel-b.el</file> \e$B$NA0?H$KEv$?$k\e(B
+<file>mime.el</file> \e$B$r=q$-!"$=$NG[I[$H2~B$$r$*5v$72<$5$C$?1]JB;LCR$5\e(B
+\e$B$s$K46<U$7$^$9!#\e(B
+<p>
+\e$B$^$?!"\e(BLaTeX \e$BMQ$NFbIt\e(B method \e$B$H\e(B message/partial \e$BMQ$N<+F07k9g\e(B method \e$B$r\e(B
+\e$BDs6!$7$F2<$5$C$?2,It<wCK$5$s!"\e(Btar archive \e$BMQ$NFbIt\e(B method \e$B$rDs6!$7$F2<\e(B
+\e$B$5$C$?>eLnGn$5$s$K46<U$7$^$9!#\e(B
+<p>
+\e$B:G8e$K!"\e(Bbeta test \e$B$K6(NO$7$F2<$5$C$?F|K\8lHG!"1Q8lHGAPJ}$N\e(B tm mailing
+list \e$B$N\e(B member \e$B$K46<U$7$^$9!#\e(B
+
+
<h1> \e$B35G0:w0z\e(B
<node> Concept Index
\input texinfo.tex
@setfilename tm-view-ja.info
-@settitle{tm-view 7.77 Reference Manual\e$B!JF|K\8lHG!K\e(B}
+@settitle{tm-view 7.79 Reference Manual\e$B!JF|K\8lHG!K\e(B}
@titlepage
-@title tm-view 7.77 Reference Manual\e$B!JF|K\8lHG!K\e(B
+@title tm-view 7.79 Reference Manual\e$B!JF|K\8lHG!K\e(B
@author \e$B<i2,\e(B \e$BCNI'\e(B <morioka@@jaist.ac.jp>
-@subtitle 1996/10/11
+@subtitle 1996/12/25
@end titlepage
@node Top, Introduction, (dir), (dir)
-@top tm-view 7.77 Reference Manual\e$B!JF|K\8lHG!K\e(B
+@top tm-view 7.79 Reference Manual\e$B!JF|K\8lHG!K\e(B
@ifinfo
* method:: \e$B:F@8=hM}$N<B8=\e(B
* Two buffers for an article:: raw-article-buffer \e$B$H\e(B preview-buffer
* API:: MIME message \e$B$N\e(B decode \e$B$K4X$9$k4X?t\e(B
+* Acknowledgments:: \e$B<U<-\e(B
* Concept Index:: \e$B35G0:w0z\e(B
* Function Index:: \e$B4X?t:w0z\e(B
* Variable Index:: \e$BJQ?t:w0z\e(B
@node Introduction, MIME display, Top, Top
@chapter tm-view \e$B$C$F2?!)\e(B
+@cindex filter
+@cindex method
tm-view \e$B$O\e(B GNU Emacs \e$B$GF0:n$9$kHFMQE*$J\e(B MIME viewer \e$B$G$9!#\e(B@refill
tm-view \e$B$O\e(B MIME message \e$B$r1\Mw$9$k$?$a$N\e(B user interface \e$B$N3K$G$"$j!"$=$N\e(B
\e$B>e$G3F\e(B content-type (@ref{(tm-ja)content-type}) \e$B$r07$&$?$a$N\e(B
-@cindex{method}@strong{method} (@ref{method}) \e$B$H8F$P$l$k%W%m%0%i%`$rF0:n\e(B
-\e$B$5$;$^$9!#$^$?!"\e(BMIME message \e$B$NI=<($N;EJ}$r7h$a$k\e(B
-@cindex{filter}@strong{filter} (@ref{Two buffers for an article}) \e$B$H8F$P\e(B
-\e$B$l$k%W%m%0%i%`$r5/F0;~$K8F$S=P$7$^$9!#\e(Bmethod \e$B$H\e(B filter \e$B$r\e(B tm-view \e$B$KAH$_\e(B
-\e$B9~$`;v$K$h$C$F!"\e(B@code{mime/viewer-mode} \e$B$G$5$^$6$^$J\e(B MIME content-type
-\e$B$r07$&;v$,$G$-$^$9!#\e(B
+@strong{method} (@ref{method}) \e$B$H8F$P$l$k%W%m%0%i%`$rF0:n$5$;$^$9!#$^$?!"\e(B
+MIME message \e$B$NI=<($N;EJ}$r7h$a$k\e(B @strong{filter} (@ref{Two buffers for an article}) \e$B$H8F$P$l$k%W%m%0%i%`$r5/F0;~$K8F$S=P$7$^$9!#\e(Bmethod \e$B$H\e(B
+filter \e$B$r\e(B tm-view \e$B$KAH$_9~$`;v$K$h$C$F!"\e(B@code{mime/viewer-mode} \e$B$G$5$^$6\e(B
+\e$B$^$J\e(B MIME content-type \e$B$r07$&;v$,$G$-$^$9!#\e(B
@node MIME display, mime/viewer-mode, Introduction, Top
@node content-button, content-header, MIME display, MIME display
@section content-button
+@cindex content-number
+@cindex content-button
-@cindex{content-button}@strong{content-button} \e$B$O\e(B part \e$B$N@hF,$K$"$C$F!"\e(B
-\e$B$=$N\e(B part \e$B$K4X$9$kBg$^$+$J>pJs$rI=<($9$kItJ,$G$9!#\e(B@refill
+@strong{content-button} \e$B$O\e(B part \e$B$N@hF,$K$"$C$F!"$=$N\e(B part \e$B$K4X$9$kBg$^$+\e(B
+\e$B$J>pJs$rI=<($9$kItJ,$G$9!#\e(B@refill
\e$BI8=`$G$O\e(B
\e$B$N$h$&$J46$8$KI=<($5$l$^$9!#\e(B
\e$B:G=i$N?t;z$O\e(B message \e$BCf$N$3$N\e(B part \e$B$N0LCV$r@aHV9f$N$h$&$KI=$7$?$b$N$G!"\e(B
-@cindex{content-number}@strong{content-number} \e$B$H8F$S$^$9!#\e(B@refill
+@strong{content-number} \e$B$H8F$S$^$9!#\e(B@refill
\e$B#2HVL\$NJ8;zNs$OI=Bj$rI=$7$^$9!#$3$N>pJs$O!"\e(B
@node content-header, content-body, content-button, MIME display
@section content-header
+@cindex content-header-filter
+@cindex content-header
-@cindex{content-header}@strong{content-header} \e$B$O$"$k\e(B part \e$B$N\e(B header \e$B$r\e(B
-\e$BI=<($9$kItJ,$G$9!#$7$+$7!"A4$F$N\e(B part \e$B$N\e(B content-header \e$B$rI=<($9$k$N$O]5\e(B
-\e$BF+$7$$$N$G!"0J2<$N$h$&$J\e(B mechanism \e$B$K$h$C$FI=<($9$k$+$7$J$$$+$r7h$a$F$$\e(B
-\e$B$^$9!#\e(B@refill
+@strong{content-header} \e$B$O$"$k\e(B part \e$B$N\e(B header \e$B$rI=<($9$kItJ,$G$9!#$7$+$7!"\e(B
+\e$BA4$F$N\e(B part \e$B$N\e(B content-header \e$B$rI=<($9$k$N$O]5F+$7$$$N$G!"0J2<$N$h$&$J\e(B
+mechanism \e$B$K$h$C$FI=<($9$k$+$7$J$$$+$r7h$a$F$$$^$9!#\e(B@refill
\e$B$"$k\e(B part \e$B$N\e(B reversed-content-number \e$B$r4X?t\e(B
@code{mime-viewer/header-visible-p} \e$B$KM?$($?;~$NJV$jCM$,\e(B @code{t} \e$B$K$J$k\e(B
\e$B$$!#\e(B@refill
content-header \e$B$,I=<($5$l$k>l9g!"\e(Bcontent-header \e$B$O\e(B
-@cindex{content-header-filter}@strong{content-header-filter} \e$B$H8F$P$l$k\e(B
-program \e$B$K$h$C$F@07A$5$l$^$9!#\e(Bcontent-header-filter \e$B$O\e(B
-raw-article-buffer (@ref{raw-article-buffer}) \e$B$N\e(B major-mode \e$B$r\e(B key \e$B$H$7\e(B
-\e$B$FJQ?t\e(B @code{mime-viewer/content-header-filter-alist} \e$B$+$iC5$5$l$^$9!#$b\e(B
-\e$B$7!"\e(Bcontent-header-filter \e$B$,8+$D$+$i$J$+$C$?>l9g!"4X?t\e(B
+@strong{content-header-filter} \e$B$H8F$P$l$k\e(B program \e$B$K$h$C$F@07A$5$l$^$9!#\e(B
+content-header-filter \e$B$O\e(B raw-article-buffer (@ref{raw-article-buffer})
+\e$B$N\e(B major-mode \e$B$r\e(B key \e$B$H$7$FJQ?t\e(B
+@code{mime-viewer/content-header-filter-alist} \e$B$+$iC5$5$l$^$9!#$b$7!"\e(B
+content-header-filter \e$B$,8+$D$+$i$J$+$C$?>l9g!"4X?t\e(B
@code{mime-viewer/default-content-header-filter} \e$B$,8F$P$l$^$9!#\e(B@refill
@node content-body, content-separator, content-header, MIME display
@section content-body
+@cindex content-filter
+@cindex content-body
-@cindex{content-body}@strong{content-body} \e$B$O\e(B part \e$B$NFbMF$rI=<($9$kItJ,\e(B
-\e$B$G$9!#\e(B@refill
+@strong{content-body} \e$B$O\e(B part \e$B$NFbMF$rI=<($9$kItJ,$G$9!#\e(B@refill
\e$BA4$F$N\e(B part \e$B$NFbMF$rI=<($G$-$k$H$O8B$i$J$$$7!"$^$?!"I=<($7$?$/$J$$\e(B part
\e$B$bB8:_$9$k$N$G!"0J2<$N$h$&$JJ}K!$GI=<($9$k$+$7$J$$$+$r7h$a$F$$$^$9!#\e(B
\e$B$KI=<($5$l$^$9!#\e(B@refill
\e$B$"$k\e(B part \e$B$N\e(B content-body \e$B$,I=<($5$l$k;~!"\e(Bpreview buffer \e$B$K$O\e(B part \e$B$NFb\e(B
-\e$BMF$r\e(B @cindex{content-filter}@strong{content-filter} \e$B$H8F$P$l$k\e(B program
-\e$B$K$h$C$F@07A$5$l$?$b$N$,I=<($5$l$^$9!#8F$P$l$k\e(B content-filter \e$B$O\e(B
-raw-article-buffer (@ref{raw-article-buffer}) \e$B$N\e(B major-mode \e$B$r\e(B key \e$B$H$7\e(B
-\e$B$FJQ?t\e(B @code{mime-viewer/content-filter-alist} \e$B$+$iC5$5$l$^$9!#$b$7!"$3\e(B
-\e$B$NJQ?t$KEPO?$5$l$F$$$J$+$C$?>l9g!"4X?t\e(B
-@code{mime-viewer/default-content-filter} \e$B$,8F$P$l$^$9!#\e(B
+\e$BMF$r\e(B @strong{content-filter} \e$B$H8F$P$l$k\e(B program \e$B$K$h$C$F@07A$5$l$?$b$N$,\e(B
+\e$BI=<($5$l$^$9!#8F$P$l$k\e(B content-filter \e$B$O\e(B raw-article-buffer
+(@ref{raw-article-buffer}) \e$B$N\e(B major-mode \e$B$r\e(B key \e$B$H$7$FJQ?t\e(B
+@code{mime-viewer/content-filter-alist} \e$B$+$iC5$5$l$^$9!#$b$7!"$3$NJQ?t$K\e(B
+\e$BEPO?$5$l$F$$$J$+$C$?>l9g!"4X?t\e(B @code{mime-viewer/default-content-filter}
+\e$B$,8F$P$l$^$9!#\e(B
@defvar mime-viewer/default-showing-Content-Type-list
@node content-separator, , content-body, MIME display
@section content-separator
+@cindex content-separator
-@cindex{content-separator}@strong{content-separator} \e$B$O\e(B part \e$B$N0lHV:G8e\e(B
-\e$B$K\e(B part \e$B4V$N6-L\$rL@$i$+$K$9$k$?$a$KI=<($5$l$^$9!#\e(B@refill
+@strong{content-separator} \e$B$O\e(B part \e$B$N0lHV:G8e$K\e(B part \e$B4V$N6-L\$rL@$i$+$K\e(B
+\e$B$9$k$?$a$KI=<($5$l$^$9!#\e(B@refill
content-separator \e$B$O4X?t\e(B @code{mime-viewer/default-content-separator}\e$B$K\e(B
\e$B$h$C$FI=<($5$l$^$9!#I8=`$G$O!"\e(Bcontent-header \e$B$b\e(B content-body \e$B$bI=<($5$l\e(B
@node method, Two buffers for an article, mime/viewer-mode, Top
@chapter \e$B:F@8=hM}$N<B8=\e(B
+@cindex \e$B30It\e(B method
+@cindex \e$BFbIt\e(B method
+@cindex method
+@cindex decoding-mode
@code{mime/viewer-mode} \e$B$G$O!"3F\e(B part \e$B$KBP$7$F!"\e(Bplay (@kbd{v}), extract
(@kbd{e}), print (@kbd{C-c C-p}) \e$B$H$$$&A`:n$r9T$J$&$3$H$,$G$-$^$9!#$3$&\e(B
\e$B$7$?A`:n$N$3$H$r!X!J\e(Bpart \e$B$KBP$9$k!K\e(Bdecode \e$BA`:n!Y$H8F$V$3$H$K$7$^$9!#$^$?!"\e(B
play, extract, print \e$B$H$$$&\e(B decode \e$BA`:n$N<oN`$N$3$H$r\e(B
-@cindex{decoding-mode}@strong{decoding-mode} \e$B$H8F$V$3$H$K$7$^$9!#\e(B@refill
+@strong{decoding-mode} \e$B$H8F$V$3$H$K$7$^$9!#\e(B@refill
decode \e$BA`:n$,9T$J$o$l$?;~!"$=$N\e(B part \e$B$N\e(B content-type
(@ref{(tm-ja)content-type}) \e$B$J$I$N>r7o$d$=$N>l$N4D6-$K1~$8$F<B:]$K$=$NA`\e(B
-\e$B:n$r<B9T$9$k<jB3$-$,8F$P$l$^$9!#$3$N<jB3$-$N$3$H$r\e(B
-@cindex{method}@strong{method} \e$B$H8F$S$^$9!#\e(B@refill
+\e$B:n$r<B9T$9$k<jB3$-$,8F$P$l$^$9!#$3$N<jB3$-$N$3$H$r\e(B @strong{method} \e$B$H8F\e(B
+\e$B$S$^$9!#\e(B@refill
-method \e$B$K$O!"\e(BEmacs Lisp \e$B$G=q$+$l$?\e(B @cindex{\e$BFbIt\e(B method}@strong{\e$BFbIt\e(B method} \e$B$H!"\e(B
-\e$B30It\e(B program \e$B$G<B8=$5$l$?\e(B @cindex{\e$B30It\e(B method}@strong{\e$B30It\e(B method} \e$B$,$"$j$^$9!#\e(B
+method \e$B$K$O!"\e(BEmacs Lisp \e$B$G=q$+$l$?\e(B @strong{\e$BFbIt\e(B method} \e$B$H!"\e(B
+\e$B30It\e(B program \e$B$G<B8=$5$l$?\e(B @strong{\e$B30It\e(B method} \e$B$,$"$j$^$9!#\e(B
\e$BFbIt\e(B method \e$B$O\e(B Emacs \e$B$N5!G=$r;H$C$F$-$a:Y$+$$=hM}$r9T$J$&$3$H$,$G$-$^\e(B
\e$B$9!#30It\e(B method \e$B$OHsF14|%W%m%;%98F$S=P$7$r;H$C$F<B8=$5$l$F$$$k$N$G!"<B\e(B
\e$B9TCfBT$?$5$l$:$K$9$_$^$9!#$3$N$?$a!"@E;_2h$dF02h$J$I$N5pBg$J\e(B data \e$B$r:F\e(B
@node Two buffers for an article, API, method, Top
@chapter raw-article-buffer \e$B$H\e(B preview-buffer
+@cindex filter
+@cindex content-filter
+@cindex header-filter
+@cindex preview-buffer
+@cindex raw-article-buffer
tm-view \e$B$O!"\e(BMIME \e$B=hM}$r9T$J$&A0$N@8$N\e(B message \e$B$,F~$C$F$$$k\e(B
-@cindex{raw-article-buffer}@strong{raw-article-buffer} \e$B$H$=$NFbMF$r\e(B user
-\e$B$K4J7i$KI=<($7!"\e(Buser \e$B$,A`:n$9$k$?$a$N\e(B
-@cindex{preview-buffer}@strong{preview-buffer} \e$B$H$$$$D$N\e(B buffer \e$B$r4I\e(B
-\e$BM}$7$^$9!#\e(Braw-article-buffer \e$B$N\e(B major-mode \e$B$O$b$H$b$H$N\e(B MUA \e$B$N\e(B article
-\e$BI=<(MQ$N\e(B major-mode \e$B$G$"$j!"\e(Bpreview-buffer \e$B$N\e(B major-mode \e$B$O\e(B
+@strong{raw-article-buffer} \e$B$H$=$NFbMF$r\e(B user \e$B$K4J7i$KI=<($7!"\e(Buser \e$B$,A`\e(B
+\e$B:n$9$k$?$a$N\e(B @strong{preview-buffer} \e$B$H$$$$D$N\e(B buffer \e$B$r4IM}$7$^$9!#\e(B
+raw-article-buffer \e$B$N\e(B major-mode \e$B$O$b$H$b$H$N\e(B MUA \e$B$N\e(B article \e$BI=<(MQ$N\e(B
+major-mode \e$B$G$"$j!"\e(Bpreview-buffer \e$B$N\e(B major-mode \e$B$O\e(B
@code{mime/viewer-mode} (@ref{mime/viewer-mode}) \e$B$H$J$j$^$9!#\e(B@refill
@code{mime/viewer-mode} \e$B$r<B9T$9$k$H!"\e(Btm-view \e$B$O$^$:\e(B raw-article-buffer
\e$B<!$K!"$3$N7k2L$r85$K\e(B raw-article-buffer \e$B$KBP1~$9$k\e(B preview-buffer \e$B$r:n$j\e(B
\e$B$^$9!#$3$N:]!"\e(Bcontent-type \e$B$K1~$8$F!"\e(Bpart \e$BC10L$G\e(B header \e$B$d\e(B body \e$B$r2C9)$9\e(B
\e$B$k$3$H$,$G$-$^$9!#$3$N\e(B header \e$B$r2C9)$9$k%W%m%0%i%`$r\e(B
-@cindex{header-filter}@strong{header-filter} (@ref{content-header}),
-body \e$B$r2C9)$9$k%W%m%0%i%`$r\e(B
-@cindex{content-filter}@strong{content-filter} (@ref{content-body}) \e$B$H8F\e(B
-\e$B$S!"$3$l$i$rAm>N$7$F\e(B @cindex{filter}@strong{filter} \e$B$H8F$S$^$9!#\e(B
+@strong{header-filter} (@ref{content-header}), body \e$B$r2C9)$9$k%W%m%0%i%`\e(B
+\e$B$r\e(B @strong{content-filter} (@ref{content-body}) \e$B$H8F$S!"$3$l$i$rAm>N$7$F\e(B
+@strong{filter} \e$B$H8F$S$^$9!#\e(B@refill
preview-buffer \e$B$r:n@.$9$k;~$K!"\e(Bmessage \e$B$NI=<(>e$N9=B$$r5-O?$7$?\e(B
preview-buffer \e$B$N\e(B buffer local \e$BJQ?t\e(B @code{mime::preview/content-list} \e$B$,\e(B
@node raw-article-buffer, preview-buffer, Two buffers for an article, Two buffers for an article
@section raw-article-buffer \e$B$N\e(B buffer local \e$BJQ?t\e(B
+@cindex content-info
@deffn{Structure} mime::content-info rcnum point-min point-max type parameters encoding children
raw-article-buffer \e$B$K$*$1$k\e(B MIME part \e$B$K4X$9$k>pJs$r3JG<$9$k$?$a$N9=B$BN!#\e(B
-\e$BC1$K\e(B @cindex{content-info}@strong{content-info} \e$B$H$b8F$V!#\e(B@refill
+\e$BC1$K\e(B @strong{content-info} \e$B$H$b8F$V!#\e(B@refill
\e$B$3$N9=B$BN$r;2>H$9$k$K$O!"\e(B@code{mime::content-info/\e$B%9%m%C%HL>\e(B} \e$B$H$$$&\e(B
content-info \e$B$r0z?t$K$H$k4X?t$rMQ$$$k!#\e(B@refill
@node preview-buffer, , raw-article-buffer, Two buffers for an article
@section preview-buffer \e$B$N\e(B buffer local \e$BJQ?t\e(B
+@cindex preview-content-info
@defvar mime::preview/mother-buffer
@deffn{Structure} mime::preview-content-info point-min point-max buffer content-info
preview-buffer \e$B$K$*$1$k\e(B MIME content \e$B$K4X$9$k>pJs$r3JG<$9$k$?$a$N9=B$BN!#\e(B
-\e$BC1$K\e(B @cindex{preview-content-info}@strong{preview-content-info} \e$B$H$b8F$V!#\e(B
-@refill
+\e$BC1$K\e(B @strong{preview-content-info} \e$B$H$b8F$V!#\e(B@refill
\e$B$3$N9=B$BN$r;2>H$9$k$K$O!"\e(B@code{mime::content-info/\e$B%9%m%C%HL>\e(B} \e$B$H$$$&\e(B
content-info \e$B$r0z?t$K$H$k4X?t$rMQ$$$k!#\e(B@refill
-@node API, Concept Index, Two buffers for an article, Top
+@node API, Acknowledgments, Two buffers for an article, Top
@chapter MIME message \e$B$N\e(B decode \e$B$K4X$9$k4X?t\e(B
tm-view \e$B$NDs6!$9$k4X?t$r3F\e(B MUA (@ref{(tm-ja)MUA}) \e$B$KAH$_9~$`;v$K$h$C$F!"\e(B
-@node Concept Index, Function Index, API, Top
+@node Acknowledgments, Concept Index, API, Top
+@chapter \e$B<U<-\e(B
+
+\e$B:G=i$K!";d$,\e(B tm-view \e$B$r:G=i$K:n$C$?;~$K!"87$7$$CmJ8$HM-1W$J=u8@$r2<$5$j!"\e(B
+\e$B$=$N@_7W$KB?Bg$JM?$($i$l$?>#C+J]Gn$5$s$K46<U$7$^$9!#\e(B@refill
+
+\e$B<!$K!"\e(B@file{tm-ew-d.el} \e$B$H\e(B @file{mel-b.el} \e$B$NA0?H$KEv$?$k\e(B@file{mime.el}
+\e$B$r=q$-!"$=$NG[I[$H2~B$$r$*5v$72<$5$C$?1]JB;LCR$5$s$K46<U$7$^$9!#\e(B@refill
+
+\e$B$^$?!"\e(BLaTeX \e$BMQ$NFbIt\e(B method \e$B$H\e(B message/partial \e$BMQ$N<+F07k9g\e(B method \e$B$rDs\e(B
+\e$B6!$7$F2<$5$C$?2,It<wCK$5$s!"\e(Btar archive \e$BMQ$NFbIt\e(B method \e$B$rDs6!$7$F2<$5$C\e(B
+\e$B$?>eLnGn$5$s$K46<U$7$^$9!#\e(B@refill
+
+\e$B:G8e$K!"\e(Bbeta test \e$B$K6(NO$7$F2<$5$C$?F|K\8lHG!"1Q8lHGAPJ}$N\e(B tm mailing
+list \e$B$N\e(B member \e$B$K46<U$7$^$9!#\e(B
+
+
+@node Concept Index, Function Index, Acknowledgments, Top
@chapter \e$B35G0:w0z\e(B
@printindex cp
--- /dev/null
+;;; tm-edit-tipgp.el -- TinyPgp.el PGP interface
+
+;; Copyright (C) 1996 Jari aalto
+
+;; Author: Jari Aalto <jari.aalto@poboxes.com>
+;; Version: $Id: tm-edit-tipgp.el,v 1.1 1996/12/04 11:11:47 jaalto Beta $
+;; Keywords: mail, news, MIME, multimedia, multilingual, security, PGP
+
+;; This file is part of tm (Tools for MIME).
+
+;; This program is free software; you can redistribute it and/or
+;; modify it under the terms of the GNU General Public License as
+;; published by the Free Software Foundation; either version 2, or (at
+;; your option) any later version.
+
+;; This program is distributed in the hope that it will be useful, but
+;; WITHOUT ANY WARRANTY; without even the implied warranty of
+;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+;; General Public License for more details.
+
+;; You should have received a copy of the GNU General Public License
+;; along with GNU Emacs; see the file COPYING. If not, write to the
+;; Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+;; Boston, MA 02111-1307, USA.
+
+;;; Code:
+
+(require 'tinypgpa.el)
+
+(defun tm:tipgp-process-region (result-buffer boundary)
+ (let ((obuf (current-buffer))
+ )
+ (cond
+ (boundary
+ (goto-char (point-min))
+ (insert (format "--%s\n" boundary))
+ (goto-char (point-max))
+ (insert (format "\n--%s
+Content-Type: application/pgp-signature
+Content-Transfer-Encoding: 7bit
+
+" boundary))
+ (insert-buffer-substring result-buffer)
+ (goto-char (point-max))
+ (insert (format "\n--%s--\n" boundary))
+ )
+ (t
+ (delete-region beg end)
+ (goto-char beg)
+ (insert-buffer-substring result-buffer)
+ ))
+ ))
+
+
+
+
+(defun tm:tipgp-sign-region (start end &optional id unclear boundary)
+ ;; start end = Region
+ ;; id =
+ ;; unclear =
+ ;; boundary = pgp-sign-Multipart_Wed_Dec__4_11:14:41_1996-1
+
+ (let (tipgp-:xpgp-header-mode ;Do not use X-Pgp signing
+ passwd
+ ret
+ )
+
+ (setq passwd (tipgp-password-get-old "Sign pass phrase: "))
+
+
+ ;; The region is already narrowed by TM, so we pass the
+ ;; point-min point-max
+ ;;
+ ;; The macro tipgp-run-in-tmp-buffer cpies the contents to
+ ;; another buffer and when signing is over, it will
+ ;; contain fully signed message
+ ;;
+ (setq
+ ret
+ (tipgp-run-in-tmp-buffer nil
+ (tipgp-sign-region
+ (point-min) (point-max) passwd 'verb
+ (format
+ "+comment=\"Processed by TinyPgp.el %s\""
+ (strmatget "[0-9][0-9.]+" 0 tipgp-version-id)
+ )
+ 'noerr
+ )))
+
+ (if ret
+ (tm:tipgp-process-region tipgp-:buffer-tmp-copy boundary))
+
+ (cond
+ ((and boundary ret)
+ (goto-char (point-min))
+ (insert
+ (format "\
+--[[multipart/signed; protocol=\"application/pgp-signature\";
+ boundary=\"%s\"; micalg=pgp-md5][7bit]]\n" boundary))
+ ))
+ ret
+ ))
+
+
+
+(defun tm:tipgp-pgp-encrypt-region (recipients start end &optional id sign)
+ (let (;; do not use these hooks while in TM
+
+ tipgp-cmd-macro-before-hook
+ tipgp-cmd-macro-after-hook
+
+ ;; TinyPgp.el: has separate encrypt and signing functions.
+ ;;
+;;; (mc-pgp-always-sign
+;;; (if (eq sign 'maybe)
+;;; mc-pgp-always-sign
+;;; 'never))
+
+ (elist (ti::mt-email-from-string recipients))
+ )
+ (if (null elist)
+ (error "TO,CC,BCC fields don't contain email addresses."))
+ (tipgp-encrypt-region (point-min) (point-max) elist nil 'verb)
+ ))
+
+
+;;; @ end
+;;;
+
+(provide 'tm-edit-tipgp)
+
+;;; tm-edit-tipgp.el ends here
;; MORIOKA Tomohiko <morioka@jaist.ac.jp>
;; Maintainer: MORIOKA Tomohiko <morioka@jaist.ac.jp>
;; Created: 1994/08/21 renamed from mime.el
-;; Version: $Revision: 7.99 $
+;; Version: $Revision: 7.100 $
;; Keywords: mail, news, MIME, multimedia, multilingual
;; This file is part of tm (Tools for MIME).
;;;
(defconst mime-editor/RCS-ID
- "$Id: tm-edit.el,v 7.99 1996/12/24 12:08:50 morioka Exp $")
+ "$Id: tm-edit.el,v 7.100 1996/12/25 17:10:58 morioka Exp $")
(defconst mime-editor/version (get-version-string mime-editor/RCS-ID))
;;;
(defvar mime-editor/transfer-level 7
- "*A number of network transfer level. It should be bigger than 7.")
+ "*A number of network transfer level. It should be bigger than 7.")
(make-variable-buffer-local 'mime-editor/transfer-level)
(defvar mime-editor/transfer-level-string
In this mode, basically, the message is composed in the tagged MIME
format. The message tag looks like:
- `--[[text/plain; charset=ISO-2022-JP][7bit]]'.
+ --[[text/plain; charset=ISO-2022-JP][7bit]]
The tag specifies the MIME content type, subtype, optional parameters
and transfer encoding of the message following the tag. Messages
which key is MIME charset and value is coding-system.
Following commands are available in addition to major mode commands:
+
+\[make single part\]
\\[mime-editor/insert-text] insert a text message.
\\[mime-editor/insert-file] insert a (binary) file.
\\[mime-editor/insert-external] insert a reference to external body.
\\[mime-editor/insert-message] insert a mail or news message.
\\[mime-editor/insert-mail] insert a mail message.
\\[mime-editor/insert-signature] insert a signature file at end.
+\\[mime-editor/insert-key] insert PGP public key.
\\[mime-editor/insert-tag] insert a new MIME tag.
+
+\[make enclosure (maybe multipart)\]
\\[mime-editor/enclose-alternative-region] enclose as multipart/alternative.
\\[mime-editor/enclose-parallel-region] enclose as multipart/parallel.
\\[mime-editor/enclose-mixed-region] enclose as multipart/mixed.
\\[mime-editor/enclose-digest-region] enclose as multipart/digest.
\\[mime-editor/enclose-signed-region] enclose as PGP signed.
\\[mime-editor/enclose-encrypted-region] enclose as PGP encrypted.
-\\[mime-editor/insert-key] insert PGP public key.
+\\[mime-editor/enclose-quote-region] enclose as verbose mode (to avoid to expand tags)
+
+\[other commands\]
+\\[mime-editor/set-transfer-level-7bit] set transfer-level as 7.
+\\[mime-editor/set-transfer-level-8bit] set transfer-level as 8.
+\\[mime-editor/set-split] set message splitting mode.
+\\[mime-editor/set-sign] set PGP-sign mode.
+\\[mime-editor/set-encrypt] set PGP-encryption mode.
\\[mime-editor/preview-message] preview editing MIME message.
\\[mime-editor/exit] exit and translate into a MIME compliant message.
-\\[mime-editor/maybe-translate] exit and translate if in MIME mode, then split.
\\[mime-editor/help] show this help.
+\\[mime-editor/maybe-translate] exit and translate if in MIME mode, then split.
Additional commands are available in some major modes:
C-c C-c exit, translate and run the original command.
mime-ignore-trailing-spaces
Trailing white spaces in a message body are ignored if non-nil.
- mime-auto-fill-header
- Fill header fields that contain encoded-words if non-nil.
-
mime-auto-hide-body
Hide a non-textual body message encoded in base64 after insertion
if non-nil.
+ mime-editor/transfer-level
+ A number of network transfer level. It should be bigger than 7.
+ If you are in 8bit-through environment, please set 8.
+
mime-editor/voice-recorder
Specifies a function to record a voice message and encode it.
The function `mime-editor/voice-recorder-for-sun' is for Sun
projects / elisp / tm.git / commitdiff