Mercurial > hg > xemacs-beta

comparison man/tm/tm-en.sgml @ 76:c0c698873ce1 r20-0b33

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r20-0b33
author cvs
date Mon, 13 Aug 2007 09:05:10 +0200
parents 54cc21c15cbb
children 364816949b59
comparison
equal deleted inserted replaced
75:a4e0195b387b 76:c0c698873ce1
1 <!doctype sinfo system> 1 <!doctype sinfo system>
2 <!-- $Id: tm-en.sgml,v 1.1.1.1 1996/12/21 20:51:39 steve Exp $ --> 2 <!-- $Id: tm-en.sgml,v 1.2 1996/12/28 21:03:29 steve Exp $ -->
3 <head> 3 <head>
4 <title>tm 7.90 Manual (English Version) 4 <title>tm 7.100 Manual (English Version)
5 <author>MORIOKA Tomohiko <mail>morioka@jaist.ac.jp</mail> 5 <author>MORIOKA Tomohiko <mail>morioka@jaist.ac.jp</mail>
6 <date>1996/10/15 6 <date>1996/12/25
7 7
8 <toc> 8 <toc>
9 </head> 9 </head>
10 10
11 <body> 11 <body>
18 <h1> What is tm? 18 <h1> What is tm?
19 <node> Introduction 19 <node> Introduction
20 <p> 20 <p>
21 The tm package is a set of modules to enjoy MIME on GNU Emacs. Using 21 The tm package is a set of modules to enjoy MIME on GNU Emacs. Using
22 tm, you can 22 tm, you can
23 23 <p>
24 <ul> 24 <ul>
25 <li> playback or view the MIME messages using tm-view 25 <li> playback or view the MIME messages using tm-view
26 <li> compose MIME message using tm-edit 26 <li> compose MIME message using tm-edit
27 <li> use the enhanced MIME features with mh-e, GNUS, Gnus, RMAIL and VM 27 <li> use the enhanced MIME features with mh-e, GNUS, Gnus, RMAIL and VM
28 </ul> 28 </ul>
126 126
127 127
128 <h3> ASCII 128 <h3> ASCII
129 <node> ASCII 129 <node> ASCII
130 <p> 130 <p>
131 $B%"%a%j%+O"K.$G;H$o$l$kJ8;z$rId9f2=$7$?(B <dref>94-character set</dref>. 131 <concept>ASCII</concept> is a <dref>94-character set</dref> contains
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 132 primary latin characters (A-Z, a-z), numbers and some characters. It
133 646">ISO 646</a> $B$N0l$D!#(B 133 is a standard of the United States of America. It is a variant of <a
134 node="ISO 646">ISO 646</a>.
134 135
135 <standard abbrev="ASCII" title-en="Coded Character Set -- 7-Bit 136 <standard abbrev="ASCII" title-en="Coded Character Set -- 7-Bit
136 American Standard Code for Information Interchange" 137 American Standard Code for Information Interchange"
137 number="ANSI X3.4" year="1986"> 138 number="ANSI X3.4" year="1986">
138 139
154 155
155 156
156 <h3> binary 157 <h3> binary
157 <node> binary 158 <node> binary
158 <p> 159 <p>
159 $BG$0U$N(B byte $BNs$r(B <concept>binary</concept> $B$H8F$V$3$H$K$7$^$9!#(B 160 Any byte stream is called <concept>binary</concept>.
160 <p> 161 <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 It does not require structureof lines. It differs from from <a
162 $B$9!#(B 163 node="8bit">8bit</a>.
163 <p> 164 <p>
164 $B$^$?!"9T$N9=B$$,$"$C$F$b!"(B999 byte $B0J>e$+$i$J$k9T$,$"$k>l9g$b(B binary 165 In addition, if line structured data contain too long line (more than
165 $B$H8F$V$3$H$K$7$^$9!#(B 166 998 bytes), it is regarded as binary.
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 167
177 168
178 <h3> cn-gb, gb2312 169 <h3> cn-gb, gb2312
179 <node> cn-gb 170 <node> cn-gb
180 <p> 171 <p>
181 $BCf9qBgN&$G$i$l$F$$$k4JBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B <a 172 A <a node="MIME charset">MIME charset</a> for simplified Chinese
182 node="MIME charset">MIME charset</a> $B$N#1$D!#(B 173 mainly used in the Chinese mainland.
183 <p> 174 <p>
184 <dref>ISO 2022</dref> $B$K4p$$$F(B <dref>ASCII</dref> $B$K(B <dref>GB 175 It is a <dref>8bit</dref> <dref>coded character set</dref> based on
185 2312</dref> $B$r(B <dref>8bit</dref> $B$G(B<a node="Code extension">$BId9f(B 176 <dref>ISO 2022</dref>. It extends <dref>ASCII</dref> to combine
186 $B3HD%(B</a>$B$7$F$$$k!#(B 177 <dref>GB 2312</dref>.
187 <p> 178 <p>
188 <a node="RFC 1922">RFC 1922</a> $B$GDj5A$5$l$F$$$k!#(B 179 It is defined in <a node="RFC 1922">RFC 1922</a>.
189 180
190 181
191 <h3> cn-big5, big5 182 <h3> cn-big5, big5
192 <node> cn-big5 183 <node> cn-big5
193 <p> 184 <p>
194 $BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B 185 A <a node="MIME charset">MIME charset</a> for traditional Chinese
195 <a node="MIME charset">MIME charset</a> $B$N#1$D!#(B 186 mainly used in Taiwan and Hon Kong.
196 <p> 187 <p>
197 <dref>ISO 2022</dref> $B$K4p$+$J$$(B <dref>8bit</dref> $B$N(B 188 It is a <dref>8bit</dref> <dref>coded character set</dref> not based
198 <dref>coded character set</dref>$B$G(B de-fact standard $B$G(B 189 on <dref>ISO 2022</dref>. It is a de-fact standard.
199 $B$"$k!#(B<a node="RFC 1922">RFC 1922</a> $B$GDj5A$5$l$F$$$k!#(B 190 <p>
191 It is defined in <a node="RFC 1922">RFC 1922</a>.
200 <p> 192 <p>
201 cf. <report abbrev="BIG5" author="Institute for Information Industry" 193 cf. <report abbrev="BIG5" author="Institute for Information Industry"
202 title-en="Chinese Coded Character Set in Computer" 194 title-en="Chinese Coded Character Set in Computer"
203 date="March 1984"> 195 date="March 1984">
204 <p> 196 <p>
205 <a node="CNS">CNS 11643-1986</a> $B$HBP1~4X78$,$"$k!#(B 197 It corresponds to <dref>CNS 11643</dref>.
206 198
207 199
208 <h3> CNS 11643-1992 200 <h3> CNS 11643-1992
209 <node> CNS 201 <node> CNS 11643
210 <p> 202 <p>
211 $BBfOQ$d9a9A$GMQ$$$i$l$F$$$k<g$KHKBN;z$GI=5-$5$l$kCf9q8l$rI=8=$9$k$?$a$N(B 203 <a node="graphic character set">Graphic character sets</a> for Chinese
212 <a node="Character set">$BJ8;z=89g(B</a>$B!#BfOQ$NI8=`!#8=:_!"(B<a node="94x94 204 mainly written by traditional Chinese mainly used in Taiwan and Hong
213 character set">94$B!_(B94</a> $B$NLL$,Bh#1LL$+$iBh#7LL$^$G$"$k!#(B 205 Kong. It is a standard of Taiwan. Currently there are seven
214 <p> 206 <dref>94x94-character set</dref>.
215 <dref>ISO 2022</dref> $B$G$N=*C<J8;z$O!"Bh#1LL$,(B `G', $BBh#2LL$,(B 207 <p>
216 `H', $BBh#3LL$,(B `I', $BBh#4LL$,(B `J', $BBh#5LL$,(B `K', $BBh#6LL$,(B `L', $BBh#7LL$,(B 208 Final byte of <dref>ISO 2022</dref> are following:
217 `M' $B$G$"$k!#(B 209
210 <dl>
211 <dt>plane 1<dd>04/07 (`G')
212 <dt>plane 2<dd>04/08 (`H')
213 <dt>plane 3<dd>04/09 (`I')
214 <dt>plane 4<dd>04/10 (`J')
215 <dt>plane 5<dd>04/11 (`K')
216 <dt>plane 6<dd>04/12 (`L')
217 <dt>plane 7<dd>04/13 (`M')
218 </dl>
218 219
219 <standard abbrev="CNS 11643-1992" title-en="Standard Interchange Code 220 <standard abbrev="CNS 11643-1992" title-en="Standard Interchange Code
220 for Generally-Used Chinese Characters" number="CNS 221 for Generally-Used Chinese Characters" number="CNS
221 11643" year="1992"> 222 11643" year="1992">
222 223
237 238
238 239
239 <h3> Content-Disposition field 240 <h3> Content-Disposition field
240 <node> Content-Disposition 241 <node> Content-Disposition
241 <p> 242 <p>
242 Content $B$NI=<($N;EJ}$d(B file $BL>$rI=8=$9$k$?$a$N(B field. <a 243 A field to specify presentation of entity or file name. It is an
243 node="MIME">MIME</a> $B$N3HD%$N#1$D!#(B 244 extension for <dref>MIME</dref>.
244 <p> 245 <p>
245 <rfc number="1806" type="Experimental" author="E R. Troost and 246 <rfc number="1806" type="Experimental" author="E R. Troost and
246 S. Dorner" title="Communicating Presentation Information 247 S. Dorner" title="Communicating Presentation Information
247 in Internet Messages: The Content-Disposition Header" 248 in Internet Messages: The Content-Disposition Header"
248 date="June 1995"> 249 date="June 1995">
249 250
250 251
252 <h3> Content-Type field
253 <node> Content-Type field
254 <p>
255 Header field to represent information about body, such as <dref>media
256 type</dref>, <dref>MIME charset</dref>. It is defined in <dref>RFC
257 2045</dref>.
258
259 <memo>
260 <p>
261 Historically, Content-Type field was proposed in RFC 1049. In it,
262 Content-Type did not distinguish type and subtype. However MIME
263 parser may be able to accept RFC 1049 based Content-Type as unknown
264 type.
265 </memo>
266
267 <p>
268 Content-Type field is defined as following:
269
270 <quote>
271 ``Content-Type'' ``:'' <concept>type</concept> ``/''
272 <concept>subtype</concept> *( ``;'' <concept>parameter</concept> )
273 </quote>
274
275 <p>
276 For example:
277
278 <quote>
279 <verb>
280 Content-Type: image/jpeg
281 </verb>
282 </quote>
283
284 <quote>
285 <verb>
286 Content-Type: text/plain; charset=iso-2022-jp
287 </verb>
288 </quote>
289
290 <memo>
291 <p>
292 A part does not have content-type field is regarded as
293
294 <quote>
295 <verb>
296 Content-Type: text/plain; charset=us-ascii
297 </verb>
298 </quote>
299
300 <noindent>
301 <cf node="us-ascii">
302
303 And a part has unknown type/subtype is regarded as
304
305 <quote>
306 <verb>
307 Content-Type: application/octet-stream
308 </verb>
309 </quote>
310
311 </memo>
312
313
314 <h3> Emacs
315 <node> Emacs
316 <p>
317 In this document, `Emacs' means GNU Emacs released by FSF, and `emacs'
318 means any variants of GNU Emacs.
319
320
321 <h3> encoded-word
322 <node> encoded-word
323 <p>
324 Representation non <dref>ASCII</dref> characters in header. It
325 is defined in <concept>RFC 2047</concept>.
326 <p>
327 <rfc number="2047" type="Standards Track" author="K. Moore"
328 title="MIME (Multipurpose Internet Mail Extensions) Part
329 Three: Message Header Extensions for Non-ASCII Text"
330 date="November 1996" obsolete="1521,1522,1590">
331
332
333 <h3> encapsulation
334 <node> encapsulation
335 <p>
336 Method to insert whole <a node="RFC 822">Internet message</a> into
337 another Internet message.
338 <p>
339 For example, it is used to forward a message.
340 <p>
341 <cf node="message/rfc822">
342
343
344 <h3> Entity
345 <node> entity
346 <p>
347 Header fields and contents of a message or one of the parts in the
348 body of a <dref>multipart</dref> entity.
349
350 <memo>
351 <p>
352 In this document, `entity' might be called ``part''.
353 </memo>
354
355
356 <h3> euc-kr
357 <node> euc-kr
358 <p>
359 A <dref>MIME charset</dref> for Korean.
360 <p>
361 It is a <dref>8bit</dref> <dref>coded character set</dref> based on
362 <dref>ISO 2022</dref>. It extends <dref>ASCII</dref> to combine
363 <dref>KS C5601</dref>.
364 <p>
365 It is defined in <dref>RFC 1557</dref>.
366 <p>
367 cf. <standard abbrev="euc-kr" org="Korea Industrial Standards
368 Association" title-en="Hangul Unix Environment"
369 number="KS C 5861" year="1992">
370
371
372 <h3> FTP <node> FTP
373 <p>
374 <rfc name="FTP" number="959" type="STD 9" author="Postel, J. and
375 J. Reynolds" title="File Transfer Protocol"
376 date="October 1985">
377
378
379 <h3> GB 2312-1980
380 <node> GB 2312
381 <p>
382 A <dref>94x94-character set</dref> for Chinese mainly written by
383 simplified Chinese mainly used in the Chinese mainland. It is a
384 standard of China.
385 <p>
386 Final byte of <dref>ISO 2022</dref> is 04/01 (`A').
387
388 <standard abbrev="GB 2312"
389 title-en="Code of Chinese Graphic Character Set for
390 Information Interchange - Primary Set" number="GB 2312"
391 year="1980">
392
393
394 <h3> GB 8565.2-1988
395 <node> GB 8565.2
396 <p>
397 A <dref>94x94-character set</dref> for Chinese as supplement to
398 <dref>GB 2312</dref>. It is a standard of China.
399
400 <standard abbrev="GB 8565.2" title-en="Information Processing - Coded
401 Character Sets for Text Communication - Part 2: Graphic
402 Characters used with Primary Set" number="GB 8565.2"
403 year="1988">
404
405
406 <h3> Graphic Character Set
407 <node> graphic character set
408 <p>
409 <a node="coded character set">Coded character set</a> for graphic
410 characters.
411
412
413 <h3> hz-gb2312
414 <node> hz-gb2312
415 <p>
416 A <a node="MIME charset">MIME charset</a> for simplified Chinese
417 mainly used in the Chinese mainland.
418 <p>
419 It extends <dref>ASCII</dref> to combine <dref>GB 2312</dref>, its
420 technique is like <dref>iso-2022-jp</dref>, but it is designed to be
421 ASCII printable to use special form for ESC sequence to designate GB
422 2312 to G0.
423 <p>
424 It is defined in RFC 1842 and 1843.
425
426 <rfc number="1842" type="Informational" author="Y. Wei, Y. Zhang,
427 J. Li, J. Ding and Y. Jiang" title="ASCII Printable
428 Characters-Based Chinese Character Encoding for Internet
429 Messages" date="August 1995">
430 <rfc number="1843" type="Informational" author="F. Lee" title="HZ - A
431 Data Format for Exchanging Files of Arbitrarily Mixed
432 Chinese and ASCII characters" date="August 1995">
433
434
435 <h3> ISO 2022
436 <node> ISO 2022
437 <p>
438 It is a standard for character code structure and <dref>code
439 extension</dref> technique.
440
441 <standard abbrev="ISO 2022" org="International Organization for
442 Standardization (ISO)" title-en="Information Processing:
443 ISO 7-bit and 8-bit coded character sets: Code extension
444 techniques" number="ISO/IEC 2022" year="1994">
445
446
447 <h3> iso-2022-cn
448 <node> iso-2022-cn
449 <p>
450 A <dref>MIME charset</dref> for Chinese.
451 <p>
452 It is a <dref>7bit</dref> <dref>coded character set</dref> based on
453 <dref>ISO 2022</dref>. It extends <dref>ASCII</dref> to combine
454 <dref>GB 2312</dref> and/or <a node="CNS 11643">CNS 11643 plain 1,
455 plain 2</a>.
456 <p>
457 It is defined in <dref>RFC 1922</dref>.
458
459
460 <h3> iso-2022-cn-ext
461 <node> iso-2022-cn-ext
462 <p>
463 A <dref>MIME charset</dref> for Chinese.
464 <p>
465 It is a <dref>7bit</dref> <dref>coded character set</dref> based on
466 <dref>ISO 2022</dref>. It extends <dref>ASCII</dref> to combine
467 <dref>GB 2312</dref>, <a node="CNS 11643">CNS 11643 plain 1 .. 7</a>,
468 <dref>ISO-IR-165</dref> and other Chinese graphic character sets.
469 <p>
470 It is defined in <dref>RFC 1922</dref>.
471 <p>
472 <memo>
473 MULE 2.3 and current XEmacs/mule can not use it correctly.
474 <p>
475 Emacs/mule can use it.
476 </memo>
477
478
479 <h3> iso-2022-jp
480 <node> iso-2022-jp
481 <p>
482 A <dref>MIME charset</dref> for Japanese.
483 <p>
484 It is a <dref>7bit</dref> <dref>coded character set</dref> based on
485 old <dref>ISO 2022</dref>. It switches <dref>ASCII</dref>, JIS
486 X0201-Latin, <a node="JIS C6226">JIS X0208-1978</a> and <a node="JIS
487 X0208">JIS X0208-1983</a>.
488 <p>
489 It is defined in RFC 1468.
490 <p>
491 <memo>
492 JIS X0208-1997? will define it in annex as non-<dref>ISO 2022</dref>
493 encoding.
494 </memo>
495
496 <rfc name="iso-2022-jp" number="1468" author="Murai J., M. Crispin,
497 and E. van der Poel" title="Japanese Character Encoding
498 for Internet Messages" date="June 1993">
499
500
501 <h3> iso-2022-jp-2
502 <node> iso-2022-jp-2
503 <p>
504 A <dref>MIME charset</dref>, which is a multilingual extension of
505 <dref>iso-2022-jp</dref>.
506 <p>
507 It is defined in RFC 1554.
508
509 <rfc name="iso-2022-jp-2" number="1554" type="Informational"
510 author="Ohta M. and Handa K." title="ISO-2022-JP-2:
511 Multilingual Extension of ISO-2022-JP" date="December
512 1993">
513
514
515 <h3> iso-2022-kr
516 <node> iso-2022-kr
517 <p>
518 A <a node="MIME charset">MIME charset</a> for Korean language (Hangul
519 script).
520 <p>
521 It is based on <dref>ISO 2022</dref> <dref>code extension</dref>
522 technique to extend <dref>ASCII</dref> to use <dref>KS C5601</dref> as
523 <dref>7bit</dref> text.
524 <p>
525 It is defined in <dref>RFC 1557</dref>.
526
527
528 <h3> ISO 646
529 <node> ISO 646
530 <p>
531 <standard abbrev="ISO 646" org="International Organization for
532 Standardization (ISO)" title-en="Information technology:
533 ISO 7-bit coded character set for information
534 interchange" number="ISO/IEC 646" year="1991">
535
536
537 <h3> ISO 8859-1
538 <node> ISO 8859-1
539 <p>
540 <standard abbrev="ISO 8859-1" org="International Organization for
541 Standardization (ISO)" title-en="Information Processing
542 -- 8-bit Single-Byte Coded Graphic Character Sets --
543 Part 1: Latin Alphabet No.1" number="ISO 8859-1"
544 year="1987">
545
546
547 <h3> iso-8859-1
548 <node> iso-8859-1
549 <p>
550 <concept>iso-8859-1</concept> is a <dref>MIME charset</dref> for
551 west-European languages written by Latin script.
552 <p>
553 It is a <dref>8bit</dref> <dref>coded character set</dref> based on
554 <dref>ISO 2022</dref>. It extends <dref>ASCII</dref> to combine
555 <dref>ISO 8859-1</dref>.
556 <p>
557 It is defined in <dref>RFC 2046</dref>.
558
559
560 <h3> ISO 8859-2
561 <node> ISO 8859-2
562 <p>
563 <standard abbrev="ISO 8859-2" org="International Organization for
564 Standardization (ISO)" title-en="Information Processing
565 -- 8-bit Single-Byte Coded Graphic Character Sets --
566 Part 2: Latin alphabet No.2" number="ISO 8859-2"
567 year="1987">
568
569
570 <h3> iso-8859-2
571 <node> iso-8859-2
572 <p>
573 <concept>iso-8859-2</concept> is a <dref>MIME charset</dref> for
574 east-European languages written by Latin script.
575 <p>
576 It is a <dref>8bit</dref> <dref>coded character set</dref> based on
577 <dref>ISO 2022</dref>. It extends <dref>ASCII</dref> to combine
578 <dref>ISO 8859-2</dref>.
579 <p>
580 It is defined in <dref>RFC 2046</dref>.
581
582
583 <h3> ISO 8859-3
584 <node> ISO 8859-3
585 <p>
586 <standard abbrev="ISO 8859-3" org="International Organization for
587 Standardization (ISO)" title-en="Information
588 Processing -- 8-bit Single-Byte Coded Graphic
589 Character Sets -- Part 3: Latin alphabet No.3"
590 number="ISO 8859-3" year="1988">
591
592
593 <h3> ISO 8859-4
594 <node> ISO 8859-4
595 <p>
596 <standard abbrev="ISO 8859-4" org="International Organization for
597 Standardization (ISO)" title-en="Information
598 Processing -- 8-bit Single-Byte Coded Graphic
599 Character Sets -- Part 4: Latin alphabet No.4"
600 number="ISO 8859-4" year="1988">
601
602
603 <h3> ISO 8859-5
604 <node> ISO 8859-5
605 <p>
606 <standard abbrev="ISO 8859-5" org="International Organization for
607 Standardization (ISO)" title-en="Information Processing
608 -- 8-bit Single-Byte Coded Graphic Character Sets --
609 Part 5: Latin/Cyrillic alphabet" number="ISO 8859-5"
610 year="1988">
611
612
613 <h3> iso-8859-5
614 <node> iso-8859-5
615 <p>
616 <concept>iso-8859-5</concept> is a <dref>MIME charset</dref> for
617 Cyrillic script.
618 <p>
619 It is a <dref>8bit</dref> <dref>coded character set</dref> based on
620 <dref>ISO 2022</dref>. It extends <dref>ASCII</dref> to combine
621 <dref>ISO 8859-5</dref>.
622 <p>
623 It is defined in <dref>RFC 2046</dref>.
624
625
626 <h3> ISO 8859-6
627 <node> ISO 8859-6
628 <p>
629 <standard abbrev="ISO 8859-6" org="International Organization for
630 Standardization (ISO)" title-en="Information
631 Processing -- 8-bit Single-Byte Coded Graphic
632 Character Sets -- Part 6: Latin/Arabic alphabet"
633 number="ISO 8859-6" year="1987">
634
635
636 <h3> ISO 8859-7
637 <node> ISO 8859-7
638 <p>
639 <standard abbrev="ISO 8859-7" org="International Organization for
640 Standardization (ISO)" title-en="Information Processing
641 -- 8-bit Single-Byte Coded Graphic Character Sets --
642 Part 7: Latin/Greek alphabet" number="ISO 8859-7"
643 year="1987">
644
645
646 <h3> iso-8859-7
647 <node> iso-8859-7
648 <p>
649 <concept>iso-8859-7</concept> is a <dref>MIME charset</dref> for
650 Greek script.
651 <p>
652 It is a <dref>8bit</dref> <dref>coded character set</dref> based on
653 <dref>ISO 2022</dref>. It extends <dref>ASCII</dref> to combine
654 <dref>ISO 8859-7</dref>.
655 <p>
656 It is defined in RFC 1947.
657
658 <rfc name="iso-8859-7" number="1947" type="Informational"
659 author="D. Spinellis" title="Greek Character Encoding
660 for Electronic Mail Messages" date="May 1996">
661
662
663 <h3> ISO 8859-8
664 <node> ISO 8859-8
665 <p>
666 <standard abbrev="ISO 8859-8" org="International Organization for
667 Standardization (ISO)" title-en="Information
668 Processing -- 8-bit Single-Byte Coded Graphic
669 Character Sets -- Part 8: Latin/Hebrew alphabet"
670 number="ISO 8859-8" year="1988">
671
672
673 <h3> ISO 8859-9
674 <node> ISO 8859-9
675 <p>
676 <standard abbrev="ISO 8859-9" org="International Organization for
677 Standardization (ISO)" title-en="Information
678 Processing -- 8-bit Single-Byte Coded Graphic
679 Character Sets -- Part 9: Latin alphabet No.5"
680 number="ISO 8859-9" year="1990">
681
682
683 <h3> ISO-IR-165, CCITT Extended GB <node> ISO-IR-165
684 <p>
685 A <dref>94x94-character set</dref> for Chinese mainly written by
686 simplified Chinese mainly used in the Chinese mainland registered by
687 CCITT.
688 <p>
689 It consists of <dref>GB 2312</dref>, <dref>GB 8565.2</dref> and
690 additional 150 characters.
691 <p>
692 Final byte of <dref>ISO 2022</dref> is 04/05 (`E').
693
694
695 <h3> JIS X0201
696 <node> JIS X0201
697 <p>
698 It defines two <dref>94-character set</dref>, for Latin script (a
699 variant of <dref>ISO 646</dref>) and Katakana script, and 7bit and
700 8bit <dref>coded character set</dref>s.
701 <p>
702 It was renamed from <concept>JIS C6220-1976</concept>.
703
704 <standard abbrev="JIS X0201-1976" org="Japanese Standards Association"
705 title-en="Code for Information Interchange" number="JIS
706 X 0201-1976">
707
708 In addition, revised version will be published in 1997.
709
710 <standard abbrev="JIS X0201-1997?" org="Japanese Standards
711 Association" title-en="7-bit and 8-bit coded character
712 sets for information interchange" number="JIS X 0201"
713 year="1997? draft">
714
715
716 <h3> JIS C6226-1978
717 <node> JIS C6226
718 <p>
719 A <dref>94x94-character set</dref> for Japanese. It was renamed to
720 JIS X0208-1978.
721 <p>
722 <cf node="JIS X0208">
723
724
725 <h3> JIS X0208
726 <node> JIS X0208
727 <p>
728 A <dref>94x94-character set</dref> for Japanese. Japanese standard.
729 It was published in 1978, and revised in 1983 and 1990. In the
730 Internet message, 1983 edition is major.
731 <p>
732 JIS X0208 contains some symbols, numbers, primary Latin script,
733 Hiragana script, Katakana script, Greek script, Cyrillic script, box
734 drawing parts, Kanji (Ideographic characters used in Japanese).
735 Notice that some symbols and box drawing parts were added in 1983 and
736 some Kanjis were changed or swapped code points. So 1978 edition and
737 1983 edition are regarded as different graphic character set.
738 <p>
739 1990 edition added some characters, so designation of 1990 edition
740 requires `identify revised registration' sequence, ESC 02/06 4/0 as
741 prefix of designation sequence.
742
743 <standard abbrev="JIS X0208-1978" org="Japanese Standards Association"
744 title-en="Code of the Japanese graphic character set for
745 information interchange" number="JIS C6226" year="1978">
746 <standard abbrev="JIS X0208-1983,1990" org="Japanese Standards
747 Association" title-en="Code of the Japanese graphic
748 character set for information interchange" number="JIS
749 X0208" year="1983,1990">
750
751 <p>
752 In addition, revised version will be published in 1997. (It does not
753 change graphic character set)
754
755 <standard abbrev="JIS X0208-1997?" org="Japanese Standards
756 Association" title-en="7-bit and 8-bit double byte coded
757 Kanji sets for information interchange" number="JIS X
758 0208" year="1997? draft">
759
760
761 <h3> JIS X0212-1990
762 <node> JIS X0212
763 <p>
764 A <dref>94x94-character set</dref> for Japanese as supplement to
765 <dref>JIS X0208</dref>. It is a standard of Japan.
766 <p>
767 Final byte of <dref>ISO 2022</dref> is 04/04 (`D').
768
769
770 <h3> koi8-r
771 <node> koi8-r
772 <p>
773 A <dref>MIME charset</dref> for Cyrillic script for Russian or other
774 languages.
775 <p>
776 It is a 1 byte <dref>8bit</dref> <dref>coded character set</dref>, not
777 based on <dref>ISO 2022</dref>. It is a de-fact standard.
778 <p>
779 It is defined in RFC 1489.
780 <p>
781 <rfc number="1489" author="A. Chernov" title="Registration of a
782 Cyrillic Character Set" date="July 1993">
783
784
785 <h3> KS C5601-1987
786 <node> KS C5601
787 <p>
788 A <dref>94x94-character set</dref> for Korean language (Hangul
789 script). Korean Standard. Final byte of <dref>ISO 2022</dref> is
790 04/03 (`C').
791
792 <standard abbrev="KS C5601" org="Korea Industrial Standards
793 Association" title-en="Code for Information Interchange
794 (Hangul and Hanja)" number="KS C 5601" year="1987">
795
796
251 <h3> media type 797 <h3> media type
252 <node> media type 798 <node> media type
253 <p> 799 <p>
254 <concept>media type</concept> specifies the nature of the data in the 800 <concept>media type</concept> specifies the nature of the data in the
255 body of <dref>MIME</dref> <dref>entity</dref>. It consists of 801 body of <dref>MIME</dref> <dref>entity</dref>. It consists of
256 <concept>type</> and <concept>subtype</concept>. It is defined in 802 <concept>type</concept> and <concept>subtype</concept>. It is defined
257 <dref>RFC 2046</dref>. 803 in <dref>RFC 2046</dref>.
258 <p> 804 <p>
259 Currently there are following types: 805 Currently there are following types:
260 806
261 <ul> 807 <ul>
262 <li><concept>text</concept> 808 <li><concept>text</concept>
288 not use them in public. 834 not use them in public.
289 <p> 835 <p>
290 <cf node="Content-Type field"> 836 <cf node="Content-Type field">
291 837
292 838
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 839 <h3> message
833 <node> message 840 <node> message
834 <p> 841 <p>
835 $B$3$3$G$O(B <dref>RFC 822</dref> $B$GDj5A$5$l$k(B mail $B$H(B <dref>RFC 842 In this document, it means mail defined in <dref>RFC 822</dref> and
836 1036</dref> $B$GDj5A$5$l$k(B news $B5-;v$NAm>N$H$7$FMQ$$$k!#(B 843 news message defined in <dref>RFC 1036</dref>.
837 844
838 845
839 <h3> message/rfc822 846 <h3> message/rfc822
840 <node> message/rfc822 847 <node> message/rfc822
841 <p> 848 <p>
846 853
847 854
848 <h3> method 855 <h3> method
849 <node> method 856 <node> method
850 <p> 857 <p>
851 tm $B$GFCDj$N<oN`$N(B data $B$r:F@8$7$?$H$-<B:]$K$=$N=hM}$r9T$J$&(B 858 Application program of tm-view to process for specified <dref>media
852 program. Emacs Lisp $B$G=q$+$l$?(B <concept>internal method</concept> $B$H(B C 859 type</dref> when user plays an entity.
853 $B$d(B script $B8@8l$J$I$G=q$+$l$?(B <concept>external method</concept> $B$,$"$k!#(B 860 <p>
861 There are two kinds of methods, <concept>internal method</concept> and
862 <concept>external method</concept>. Internal method is written by
863 Emacs Lisp. External method is written by C or script languages and
864 called by asynchronous process call.
854 <p> 865 <p>
855 <cf file="tm-view-en" node="method"> 866 <cf file="tm-view-en" node="method">
856 867
857 868
858 <h3> MIME 869 <h3> MIME
887 898
888 899
889 <h3> MIME charset 900 <h3> MIME charset
890 <node> MIME charset 901 <node> MIME charset
891 <p> 902 <p>
892 <dref>Coded character set</dref> used in <dref>Content-Type 903 <a node="coded character set">Coded character set</a> used in
893 field</dref> or charset parameter of <a 904 <dref>Content-Type field</dref> or charset parameter of <a
894 node="encoded-word">encoded-word</a>. 905 node="encoded-word">encoded-word</a>.
895 <p> 906 <p>
896 It is defined in <dref>RFC 2045</dref>. 907 It is defined in <dref>RFC 2045</dref>.
897 <p> 908 <p>
898 <dref>iso-2022-jp</dref> $B$d(B <a node="euc-kr">euc-kr</a> $B$O$=$N#1$D!#(B 909 <dref>iso-2022-jp</dref> or <dref>euc-kr</dref> are kinds of it. (In
899 $B!J$3$3$G$O!"(BMIME charset $B$O(B<a node="Character set">$BJ8;z=89g(B</a>$B$H6hJL(B 910 this document, MIME charsets are written by small letters to
900 $B$7$F>.J8;z$G=q$$$F$$$k!K(B 911 distinguish <dref>graphic character set</dref>. For example, ISO
912 8859-1 is a graphic character set, and iso-8859-1 is a MIME charset)
901 913
902 914
903 <h3> MTA 915 <h3> MTA
904 <node> MTA 916 <node> MTA
905 <p> 917 <p>
906 <concept>Message Transfer Agent</concept> $B$NN,$G!"(Bsendmail $B$J$I$N(B mail 918 <concept>Message Transfer Agent</concept>. It means mail transfer
907 $BG[Aw(B program $B$H(B news server $B$NAm>N!#(B 919 programs (ex. sendmail) and news servers.
908 <p> 920 <p>
909 <cf node="MUA"> 921 <cf node="MUA">
910 922
911 923
912 <h3> MUA 924 <h3> MUA
913 <node> MUA 925 <node> MUA
914 <p> 926 <p>
915 <concept>Message User Agent</concept> $B$NN,$G!"(Bmail reader $B$H(B news 927 <concept>Message User Agent</concept>. It means mail readers and news
916 reader $B$NAm>N!#(B 928 readers.
917 <p> 929 <p>
918 <cf node="MTA"> 930 <cf node="MTA">
919 931
920 932
921 <h3> MULE 933 <h3> MULE
922 <node> MULE 934 <node> MULE
923 <p> 935 <p>
924 $BH>ED(B $B7u0l;a$i$,:n$C$?!"B?8@8l$5$l$?(B <a node="Emacs">Emacs</a>. 936 Multilingual extension of GNU <dref>Emacs</dref> by HANDA Ken'ichi et
925 <p> 937 al.
926 [MULE] Nishikimi M., Handa K. and Tomura S., ``Mule: MULtilingual 938
927 Enhancement to GNU Emacs'', Proc. of INET'93, August, 1993. 939 <inproc abbrev="MULE" author="Nishikimi M., Handa K. and Tomura S."
928 <p> 940 title-en="Mule: MULtilingual Enhancement to GNU Emacs"
929 $B8=:_!"(BMULE $B$N5!G=$r(B Emacs $B$K(B merge $B$9$k:n6H$,9T$o$l$F$*$j!"(B<a 941 book-en="Proc. of INET'93" date="August, 1993">
930 href="ftp://etlport.etl.go.jp/pub/mule/mule-19.33-gamma.taz"> alpha $BHG(B 942 <p>
931 </a> $B$,B8:_$9$k!#(B 943 Now, FSF and HANDA Ken'ichi et al. are working to merge MULE feature
932 <p> 944 into Emacs, there is <a
933 $B$=$NB>!"(BXEmacs $B$K(B merge $B$7$?$b$N$bB8:_$9$k!#(B 945 href="ftp://etlport.etl.go.jp/pub/mule/mule-19.33-delta.taz">alpha
934 <p> 946 version of mule merged emacs</a>.
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 947 <p>
936 $B$K$J$k!#(B 948 In addition, there is XEmacs with mule feature.
937 <p> 949 <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 950 So now, there are 3 kinds of mule variants.
939 $B$N(B MULE $B$r(B <concept>MULE</concept>, mule $B5!G=$r(B merge $B$7$?(B Emacs $B$r(B 951 <p>
940 <concept>Emacs/mule</concept>, mule $B5!G=$r(B merge $B$7$?(B XEmacs $B$r(B 952 In this document, <concept>mule</concept> means any mule variants,
941 <concept>XEmacs/mule</concept> $B$H8F$V$3$H$K$9$k!#(B 953 <concept>MULE</concept> means original MULE (..2.3),
954 <concept>Emacs/mule</concept> means mule merged Emacs,
955 <concept>XEmacs/mule</concept> means XEmacs with mule feature.
942 956
943 957
944 <h3> Multipart 958 <h3> Multipart
945 <node> multipart 959 <node> multipart
946 <p> 960 <p>
947 <concept>multipart</concept> means <dref>media type</dref> to insert 961 <concept>multipart</concept> means <dref>media type</dref> to insert
948 multiple <dref>entities</dref> in a single body. Or it also indicates 962 multiple <a node="entity">entities</a> in a single body. Or it also
949 a message consists of multiple entities. 963 indicates a message consists of multiple entities.
950 <p> 964 <p>
951 There are following subtypes registered in <dref>RFC 2046</dref>: 965 There are following subtypes registered in <dref>RFC 2046</dref>:
952 966
953 <ul> 967 <ul>
954 <li><dref>multipart/mixed</dref> 968 <li><dref>multipart/mixed</dref>
995 1009
996 1010
997 <h3> multipart/encrypted 1011 <h3> multipart/encrypted
998 <node> multipart/encrypted 1012 <node> multipart/encrypted
999 <p> 1013 <p>
1000 RFC 1847 $B$GDj5A$5$l$?(B <dref>Security multipart</dref> $B$N#1$D$G!"0E9f2=(B 1014 It is a <dref>Security multipart</dref> defined in
1001 $B$5$l$?(B message $B$rI=8=$9$k$N$KMQ$$$k!#(B 1015 RFC 1847, used to represent encrypted message.
1002 <p> 1016 <p>
1003 <cf node="PGP/MIME"> 1017 <cf node="PGP/MIME">
1004 1018
1005 1019
1006 <h3> multipart/mixed 1020 <h3> multipart/mixed
1026 1040
1027 1041
1028 <h3> multipart/signed 1042 <h3> multipart/signed
1029 <node> multipart/signed 1043 <node> multipart/signed
1030 <p> 1044 <p>
1031 RFC 1847 $B$GDj5A$5$l$?(B <dref>Security multipart</dref> $B$N#1$D$G!"EE;R=p(B 1045 It is a <dref>Security multipart</dref> defined in
1032 $BL>$rI=8=$9$k$N$KMQ$$$k!#(B 1046 RFC 1847, used to represent signed message.
1033 <p> 1047 <p>
1034 <cf node="PGP/MIME"> 1048 <cf node="PGP/MIME">
1035 1049
1036 1050
1037 <h3> PGP 1051 <h3> PGP
1038 <node> PGP 1052 <node> PGP
1039 <p> 1053 <p>
1040 Phil Zimmermann $B;a$,:n@.$7$?8x3+800E9f=hM}7O$N#1$D!#(B 1054 A public key encryption program by Phil Zimmermann. It provides
1041 <dref>message</dref> $B$N0E9f2=$dEE;R=pL>$r9T$&$3$H$,$G$-$k!#(BPretty Good 1055 encryption and signature for <dref>message</dref>. PGP stands for
1042 Privacy $B$NN,!#(B 1056 <concept>Pretty Good Privacy</concept>.
1043 <p> 1057 <p>
1044 $BEAE}E*$J(B PGP $B$G$O(B <dref>encapsulation</dref> $B$K(B <dref>RFC 934</dref>$B$K(B 1058 Traditional PGP uses <dref>RFC 934</dref> <dref>encapsulation</dref>.
1045 $B=`$8$?J}K!$rMQ$$$k!#$3$l$O(B <dref>MIME</dref> $B$HL7=b$9$k$N$G(B 1059 It is conflict with <dref>MIME</dref>. So <dref>PGP/MIME</dref> is
1046 <dref>PGP/MIME</dref> $B$,Ds0F$5$l$F$$$k!#0lJ}!"(BMIME $B$K$*$$$F(B PGP $B$N(B 1060 defined. On the other hand, <dref>PGP-kazu</dref> was proposed to use
1047 encapsulation $B$rMQ$$$kJ}K!(B <cf node="PGP-kazu"> $B$bMxMQ$5$l$F$-$?!#$7$+(B 1061 PGP encapsulation in MIME. But it is obsoleted.
1048 $B$7!":#8e$O(B PGP/MIME $B$KE}0l$7$F$$$/J}$,K>$^$7$$!#(B
1049 <p> 1062 <p>
1050 <rfc name="PGP" number="1991" type="Informational" author="D. Atkins, 1063 <rfc name="PGP" number="1991" type="Informational" author="D. Atkins,
1051 W. Stallings and P. Zimmermann" title="PGP Message 1064 W. Stallings and P. Zimmermann" title="PGP Message
1052 Exchange Formats" date="August 1996"> 1065 Exchange Formats" date="August 1996">
1053 1066
1054 1067
1055 1068
1056 <h3> PGP-kazu 1069 <h3> PGP-kazu
1057 <node> PGP-kazu 1070 <node> PGP-kazu
1058 <p> 1071 <p>
1059 $B;3K\(B $BOBI'(B $B;a$,Ds0F$7$?(B <a node="MIME">MIME</a> $B$G(B <a 1072 In this document, <concept>PGP-kazu</concept> means a method to use
1060 node="PGP">PGP</a> $B$rMxMQ$9$k$?$a$NJ}K!$r$3$3$G$O(B 1073 traditional PGP encapsulation in <dref>MIME</dref>, proposed by
1061 <concept>PGP-kazu</concept> $B$H8F$V$3$H$K$9$k!#(B 1074 YAMAMOTO Kazuhiko.
1062 <p> 1075 <p>
1063 PGP-kazu $B$O(B <concept>application/pgp</concept> $B$H$$$&(B 1076 PGP-kazu defines a <dref>media type</dref>,
1064 <dref>content-type</dref> $B$rDj5A$9$k!#(B 1077 <concept>application/pgp</concept>.
1065 <p> 1078 <p>
1066 application/pgp $B$N(B part $B$G$O(B PGP $B$N(B <dref>encapsulation</dref> $B$,MQ$$(B 1079 In application/pgp entity, PGP <dref>encapsulation</dref> is used.
1067 $B$i$l$k!#(BPGP $B$N(B encapsulation <cf node="RFC 934"> $B$H(B MIME $B$N(B 1080 PGP encapsulation conflicts with MIME, so it requires PGP-processing
1068 encapsulation $B$OL7=b$9$k$N$G!"(BPGP $B$N(B encapsulation $B$r2r$+$J$$8B$j!"Cf(B 1081 to read as MIME message.
1069 $B$K4^$^$l$?(B MIME message $B$rFI$`$3$H$,$G$-$J$/$J$k!#B($A!"(BPGP-kazu $B$KBP(B 1082 <p>
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 1083 It was obsoleted, so you should use <dref>PGP/MIME</dref>. However if
1071 $B$k!#$=$NBe$o$j!"(BMIME $B$KBP1~$7$F$$$J$$(B PGP $BBP1~$N(B <dref>MUA</dref> $B$G$b(B 1084 you want to use traditional PGP message, it might be available.
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$$$&#2$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
1085 1086
1086 <h3> PGP/MIME 1087 <h3> PGP/MIME
1087 <node> PGP/MIME 1088 <node> PGP/MIME
1088 <p> 1089 <p>
1089 Michael Elkins $B;a$,Ds0F$7$?(B <a node="MIME">MIME</a> $B$G(B <a 1090 <dref>PGP</dref> and <dref>MIME</dref> integration proposed by Michael
1090 node="PGP">PGP</a> $B$rMxMQ$9$k$?$a$NJ}K!!#(B 1091 Elkins.
1091 <p> 1092 <p>
1092 <a node="Security multipart">RFC 1847</a> $B$K4p$-!"(BMIME $B$N(B multipart $B$K(B 1093 It is based on <a node="Security multipart">RFC 1847</a>, so it is
1093 $B$h$k(B <dref>encapsulation</dref> $B$r9T$&!#$3$N$?$a!"(BMIME $B$N<+A3$J3HD%$K(B 1094 harmonious with MIME, but it is not compatible with traditional PGP
1094 $B$J$C$F$$$k!#$7$+$7!"EAE}E*$J(B PGP$B$H$N8_49@-$,<:$o$l$F$$$k!#(B 1095 encapsulation. However MIME MUA can read PGP/MIME signed message even
1095 <p> 1096 if it does not support PGP/MIME.
1096 PGP/MIME $B$G$O(B <dref>PGP-kazu</dref> $B$H0[$J$j!"(BMIME $B$N(B encapsulation $B$N(B 1097 <p>
1097 $B$_$rMQ$$$k!#$^$?!"$3$N$?$a!"(BPGP $B$N=hM}$r9T$&A0$K(B message $B$N(B parse $B$r9T(B 1098 <dref>PGP/MIME</dref> will be standard of PGP message.
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 1099
1104 <rfc name="PGP/MIME" number="2015" type="Standards Track" 1100 <rfc name="PGP/MIME" number="2015" type="Standards Track"
1105 author="M. Elkins" title="MIME Security with Pretty Good 1101 author="M. Elkins" title="MIME Security with Pretty Good
1106 Privacy (PGP)" date="October 1996"> 1102 Privacy (PGP)" date="October 1996">
1107 1103
1119 1115
1120 1116
1121 <h3> RFC 821 1117 <h3> RFC 821
1122 <node> RFC 821 1118 <node> RFC 821
1123 <p> 1119 <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" 1120 <rfc name="SMTP" number="821" type="STD 10" author="J. Postel"
1128 title="Simple Mail Transfer Protocol" date="August 1121 title="Simple Mail Transfer Protocol" date="August
1129 1982"> 1122 1982">
1130 1123
1131 1124
1132 <h3> RFC 822 1125 <h3> RFC 822
1133 <node> RFC 822 1126 <node> RFC 822
1134 <p> 1127 <p>
1135 Internet mail $B$N<g$K(B <concept>message header</concept> $B$K4X$9$k7A<0$K(B 1128 A RFC defines format of Internet mail message, mainly <concept>message
1136 $B4X$9$kI8=`$rDj$a$F$$$k(B RFC. 1129 header</concept>.
1137 1130
1138 <memo> 1131 <memo>
1139 <p> 1132 <p>
1140 news message $B$b$3$l$K=`$8$F$$$k$N$G!"(B<concept>Internet mail</concept> 1133 news message is based on RFC 822, so <concept>Internet
1141 $B$H=q$/$h$j$b!"(B<concept>Internet message</concept> $B$H=q$$$?J}$,NI$$$+$b(B 1134 message</concept> may be more suitable than <concept>Internet
1142 $B$7$l$J$$!#(B 1135 mail</concept> .
1143 </memo> 1136 </memo>
1144 1137
1145 <rfc number="822" type="STD 11" author="D. Crocker" title="Standard 1138 <rfc number="822" type="STD 11" author="D. Crocker" title="Standard
1146 for the Format of ARPA Internet Text Messages" 1139 for the Format of ARPA Internet Text Messages"
1147 date="August 1982"> 1140 date="August 1982">
1148 1141
1149 1142
1150 <h3> RFC 934 1143 <h3> RFC 934
1151 <node> RFC 934 1144 <node> RFC 934
1152 <p> 1145 <p>
1153 <a node="RFC 822">Internet mail</a> $B$N(B <a node="encapsulation"> 1146 A RFC defines an <a node="encapsulation">
1154 <concept>encapsulation</concept></a> $B$NJ}K!$rDj$a$?(B RFC. 1147 <concept>encapsulation</concept></a> method for <a node="RFC
1155 <p> 1148 822">Internet mail</a>.
1156 <dref>MIME</dref> $B$HL7=b$9$k$N$G!"8=:_$G$O(B <dref>message/rfc822</dref> 1149 <p>
1157 $B$rMQ$$$k$Y$-$G$"$k!#(B 1150 It conflicts with <dref>MIME</dref>, so you should use
1158 1151 <dref>message/rfc822</dref>.
1159 1152
1160 <rfc number="934" author="Marshall T. Rose and Einar A. Stefferud" 1153 <rfc number="934" author="Marshall T. Rose and Einar A. Stefferud"
1161 title="Proposed Standard for Message Encapsulation" 1154 title="Proposed Standard for Message Encapsulation"
1162 date="January 1985"> 1155 date="January 1985">
1163 1156
1164 1157
1165 <h3> RFC 1036 1158 <h3> RFC 1036
1166 <node> RFC 1036 1159 <node> RFC 1036
1167 <p> 1160 <p>
1168 USENET $B$G$N(B message $B$N7A<0$rDj$a$?(B RFC. <a node="RFC 822">RFC 822</a> 1161 A RFC defines format of USENET message. It is a subset of <dref>RFC
1169 $B$N(B subset $B$K$J$C$F$$$k!#(BInternet $B$NI8=`$G$O$J$$$,!"(BUSENET $B0J30$N(B 1162 822</dref>. It is not Internet standard, but a lot of netnews
1170 netnews $B$G$b$3$l$K=`$8$F$$$k$b$N$,B?$$!#(B 1163 excepting Usenet uses it.
1171 1164
1172 <rfc name="USENET" number="1036" author="M. Horton and R. Adams" 1165 <rfc name="USENET" number="1036" author="M. Horton and R. Adams"
1173 title="Standard for Interchange of USENET Messages" 1166 title="Standard for Interchange of USENET Messages"
1174 date="December 1987" obsolete="850"> 1167 date="December 1987" obsolete="850">
1175 1168
1176 1169
1177 <h3> RFC 1153 1170 <h3> RFC 1153
1178 <node> RFC 1153 1171 <node> RFC 1153
1179 <p> 1172 <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" 1173 <rfc number="1153" author="F. Wancho" title="Digest Message Format"
1190 date="April 1990"> 1174 date="April 1990">
1191 1175
1192 1176
1193 <h3> RFC 1557 1177 <h3> RFC 1557
1194 <node> RFC 1557 1178 <node> RFC 1557
1195 <p> 1179 <p>
1196 <dref>euc-kr</dref> $B$H(B <dref>iso-2022-kr</dref> $B$H$$$&4Z9q8l$N$?$a$N(B 1180 A RFC defines <dref>MIME charset</dref>s for Korean,
1197 <a node="MIME charset">MIME charset</a> $B$rDj5A$7$F$$$k(B RFC. 1181 <dref>euc-kr</dref> and <dref>iso-2022-kr</dref>.
1198 1182
1199 <rfc number="1557" type="Informational" author="U. Choi, K. Chon and 1183 <rfc number="1557" type="Informational" author="U. Choi, K. Chon and
1200 H. Park" title="Korean Character Encoding for Internet 1184 H. Park" title="Korean Character Encoding for Internet
1201 Messages" date="December 1993"> 1185 Messages" date="December 1993">
1202 1186
1203 1187
1204 <h3> RFC 1922 1188 <h3> RFC 1922
1205 <node> RFC 1922 1189 <node> RFC 1922
1206 <p> 1190 <p>
1191 A RFC defines <dref>MIME charset</dref>s for Chinese,
1207 <dref>iso-2022-cn</dref>, <dref>iso-2022-cn-ext</dref>, 1192 <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 1193 <dref>cn-gb</dref>, <dref>cn-big5</dref>, etc.
1209 node="MIME charset">MIME charset</a> $B$rDj5A$7$F$$$k(B RFC. 1194 <p>
1210 <p> 1195 In addition, it defines additional parameters of <dref>Content-Type
1211 $B$3$l$K2C$($F!"(B<concept>charset-edition</concept> $B$H(B 1196 field</dref> field, <concept>charset-edition</concept> and
1212 <concept>charset-extension</concept> $B$H$$$&(B <dref>Content-Type 1197 <concept>charset-extension</concept>.
1213 field</dref> $B$N(B parameter $B$rDj5A$7$F$$$k!#(B
1214 1198
1215 <rfc number="1922" type="Informational" author="Zhu, HF., Hu, DY., 1199 <rfc number="1922" type="Informational" author="Zhu, HF., Hu, DY.,
1216 Wang, ZG., Kao, TC., Chang, WCH. and Crispin, M." 1200 Wang, ZG., Kao, TC., Chang, WCH. and Crispin, M."
1217 title="Chinese Character Encoding for Internet Messages" 1201 title="Chinese Character Encoding for Internet Messages"
1218 date="March 1996"> 1202 date="March 1996">
1257 1241
1258 1242
1259 <h3> plain text 1243 <h3> plain text
1260 <node> plain text 1244 <node> plain text
1261 <p> 1245 <p>
1262 $B=qBN$dAHHG$K4X$9$k>pJs$r;}$?$J$$(B <a node="Coded character set">$BJ8;zId(B 1246 A textual data represented by only <dref>coded character set</dref>.
1263 $B9f(B</a>$B$N$_$GI=8=$5$l$k(B text $B>pJs!#(B<cf node="text/plain"> 1247 It does not have information about font or typesetting.
1248 <cf node="text/plain">
1264 1249
1265 1250
1266 <h3> Security multipart 1251 <h3> Security multipart
1267 <node> Security multipart 1252 <node> Security multipart
1268 <p> 1253 <p>
1269 <a node="MIME">MIME</a> $B$G0E9f$dEE;R=qL>$rMQ$$$k$?$a$N7A<0!#(B<a 1254 A format to represent signed/encrypted message in <dref>MIME</dref>.
1270 node="multipart/signed"><concept>multipart/signed</concept></a> $B$H(B <a 1255 <p>
1271 node="multipart/encrypted"><concept>multipart/encrypted</concept></a> 1256 It defines two multipart media types, <a
1272 $B$H$$$&(B multipart $B$rMQ$$$k!#(BMOSS $B$d(B <a node="PGP/MIME">PGP/MIME</a> $B$O(B 1257 node="multipart/signed"><concept>multipart/signed</concept></a> and <a
1273 $B$3$l$K4p$$$F$$$k!#(B 1258 node="multipart/encrypted"><concept>multipart/encrypted</concept></a>.
1259 <p>
1260 MOSS and <dref>PGP/MIME</dref> are based on it.
1274 1261
1275 <rfc name="Security multipart" number="1847" type="Standards Track" 1262 <rfc name="Security multipart" number="1847" type="Standards Track"
1276 author="James Galvin, Gale Murphy, Steve Crocker and Ned 1263 author="James Galvin, Gale Murphy, Steve Crocker and Ned
1277 Freed" title="Security Multiparts for MIME: 1264 Freed" title="Security Multiparts for MIME:
1278 Multipart/Signed and Multipart/Encrypted" date="October 1265 Multipart/Signed and Multipart/Encrypted" date="October
1280 1267
1281 1268
1282 <h3> text/enriched 1269 <h3> text/enriched
1283 <node> text/enriched 1270 <node> text/enriched
1284 <p> 1271 <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 1272 <rfc name="text/enriched" number="1896" author="P. Resnick and
1290 A. Walker" title="The text/enriched MIME Content-type" 1273 A. Walker" title="The text/enriched MIME Content-type"
1291 date="February 1996" obsolete="1563"> 1274 date="February 1996" obsolete="1563">
1292 1275
1293 1276
1305 1288
1306 1289
1307 <h3> tm-kernel, tm 1290 <h3> tm-kernel, tm
1308 <node> tm-kernel 1291 <node> tm-kernel
1309 <p> 1292 <p>
1310 Emacs $B$G(B <a node="MIME">MIME</a> $B$rMxMQ$9$k$?$a$N(B user interface $B$rDs(B 1293 A libraries to provide user interface about <dref>MIME</dref> for
1311 $B6!$9$k(B library $B72!#(B`tools for MIME' $B$NN,!#(B 1294 emacs. tm stands for `tools for MIME'.
1312 1295
1313 <memo title="$B$I$&$G$bNI$$$3$H(B(^-^;"> 1296 <memo title="Unimportant notice(^-^;">
1314 <p> 1297 <p>
1315 <ul> 1298 <ul>
1316 <li> tm $B$O(B ``tiny-mime'' $B$NN,$8$c$J$$$i$7$$$>(B (^-^; 1299 <li> tm may not stand for ``tiny-mime''(^-^;
1317 <li> tm $B$O:n<T$N%$%K%7%c%k$8$c$J$$$i$7$$$>(B (^-^; 1300 <li> tm may not stand for initial of an author (^-^;
1318 <li> ``Tools for MIME'' $B$NN,$H$$$&$N$O$3$8$D$1$i$7$$$>(B (^-^; 1301 <li> ``Tools for MIME'' may be strained (^-^;
1319 </ul> 1302 </ul>
1320 </memo> 1303 </memo>
1321 1304
1322 1305
1323 <h3> tm-MUA 1306 <h3> tm-MUA
1324 <node> tm-MUA 1307 <node> tm-MUA
1325 <p> 1308 <p>
1326 <a node="tm-kernel">tm</a> $B$rMQ$$$?(B <a node="MUA">MUA</a> $B$b$7$/$O(B MUA 1309 <dref>MUA</dref> or MUA extender using <a node="tm-kernel">tm</a>.
1327 $B$KBP$9$k(B extender. 1310 <p>
1328 <p> 1311 <concept>tm oomori package</concept> has following extenders:
1329 <concept>tm $BBg@9$j(B package</concept> $B$K$O(B
1330 1312
1331 <ul> 1313 <ul>
1332 <li><a file="mh-e">mh-e</a> $BMQ$N(B <concept>tm-mh-e</concept> 1314 <li><a file="tm-mh-e-en"><concept>tm-mh-e</concept></a>
1333 <li>GNUS $BMQ$N(B <concept>tm-gnus</concept> 1315 for <a file="mh-e">mh-e</a>
1334 <li>Gnus $BMQ$N(B <a file="gnus-mime-en"><concept>gnus-mime</concept></a> 1316 <li><a file="tm-gnus_en"><concept>tm-gnus</concept></a> for GNUS
1335 <li>VM $BMQ$N(B <concept>tm-vm</concept> 1317 <li><a file="gnus-mime-en"><concept>gnus-mime</concept></a> for Gnus
1336 <li>RMAIL $BMQ$N(B <concept>tm-rmail</concept> 1318 <li><a file="tm-vm_en"><concept>tm-vm</concept></a> for VM
1319 <li><concept>tm-rmail</concept> for RMAIL
1337 </ul> 1320 </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 1321
1344 1322
1345 <h3> us-ascii 1323 <h3> us-ascii
1346 <node> us-ascii 1324 <node> us-ascii
1347 <p> 1325 <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 1326 A <a node="MIME charset">MIME charset</a> for primary Latin script
1349 charset">MIME charset</a> $B$N#1$D!#(B 1327 mainly written by English or other languages.
1350 <p> 1328 <p>
1351 <dref>ASCII</dref> $B$N$_$+$i$J$j(B <dref>ISO 2022</dref> $B$K$h$k(B<a 1329 It is a 7bit <dref>coded character set</dref> based on <dref>ISO
1352 node="Code extension">$BId9f3HD%(B</a>$B$O5v$5$l$J$$!#(B 1330 2022</dref>, it contains only
1353 <p> 1331 <dref>ASCII</dref> and <dref>code extension</dref> is not allowed.
1354 Internet mail $B$K$*$1$kI8=`$N(B<a node="Coded character set">$BId9f2=J8;z=8(B 1332 <p>
1355 $B9g(B</a>$B$G$"$j!"L@<(E*$K(B MIME charset $B$,<($5$l$J$$>l9g$O86B'$H$7$F(B 1333 It is standard coded character set of Internet mail. If MIME charset
1356 <concept>us-ascii</concept> $B$,;H$o$l$k!#(B 1334 is not specified, <concept>us-ascii</concept> is used as default.
1357 <p> 1335 <p>
1358 $B$^$?!"(B<a node="RFC 822">RFC 822</a> $B$K$*$1$k(B <concept>ASCII</concept> 1336 In addition, <concept>ASCII</concept> of <dref>RFC 822</dref> should
1359 $B$O(B us-ascii $B$r;X$9$b$N$H2r<a$9$Y$-$G$"$k!#(B 1337 be interpreted as us-ascii.
1360 1338
1361 1339
1362 <h1> Setting 1340 <h1> Setting
1363 <node> Setting 1341 <node> Setting
1364 <p> 1342 <p>
1566 <noindent> 1544 <noindent>
1567 Since the user registration is done manually, please write the mail 1545 Since the user registration is done manually, please write the mail
1568 body in human-recognizable language (^_^). 1546 body in human-recognizable language (^_^).
1569 1547
1570 1548
1549 <h1> Acknowledgments
1550 <node> Acknowledgments
1551 <p>
1552 I thank MASUTANI Yasuhiro. He requested me a lot of important
1553 features and gave me a lot of suggestions when tm-view was born.
1554 tm-view is based on his influence.
1555 <p>
1556 I thank ENAMI Tsugutomo for work of <file>mime.el</file>, which is an
1557 origin of <file>tm-ew-d.el</file> and <file>mel-b.el</file>, and
1558 permission to rewrite for tm.
1559 <p>
1560 I thank OKABE Yasuo for work of internal method for LaTeX and
1561 automatic assembling method for message/partial. I thank UENO
1562 Hiroshi for work of internal method for tar archive.
1563 <p>
1564 I thank UMEDA Masanobu for his work of <file>mime.el</file>, which is
1565 the origin of tm-edit, and permission to rewrite his work as tm-edit.
1566 <p>
1567 I thank KOBAYASHI Shuhei for his work as a tm maintainer. In
1568 addition, he often points out or suggests about conformity with RFCs.
1569 <p>
1570 I thank Oscar Figueiredo for his work as the maintainer of tm-vm. He
1571 improves tm-vm and wrote a good manual of tm-vm.
1572 <p>
1573 Last of all, I thank members of two tm mailing lists, Japanese and
1574 English version.
1575
1576
1571 <h1> Concept Index 1577 <h1> Concept Index
1572 <node> Concept Index 1578 <node> Concept Index
1573 1579
1574 <cindex> 1580 <cindex>
1575 1581