|
8
|
1 <!doctype sinfo system>
|
|
|
2 <!-- $Id: tm-en.sgml,v 1.1 1996/12/22 00:09:33 steve Exp $ -->
|
|
|
3 <head>
|
|
|
4 <title>tm 7.90 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, a MIME package for GNU Emacs.
|
|
|
16 </abstract>
|
|
|
17
|
|
|
18 <h1> What is tm?
|
|
|
19 <node> Introduction
|
|
|
20 <p>
|
|
|
21 The tm package is a set of modules to enjoy MIME on GNU Emacs. Using
|
|
|
22 tm, you can
|
|
|
23
|
|
|
24 <ul>
|
|
|
25 <li> playback or view the MIME messages using tm-view
|
|
|
26 <li> compose MIME message using tm-edit
|
|
|
27 <li> use the enhanced MIME features with mh-e, GNUS, Gnus, RMAIL and VM
|
|
|
28 </ul>
|
|
|
29
|
|
|
30 <noindent>
|
|
|
31 and more.
|
|
|
32 <p>
|
|
|
33 Please read following about each topics:
|
|
|
34
|
|
|
35 <ul>
|
|
|
36 <li><a file="gnus-mime-en">tm-MUA for Gnus</a>
|
|
|
37 <li><a file="tm-gnus-en">tm-MUA for GNUS</a>
|
|
|
38 <li><a file="tm-mh-e-en">tm-MUA for mh-e</a>
|
|
|
39 <li><a file="tm-view-en">mime/viewer-mode</a>
|
|
|
40 <li><a file="tm-edit-en">mime/editor-mode</a>
|
|
|
41 </ul>
|
|
|
42
|
|
|
43
|
|
|
44 <h2> Glossary
|
|
|
45 <node> Glossary
|
|
|
46
|
|
|
47 <h3> 7bit
|
|
|
48 <node> 7bit
|
|
|
49 <p>
|
|
|
50 <concept>7bit</concept> means any integer between 0 .. 127.
|
|
|
51 <p>
|
|
|
52 Any data represented by 7bit integers is called <concept>7bit
|
|
|
53 data</concept>.
|
|
|
54 <p>
|
|
|
55 Textual string consisted of Control characters between 0 .. 31 and
|
|
|
56 127, and space represented by 32, and graphic characters between 33
|
|
|
57 .. 236 are called <concept>7bit (textual) string</concept>.
|
|
|
58 <p>
|
|
|
59 Traditional Internet <a node="MTA">MTA</a> can translate 7bit data, so
|
|
|
60 it is no need to translate by <a
|
|
|
61 node="Quoted-Printable">Quoted-Printable</a> or <a
|
|
|
62 node="Base64">Base64</a> for 7bit data.
|
|
|
63 <p>
|
|
|
64 However if there are too long lines, it can not translate by 7bit MTA
|
|
|
65 even if it is 7bit data. <dref>RFC 821</dref> and <dref>RFC
|
|
|
66 2045</dref> require lines in 7bit data must be less than 998 bytes.
|
|
|
67 So if a ``7bit data'' has a line more than 999 bytes, it is regarded
|
|
|
68 as <dref>binary</dref>. For example, Postscript file should be
|
|
|
69 encoded by Quoted-Printable.
|
|
|
70
|
|
|
71
|
|
|
72 <h3> 8bit
|
|
|
73 <node> 8bit
|
|
|
74 <p>
|
|
|
75 <concept>8bit</concept> means any integer between 0 .. 255.
|
|
|
76 <p>
|
|
|
77 Any data represented by 8bit integers is called <concept>8bit
|
|
|
78 data</concept>.
|
|
|
79 <p>
|
|
|
80 Textual string consisted of Control characters between 0 .. 31, 127,
|
|
|
81 and 128 .. 159, and space represented by 32, and graphic characters
|
|
|
82 between 33 .. 236 and 160 .. 255 are called <concept>8bit (textual)
|
|
|
83 string</concept>.
|
|
|
84 <p>
|
|
|
85 For example, <dref>iso-8859-1</dref> or <dref>euc-kr</dref> are
|
|
|
86 coded-character-set represented by 8bit textual string.
|
|
|
87 <p>
|
|
|
88 Traditional Internet <a node="MTA">MTA</a> can translate only
|
|
|
89 <dref>7bit</dref> data, so if a 8bit data will be translated such MTA,
|
|
|
90 it must be encoded by <dref>Quoted-Printable</dref> or
|
|
|
91 <dref>Base64</dref>.
|
|
|
92 <p>
|
|
|
93 However 8bit MTA are increasing today.
|
|
|
94 <p>
|
|
|
95 However if there are too long lines, it can not translate by 8bit MTA
|
|
|
96 even if it is 8bit data. <dref>RFC 2045</dref> require lines in 8bit
|
|
|
97 data must be less than 998 bytes. So if a ``8bit data'' has a line
|
|
|
98 more than 999 bytes, it is regarded as <dref>binary</dref>, so it must
|
|
|
99 be encoded by Base64 or Quoted-Printable.
|
|
|
100
|
|
|
101
|
|
|
102 <h3> 94-character set
|
|
|
103 <node> 94-character set
|
|
|
104 <p>
|
|
|
105 <concept>94-character set</concept> is a kind of 1 byte <dref>graphic
|
|
|
106 character set</dref>, each characters are in positions 02/01 (33) to
|
|
|
107 07/14 (126) or 10/01 (161) to 15/14 (254). (ex. <dref>ASCII</dref>,
|
|
|
108 JIS X0201-Latin)
|
|
|
109
|
|
|
110
|
|
|
111 <h3> 96-character set
|
|
|
112 <node> 96-character set
|
|
|
113 <p>
|
|
|
114 <concept>96-character set</concept> is a kind of 1 byte <dref>graphic
|
|
|
115 character set</dref>, each characters are in positions 02/00 (32) to
|
|
|
116 07/15 (126) or 10/00 (160) to 15/15 (255). (ex. ISO 8859)
|
|
|
117
|
|
|
118
|
|
|
119 <h3> 94x94-character set
|
|
|
120 <node> 94x94-character set
|
|
|
121 <p>
|
|
|
122 <concept>94x94-character set</concept> is a kind of 2 byte
|
|
|
123 <dref>graphic character set</dref>, each bytes are in positions 02/01
|
|
|
124 (33) to 07/14 (126) or 10/01 (161) to 15/14 (254). (ex. <dref>JIS
|
|
|
125 X0208</dref>, <dref>GB 2312</dref>)
|
|
|
126
|
|
|
127
|
|
|
128 <h3> ASCII
|
|
|
129 <node> ASCII
|
|
|
130 <p>
|
|
|
131 $B%"%a%j%+O"K.$G;H$o$l$kJ8;z$rId9f2=$7$?(B <dref>94-character set</dref>.
|
|
|
132 A-Z, a-z $B$N(B Latin $BJ8;z$H?t;z!"4v$D$+$N5-9f$+$i$J$k!#(B<a node="ISO
|
|
|
133 646">ISO 646</a> $B$N0l$D!#(B
|
|
|
134
|
|
|
135 <standard abbrev="ASCII" title-en="Coded Character Set -- 7-Bit
|
|
|
136 American Standard Code for Information Interchange"
|
|
|
137 number="ANSI X3.4" year="1986">
|
|
|
138
|
|
|
139
|
|
|
140 <h3> Base64
|
|
|
141 <node> Base64
|
|
|
142 <p>
|
|
|
143 <concept>Base64</concept> is a transfer encoding method of
|
|
|
144 <dref>MIME</dref> defined in <dref>RFC 2045</dref>.
|
|
|
145 <p>
|
|
|
146 The encoding process represents 24-bit groups of input bits as output
|
|
|
147 strings of 4 encoded characters. Encoded characters represent integer
|
|
|
148 0 .. 63 or <concept>pad</concept>. Base64 data must be 4 * n bytes,
|
|
|
149 so pad is used to adjust size.
|
|
|
150 <p>
|
|
|
151 These 65 characters are subset of all versions of ISO 646, including
|
|
|
152 US-ASCII, and all versions of EBCDIC. So it is safe even if it is
|
|
|
153 translated by non-Internet gateways.
|
|
|
154
|
|
|
155
|
|
|
156 <h3> binary
|
|
|
157 <node> binary
|
|
|
158 <p>
|
|
|
159 $BG$0U$N(B byte $BNs$r(B <concept>binary</concept> $B$H8F$V$3$H$K$7$^$9!#(B
|
|
|
160 <p>
|
|
|
161 <a node="8bit">8bit</a> $B$H0[$J$k$N$O(B data $B$K9T$N9=B$$r2>Dj$7$J$$$3$H$G(B
|
|
|
162 $B$9!#(B
|
|
|
163 <p>
|
|
|
164 $B$^$?!"9T$N9=B$$,$"$C$F$b!"(B999 byte $B0J>e$+$i$J$k9T$,$"$k>l9g$b(B binary
|
|
|
165 $B$H8F$V$3$H$K$7$^$9!#(B
|
|
|
166 <p>
|
|
|
167 $B$A$J$_$K!"(B<a node="7bit">7bit</a> $B$d(B 8bit $B$GI=8=$G$-$k(B data $B$O(B binary
|
|
|
168 $B$G$bI=8=$G$-$^$9!#$h$C$F!"(B<concept>binary data</concept> $B$H8@$C$?>l9g!"(B
|
|
|
169 $BG$0U$N(B data $B$r;X$9$3$H$,$"$j$^$9!#(B
|
|
|
170
|
|
|
171
|
|
|
172 <h3> Graphic Character Set
|
|
|
173 <node> graphic character set
|
|
|
174 <p>
|
|
|
175 <dref>Coded character set</dref> for graphic characters.
|
|
|
176
|
|
|
177
|
|
|
178 <h3> cn-gb, gb2312
|
|
|
179 <node> cn-gb
|
|
|
180 <p>
|
|
|
181 $BCf9qBgN&$G$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B <a
|
|
|
182 node="MIME charset">MIME charset</a> $B$N#1$D!#(B
|
|
|
183 <p>
|
|
|
184 <dref>ISO 2022</dref> $B$K4p$$$F(B <dref>ASCII</dref> $B$K(B <dref>GB
|
|
|
185 2312</dref> $B$r(B <dref>8bit</dref> $B$G(B<a node="Code extension">$BId9f(B
|
|
|
186 $B3HD%(B</a>$B$7$F$$$k!#(B
|
|
|
187 <p>
|
|
|
188 <a node="RFC 1922">RFC 1922</a> $B$GDj5A$5$l$F$$$k!#(B
|
|
|
189
|
|
|
190
|
|
|
191 <h3> cn-big5, big5
|
|
|
192 <node> cn-big5
|
|
|
193 <p>
|
|
|
194 $BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B
|
|
|
195 <a node="MIME charset">MIME charset</a> $B$N#1$D!#(B
|
|
|
196 <p>
|
|
|
197 <dref>ISO 2022</dref> $B$K4p$+$J$$(B <dref>8bit</dref> $B$N(B
|
|
|
198 <dref>coded character set</dref>$B$G(B de-fact standard $B$G(B
|
|
|
199 $B$"$k!#(B<a node="RFC 1922">RFC 1922</a> $B$GDj5A$5$l$F$$$k!#(B
|
|
|
200 <p>
|
|
|
201 cf. <report abbrev="BIG5" author="Institute for Information Industry"
|
|
|
202 title-en="Chinese Coded Character Set in Computer"
|
|
|
203 date="March 1984">
|
|
|
204 <p>
|
|
|
205 <a node="CNS">CNS 11643-1986</a> $B$HBP1~4X78$,$"$k!#(B
|
|
|
206
|
|
|
207
|
|
|
208 <h3> CNS 11643-1992
|
|
|
209 <node> CNS
|
|
|
210 <p>
|
|
|
211 $BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B
|
|
|
212 <a node="Character set">$BJ8;z=89g(B</a>$B!#BfOQ$NI8=`!#8=:_!"(B<a node="94x94
|
|
|
213 character set">94$B!_(B94</a> $B$NLL$,Bh#1LL$+$iBh#7LL$^$G$"$k!#(B
|
|
|
214 <p>
|
|
|
215 <dref>ISO 2022</dref> $B$G$N=*C<J8;z$O!"Bh#1LL$,(B `G', $BBh#2LL$,(B
|
|
|
216 `H', $BBh#3LL$,(B `I', $BBh#4LL$,(B `J', $BBh#5LL$,(B `K', $BBh#6LL$,(B `L', $BBh#7LL$,(B
|
|
|
217 `M' $B$G$"$k!#(B
|
|
|
218
|
|
|
219 <standard abbrev="CNS 11643-1992" title-en="Standard Interchange Code
|
|
|
220 for Generally-Used Chinese Characters" number="CNS
|
|
|
221 11643" year="1992">
|
|
|
222
|
|
|
223
|
|
|
224 <h3> Coded character set, Character code
|
|
|
225 <node> coded character set
|
|
|
226 <p>
|
|
|
227 A set of unambiguous rules that establishes a character set and the
|
|
|
228 one-to-one relationship between the characters of the set and their
|
|
|
229 bit combinations.
|
|
|
230
|
|
|
231
|
|
|
232 <h3> Code extension
|
|
|
233 <node> code extension
|
|
|
234 <p>
|
|
|
235 The techniques for the encoding of characters that are not included in
|
|
|
236 the character set of a given code. (ex. <dref>ISO 2022</dref>)
|
|
|
237
|
|
|
238
|
|
|
239 <h3> Content-Disposition field
|
|
|
240 <node> Content-Disposition
|
|
|
241 <p>
|
|
|
242 Content $B$NI=<($N;EJ}$d(B file $BL>$rI=8=$9$k$?$a$N(B field. <a
|
|
|
243 node="MIME">MIME</a> $B$N3HD%$N#1$D!#(B
|
|
|
244 <p>
|
|
|
245 <rfc number="1806" type="Experimental" author="E R. Troost and
|
|
|
246 S. Dorner" title="Communicating Presentation Information
|
|
|
247 in Internet Messages: The Content-Disposition Header"
|
|
|
248 date="June 1995">
|
|
|
249
|
|
|
250
|
|
|
251 <h3> media type
|
|
|
252 <node> media type
|
|
|
253 <p>
|
|
|
254 <concept>media type</concept> specifies the nature of the data in the
|
|
|
255 body of <dref>MIME</dref> <dref>entity</dref>. It consists of
|
|
|
256 <concept>type</> and <concept>subtype</concept>. It is defined in
|
|
|
257 <dref>RFC 2046</dref>.
|
|
|
258 <p>
|
|
|
259 Currently there are following types:
|
|
|
260
|
|
|
261 <ul>
|
|
|
262 <li><concept>text</concept>
|
|
|
263 </li>
|
|
|
264 <li><concept>image</concept>
|
|
|
265 </li>
|
|
|
266 <li><concept>audio</concept>
|
|
|
267 </li>
|
|
|
268 <li><concept>video</concept>
|
|
|
269 </li>
|
|
|
270 <li><concept>application</concept>
|
|
|
271 </li>
|
|
|
272 <li><a node="multipart"><concept>multipart</concept></a>
|
|
|
273 </li>
|
|
|
274 <li><concept>message</concept>
|
|
|
275 </ul>
|
|
|
276
|
|
|
277 <p>
|
|
|
278 And there are various subtypes, for example, application/octet-stream,
|
|
|
279 audio/basic, image/jpeg, <dref>multipart/mixed</dref>,
|
|
|
280 <dref>text/plain</dref>, video/mpeg...
|
|
|
281 <p>
|
|
|
282 You can refer registered media types at <a
|
|
|
283 href="ftp://ftp.isi.edu/in-notes/iana/assignments/media-types">MEDIA
|
|
|
284 TYPES</a>.
|
|
|
285 <p>
|
|
|
286 In addition, you can use private type or subtype using
|
|
|
287 <concept>x-token</concept>, which as the prefix `x-'. However you can
|
|
|
288 not use them in public.
|
|
|
289 <p>
|
|
|
290 <cf node="Content-Type field">
|
|
|
291
|
|
|
292
|
|
|
293 <h3> Content-Type field
|
|
|
294 <node> Content-Type field
|
|
|
295 <p>
|
|
|
296 Header field to represent information about body, such as <dref>media
|
|
|
297 type</dref>, <dref>MIME charset</dref>. It is defined in <dref>RFC
|
|
|
298 2045</dref>.
|
|
|
299
|
|
|
300 <memo>
|
|
|
301 <p>
|
|
|
302 Historically, Content-Type field was proposed in RFC 1049. In it,
|
|
|
303 Content-Type did not distinguish type and subtype. However MIME
|
|
|
304 parser may be able to accept RFC 1049 based Content-Type as unknown
|
|
|
305 type.
|
|
|
306 </memo>
|
|
|
307
|
|
|
308 <p>
|
|
|
309 Content-Type field is defined as following:
|
|
|
310
|
|
|
311 <quote>
|
|
|
312 ``Content-Type'' ``:'' <concept>type</concept> ``/''
|
|
|
313 <concept>subtype</concept> *( ``;'' <concept>parameter</concept> )
|
|
|
314 </quote>
|
|
|
315
|
|
|
316 <p>
|
|
|
317 For example:
|
|
|
318
|
|
|
319 <quote>
|
|
|
320 <verb>
|
|
|
321 Content-Type: image/jpeg
|
|
|
322 </verb>
|
|
|
323 </quote>
|
|
|
324
|
|
|
325 <quote>
|
|
|
326 <verb>
|
|
|
327 Content-Type: text/plain; charset=iso-2022-jp
|
|
|
328 </verb>
|
|
|
329 </quote>
|
|
|
330
|
|
|
331 <memo>
|
|
|
332 <p>
|
|
|
333 A part does not have content-type field is regarded as
|
|
|
334
|
|
|
335 <quote>
|
|
|
336 <verb>
|
|
|
337 Content-Type: text/plain; charset=us-ascii
|
|
|
338 </verb>
|
|
|
339 </quote>
|
|
|
340
|
|
|
341 <noindent>
|
|
|
342 <cf node="us-ascii">
|
|
|
343
|
|
|
344 And a part has unknown type/subtype is regarded as
|
|
|
345
|
|
|
346 <quote>
|
|
|
347 <verb>
|
|
|
348 Content-Type: application/octet-stream
|
|
|
349 </verb>
|
|
|
350 </quote>
|
|
|
351
|
|
|
352 </memo>
|
|
|
353
|
|
|
354
|
|
|
355 <h3> Emacs
|
|
|
356 <node> Emacs
|
|
|
357 <p>
|
|
|
358 $B$3$3$G$O(B `Emacs' $B$G(B FSF $B$,G[I[$7$F$$$k(B GNU Emacs $B$r;X$7!"(B`emacs' $B$G(B
|
|
|
359 GNU Emacs $B$NJQ<o$NAm>N$H$9$k!#(B
|
|
|
360
|
|
|
361
|
|
|
362 <h3> encoded-word
|
|
|
363 <node> encoded-word
|
|
|
364 <p>
|
|
|
365 Representation non <dref>ASCII</dref> characters in header. It
|
|
|
366 is defined in <concept>RFC 2047</concept>.
|
|
|
367 <p>
|
|
|
368 <rfc number="2047" type="Standards Track" author="K. Moore"
|
|
|
369 title="MIME (Multipurpose Internet Mail Extensions) Part
|
|
|
370 Three: Message Header Extensions for Non-ASCII Text"
|
|
|
371 date="November 1996" obsolete="1521,1522,1590">
|
|
|
372
|
|
|
373
|
|
|
374 <h3> encapsulation
|
|
|
375 <node> encapsulation
|
|
|
376 <p>
|
|
|
377 <a node="RFC 822">Internet mail</a> $B$rB>$N5-;v$K$^$k$4$HF~$l$kJ}K!!#(B
|
|
|
378 <p>
|
|
|
379 $BNc$($P!"5-;v$rE>Aw$7$?$j$9$k$N$KMQ$$$k!#(B
|
|
|
380 <p>
|
|
|
381 <cf node="message/rfc822">
|
|
|
382
|
|
|
383
|
|
|
384 <h3> euc-kr
|
|
|
385 <node> euc-kr
|
|
|
386 <p>
|
|
|
387 $B4Z9q8l$rI=8=$9$k$?$a$N(B <a node="MIME charset">MIME charset</a> $B$N#1$D!#(B
|
|
|
388 <p>
|
|
|
389 <dref>ISO 2022</dref> $B$K4p$$$F(B <dref>ASCII</dref> $B$K(B
|
|
|
390 <a node="KS C5601">KS C5601</a> $B$r(B <dref>8bit</dref> $B$G(B<a
|
|
|
391 node="Code extension">$BId9f3HD%(B</a>$B$7$F$$$k!#(B
|
|
|
392 <p>
|
|
|
393 <a node="RFC 1557">RFC 1557</a> $B$GDj5A$5$l$F$$$k!#(B
|
|
|
394 <p>
|
|
|
395 cf. <standard abbrev="euc-kr" org="Korea Industrial Standards
|
|
|
396 Association" title-en="Hangul Unix Environment"
|
|
|
397 number="KS C 5861" year="1992">
|
|
|
398
|
|
|
399
|
|
|
400 <h3> FTP <node> FTP
|
|
|
401 <p>
|
|
|
402 Internet $B$G(B file $B$rE>Aw$9$k$?$a$N(B protocol $B$N#1$D!#(BRFC 959 $B$GDj5A$5$l(B
|
|
|
403 $B$F$$$k!#(B
|
|
|
404 <p>
|
|
|
405 <rfc name="FTP" number="959" type="STD 9" author="Postel, J. and
|
|
|
406 J. Reynolds" title="File Transfer Protocol"
|
|
|
407 date="October 1985">
|
|
|
408
|
|
|
409
|
|
|
410 <h3> GB 2312-1980
|
|
|
411 <node> GB 2312
|
|
|
412 <p>
|
|
|
413 $BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=$9$?$a$N(B
|
|
|
414 <dref>94x94-character set</dref>$B!#Cf9q$N9q2HI8=`!#(B<a node="ISO
|
|
|
415 2022">ISO 2022</a> $B$G$N=*C<J8;z$O(B `A'.
|
|
|
416 <p>
|
|
|
417 $B$3$l$O(B GB $B$K$*$1$k4pK\=8$G$"$k!#(B
|
|
|
418
|
|
|
419 <standard abbrev="GB 2312"
|
|
|
420 title-cn="$B?.B)8r49MQ4A;zJTb{;zId=8(B -- $B4pK\=8(B"
|
|
|
421 title-en="Code of Chinese Graphic Character Set for
|
|
|
422 Information Interchange - Primary Set" number="GB 2312"
|
|
|
423 year="1980">
|
|
|
424
|
|
|
425
|
|
|
426 <h3> GB 8565.2-1988
|
|
|
427 <node> GB 8565.2
|
|
|
428 <p>
|
|
|
429 $BCf9q8l$N$?$a$NJd=u(B<a node="Character set">$BJ8;z=89g(B</a>$B!#Cf9q$N9q2HI8=`!#(B
|
|
|
430 <a node="GB 2312">GB 2312</a> $B$N6u$-ItJ,$KJd=<$9$k$h$&$KDj5A$5$l$?$i$7(B
|
|
|
431 $B$$!#(B
|
|
|
432
|
|
|
433 <standard abbrev="GB 8565.2" title-en="Information Processing - Coded
|
|
|
434 Character Sets for Text Communication - Part 2: Graphic
|
|
|
435 Characters used with Primary Set" number="GB 8565.2"
|
|
|
436 year="1988">
|
|
|
437
|
|
|
438
|
|
|
439 <h3> hz-gb2312
|
|
|
440 <node> hz-gb2312
|
|
|
441 <p>
|
|
|
442 $BCf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B <a
|
|
|
443 node="MIME charset">MIME charset</a> $B$N#1$D!#(B
|
|
|
444 <p>
|
|
|
445 <dref>ASCII</dref> $B$K(B <a node="GB 2312">GB 2312</a> $B$r(B 7bit $B$G(B
|
|
|
446 <a node="Code extension">$BId9f3HD%(B</a>$B$7$?$b$N$r(B ASCII printable $B$K$J$k(B
|
|
|
447 $B$h$&$K9)IW$7$F$$$k!#(B
|
|
|
448 <p>
|
|
|
449 RFC 1842, 1843 $B$GDj5A$5$l$F$$$k!#(B
|
|
|
450
|
|
|
451 <rfc number="1842" type="Informational" author="Y. Wei, Y. Zhang,
|
|
|
452 J. Li, J. Ding and Y. Jiang" title="ASCII Printable
|
|
|
453 Characters-Based Chinese Character Encoding for Internet
|
|
|
454 Messages" date="August 1995">
|
|
|
455 <rfc number="1843" type="Informational" author="F. Lee" title="HZ - A
|
|
|
456 Data Format for Exchanging Files of Arbitrarily Mixed
|
|
|
457 Chinese and ASCII characters" date="August 1995">
|
|
|
458
|
|
|
459
|
|
|
460 <h3> ISO 2022
|
|
|
461 <node> ISO 2022
|
|
|
462 <p>
|
|
|
463 <a node="Code extension">$BId9f3HD%(B</a>$B$N$?$a$N9q:]I8=`!#(B
|
|
|
464 <p>
|
|
|
465 $B$3$l$rMQ$$$FJ#?t$N(B<a node="Character set">$BJ8;z=89g(B</a>$B$rAH9g$;$F(B <a
|
|
|
466 node="7bit">7bit</a> $B$J$$$7(B <dref>8bit</dref> $B$N(B <a node="Coded
|
|
|
467 character set">$BId9f2=J8;z=89g(B</a> $B$r:n$k$3$H$,$G$-$k!#(B
|
|
|
468
|
|
|
469 <standard abbrev="ISO 2022" org="International Organization for
|
|
|
470 Standardization (ISO)" title-en="Information Processing:
|
|
|
471 ISO 7-bit and 8-bit coded character sets: Code extension
|
|
|
472 techniques" number="ISO/IEC 2022" year="1994">
|
|
|
473
|
|
|
474
|
|
|
475 <h3> iso-2022-cn
|
|
|
476 <node> iso-2022-cn
|
|
|
477 <p>
|
|
|
478 $BCf9q8l$rI=8=$9$k$?$a$N(B <a node="MIME charset">MIME charset</a> $B$N#1$D!#(B
|
|
|
479 <p>
|
|
|
480 <dref>ISO 2022</dref> $B$K4p$$$F(B <dref>ASCII</dref> $B$K(B
|
|
|
481 <a node="GB 2312">GB 2312</a>, <a node="CNS">CNS 11643 plain 1, plain
|
|
|
482 2</a> $B$r(B <a node="7bit">7bit</a> $B$G(B<a node="Code extension">$BId9f3HD%(B
|
|
|
483 </a>$B$7$F$$$k!#(B
|
|
|
484 <p>
|
|
|
485 <a node="RFC 1922">RFC 1922</a> $B$GDj5A$5$l$F$$$k!#(B
|
|
|
486
|
|
|
487
|
|
|
488 <h3> iso-2022-cn-ext
|
|
|
489 <node> iso-2022-cn-ext
|
|
|
490 <p>
|
|
|
491 $BCf9q8l$rI=8=$9$k$?$a$N(B <a node="MIME charset">MIME charset</a> $B$N#1$D!#(B
|
|
|
492 <p>
|
|
|
493 <dref>ISO 2022</dref> $B$K4p$$$F(B <dref>ASCII</dref> $B$K(B
|
|
|
494 <a node="GB 2312">GB 2312</a>, <a node="CNS">CNS 11643 plain 1
|
|
|
495 .. 7</a>, <a node="ISO-IR-165">ISO-IR-165</a> $BEy$r(B <a
|
|
|
496 node="7bit">7bit</a> $B$G(B<a node="Code extension">$BId9f3HD%(B</a>$B$7$F$$$k!#(B
|
|
|
497 <p>
|
|
|
498 <a node="RFC 1922">RFC 1922</a> $B$GDj5A$5$l$F$$$k!#(B
|
|
|
499 <p>
|
|
|
500 <memo>
|
|
|
501 MULE 2.3 $B$*$h$S!"8=:_$N(B XEmacs/mule $B$G$O@5$7$/07$&$3$H$O$G$-$J$$!#(B
|
|
|
502 <p>
|
|
|
503 Emacs/mule $B$G$OMxMQ2DG=$G$"$k!#(B
|
|
|
504 </memo>
|
|
|
505
|
|
|
506
|
|
|
507 <h3> iso-2022-jp
|
|
|
508 <node> iso-2022-jp
|
|
|
509 <p>
|
|
|
510 $BF|K\8l$rI=8=$9$k$?$a$N(B <a node="MIME charset">MIME charset</a> $B$N0l$D!#(B
|
|
|
511 <p>
|
|
|
512 $B8E$$(B <dref>ISO 2022</dref> $B$K4p$$$F(B <a
|
|
|
513 node="ASCII">ASCII</a>, JIS X0201-Latin, <a node="JIS C6226-1978">JIS
|
|
|
514 X0208-1978</a>, <a node="JIS X0208">JIS X0208-1983</a> $B$r@Z$jBX$($k(B <a
|
|
|
515 node="7bit">7bit</a> $BJ8;zId9f!#(B
|
|
|
516 <p>
|
|
|
517 RFC 1468 $B$GDj5A$5$l$F$$$k!#(B
|
|
|
518 <p>
|
|
|
519 <memo>
|
|
|
520 JIS X0208-1996? $B$G$O(B <dref>ISO 2022</dref> $B$HFHN)$KDj5A$5$l(B
|
|
|
521 $B$kM=Dj!#(B
|
|
|
522 </memo>
|
|
|
523
|
|
|
524 <rfc name="iso-2022-jp" number="1468" author="Murai J., M. Crispin,
|
|
|
525 and E. van der Poel" title="Japanese Character Encoding
|
|
|
526 for Internet Messages" date="June 1993">
|
|
|
527
|
|
|
528
|
|
|
529 <h3> iso-2022-jp-2
|
|
|
530 <node> iso-2022-jp-2
|
|
|
531 <p>
|
|
|
532 A <dref>MIME charset</dref>, which is a multilingual extension of
|
|
|
533 <dref>iso-2022-jp</dref>.
|
|
|
534 <p>
|
|
|
535 It is defined in RFC 1554.
|
|
|
536
|
|
|
537 <rfc name="iso-2022-jp-2" number="1554" type="Informational"
|
|
|
538 author="Ohta M. and Handa K." title="ISO-2022-JP-2:
|
|
|
539 Multilingual Extension of ISO-2022-JP" date="December
|
|
|
540 1993">
|
|
|
541
|
|
|
542
|
|
|
543 <h3> iso-2022-kr
|
|
|
544 <node> iso-2022-kr
|
|
|
545 <p>
|
|
|
546 A <a node="MIME charset">MIME charset</a> for Korean language (Hangul
|
|
|
547 script).
|
|
|
548 <p>
|
|
|
549 It is based on <dref>ISO 2022</dref> <dref>code extension</dref>
|
|
|
550 technique to extends <dref>ASCII</dref> to use <dref>KS C5601</dref>
|
|
|
551 as <dref>7bit</dref> text.
|
|
|
552 <p>
|
|
|
553 It is defined in <dref>RFC 1557</dref>.
|
|
|
554
|
|
|
555
|
|
|
556 <h3> ISO 646
|
|
|
557 <node> ISO 646
|
|
|
558 <p>
|
|
|
559 $B3F9q$G6&DL$K;H$($k:G>.8BEY$N(B<a node="Character set">$BJ8;z=89g(B</a>$B$rDj$a(B
|
|
|
560 $B$?$b$N!#(B<a node="94 character set">94 $BJ8;z=89g(B</a>$B$N#1$D!#(BISO 646 IRV
|
|
|
561 $B!J9q:]4p=`HG!K$r85$K4v$D$+$NJ8;z$O3F9q$G0c$&J8;z$r3dEv$k$3$H$r5v$7$F$$(B
|
|
|
562 $B$F!"4v$D$+$NJQ<o$,B8:_$9$k!#(B<dref>ASCII</dref> $B$d(B JIS
|
|
|
563 X0201-Latin $B$O$=$N0l<o!#(B
|
|
|
564
|
|
|
565 <standard abbrev="ISO 646" org="International Organization for
|
|
|
566 Standardization (ISO)" title-en="Information technology:
|
|
|
567 ISO 7-bit coded character set for information
|
|
|
568 interchange" number="ISO/IEC 646" year="1991">
|
|
|
569
|
|
|
570
|
|
|
571 <h3> ISO 8859-1
|
|
|
572 <node> ISO 8859-1
|
|
|
573 <p>
|
|
|
574 <standard abbrev="ISO 8859-1" org="International Organization for
|
|
|
575 Standardization (ISO)" title-en="Information Processing
|
|
|
576 -- 8-bit Single-Byte Coded Graphic Character Sets --
|
|
|
577 Part 1: Latin Alphabet No.1" number="ISO 8859-1"
|
|
|
578 year="1987">
|
|
|
579
|
|
|
580
|
|
|
581 <h3> iso-8859-1
|
|
|
582 <node> iso-8859-1
|
|
|
583 <p>
|
|
|
584 <concept>iso-8859-1</concept> is a <dref>MIME charset</dref> for
|
|
|
585 west-European languages written by Latin script.
|
|
|
586 <p>
|
|
|
587 <dref>ISO 2022</dref> $B$K4p$$$F!"(B<dref>ASCII</dref> $B$K(B
|
|
|
588 <a node="ISO 8859-1">ISO 8859-1</a> $B$r(B <dref>8bit</dref> $B$G(B<a
|
|
|
589 node="Code extension">$BId9f3HD%(B</a>$B$7$F$$$k!#(B
|
|
|
590 <p>
|
|
|
591 It is defined in <dref>RFC 2046</dref>.
|
|
|
592
|
|
|
593
|
|
|
594 <h3> ISO 8859-2
|
|
|
595 <node> ISO 8859-2
|
|
|
596 <p>
|
|
|
597 <standard abbrev="ISO 8859-2" org="International Organization for
|
|
|
598 Standardization (ISO)" title-en="Information Processing
|
|
|
599 -- 8-bit Single-Byte Coded Graphic Character Sets --
|
|
|
600 Part 2: Latin alphabet No.2" number="ISO 8859-2"
|
|
|
601 year="1987">
|
|
|
602
|
|
|
603
|
|
|
604 <h3> iso-8859-2
|
|
|
605 <node> iso-8859-2
|
|
|
606 <p>
|
|
|
607 <concept>iso-8859-2</concept> is a <dref>MIME charset</dref> for
|
|
|
608 east-European languages written by Latin script.
|
|
|
609 <p>
|
|
|
610 <dref>ISO 2022</dref> $B$K4p$$$F!"(B<dref>ASCII</dref> $B$K(B
|
|
|
611 <a node="ISO 8859-2">ISO 8859-2</a> $B$r(B <dref>8bit</dref> $B$G(B<a
|
|
|
612 node="Code extension">$BId9f3HD%(B</a>$B$7$F$$$k!#(B
|
|
|
613 <p>
|
|
|
614 It is defined in <dref>RFC 2046</dref>.
|
|
|
615
|
|
|
616
|
|
|
617 <h3> ISO 8859-3
|
|
|
618 <node> ISO 8859-3
|
|
|
619 <p>
|
|
|
620 <standard abbrev="ISO 8859-3" org="International Organization for
|
|
|
621 Standardization (ISO)" title-en="Information
|
|
|
622 Processing -- 8-bit Single-Byte Coded Graphic
|
|
|
623 Character Sets -- Part 3: Latin alphabet No.3"
|
|
|
624 number="ISO 8859-3" year="1988">
|
|
|
625
|
|
|
626
|
|
|
627 <h3> ISO 8859-4
|
|
|
628 <node> ISO 8859-4
|
|
|
629 <p>
|
|
|
630 <standard abbrev="ISO 8859-4" org="International Organization for
|
|
|
631 Standardization (ISO)" title-en="Information
|
|
|
632 Processing -- 8-bit Single-Byte Coded Graphic
|
|
|
633 Character Sets -- Part 4: Latin alphabet No.4"
|
|
|
634 number="ISO 8859-4" year="1988">
|
|
|
635
|
|
|
636
|
|
|
637 <h3> ISO 8859-5
|
|
|
638 <node> ISO 8859-5
|
|
|
639 <p>
|
|
|
640 <standard abbrev="ISO 8859-5" org="International Organization for
|
|
|
641 Standardization (ISO)" title-en="Information Processing
|
|
|
642 -- 8-bit Single-Byte Coded Graphic Character Sets --
|
|
|
643 Part 5: Latin/Cyrillic alphabet" number="ISO 8859-5"
|
|
|
644 year="1988">
|
|
|
645
|
|
|
646
|
|
|
647 <h3> iso-8859-5
|
|
|
648 <node> iso-8859-5
|
|
|
649 <p>
|
|
|
650 <concept>iso-8859-5</concept> is a <dref>MIME charset</dref> for
|
|
|
651 Cyrillic script.
|
|
|
652 <p>
|
|
|
653 <dref>ISO 2022</dref> $B$K4p$$$F!"(B<dref>ASCII</dref> $B$K(B
|
|
|
654 <a node="ISO 8859-5">ISO 8859-5</a> $B$r(B <dref>8bit</dref> $B$G(B<a
|
|
|
655 node="Code extension">$BId9f3HD%(B</a>$B$7$F$$$k!#(B
|
|
|
656 <p>
|
|
|
657 It is defined in <dref>RFC 2046</dref>.
|
|
|
658
|
|
|
659
|
|
|
660 <h3> ISO 8859-6
|
|
|
661 <node> ISO 8859-6
|
|
|
662 <p>
|
|
|
663 <standard abbrev="ISO 8859-6" org="International Organization for
|
|
|
664 Standardization (ISO)" title-en="Information
|
|
|
665 Processing -- 8-bit Single-Byte Coded Graphic
|
|
|
666 Character Sets -- Part 6: Latin/Arabic alphabet"
|
|
|
667 number="ISO 8859-6" year="1987">
|
|
|
668
|
|
|
669
|
|
|
670 <h3> ISO 8859-7
|
|
|
671 <node> ISO 8859-7
|
|
|
672 <p>
|
|
|
673 <standard abbrev="ISO 8859-7" org="International Organization for
|
|
|
674 Standardization (ISO)" title-en="Information Processing
|
|
|
675 -- 8-bit Single-Byte Coded Graphic Character Sets --
|
|
|
676 Part 7: Latin/Greek alphabet" number="ISO 8859-7"
|
|
|
677 year="1987">
|
|
|
678
|
|
|
679
|
|
|
680 <h3> iso-8859-7
|
|
|
681 <node> iso-8859-7
|
|
|
682 <p>
|
|
|
683 <concept>iso-8859-7</concept> is a <dref>MIME charset</dref> for
|
|
|
684 Greek script.
|
|
|
685 <p>
|
|
|
686 <dref>ISO 2022</dref> $B$K4p$$$F!"(B<dref>ASCII</dref> $B$K(B
|
|
|
687 <a node="ISO 8859-7">ISO 8859-7</a> $B$r(B <dref>8bit</dref> $B$G(B<a
|
|
|
688 node="Code extension">$BId9f3HD%(B</a>$B$7$F$$$k!#(B
|
|
|
689 <p>
|
|
|
690 It is defined in RFC 1947.
|
|
|
691
|
|
|
692 <rfc name="iso-8859-7" number="1947" type="Informational"
|
|
|
693 author="D. Spinellis" title="Greek Character Encoding
|
|
|
694 for Electronic Mail Messages" date="May 1996">
|
|
|
695
|
|
|
696
|
|
|
697 <h3> ISO 8859-8
|
|
|
698 <node> ISO 8859-8
|
|
|
699 <p>
|
|
|
700 <standard abbrev="ISO 8859-8" org="International Organization for
|
|
|
701 Standardization (ISO)" title-en="Information
|
|
|
702 Processing -- 8-bit Single-Byte Coded Graphic
|
|
|
703 Character Sets -- Part 8: Latin/Hebrew alphabet"
|
|
|
704 number="ISO 8859-8" year="1988">
|
|
|
705
|
|
|
706
|
|
|
707 <h3> ISO 8859-9
|
|
|
708 <node> ISO 8859-9
|
|
|
709 <p>
|
|
|
710 <standard abbrev="ISO 8859-9" org="International Organization for
|
|
|
711 Standardization (ISO)" title-en="Information
|
|
|
712 Processing -- 8-bit Single-Byte Coded Graphic
|
|
|
713 Character Sets -- Part 9: Latin alphabet No.5"
|
|
|
714 number="ISO 8859-9" year="1990">
|
|
|
715
|
|
|
716
|
|
|
717 <h3> ISO-IR-165, CCITT Extended GB <node> ISO-IR-165
|
|
|
718 <p>
|
|
|
719 CCITT $B$,EPO?$7$?!"Cf9qBgN&$GMQ$$$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=(B
|
|
|
720 $B8=$9$k$?$a$N(B <dref>94x94-character set</dref>$B!#(B
|
|
|
721 <p>
|
|
|
722 <a node="GB 2312">GB 2312</a> $B$H(B <a node="GB 8865.2">GB 8565 $BI=#2(B</a>
|
|
|
723 $B$K(B 150 $BJ8;z$[$I$rDI2C$7$?$b$N$i$7$$!#(B
|
|
|
724 <p>
|
|
|
725 <dref>ISO 2022</dref> $B$G$N=*C<J8;z$O(B `E' $B$G$"$k!#(B
|
|
|
726
|
|
|
727
|
|
|
728 <h3> JIS X0201
|
|
|
729 <node> JIS X0201
|
|
|
730 <p>
|
|
|
731 <a node="ISO 646">ISO 646</a> $B$NJQ<o$N#1$D$G$"$k(B Latin $BJ8;z=89g$H(B 1
|
|
|
732 byte $B$N%+%?%+%JJ8;z=89g$+$i$J$k!#(B
|
|
|
733 <p>
|
|
|
734 $B85$O(B <concept>JIS C6220-1976</concept> $B$H8@$C$?$,(B <concept>JIS
|
|
|
735 X0201</concept> $B$KHV9f$,JQ99$5$l$?!#(B
|
|
|
736
|
|
|
737 <standard abbrev="JIS X0201-1976" org="$BF|K\5,3J6(2q(B (Japanese
|
|
|
738 Standards Association)" title-ja="$B>pJs8r49MQId9f(B"
|
|
|
739 title-en="Code for Information Interchange" number="JIS
|
|
|
740 X 0201-1976">
|
|
|
741
|
|
|
742 $B$^$?!"(B1996 $BG/$K2~DjHG$,=P$kM=Dj!#(B
|
|
|
743
|
|
|
744 <standard abbrev="JIS X0201-1996?" org="$BF|K\5,3J6(2q(B (Japanese
|
|
|
745 Standards Association)"
|
|
|
746 title-ja="$B#7%S%C%H5Z$S#8%S%C%H$N>pJs8r49MQId9f2=J8;z=89g(B"
|
|
|
747 title-en="7-bit and 8-bit coded character sets for
|
|
|
748 information interchange" number="JIS X 0201" year="1996?
|
|
|
749 draft">
|
|
|
750
|
|
|
751
|
|
|
752 <h3> JIS C6226-1978
|
|
|
753 <node> JIS C6226
|
|
|
754 <p>
|
|
|
755 $BF|K\8l$rI=$9$?$a$K:n$i$l$?(B <dref>94x94-character set</dref>$B!#F|K\$N9q(B
|
|
|
756 $B2HI8=`!#(BJIS X0208-1978 $B$H$b$$$&!#(B
|
|
|
757 <p>
|
|
|
758 <cf node="JIS X0208">
|
|
|
759
|
|
|
760
|
|
|
761 <h3> JIS X0208
|
|
|
762 <node> JIS X0208
|
|
|
763 <p>
|
|
|
764 $BF|K\8l$rI=$9$?$a$K:n$i$l$?(B <dref>94x94-character set</dref>$B!#F|K\$N9q(B
|
|
|
765 $B2HI8=`!#(B1978 $BG/HG!"(B1983 $BG/HG!"(B1990 $BG/HG$,$"$k$,!"(BInternet $B$G$O(B 1983 $BG/(B
|
|
|
766 $BHG$,$b$C$H$bNI$/;H$o$l$F$$$k!#(B
|
|
|
767 <p>
|
|
|
768 JIS X0208 $B$O5-9f!"?t;z!"%m!<%^;z!"$R$i$,$J!"%+%?%+%J!"%.%j%7%cJ8;z!"%-(B
|
|
|
769 $B%j%kJ8;z!"7S@~AG!"Bh#1?e=`!"Bh#2?e=`$N4A;z$,4^$^$l$k!#C"$7!"(B1983 $BG/HG(B
|
|
|
770 $B$N0lIt$N5-9f$H7S@~AG$O(B 1978 $BG/HG$K$O$J$$!#$^$?!"0lIt$N4A;z$N;z7A$,(B
|
|
|
771 1983 $BG/HG$G$OJQ99$5$l!"$^$?!"Bh#1?e=`$HBh#2?e=`$,F~$lBX$o$C$F$$$?$j$9(B
|
|
|
772 $B$k!#$3$N$?$a!"(B1978 $BG/HG$H(B 1983 $BG/HG$O0[$J$kJ8;z=89g$H$7$F07$o$l$k!#(B
|
|
|
773 <p>
|
|
|
774 1990 $BG/$N2~Dj$G$O(B 1983 $BG/HG$KBP$9$kDI2C$,9T$o$l$?!#$3$N$?$a!"(B1990 $BG/HG(B
|
|
|
775 $B$r;X<($9$k>l9g$OA0$K99?7%7!<%1%s%9$rMQ$$$k!#(B
|
|
|
776
|
|
|
777 <standard abbrev="JIS X0208-1978" org="$BF|K\5,3J6(2q(B (Japanese Standards
|
|
|
778 Association)" title-ja="$B>pJs8r49MQ4A;zId9f7O(B"
|
|
|
779 title-en="Code of the Japanese graphic character set for
|
|
|
780 information interchange" number="JIS C6226" year="1978">
|
|
|
781 <standard abbrev="JIS X0208-1983,1990" org="$BF|K\5,3J6(2q(B (Japanese Standards
|
|
|
782 Association)" title-ja="$B>pJs8r49MQ4A;zId9f7O(B"
|
|
|
783 title-en="Code of the Japanese graphic character set for
|
|
|
784 information interchange" number="JIS X0208" year="1983,1990">
|
|
|
785
|
|
|
786 <p>
|
|
|
787 $B$^$?!"(B1996 $BG/$K2~DjHG$,=PHG$5$l$kM=Dj!#!J;z7A$NJQ99$O9T$o$l$J$$$N$GJ8(B
|
|
|
788 $B;z=89g$H$7$F$O(B 1990 $BG/HG$HF10l$G$"$k!K(B
|
|
|
789
|
|
|
790 <standard abbrev="JIS X0208-1996?" org="$BF|K\5,3J6(2q(B (Japanese
|
|
|
791 Standards Association)" title-ja="$B#7%S%C%H5Z$S#8%S%C%H$N(B
|
|
|
792 $B#2%P%$%H>pJs8r49MQId9f2=4A;z=89g(B" title-en="7-bit and
|
|
|
793 8-bit double byte coded Kanji sets for information
|
|
|
794 interchange" number="JIS X 0208" year="1996? draft">
|
|
|
795
|
|
|
796
|
|
|
797 <h3> JIS X0212-1990
|
|
|
798 <node> JIS X0212
|
|
|
799 <p>
|
|
|
800 <a node="JIS X0208">JIS X0208</a> $B$K$J$+$C$?J8;z$r=8$a$?(B
|
|
|
801 <dref>94x94-character set</dref>$B!#!VJd=u4A;z!W$H$b8F$P$l$k!#F|K\$N9q2H(B
|
|
|
802 $BI8=`!#(B<dref>ISO 2022</dref> $B$G$N=*C<J8;z$O(B `D'.
|
|
|
803
|
|
|
804
|
|
|
805 <h3> koi8-r
|
|
|
806 <node> koi8-r
|
|
|
807 <p>
|
|
|
808 A <dref>MIME charset</dref> for Cyrillic script for Russian or other
|
|
|
809 languages.
|
|
|
810 <p>
|
|
|
811 It is a 1 byte <dref>8bit</dref> <dref>coded character set</dref>, not
|
|
|
812 based on <dref>ISO 2022</dref>. It is a de-fact standard.
|
|
|
813 <p>
|
|
|
814 It is defined in RFC 1489.
|
|
|
815 <p>
|
|
|
816 <rfc number="1489" author="A. Chernov" title="Registration of a
|
|
|
817 Cyrillic Character Set" date="July 1993">
|
|
|
818
|
|
|
819
|
|
|
820 <h3> KS C5601-1987
|
|
|
821 <node> KS C5601
|
|
|
822 <p>
|
|
|
823 A <dref>94x94-character set</dref> for Korean language (Hangul
|
|
|
824 script). Korean Standard. Final byte of <dref>ISO 2022</dref> is
|
|
|
825 `C'.
|
|
|
826
|
|
|
827 <standard abbrev="KS C5601" org="Korea Industrial Standards
|
|
|
828 Association" title-en="Code for Information Interchange
|
|
|
829 (Hangul and Hanja)" number="KS C 5601" year="1987">
|
|
|
830
|
|
|
831
|
|
|
832 <h3> message
|
|
|
833 <node> message
|
|
|
834 <p>
|
|
|
835 $B$3$3$G$O(B <dref>RFC 822</dref> $B$GDj5A$5$l$k(B mail $B$H(B <dref>RFC
|
|
|
836 1036</dref> $B$GDj5A$5$l$k(B news $B5-;v$NAm>N$H$7$FMQ$$$k!#(B
|
|
|
837
|
|
|
838
|
|
|
839 <h3> message/rfc822
|
|
|
840 <node> message/rfc822
|
|
|
841 <p>
|
|
|
842 <concept>message/rfc822</concept> indicates that the body contains an
|
|
|
843 encapsulated message, with the syntax of an <dref>RFC 822</dref>
|
|
|
844 message. It is the replacement of traditional <dref>RFC 934</dref>
|
|
|
845 encapsulation. It is defined in <dref>RFC 2046</dref>.
|
|
|
846
|
|
|
847
|
|
|
848 <h3> method
|
|
|
849 <node> method
|
|
|
850 <p>
|
|
|
851 tm $B$GFCDj$N<oN`$N(B data $B$r:F@8$7$?$H$-<B:]$K$=$N=hM}$r9T$J$&(B
|
|
|
852 program. Emacs Lisp $B$G=q$+$l$?(B <concept>internal method</concept> $B$H(B C
|
|
|
853 $B$d(B script $B8@8l$J$I$G=q$+$l$?(B <concept>external method</concept> $B$,$"$k!#(B
|
|
|
854 <p>
|
|
|
855 <cf file="tm-view-en" node="method">
|
|
|
856
|
|
|
857
|
|
|
858 <h3> MIME
|
|
|
859 <node> MIME
|
|
|
860 <p>
|
|
|
861 MIME stands for <concept>Multipurpose Internet Mail
|
|
|
862 Extensions</concept>, it is an extension for <dref>RFC 822</dref>.
|
|
|
863 <p>
|
|
|
864 According to RFC 2045:
|
|
|
865 <p>
|
|
|
866 STD 11, RFC 822, defines a message representation protocol specifying
|
|
|
867 considerable detail about US-ASCII message headers, and leaves the
|
|
|
868 message content, or message body, as flat US-ASCII text. This set of
|
|
|
869 documents, collectively called the Multipurpose Internet Mail
|
|
|
870 Extensions, or MIME, redefines the format of messages to allow for
|
|
|
871 <p>
|
|
|
872 <ol>
|
|
|
873 <li>textual message bodies in character sets other than US-ASCII,
|
|
|
874 </li>
|
|
|
875 <li>an extensible set of different formats for non-textual message
|
|
|
876 bodies,
|
|
|
877 </li>
|
|
|
878 <li>multi-part message bodies, and
|
|
|
879 </li>
|
|
|
880 <li>textual header information in character sets other than US-ASCII.
|
|
|
881 </ol>
|
|
|
882
|
|
|
883 <p>
|
|
|
884 It is defined in <dref>RFC 2045</dref>, <dref>RFC 2046</dref>, <a
|
|
|
885 node="encoded-word">RFC 2047</a>, <dref>RFC 2048</dref> and <dref>RFC
|
|
|
886 2049</dref>.
|
|
|
887
|
|
|
888
|
|
|
889 <h3> MIME charset
|
|
|
890 <node> MIME charset
|
|
|
891 <p>
|
|
|
892 <dref>Coded character set</dref> used in <dref>Content-Type
|
|
|
893 field</dref> or charset parameter of <a
|
|
|
894 node="encoded-word">encoded-word</a>.
|
|
|
895 <p>
|
|
|
896 It is defined in <dref>RFC 2045</dref>.
|
|
|
897 <p>
|
|
|
898 <dref>iso-2022-jp</dref> $B$d(B <a node="euc-kr">euc-kr</a> $B$O$=$N#1$D!#(B
|
|
|
899 $B!J$3$3$G$O!"(BMIME charset $B$O(B<a node="Character set">$BJ8;z=89g(B</a>$B$H6hJL(B
|
|
|
900 $B$7$F>.J8;z$G=q$$$F$$$k!K(B
|
|
|
901
|
|
|
902
|
|
|
903 <h3> MTA
|
|
|
904 <node> MTA
|
|
|
905 <p>
|
|
|
906 <concept>Message Transfer Agent</concept> $B$NN,$G!"(Bsendmail $B$J$I$N(B mail
|
|
|
907 $BG[Aw(B program $B$H(B news server $B$NAm>N!#(B
|
|
|
908 <p>
|
|
|
909 <cf node="MUA">
|
|
|
910
|
|
|
911
|
|
|
912 <h3> MUA
|
|
|
913 <node> MUA
|
|
|
914 <p>
|
|
|
915 <concept>Message User Agent</concept> $B$NN,$G!"(Bmail reader $B$H(B news
|
|
|
916 reader $B$NAm>N!#(B
|
|
|
917 <p>
|
|
|
918 <cf node="MTA">
|
|
|
919
|
|
|
920
|
|
|
921 <h3> MULE
|
|
|
922 <node> MULE
|
|
|
923 <p>
|
|
|
924 $BH>ED(B $B7u0l;a$i$,:n$C$?!"B?8@8l$5$l$?(B <a node="Emacs">Emacs</a>.
|
|
|
925 <p>
|
|
|
926 [MULE] Nishikimi M., Handa K. and Tomura S., ``Mule: MULtilingual
|
|
|
927 Enhancement to GNU Emacs'', Proc. of INET'93, August, 1993.
|
|
|
928 <p>
|
|
|
929 $B8=:_!"(BMULE $B$N5!G=$r(B Emacs $B$K(B merge $B$9$k:n6H$,9T$o$l$F$*$j!"(B<a
|
|
|
930 href="ftp://etlport.etl.go.jp/pub/mule/mule-19.33-gamma.taz"> alpha $BHG(B
|
|
|
931 </a> $B$,B8:_$9$k!#(B
|
|
|
932 <p>
|
|
|
933 $B$=$NB>!"(BXEmacs $B$K(B merge $B$7$?$b$N$bB8:_$9$k!#(B
|
|
|
934 <p>
|
|
|
935 $B$3$N$?$a!"8=:_$G$OB?8@8l(B Emacs $B$O!"85!9$N(B MULE $B$r4^$a$F#3<oN`$"$k$3$H(B
|
|
|
936 $B$K$J$k!#(B
|
|
|
937 <p>
|
|
|
938 $B$=$3$G!"$3$3$G$O!"B?8@8l(B Emacs $B$NAm>N$r(B <concept>mule</concept>, $B85!9(B
|
|
|
939 $B$N(B MULE $B$r(B <concept>MULE</concept>, mule $B5!G=$r(B merge $B$7$?(B Emacs $B$r(B
|
|
|
940 <concept>Emacs/mule</concept>, mule $B5!G=$r(B merge $B$7$?(B XEmacs $B$r(B
|
|
|
941 <concept>XEmacs/mule</concept> $B$H8F$V$3$H$K$9$k!#(B
|
|
|
942
|
|
|
943
|
|
|
944 <h3> Multipart
|
|
|
945 <node> multipart
|
|
|
946 <p>
|
|
|
947 <concept>multipart</concept> means <dref>media type</dref> to insert
|
|
|
948 multiple <dref>entities</dref> in a single body. Or it also indicates
|
|
|
949 a message consists of multiple entities.
|
|
|
950 <p>
|
|
|
951 There are following subtypes registered in <dref>RFC 2046</dref>:
|
|
|
952
|
|
|
953 <ul>
|
|
|
954 <li><dref>multipart/mixed</dref>
|
|
|
955 <li><dref>multipart/alternative</dref>
|
|
|
956 <li><dref>multipart/digest</dref>
|
|
|
957 <li><dref>multipart/parallel</dref>
|
|
|
958 </ul>
|
|
|
959
|
|
|
960 <noindent>
|
|
|
961 and registered in <a node="Security multipart">RFC 1847</a>:
|
|
|
962
|
|
|
963 <ul>
|
|
|
964 <li><dref>multipart/signed</dref>
|
|
|
965 <li><dref>multipart/encrypted</dref>
|
|
|
966 </ul>
|
|
|
967
|
|
|
968
|
|
|
969 <h3> multipart/alternative
|
|
|
970 <node> multipart/alternative
|
|
|
971 <p>
|
|
|
972 <concept>multipart/digest</concept> is one of <dref>multipart</dref>
|
|
|
973 media types. This type is syntactically identical to
|
|
|
974 <dref>multipart/mixed</dref>, but the semantics are different. In
|
|
|
975 particular, each of the body parts is an ``alternative'' version of
|
|
|
976 the same information.
|
|
|
977 <p>
|
|
|
978 <cf node="RFC 2046">
|
|
|
979
|
|
|
980
|
|
|
981 <h3> multipart/digest
|
|
|
982 <node> multipart/digest
|
|
|
983 <p>
|
|
|
984 <concept>multipart/digest</concept> is one of <dref>multipart</dref>
|
|
|
985 media types. This type is syntactically identical to
|
|
|
986 <dref>multipart/mixed</dref>, but the semantics are different. In
|
|
|
987 particular, in a digest, the default Content-Type value for a body
|
|
|
988 part is changed from <dref>text/plain</dref> to
|
|
|
989 <dref>message/rfc822</dref>.
|
|
|
990 <p>
|
|
|
991 This is the replacement of traditional <dref>RFC 1153</dref> based
|
|
|
992 <dref>encapsulation</dref>.
|
|
|
993 <p>
|
|
|
994 <cf node="RFC 2046">
|
|
|
995
|
|
|
996
|
|
|
997 <h3> multipart/encrypted
|
|
|
998 <node> multipart/encrypted
|
|
|
999 <p>
|
|
|
1000 RFC 1847 $B$GDj5A$5$l$?(B <dref>Security multipart</dref> $B$N#1$D$G!"0E9f2=(B
|
|
|
1001 $B$5$l$?(B message $B$rI=8=$9$k$N$KMQ$$$k!#(B
|
|
|
1002 <p>
|
|
|
1003 <cf node="PGP/MIME">
|
|
|
1004
|
|
|
1005
|
|
|
1006 <h3> multipart/mixed
|
|
|
1007 <node> multipart/mixed
|
|
|
1008 <p>
|
|
|
1009 Primary and default subtype of <dref>multipart</dref>, it is used when
|
|
|
1010 the body parts are independent and need to be bundled in a particular
|
|
|
1011 order.
|
|
|
1012 <p>
|
|
|
1013 <cf node="RFC 2046">
|
|
|
1014
|
|
|
1015
|
|
|
1016 <h3> multipart/parallel
|
|
|
1017 <node> multipart/parallel
|
|
|
1018 <p>
|
|
|
1019 <concept>multipart/parallel</concept> is a subtype of
|
|
|
1020 <dref>multipart</dref>. This type is syntactically identical to
|
|
|
1021 <dref>multipart/mixed</dref>, but the semantics are different. In
|
|
|
1022 particular, in a parallel entity, the order of body parts is not
|
|
|
1023 significant.
|
|
|
1024 <p>
|
|
|
1025 <cf node="RFC 2046">
|
|
|
1026
|
|
|
1027
|
|
|
1028 <h3> multipart/signed
|
|
|
1029 <node> multipart/signed
|
|
|
1030 <p>
|
|
|
1031 RFC 1847 $B$GDj5A$5$l$?(B <dref>Security multipart</dref> $B$N#1$D$G!"EE;R=p(B
|
|
|
1032 $BL>$rI=8=$9$k$N$KMQ$$$k!#(B
|
|
|
1033 <p>
|
|
|
1034 <cf node="PGP/MIME">
|
|
|
1035
|
|
|
1036
|
|
|
1037 <h3> PGP
|
|
|
1038 <node> PGP
|
|
|
1039 <p>
|
|
|
1040 Phil Zimmermann $B;a$,:n@.$7$?8x3+800E9f=hM}7O$N#1$D!#(B
|
|
|
1041 <dref>message</dref> $B$N0E9f2=$dEE;R=pL>$r9T$&$3$H$,$G$-$k!#(BPretty Good
|
|
|
1042 Privacy $B$NN,!#(B
|
|
|
1043 <p>
|
|
|
1044 $BEAE}E*$J(B PGP $B$G$O(B <dref>encapsulation</dref> $B$K(B <dref>RFC 934</dref>$B$K(B
|
|
|
1045 $B=`$8$?J}K!$rMQ$$$k!#$3$l$O(B <dref>MIME</dref> $B$HL7=b$9$k$N$G(B
|
|
|
1046 <dref>PGP/MIME</dref> $B$,Ds0F$5$l$F$$$k!#0lJ}!"(BMIME $B$K$*$$$F(B PGP $B$N(B
|
|
|
1047 encapsulation $B$rMQ$$$kJ}K!(B <cf node="PGP-kazu"> $B$bMxMQ$5$l$F$-$?!#$7$+(B
|
|
|
1048 $B$7!":#8e$O(B PGP/MIME $B$KE}0l$7$F$$$/J}$,K>$^$7$$!#(B
|
|
|
1049 <p>
|
|
|
1050 <rfc name="PGP" number="1991" type="Informational" author="D. Atkins,
|
|
|
1051 W. Stallings and P. Zimmermann" title="PGP Message
|
|
|
1052 Exchange Formats" date="August 1996">
|
|
|
1053
|
|
|
1054
|
|
|
1055
|
|
|
1056 <h3> PGP-kazu
|
|
|
1057 <node> PGP-kazu
|
|
|
1058 <p>
|
|
|
1059 $B;3K\(B $BOBI'(B $B;a$,Ds0F$7$?(B <a node="MIME">MIME</a> $B$G(B <a
|
|
|
1060 node="PGP">PGP</a> $B$rMxMQ$9$k$?$a$NJ}K!$r$3$3$G$O(B
|
|
|
1061 <concept>PGP-kazu</concept> $B$H8F$V$3$H$K$9$k!#(B
|
|
|
1062 <p>
|
|
|
1063 PGP-kazu $B$O(B <concept>application/pgp</concept> $B$H$$$&(B
|
|
|
1064 <dref>content-type</dref> $B$rDj5A$9$k!#(B
|
|
|
1065 <p>
|
|
|
1066 application/pgp $B$N(B part $B$G$O(B PGP $B$N(B <dref>encapsulation</dref> $B$,MQ$$(B
|
|
|
1067 $B$i$l$k!#(BPGP $B$N(B encapsulation <cf node="RFC 934"> $B$H(B MIME $B$N(B
|
|
|
1068 encapsulation $B$OL7=b$9$k$N$G!"(BPGP $B$N(B encapsulation $B$r2r$+$J$$8B$j!"Cf(B
|
|
|
1069 $B$K4^$^$l$?(B MIME message $B$rFI$`$3$H$,$G$-$J$/$J$k!#B($A!"(BPGP-kazu $B$KBP(B
|
|
|
1070 $B1~$7$F$$$J$$(B MIME $B$KBP1~$7$?(B <dref>MUA</dref> $B$O$=$N(B part $B$,FI$a$J$/$J(B
|
|
|
1071 $B$k!#$=$NBe$o$j!"(BMIME $B$KBP1~$7$F$$$J$$(B PGP $BBP1~$N(B <dref>MUA</dref> $B$G$b(B
|
|
|
1072 message $B$rFI$`$3$H$,$G$-$k!#(B
|
|
|
1073 <p>
|
|
|
1074 PGP-kazu $B$G$O(B MUA $B$O(B PGP $B$N$H(B MIME $B$N$H$$$$D$N(B encapsulation $B$rCN$i(B
|
|
|
1075 $B$J$1$l$P$J$i$J$$!#$^$?!"(Bapplication/pgp part $B$r(B parse $B$9$k$?$a$K$O!"$^(B
|
|
|
1076 $B$:!"(Bpgp $B$N=hM}$r9T$o$J$1$l$P$J$i$J$$$N$G!"(Bparse $B=hM}$,J#;($K$J$k!#(B
|
|
|
1077 <p>
|
|
|
1078 $B$^$?!"(BInternet $B$G$O:#8e(B <dref>PGP/MIME</dref> $B$NJ}8~$GI8=`2=$7$F$$$3$&(B
|
|
|
1079 $B$H$$$&$3$H$G9g0U$,<h$l$F$$$k!#$h$C$F!":#8e$O(B PGP-kazu $B$OMQ$$$J$$$N$,K>(B
|
|
|
1080 $B$^$7$$!#(B
|
|
|
1081 <p>
|
|
|
1082 [draft-kazu-pgp-mime-00.txt] Yamamoto K., ``PGP MIME Integration'',
|
|
|
1083 October, 1995
|
|
|
1084
|
|
|
1085
|
|
|
1086 <h3> PGP/MIME
|
|
|
1087 <node> PGP/MIME
|
|
|
1088 <p>
|
|
|
1089 Michael Elkins $B;a$,Ds0F$7$?(B <a node="MIME">MIME</a> $B$G(B <a
|
|
|
1090 node="PGP">PGP</a> $B$rMxMQ$9$k$?$a$NJ}K!!#(B
|
|
|
1091 <p>
|
|
|
1092 <a node="Security multipart">RFC 1847</a> $B$K4p$-!"(BMIME $B$N(B multipart $B$K(B
|
|
|
1093 $B$h$k(B <dref>encapsulation</dref> $B$r9T$&!#$3$N$?$a!"(BMIME $B$N<+A3$J3HD%$K(B
|
|
|
1094 $B$J$C$F$$$k!#$7$+$7!"EAE}E*$J(B PGP$B$H$N8_49@-$,<:$o$l$F$$$k!#(B
|
|
|
1095 <p>
|
|
|
1096 PGP/MIME $B$G$O(B <dref>PGP-kazu</dref> $B$H0[$J$j!"(BMIME $B$N(B encapsulation $B$N(B
|
|
|
1097 $B$_$rMQ$$$k!#$^$?!"$3$N$?$a!"(BPGP $B$N=hM}$r9T$&A0$K(B message $B$N(B parse $B$r9T(B
|
|
|
1098 $B$&$3$H$,$G$-$k!#(B
|
|
|
1099 <p>
|
|
|
1100 Internet $B$G$O:#8e(B <dref>PGP/MIME</dref> $B$NJ}8~$GI8=`2=$7$F$$$3$&$H$$$&(B
|
|
|
1101 $B$3$H$G9g0U$,<h$l$F$$$k!#$h$C$F!":#8e$O(B PGP $B$rMQ$$$k>l9g$O(B PGP/MIME$B$rMQ(B
|
|
|
1102 $B$$$k$N$,K>$^$7$$!#(B
|
|
|
1103
|
|
|
1104 <rfc name="PGP/MIME" number="2015" type="Standards Track"
|
|
|
1105 author="M. Elkins" title="MIME Security with Pretty Good
|
|
|
1106 Privacy (PGP)" date="October 1996">
|
|
|
1107
|
|
|
1108
|
|
|
1109 <h3> Quoted-Printable
|
|
|
1110 <node> Quoted-Printable
|
|
|
1111 <p>
|
|
|
1112 <concept>Quoted-Printable</concept> is a transfer encoding method of
|
|
|
1113 <dref>MIME</dref> defined in <dref>RFC 2045</dref>.
|
|
|
1114 <p>
|
|
|
1115 If the data being encoded are mostly US-ASCII text, the encoded form
|
|
|
1116 of the data remains largely recognizable by humans.
|
|
|
1117 <p>
|
|
|
1118 <cf node="Base64">
|
|
|
1119
|
|
|
1120
|
|
|
1121 <h3> RFC 821
|
|
|
1122 <node> RFC 821
|
|
|
1123 <p>
|
|
|
1124 <concept>SMTP</concept> $B$H8F$P$l$k(B Internet mail $B$NG[AwK!$NI8=`$rDj$a(B
|
|
|
1125 $B$F$$$k(B RFC.
|
|
|
1126
|
|
|
1127 <rfc name="SMTP" number="821" type="STD 10" author="J. Postel"
|
|
|
1128 title="Simple Mail Transfer Protocol" date="August
|
|
|
1129 1982">
|
|
|
1130
|
|
|
1131
|
|
|
1132 <h3> RFC 822
|
|
|
1133 <node> RFC 822
|
|
|
1134 <p>
|
|
|
1135 Internet mail $B$N<g$K(B <concept>message header</concept> $B$K4X$9$k7A<0$K(B
|
|
|
1136 $B4X$9$kI8=`$rDj$a$F$$$k(B RFC.
|
|
|
1137
|
|
|
1138 <memo>
|
|
|
1139 <p>
|
|
|
1140 news message $B$b$3$l$K=`$8$F$$$k$N$G!"(B<concept>Internet mail</concept>
|
|
|
1141 $B$H=q$/$h$j$b!"(B<concept>Internet message</concept> $B$H=q$$$?J}$,NI$$$+$b(B
|
|
|
1142 $B$7$l$J$$!#(B
|
|
|
1143 </memo>
|
|
|
1144
|
|
|
1145 <rfc number="822" type="STD 11" author="D. Crocker" title="Standard
|
|
|
1146 for the Format of ARPA Internet Text Messages"
|
|
|
1147 date="August 1982">
|
|
|
1148
|
|
|
1149
|
|
|
1150 <h3> RFC 934
|
|
|
1151 <node> RFC 934
|
|
|
1152 <p>
|
|
|
1153 <a node="RFC 822">Internet mail</a> $B$N(B <a node="encapsulation">
|
|
|
1154 <concept>encapsulation</concept></a> $B$NJ}K!$rDj$a$?(B RFC.
|
|
|
1155 <p>
|
|
|
1156 <dref>MIME</dref> $B$HL7=b$9$k$N$G!"8=:_$G$O(B <dref>message/rfc822</dref>
|
|
|
1157 $B$rMQ$$$k$Y$-$G$"$k!#(B
|
|
|
1158
|
|
|
1159
|
|
|
1160 <rfc number="934" author="Marshall T. Rose and Einar A. Stefferud"
|
|
|
1161 title="Proposed Standard for Message Encapsulation"
|
|
|
1162 date="January 1985">
|
|
|
1163
|
|
|
1164
|
|
|
1165 <h3> RFC 1036
|
|
|
1166 <node> RFC 1036
|
|
|
1167 <p>
|
|
|
1168 USENET $B$G$N(B message $B$N7A<0$rDj$a$?(B RFC. <a node="RFC 822">RFC 822</a>
|
|
|
1169 $B$N(B subset $B$K$J$C$F$$$k!#(BInternet $B$NI8=`$G$O$J$$$,!"(BUSENET $B0J30$N(B
|
|
|
1170 netnews $B$G$b$3$l$K=`$8$F$$$k$b$N$,B?$$!#(B
|
|
|
1171
|
|
|
1172 <rfc name="USENET" number="1036" author="M. Horton and R. Adams"
|
|
|
1173 title="Standard for Interchange of USENET Messages"
|
|
|
1174 date="December 1987" obsolete="850">
|
|
|
1175
|
|
|
1176
|
|
|
1177 <h3> RFC 1153
|
|
|
1178 <node> RFC 1153
|
|
|
1179 <p>
|
|
|
1180 $BJ#?t$N(B <a node="RFC 822">Internet mail</a> $B$r(B <a node="encapsulation">
|
|
|
1181 <concept>encapsulation</concept></a> $B$9$k$?$a$NJ}K!$rDj$a$?(B
|
|
|
1182 RFC. <dref>RFC 934</dref> $B$rMQ$$$k!#(B
|
|
|
1183 <p>
|
|
|
1184 <dref>MIME</dref> $B$HL7=b$9$k$N$G!"8=:_$G$O(B <dref>message/rfc822</dref>
|
|
|
1185 $B$rMQ$$$?(B <dref>multipart</dref> $B$rMQ$$$k$Y$-$G$"$k!#(B
|
|
|
1186 <p>
|
|
|
1187 <cf node="multipart/digest">
|
|
|
1188
|
|
|
1189 <rfc number="1153" author="F. Wancho" title="Digest Message Format"
|
|
|
1190 date="April 1990">
|
|
|
1191
|
|
|
1192
|
|
|
1193 <h3> RFC 1557
|
|
|
1194 <node> RFC 1557
|
|
|
1195 <p>
|
|
|
1196 <dref>euc-kr</dref> $B$H(B <dref>iso-2022-kr</dref> $B$H$$$&4Z9q8l$N$?$a$N(B
|
|
|
1197 <a node="MIME charset">MIME charset</a> $B$rDj5A$7$F$$$k(B RFC.
|
|
|
1198
|
|
|
1199 <rfc number="1557" type="Informational" author="U. Choi, K. Chon and
|
|
|
1200 H. Park" title="Korean Character Encoding for Internet
|
|
|
1201 Messages" date="December 1993">
|
|
|
1202
|
|
|
1203
|
|
|
1204 <h3> RFC 1922
|
|
|
1205 <node> RFC 1922
|
|
|
1206 <p>
|
|
|
1207 <dref>iso-2022-cn</dref>, <dref>iso-2022-cn-ext</dref>,
|
|
|
1208 <dref>cn-gb</dref>, <dref>cn-big5</dref> $B$H$$$C$?Cf9q8l$N$?$a$N(B <a
|
|
|
1209 node="MIME charset">MIME charset</a> $B$rDj5A$7$F$$$k(B RFC.
|
|
|
1210 <p>
|
|
|
1211 $B$3$l$K2C$($F!"(B<concept>charset-edition</concept> $B$H(B
|
|
|
1212 <concept>charset-extension</concept> $B$H$$$&(B <dref>Content-Type
|
|
|
1213 field</dref> $B$N(B parameter $B$rDj5A$7$F$$$k!#(B
|
|
|
1214
|
|
|
1215 <rfc number="1922" type="Informational" author="Zhu, HF., Hu, DY.,
|
|
|
1216 Wang, ZG., Kao, TC., Chang, WCH. and Crispin, M."
|
|
|
1217 title="Chinese Character Encoding for Internet Messages"
|
|
|
1218 date="March 1996">
|
|
|
1219
|
|
|
1220
|
|
|
1221 <h3> RFC 2045
|
|
|
1222 <node> RFC 2045
|
|
|
1223 <p>
|
|
|
1224 <rfc number="2045" type="Standards Track" author="N. Freed and
|
|
|
1225 N. Borenstein" title="Multipurpose Internet Mail
|
|
|
1226 Extensions (MIME) Part One: Format of Internet Message
|
|
|
1227 Bodies" date="November 1996" obsolete="1521, 1522,
|
|
|
1228 1590">
|
|
|
1229
|
|
|
1230
|
|
|
1231 <h3> RFC 2046
|
|
|
1232 <node> RFC 2046
|
|
|
1233 <p>
|
|
|
1234 <rfc number="2046" type="Standards Track" author="N. Freed and
|
|
|
1235 N. Borenstein" title="Multipurpose Internet Mail
|
|
|
1236 Extensions (MIME) Part Two: Media Types"
|
|
|
1237 date="November 1996" obsolete="1521, 1522, 1590">
|
|
|
1238
|
|
|
1239
|
|
|
1240 <h3> RFC 2048
|
|
|
1241 <node> RFC 2048
|
|
|
1242 <p>
|
|
|
1243 <rfc number="2048" type="Standards Track" author="N. Freed, J. Klensin
|
|
|
1244 and J. Postel" title="Multipurpose Internet Mail
|
|
|
1245 Extensions (MIME) Part Four: Registration Procedures"
|
|
|
1246 date="November 1996" obsolete="1521, 1522, 1590">
|
|
|
1247
|
|
|
1248
|
|
|
1249 <h3> RFC 2049
|
|
|
1250 <node> RFC 2049
|
|
|
1251 <p>
|
|
|
1252 <rfc number="2049" type="Standards Track" author="N. Freed and
|
|
|
1253 N. Borenstein" title="Multipurpose Internet Mail
|
|
|
1254 Extensions (MIME) Part Five: Conformance Criteria and
|
|
|
1255 Examples" date="November 1996" obsolete="1521, 1522,
|
|
|
1256 1590">
|
|
|
1257
|
|
|
1258
|
|
|
1259 <h3> plain text
|
|
|
1260 <node> plain text
|
|
|
1261 <p>
|
|
|
1262 $B=qBN$dAHHG$K4X$9$k>pJs$r;}$?$J$$(B <a node="Coded character set">$BJ8;zId(B
|
|
|
1263 $B9f(B</a>$B$N$_$GI=8=$5$l$k(B text $B>pJs!#(B<cf node="text/plain">
|
|
|
1264
|
|
|
1265
|
|
|
1266 <h3> Security multipart
|
|
|
1267 <node> Security multipart
|
|
|
1268 <p>
|
|
|
1269 <a node="MIME">MIME</a> $B$G0E9f$dEE;R=qL>$rMQ$$$k$?$a$N7A<0!#(B<a
|
|
|
1270 node="multipart/signed"><concept>multipart/signed</concept></a> $B$H(B <a
|
|
|
1271 node="multipart/encrypted"><concept>multipart/encrypted</concept></a>
|
|
|
1272 $B$H$$$&(B multipart $B$rMQ$$$k!#(BMOSS $B$d(B <a node="PGP/MIME">PGP/MIME</a> $B$O(B
|
|
|
1273 $B$3$l$K4p$$$F$$$k!#(B
|
|
|
1274
|
|
|
1275 <rfc name="Security multipart" number="1847" type="Standards Track"
|
|
|
1276 author="James Galvin, Gale Murphy, Steve Crocker and Ned
|
|
|
1277 Freed" title="Security Multiparts for MIME:
|
|
|
1278 Multipart/Signed and Multipart/Encrypted" date="October
|
|
|
1279 1995">
|
|
|
1280
|
|
|
1281
|
|
|
1282 <h3> text/enriched
|
|
|
1283 <node> text/enriched
|
|
|
1284 <p>
|
|
|
1285 RFC 1521 $B$GDj5A$5$l$?(B <concept>text/richtext</concept> $B$KBe$o$C$F!"=q(B
|
|
|
1286 $BBN$dAHHG$K4X$9$k>pJs$r;}$C$?(B text$B$rI=8=$9$k$?$a$N(B <dref>media
|
|
|
1287 type</dref>.
|
|
|
1288
|
|
|
1289 <rfc name="text/enriched" number="1896" author="P. Resnick and
|
|
|
1290 A. Walker" title="The text/enriched MIME Content-type"
|
|
|
1291 date="February 1996" obsolete="1563">
|
|
|
1292
|
|
|
1293
|
|
|
1294 <h3> text/plain
|
|
|
1295 <node> text/plain
|
|
|
1296 <p>
|
|
|
1297 <concept>text/plain</concept> is a <dref>media type</dref> for
|
|
|
1298 <dref>plain text</dref>, defined in <dref>RFC 2046</dref>.
|
|
|
1299 <p>
|
|
|
1300 The default media type of ``text/plain; charset=us-ascii'' for
|
|
|
1301 Internet mail describes existing Internet practice. That is, it is
|
|
|
1302 the type of body defined by <dref>RFC 822</dref>.
|
|
|
1303 <p>
|
|
|
1304 <cf node="MIME charset"><cf node="us-ascii">
|
|
|
1305
|
|
|
1306
|
|
|
1307 <h3> tm-kernel, tm
|
|
|
1308 <node> tm-kernel
|
|
|
1309 <p>
|
|
|
1310 Emacs $B$G(B <a node="MIME">MIME</a> $B$rMxMQ$9$k$?$a$N(B user interface $B$rDs(B
|
|
|
1311 $B6!$9$k(B library $B72!#(B`tools for MIME' $B$NN,!#(B
|
|
|
1312
|
|
|
1313 <memo title="$B$I$&$G$bNI$$$3$H(B(^-^;">
|
|
|
1314 <p>
|
|
|
1315 <ul>
|
|
|
1316 <li> tm $B$O(B ``tiny-mime'' $B$NN,$8$c$J$$$i$7$$$>(B (^-^;
|
|
|
1317 <li> tm $B$O:n<T$N%$%K%7%c%k$8$c$J$$$i$7$$$>(B (^-^;
|
|
|
1318 <li> ``Tools for MIME'' $B$NN,$H$$$&$N$O$3$8$D$1$i$7$$$>(B (^-^;
|
|
|
1319 </ul>
|
|
|
1320 </memo>
|
|
|
1321
|
|
|
1322
|
|
|
1323 <h3> tm-MUA
|
|
|
1324 <node> tm-MUA
|
|
|
1325 <p>
|
|
|
1326 <a node="tm-kernel">tm</a> $B$rMQ$$$?(B <a node="MUA">MUA</a> $B$b$7$/$O(B MUA
|
|
|
1327 $B$KBP$9$k(B extender.
|
|
|
1328 <p>
|
|
|
1329 <concept>tm $BBg@9$j(B package</concept> $B$K$O(B
|
|
|
1330
|
|
|
1331 <ul>
|
|
|
1332 <li><a file="mh-e">mh-e</a> $BMQ$N(B <concept>tm-mh-e</concept>
|
|
|
1333 <li>GNUS $BMQ$N(B <concept>tm-gnus</concept>
|
|
|
1334 <li>Gnus $BMQ$N(B <a file="gnus-mime-en"><concept>gnus-mime</concept></a>
|
|
|
1335 <li>VM $BMQ$N(B <concept>tm-vm</concept>
|
|
|
1336 <li>RMAIL $BMQ$N(B <concept>tm-rmail</concept>
|
|
|
1337 </ul>
|
|
|
1338
|
|
|
1339 <noindent>
|
|
|
1340 $B$,4^$^$l$F$$$k!#(B
|
|
|
1341 <p>
|
|
|
1342 $BFHN)$7$?(B MUA $B$H$7$F$O(B <a file="cmail">cmail</a> $B$,(B tm $B$rMxMQ2DG=$G$"$k!#(B
|
|
|
1343
|
|
|
1344
|
|
|
1345 <h3> us-ascii
|
|
|
1346 <node> us-ascii
|
|
|
1347 <p>
|
|
|
1348 $B%"%a%j%+O"K.$J$I$G;H$o$l$k1Q8l$J$I$rI=8=$9$k$?$a$N(B <a node="MIME
|
|
|
1349 charset">MIME charset</a> $B$N#1$D!#(B
|
|
|
1350 <p>
|
|
|
1351 <dref>ASCII</dref> $B$N$_$+$i$J$j(B <dref>ISO 2022</dref> $B$K$h$k(B<a
|
|
|
1352 node="Code extension">$BId9f3HD%(B</a>$B$O5v$5$l$J$$!#(B
|
|
|
1353 <p>
|
|
|
1354 Internet mail $B$K$*$1$kI8=`$N(B<a node="Coded character set">$BId9f2=J8;z=8(B
|
|
|
1355 $B9g(B</a>$B$G$"$j!"L@<(E*$K(B MIME charset $B$,<($5$l$J$$>l9g$O86B'$H$7$F(B
|
|
|
1356 <concept>us-ascii</concept> $B$,;H$o$l$k!#(B
|
|
|
1357 <p>
|
|
|
1358 $B$^$?!"(B<a node="RFC 822">RFC 822</a> $B$K$*$1$k(B <concept>ASCII</concept>
|
|
|
1359 $B$O(B us-ascii $B$r;X$9$b$N$H2r<a$9$Y$-$G$"$k!#(B
|
|
|
1360
|
|
|
1361
|
|
|
1362 <h1> Setting
|
|
|
1363 <node> Setting
|
|
|
1364 <p>
|
|
|
1365 In the tm package, two files, <file>mime-setup.el</file> and
|
|
|
1366 <file>tm-setup.el</file>, are provided to ease the setup.
|
|
|
1367 <p>
|
|
|
1368 The <file>mime-setup.el</file> is used for the whole MIME related
|
|
|
1369 setup including MIME encoding using <file>tm-edit.el</file>, while
|
|
|
1370 <file>tm-setup.el</file> is used to set up tm-MUA only.
|
|
|
1371
|
|
|
1372
|
|
|
1373 <h2> Normal setting
|
|
|
1374 <node> mime-setup
|
|
|
1375 <p>
|
|
|
1376 If you want normal setting, please use <concept>mime-setup</concept>.
|
|
|
1377 For example, please insert following into <file>~/.emacs</file>:
|
|
|
1378
|
|
|
1379 <lisp>
|
|
|
1380 (load "mime-setup")
|
|
|
1381 </lisp>
|
|
|
1382
|
|
|
1383 <p>
|
|
|
1384 As <file>mime-setup.el</file> loads <file>tm-setup.el</file>, you
|
|
|
1385 don't need to load <file>tm-setup.el</file> when you use
|
|
|
1386 <file>mime-setup.el</file> (Description of old version of Gnus FAQ is
|
|
|
1387 wrong!)
|
|
|
1388
|
|
|
1389
|
|
|
1390 <h3> signature
|
|
|
1391 <node> signature
|
|
|
1392 <p>
|
|
|
1393 You can set up the <concept>automatic signature selection
|
|
|
1394 tool</concept> using <file>mime-setup</file>. If you want to
|
|
|
1395 automatically select the signature file depending on how the message
|
|
|
1396 headers show, add lines like shown below to your .emacs (Refer to the
|
|
|
1397 reference manual of <file>signature.el</file> for more details).
|
|
|
1398
|
|
|
1399 <lisp>
|
|
|
1400 (setq signature-file-alist
|
|
|
1401 '((("Newsgroups" . "jokes") . "~/.signature-jokes")
|
|
|
1402 (("Newsgroups" . ("zxr" "nzr")) . "~/.signature-sun")
|
|
|
1403 (("To" . ("ishimaru" "z-suzuki")) . "~/.signature-sun")
|
|
|
1404 (("To" . "tea") . "~/.signature-jokes")
|
|
|
1405 (("To" . ("sim" "oku" "takuo")) . "~/.signature-formal")
|
|
|
1406 ))
|
|
|
1407 </lisp>
|
|
|
1408
|
|
|
1409
|
|
|
1410 <defvar name="mime-setup-use-signature">
|
|
|
1411 <p>
|
|
|
1412 If it is not <code>nil</code>, <file>mime-setup.el</file> sets up for
|
|
|
1413 <file>signature.el</file>. Its default value is <code>t</code>.
|
|
|
1414 </defvar>
|
|
|
1415
|
|
|
1416
|
|
|
1417 <defvar name="mime-setup-signature-key-alist">
|
|
|
1418 <p>
|
|
|
1419 It defines key to bind signature inserting command for each
|
|
|
1420 major-mode. Its default value is following:
|
|
|
1421
|
|
|
1422 <lisp>
|
|
|
1423 ((mail-mode . "\C-c\C-w"))
|
|
|
1424 </lisp>
|
|
|
1425
|
|
|
1426 <p>
|
|
|
1427 If you want to change, please rewrite it. For example:
|
|
|
1428
|
|
|
1429 <lisp>
|
|
|
1430 (set-alist 'mime-setup-signature-key-alist
|
|
|
1431 'news-reply-mode "\C-c\C-w")
|
|
|
1432 </lisp>
|
|
|
1433
|
|
|
1434 </defvar>
|
|
|
1435
|
|
|
1436
|
|
|
1437 <defvar name="mime-setup-default-signature-key">
|
|
|
1438 <p>
|
|
|
1439 If key to bind signature inserting command for a major-mode is not
|
|
|
1440 found from <code>mime-setup-signature-key-alist</code>, its value is
|
|
|
1441 used as key. Its default value is <code>"\C-c\C-s"</code>.
|
|
|
1442 </defvar>
|
|
|
1443
|
|
|
1444
|
|
|
1445 <h3> Notices for GNUS
|
|
|
1446 <node> Notice about GNUS
|
|
|
1447 <p>
|
|
|
1448 When <file>mime-setup.el</file> sets up for <file>signature.el</file>,
|
|
|
1449 it sets variable <code>gnus-signature-file</code> to <code>nil</code>.
|
|
|
1450 Therefore GNUS does not insert signature automatically when it is
|
|
|
1451 sending a message. Reason of this setting is following:
|
|
|
1452 <p>
|
|
|
1453 GNUS inserts signature after <file>tm-edit.el</file> composed as MIME
|
|
|
1454 message. Therefore signature inserted by GNUS is not processed as a
|
|
|
1455 valid MIME part. In particular, for multipart message, signature
|
|
|
1456 places in outside of MIME part. So MIME MUA might not display it.
|
|
|
1457 <p>
|
|
|
1458 Other notice is key bind. In historical reason, key bind to insert
|
|
|
1459 signature is <kbd>C-c C-s</kbd> (like <a file="mh-e">mh-e</a>) instead
|
|
|
1460 of <kbd>C-c C-w</kbd>. If you change to GNUS's default, please set
|
|
|
1461 following:
|
|
|
1462
|
|
|
1463 <lisp>
|
|
|
1464 (set-alist 'mime-setup-signature-key-alist 'news-reply-mode "\C-c\C-w")
|
|
|
1465 </lisp>
|
|
|
1466
|
|
|
1467
|
|
|
1468 <h2> Setting not to use tm-edit
|
|
|
1469 <node> tm-setup
|
|
|
1470 <p>
|
|
|
1471 <concept>tm-setup</concept> only sets up <a node="tm-MUA">tm-MUA</a>s.
|
|
|
1472 In other words, it is a setting to avoid to use tm-edit. If you don't
|
|
|
1473 want to compose MIME message or want to use other MIME composer,
|
|
|
1474 please use it instead of <file>mime-setup.el</file>.
|
|
|
1475 <p>
|
|
|
1476 For example, please insert following into <file>~/.emacs</file>:
|
|
|
1477
|
|
|
1478 <lisp>
|
|
|
1479 (load "tm-setup")
|
|
|
1480 </lisp>
|
|
|
1481
|
|
|
1482 <p>
|
|
|
1483
|
|
|
1484 <memo>
|
|
|
1485 <p>
|
|
|
1486 If you use <file>mime-setup.el</file>, you you don't need to load
|
|
|
1487 <file>tm-setup.el</file>.
|
|
|
1488 </memo>
|
|
|
1489
|
|
|
1490
|
|
|
1491 <h2> Setting for VM
|
|
|
1492 <node> setting for VM
|
|
|
1493 <p>
|
|
|
1494 If you use <concept>vm</concept>, please insert following in
|
|
|
1495 <file>~/.vm</file>:
|
|
|
1496
|
|
|
1497 <lisp>
|
|
|
1498 (require 'tm-vm)
|
|
|
1499 </lisp>
|
|
|
1500
|
|
|
1501
|
|
|
1502 <memo title="Notice">
|
|
|
1503 <p>
|
|
|
1504 If you use <concept>BBDB</concept>, please insert <code>(require
|
|
|
1505 'tm-vm)</code> <bf>after</bf> <code>(bbdb-insinuate-vm)</code>.
|
|
|
1506 </memo>
|
|
|
1507
|
|
|
1508
|
|
|
1509 <h2> Setting up without loading provided setup files
|
|
|
1510 <node> manual setting
|
|
|
1511 <p>
|
|
|
1512 You may find the valuable hints in <file>mime-setup.el</file> or
|
|
|
1513 <file>tm-setup.el</file> if you want to set up MIME environment
|
|
|
1514 without loading the tm-provided setup files.
|
|
|
1515
|
|
|
1516 <memo>
|
|
|
1517 <p>
|
|
|
1518 Current tm provides some convenient features to expect tm-edit, and
|
|
|
1519 they can not use if <file>mime-setup.el</file> is not used. If you
|
|
|
1520 want to set up original setting to use tm-edit, please declare
|
|
|
1521 following setting:
|
|
|
1522
|
|
|
1523 <lisp>
|
|
|
1524 (provide 'mime-setup)
|
|
|
1525 </lisp>
|
|
|
1526
|
|
|
1527 </memo>
|
|
|
1528
|
|
|
1529
|
|
|
1530 <h1> How to report bug and about mailing list of tm
|
|
|
1531 <node> Bug report
|
|
|
1532 <p>
|
|
|
1533 If you write bug-reports and/or suggestions for improvement, please
|
|
|
1534 send them to the tm Mailing List:
|
|
|
1535
|
|
|
1536 <ul>
|
|
|
1537 <li> Japanese <mail>bug-tm-ja@chamonix.jaist.ac.jp</mail>
|
|
|
1538 <li> English <mail>bug-tm-en@chamonix.jaist.ac.jp</mail>
|
|
|
1539 </ul>
|
|
|
1540
|
|
|
1541 <p>
|
|
|
1542 Notice that, we does not welcome bug reports about too old version.
|
|
|
1543 Bugs in old version might be fixed. So please try latest version at
|
|
|
1544 first.
|
|
|
1545 <p>
|
|
|
1546 You should write <concept>good bug report</concept>. If you write
|
|
|
1547 only ``tm does not work'', we can not find such situations. At least,
|
|
|
1548 you should write name, type, variants and version of OS, emacs, tm and
|
|
|
1549 MUA, and setting. In addition, if error occurs, to send backtrace is
|
|
|
1550 very important. <cf file="emacs" node="Bugs">
|
|
|
1551 <p>
|
|
|
1552 Bug may not appear only your environment, but also in a lot of
|
|
|
1553 environment (otherwise it might not bug). Therefor if you send mail
|
|
|
1554 to author directly, we must write a lot of mails. So please send mail
|
|
|
1555 to address for tm bugs instead of author.
|
|
|
1556 <p>
|
|
|
1557 Via the tm ML, you can report tm bugs, obtain the latest release of
|
|
|
1558 tm, and discuss future enhancements to tm. To join the tm ML, send
|
|
|
1559 e-mail to:
|
|
|
1560
|
|
|
1561 <ul>
|
|
|
1562 <li> Japanese <mail>tm-ja-admin@chamonix.jaist.ac.jp</mail>
|
|
|
1563 <li> English <mail>tm-en-admin@chamonix.jaist.ac.jp</mail>
|
|
|
1564 </ul>
|
|
|
1565
|
|
|
1566 <noindent>
|
|
|
1567 Since the user registration is done manually, please write the mail
|
|
|
1568 body in human-recognizable language (^_^).
|
|
|
1569
|
|
|
1570
|
|
|
1571 <h1> Concept Index
|
|
|
1572 <node> Concept Index
|
|
|
1573
|
|
|
1574 <cindex>
|
|
|
1575
|
|
|
1576
|
|
|
1577 <h1> Variable Index
|
|
|
1578 <node> Variable Index
|
|
|
1579
|
|
|
1580 <vindex>
|
|
|
1581
|
|
|
1582 </body>
|
