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