8
|
1 \input texinfo.tex
|
|
2 @setfilename tm-mh-e-en.info
|
|
3 @settitle{tm-mh-e 7.71 Reference Manual (English Version)}
|
|
4 @titlepage
|
|
5 @title tm-mh-e 7.71 Reference Manual (English Version)
|
|
6 @author MORIOKA Tomohiko <morioka@@jaist.ac.jp>
|
|
7 @subtitle 1996/10/15
|
|
8 @end titlepage
|
|
9 @node Top, Introduction, (dir), (dir)
|
|
10 @top tm-mh-e 7.71 Reference Manual (English Version)
|
|
11
|
|
12 @ifinfo
|
|
13
|
|
14 This file documents tm-mh-e, a MIME extension for GNUS.
|
|
15 @end ifinfo
|
|
16
|
|
17 @menu
|
|
18 * Introduction:: What is tm-mh-e?
|
|
19 * mh-folder-mode:: Extension for MH-Folder mode
|
|
20 * Automatic MIME Preview:: Inline display for MIME message
|
|
21 * mule:: Internationalization
|
|
22 * MIME-Edit:: Composing MIME message
|
|
23 * Concept Index::
|
|
24 * Variable Index::
|
|
25 @end menu
|
|
26
|
|
27 @node Introduction, mh-folder-mode, Top, Top
|
|
28 @chapter What is tm-mh-e?
|
10
|
29 @cindex tm-mh-e
|
8
|
30
|
10
|
31 @strong{tm-mh-e} is a mh-e (@ref{(mh-e)}) extender to use MIME
|
|
32 (@ref{(tm-en)MIME}) feature using tm (@ref{(tm-en)tm-kernel}).@refill
|
8
|
33
|
|
34 tm-mh-e extends following features:
|
|
35
|
|
36 @itemize @bullet
|
|
37 @item
|
|
38 automatic MIME preview using tm-view (@ref{(tm-view-en)})
|
|
39 @item
|
|
40 composing MIME message using tm-edit (@ref{(tm-edit-en)})
|
|
41 @end itemize
|
|
42
|
|
43
|
|
44
|
|
45 @node mh-folder-mode, Automatic MIME Preview, Introduction, Top
|
|
46 @chapter Extension for MH-Folder mode
|
|
47
|
|
48 @table @kbd
|
|
49 @item @key{M-t}
|
|
50 Toggle whether to do automatic MIME preview or not.
|
|
51
|
|
52 @item @key{v}
|
|
53 Enter @code{mime/viewer-mode} to view a message.
|
|
54
|
|
55 @item @key{.}
|
|
56 Display current message.
|
|
57
|
|
58 @item @key{,}
|
|
59 Display current message with showing all fields.
|
|
60
|
|
61 @item @key{M-,}
|
|
62 Display current ``raw'' message.
|
|
63
|
|
64 @end table
|
|
65
|
|
66
|
|
67 mime/viewer-mode (@ref{(tm-view-en)mime/viewer-mode}) is a major-mode to
|
|
68 view and navigate MIME message. In this mode, you can move in a message
|
|
69 or play a content, interactively.
|
|
70
|
|
71
|
|
72 @node Automatic MIME Preview, mule, mh-folder-mode, Top
|
|
73 @chapter Inline display for MIME message
|
10
|
74 @cindex XEmacs
|
|
75 @cindex automatic MIME preview
|
8
|
76
|
10
|
77 @strong{automatic MIME preview} feature is available in tm-mh-e. In
|
|
78 automatic MIME preview mode, when reading an article in MH-Folder mode
|
|
79 (@ref{(mh-e)Reading Mail}), tm-mh-e displays preview buffer processed by
|
|
80 tm-view (@ref{(tm-view-en)}) instead of raw show buffer.@refill
|
8
|
81
|
|
82 Therefore if an article is encoded by Base64 (@ref{(tm-en)Base64}) or
|
|
83 Quoted-Printable (@ref{(tm-en)Quoted-Printable}), a decoded article is
|
|
84 displayed. Or rich text article, such as text/enriched
|
|
85 (@ref{(tm-en)text/enriched}) format, is automatic formated. Of course,
|
|
86 multipart (@ref{(tm-en)multipart}) article is dealt with
|
|
87 correctly.@refill
|
|
88
|
10
|
89 In addition, in @strong{XEmacs}, images are displayed in preview buffer
|
|
90 as same as text.@refill
|
8
|
91
|
|
92 Different from using metamail, speaker does not roar just then read an
|
|
93 article includes audio content, video player does not play just then
|
|
94 read an article includes video content, it does not do anonymous ftp
|
|
95 (@ref{(tm-en)ftp}) or send mail when read an article includes
|
|
96 external-message. These contents are played when you do decoding
|
|
97 command in preview buffer.@refill
|
|
98
|
|
99 However if you use a slow machine, or are just really impatient, you
|
|
100 can stop automatic MIME preview.
|
|
101
|
|
102
|
|
103 @defvar tm-mh-e/automatic-mime-preview
|
|
104
|
|
105 If it is not @code{nil}, tm-mh-e is in automatic MIME preview mode.
|
|
106 @end defvar
|
|
107
|
|
108
|
|
109
|
|
110 @node mule, MIME-Edit, Automatic MIME Preview, Top
|
|
111 @chapter Internationalization
|
|
112
|
|
113 For emacs variants includes mule feature, such as MULE
|
|
114 (@ref{(tm-en)MULE}), XEmacs/mule and Emacs/mule(*1), tm-mh-e supports
|
|
115 code-conversion by MIME charset (@ref{(tm-en)MIME charset}).
|
|
116
|
|
117 @noindent
|
|
118 @strong{[Memo]}
|
|
119 @quotation
|
|
120 (*1) It means next generation of Emacs includes mule features. Now
|
|
121 (October 1996), HANDA Ken'ichi and RMS are developing it.
|
|
122 @end quotation
|
|
123
|
|
124
|
|
125 Detail of code conversion is following:
|
|
126
|
|
127 @enumerate
|
|
128 @item
|
|
129 If a part of a MIME message has charset parameter of Content-Type field
|
|
130 (@ref{(tm-en)Content-Type field}), it is code-converted by the MIME
|
|
131 charset.
|
|
132 @item
|
|
133 encoded-word (@ref{(tm-en)encoded-word}) are code-converted by their
|
|
134 specified MIME charset (@ref{(tm-en)MIME charset}).
|
|
135 @item
|
|
136 When there are no specified MIME charset, such as message header
|
|
137 or non-MIME message, they are code-converted by
|
|
138 @code{default-mime-charset} in Summary Buffer.
|
|
139 @end enumerate
|
|
140
|
|
141
|
|
142
|
|
143 @menu
|
|
144 * evil environment:: Don't use MIME charset
|
|
145 @end menu
|
|
146
|
|
147 @node evil environment, , mule, mule
|
|
148 @section Don't use MIME charset
|
|
149
|
|
150 If MTA (@ref{(tm-en)MTA}) convert character encoding of messages from
|
|
151 network code to local code, such as EUC or Shift_JIS, MIME charset does
|
|
152 not work, so tm-mh-e can not display correct message. It is quite evil
|
|
153 environment. It does not break only MIME charset, but also electric
|
|
154 signature by PGP.@refill
|
|
155
|
|
156 If you can manage your environment, you should fix it. Otherwise you
|
|
157 should persuade the administration.@refill
|
|
158
|
|
159 Unfortunately you are in such environment and you can not it,
|
|
160 following descriptions may be available.
|
|
161
|
|
162
|
|
163 @subsection for non-MIME message or non-charset
|
|
164
|
|
165 For non-MIME message, please set the character encoding to variable
|
|
166 @code{default-mime-charset}. For example, if you use Japanese EUC:
|
|
167
|
|
168 @lisp
|
|
169 (setq default-mime-charset 'euc-japan)
|
|
170 @end lisp
|
|
171
|
|
172
|
|
173
|
|
174 @subsection To disable MIME charset
|
|
175
|
|
176 If for a text part specified MIME charset (@ref{(tm-en)MIME charset}),
|
|
177 one way is to set variable @code{mime-charset-coding-system-alist} to
|
|
178 specify the coding-system corresponding the primary MIME charset. For
|
|
179 example, to specify @code{*sjis*} or @code{*euc-japan*} as
|
|
180 @code{iso-2022-jp}. However it breaks texts encoded by Base64 or
|
|
181 Quoted-Printable.@refill
|
|
182
|
|
183 So it is better to redefine function
|
|
184 @code{tm-mh-e/decode-charset-buffer}. For example, if your MTA
|
|
185 converts iso-2022-jp to Japanese EUC, following definition may work:
|
|
186
|
|
187 @lisp
|
|
188 (defun tm-mh-e/decode-charset-buffer (charset &optional encoding)
|
|
189 (decode-mime-charset-region (point-min)(point-max) 'euc-japan)
|
|
190 )
|
|
191 @end lisp
|
|
192
|
|
193
|
|
194
|
|
195 @node MIME-Edit, Concept Index, mule, Top
|
|
196 @chapter Composing MIME message
|
|
197
|
|
198 If using mime-setup (@ref{(tm-en)mime-setup}), you can edit MIME message
|
|
199 in MH-Letter mode (@ref{(mh-e)Draft Editing}) using tm-edit
|
|
200 (@ref{(tm-edit-en)}).@refill
|
|
201
|
|
202 In addition, @kbd{f} is used for message/rfc822
|
|
203 (@ref{(tm-en)message/rfc822}) style forwarding instead of RFC 934
|
|
204 (@ref{(tm-en)RFC 934}) style forwarding.
|
|
205
|
|
206
|
|
207 @node Concept Index, Variable Index, MIME-Edit, Top
|
|
208 @chapter Concept Index
|
|
209
|
|
210 @printindex cp
|
|
211
|
|
212 @node Variable Index, , Concept Index, Top
|
|
213 @chapter Variable Index
|
|
214
|
|
215 @printindex vr
|
|
216 @bye
|