Mercurial > hg > xemacs-beta
comparison man/tm/tm-mh-e-en.texi @ 8:4b173ad71786 r19-15b5
Import from CVS: tag r19-15b5
author | cvs |
---|---|
date | Mon, 13 Aug 2007 08:47:35 +0200 |
parents | |
children | 49a24b4fd526 |
comparison
equal
deleted
inserted
replaced
7:c153ca296910 | 8:4b173ad71786 |
---|---|
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? | |
29 | |
30 @cindex{tm-mh-e}@strong{tm-mh-e} is a mh-e (@ref{(mh-e)}) extender to | |
31 use MIME (@ref{(tm-en)MIME}) feature using tm | |
32 (@ref{(tm-en)tm-kernel}).@refill | |
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 | |
74 | |
75 @cindex{automatic MIME preview}@strong{automatic MIME preview} feature | |
76 is available in tm-mh-e. In automatic MIME preview mode, when reading | |
77 an article in MH-Folder mode (@ref{(mh-e)Reading Mail}), tm-mh-e | |
78 displays preview buffer processed by tm-view (@ref{(tm-view-en)}) | |
79 instead of raw show buffer.@refill | |
80 | |
81 Therefore if an article is encoded by Base64 (@ref{(tm-en)Base64}) or | |
82 Quoted-Printable (@ref{(tm-en)Quoted-Printable}), a decoded article is | |
83 displayed. Or rich text article, such as text/enriched | |
84 (@ref{(tm-en)text/enriched}) format, is automatic formated. Of course, | |
85 multipart (@ref{(tm-en)multipart}) article is dealt with | |
86 correctly.@refill | |
87 | |
88 In addition, in @cindex{XEmacs}@strong{XEmacs}, images are displayed in | |
89 preview buffer as same as text.@refill | |
90 | |
91 Different from using metamail, speaker does not roar just then read an | |
92 article includes audio content, video player does not play just then | |
93 read an article includes video content, it does not do anonymous ftp | |
94 (@ref{(tm-en)ftp}) or send mail when read an article includes | |
95 external-message. These contents are played when you do decoding | |
96 command in preview buffer.@refill | |
97 | |
98 However if you use a slow machine, or are just really impatient, you | |
99 can stop automatic MIME preview. | |
100 | |
101 | |
102 @defvar tm-mh-e/automatic-mime-preview | |
103 | |
104 If it is not @code{nil}, tm-mh-e is in automatic MIME preview mode. | |
105 @end defvar | |
106 | |
107 | |
108 | |
109 @node mule, MIME-Edit, Automatic MIME Preview, Top | |
110 @chapter Internationalization | |
111 | |
112 For emacs variants includes mule feature, such as MULE | |
113 (@ref{(tm-en)MULE}), XEmacs/mule and Emacs/mule(*1), tm-mh-e supports | |
114 code-conversion by MIME charset (@ref{(tm-en)MIME charset}). | |
115 | |
116 @noindent | |
117 @strong{[Memo]} | |
118 @quotation | |
119 (*1) It means next generation of Emacs includes mule features. Now | |
120 (October 1996), HANDA Ken'ichi and RMS are developing it. | |
121 @end quotation | |
122 | |
123 | |
124 Detail of code conversion is following: | |
125 | |
126 @enumerate | |
127 @item | |
128 If a part of a MIME message has charset parameter of Content-Type field | |
129 (@ref{(tm-en)Content-Type field}), it is code-converted by the MIME | |
130 charset. | |
131 @item | |
132 encoded-word (@ref{(tm-en)encoded-word}) are code-converted by their | |
133 specified MIME charset (@ref{(tm-en)MIME charset}). | |
134 @item | |
135 When there are no specified MIME charset, such as message header | |
136 or non-MIME message, they are code-converted by | |
137 @code{default-mime-charset} in Summary Buffer. | |
138 @end enumerate | |
139 | |
140 | |
141 | |
142 @menu | |
143 * evil environment:: Don't use MIME charset | |
144 @end menu | |
145 | |
146 @node evil environment, , mule, mule | |
147 @section Don't use MIME charset | |
148 | |
149 If MTA (@ref{(tm-en)MTA}) convert character encoding of messages from | |
150 network code to local code, such as EUC or Shift_JIS, MIME charset does | |
151 not work, so tm-mh-e can not display correct message. It is quite evil | |
152 environment. It does not break only MIME charset, but also electric | |
153 signature by PGP.@refill | |
154 | |
155 If you can manage your environment, you should fix it. Otherwise you | |
156 should persuade the administration.@refill | |
157 | |
158 Unfortunately you are in such environment and you can not it, | |
159 following descriptions may be available. | |
160 | |
161 | |
162 @subsection for non-MIME message or non-charset | |
163 | |
164 For non-MIME message, please set the character encoding to variable | |
165 @code{default-mime-charset}. For example, if you use Japanese EUC: | |
166 | |
167 @lisp | |
168 (setq default-mime-charset 'euc-japan) | |
169 @end lisp | |
170 | |
171 | |
172 | |
173 @subsection To disable MIME charset | |
174 | |
175 If for a text part specified MIME charset (@ref{(tm-en)MIME charset}), | |
176 one way is to set variable @code{mime-charset-coding-system-alist} to | |
177 specify the coding-system corresponding the primary MIME charset. For | |
178 example, to specify @code{*sjis*} or @code{*euc-japan*} as | |
179 @code{iso-2022-jp}. However it breaks texts encoded by Base64 or | |
180 Quoted-Printable.@refill | |
181 | |
182 So it is better to redefine function | |
183 @code{tm-mh-e/decode-charset-buffer}. For example, if your MTA | |
184 converts iso-2022-jp to Japanese EUC, following definition may work: | |
185 | |
186 @lisp | |
187 (defun tm-mh-e/decode-charset-buffer (charset &optional encoding) | |
188 (decode-mime-charset-region (point-min)(point-max) 'euc-japan) | |
189 ) | |
190 @end lisp | |
191 | |
192 | |
193 | |
194 @node MIME-Edit, Concept Index, mule, Top | |
195 @chapter Composing MIME message | |
196 | |
197 If using mime-setup (@ref{(tm-en)mime-setup}), you can edit MIME message | |
198 in MH-Letter mode (@ref{(mh-e)Draft Editing}) using tm-edit | |
199 (@ref{(tm-edit-en)}).@refill | |
200 | |
201 In addition, @kbd{f} is used for message/rfc822 | |
202 (@ref{(tm-en)message/rfc822}) style forwarding instead of RFC 934 | |
203 (@ref{(tm-en)RFC 934}) style forwarding. | |
204 | |
205 | |
206 @node Concept Index, Variable Index, MIME-Edit, Top | |
207 @chapter Concept Index | |
208 | |
209 @printindex cp | |
210 | |
211 @node Variable Index, , Concept Index, Top | |
212 @chapter Variable Index | |
213 | |
214 @printindex vr | |
215 @bye |