2 @setfilename mime-en.info
3 @settitle{FLIM 1.9 Manual about MIME Features}
5 @title FLIM 1.9 Manual about MIME Features
6 @author MORIOKA Tomohiko <morioka@@jaist.ac.jp>
9 @node Top, Introduction, (dir), (dir)
10 @top FLIM 1.9 Manual about MIME Features
14 This file documents MIME features of FLIM, a Internet message
15 parsing/encoding library for GNU Emacs.
19 * Introduction:: What is FLIM?
20 * How to use:: How to use MIME features
21 * Entity:: Message and Entity
22 * Content-Type:: Information of Content-Type field
23 * Content-Disposition:: Information of Content-Disposition field
24 * Content-Transfer-Encoding:: Encoding Method
25 * encoded-word:: Network representation of header
26 * custom:: Various Customization
33 @node Introduction, How to use, Top, Top
34 @chapter What is FLIM?
36 FLIM is a library to provide basic features about message
37 representation or encoding.
40 @node How to use, Entity, Introduction, Top
41 @chapter How to use MIME features
43 Please eval following to use MIME features provided by FLIM:
51 @node Entity, Content-Type, How to use, Top
52 @chapter Message and Entity
56 According to RFC 2045 (@ref{RFC 2045}), `The term ``entity'', refers
57 specifically to the MIME-defined header fields and contents of either a
58 message or one of the parts in the body of a multipart entity.' In this
59 document, the term @strong{entity} indicates all of header fields and
62 The definition of RFC 2045 indicates that a MIME message is a tree, and
63 each node of the tree is an entity. Namely MIME extends message to tree
66 FLIM uses @strong{mime-entity} structure to represent
67 information of entity. In this document, it is called simply
72 * Entity creation:: Functions to create mime-entity
73 * Entity hierarchy:: Features about message tree
74 * Entity Attributes:: Functions about attributes of mime-entity
75 * Entity-header:: Information of entity header
76 * Entity-content:: Contents of Entity
77 * Entity buffer:: Entity as buffer representation
78 * mm-backend:: Entity representations and implementations
81 @node Entity creation, Entity hierarchy, Entity, Entity
82 @section Functions to create mime-entity
84 @defun mime-open-entity &optional type location
86 Open an entity and return it.@refill
88 @var{type} is representation-type. (cf. @ref{mm-backend}) @refill
90 @var{location} is location of entity. Specification of it is depended
91 on representation-type.
95 @defun mime-parse-buffer &optional buffer type
97 Parse @var{buffer} as message, and set the result to buffer local
98 variable @code{mime-message-structure} of @var{buffer} as
101 If @var{buffer} is omitted, current buffer is used.@refill
103 @var{type} is representation-type of created
104 mime-entity. (cf. @ref{mm-backend}) Default value is @var{buffer}.
109 @node Entity hierarchy, Entity Attributes, Entity creation, Entity
110 @section Features about message tree
112 @cindex entity-number
116 MIME message
\e$B$O
\e(B entity
\e$B$rC10L$H$9$kLZ9=B$$K$J$C$F$$$^$9!#
\e(B@refill
118 \e$B$3$NLZ$K$*$$$F:,$H$J$k@a$O
\e(B message
\e$BA4BN$rI=$9
\e(B entity
\e$B$G$9!#$3$3$G$O!"$3
\e(B
119 \e$B$l$r
\e(B @strong{root-entity}
\e$B$b$7$/$O
\e(B@strong{message}
\e$B$H8F$S$^$9!#
\e(B@refill
121 root-entity
\e$B0J30$N
\e(B entity
\e$B$O?F$r;}$A$^$9!#$^$?!"
\e(Bentity
\e$B$O;R6!$r;}$D$+$b
\e(B
122 \e$BCN$l$^$;$s!#$3$N?F;R4X78$r9M$($k$3$H$G
\e(B entity
\e$B$NAjBP4X78$r07$&$3$H$,$G$-
\e(B
123 \e$B$^$9!#
\e(B@refill
125 \e$B0lJ}!"
\e(Bentity
\e$B$N
\e(B message
\e$B$K$*$1$k0LCV$r9M$($k$3$H$b$G$-$^$9!#
\e(B@refill
127 entity
\e$B$O$3$NLZ$K$*$1$k@a$H$J$j$^$9$,!"$3$NLZ$K$O?<$5$HF1$8?<$5$NCf$N
\e(B
128 \e$B=gHV$K=>$C$FHV9f$,IU$1$k$3$H$,$G$-$^$9!#B($A!"
\e(B
132 \e$B("
\e(B nil
\e$B("
\e(B
134 \e$B(#(!(!(!(!(!(!(!(!(!(+(!(!(!(!(!(!(!(!(!($
\e(B
135 \e$B(#(*($
\e(B
\e$B(#(*($
\e(B
\e$B(#(*($
\e(B
136 \e$B("#0("
\e(B
\e$B("#1("
\e(B
\e$B("#2("
\e(B
137 \e$B(&(((%
\e(B
\e$B(&(((%
\e(B
\e$B(&(((%
\e(B
138 \e$B("
\e(B
\e$B(#(!(!(!(!(+(!(!(!(!($
\e(B
\e$B("
\e(B
139 \e$B(#(!(*(!($(#(!(*(!($(#(!(*(!($(#(!(*(!($(#(!(*(!($
\e(B
140 \e$B("
\e(B
\e$B#0
\e(B.
\e$B#0("("
\e(B
\e$B#1
\e(B.
\e$B#0("("
\e(B
\e$B#1
\e(B.
\e$B#1("("
\e(B
\e$B#1
\e(B.
\e$B#2("("
\e(B
\e$B#2
\e(B.
\e$B#0("
\e(B
141 \e$B(&(!(!(!(%(&(!(!(!(%(&(!(!(!(%(&(!(!(!(%(&(!(!(!(%
\e(B
145 \e$B$N$h$&$K?<$5
\e(B n
\e$B$N@a$K$OD9$5
\e(B n
\e$B$N@0?tNs$N@aHV9f$,?6$l$^$9!#$3$l
\e(B
146 \e$B$r
\e(B @strong{entity-number}
\e$B$H8F$S$^$9!#
\e(Bentity-number
\e$B$O
\e(B S
\e$B<0$H
\e(B
147 \e$B$7$F$O
\e(B @code{(1 2 3)}
\e$B$N$h$&$J@0?t$N%j%9%H$H$7$FI=8=$5$l$^$9!#
\e(B
149 mime-entity
\e$B$G$O!"$3$l$HF1MM$N
\e(B @strong{node-id}
\e$B$rMQ$$$^$9!#
\e(Bnode-id
\e$B$O$A$g
\e(B
150 \e$B$&$I
\e(B entity-number
\e$B$r5U$K$7$?%j%9%H$G!"
\e(Bentity-number 1.2.3
\e$B$KBP1~$9$k
\e(B
151 node-id
\e$B$O
\e(B @code{(3 2 1)}
\e$B$G$9!#
\e(B@refill
153 \e$BA0=R$N$h$&$K!"
\e(BMIME message
\e$B$O
\e(B entity
\e$B$rC10L$H$7$?LZ9=B$$K$J$C$F$$$k$N$G!"
\e(B
154 \e$B$3$N:,$G$"$k
\e(B message
\e$BA4BN$b
\e(B mime-entity
\e$B$GI=8=$9$k$3$H$,$G$-!"
\e(Bbuffer
155 local
\e$BJQ?t
\e(B @code{mime-message-structure}
\e$B$K3JG<$9$k$3$H$K$7$^$9!#
\e(B@refill
157 @code{mime-message-structure}
\e$B$r5/E@$K
\e(B entity-number
\e$B$d
\e(B node-id
158 \e$B$G<($5$l$k
\e(B entity
\e$B$r<h$j=P$9$3$H$,$G$-$^$9!#
\e(B
160 @defvar mime-message-structure
162 Buffer local variable to store mime-entity structure of message.
166 @defun mime-entity-children entity
168 Return list of entities included in the @var{entity}.
172 @defun mime-entity-parent entity &optional message
174 Return parent entity of the @var{entity}.@refill
176 If @var{message} is specified, it is regarded as root instead of
177 @code{mime-message-structure}.
181 @defun mime-root-entity-p entity
183 Return non-@code{nil} if @var{entity} is root entity (message).
187 @defun mime-entity-node-id entity
189 Return node-id of @var{entity}.
193 @defun mime-entity-number entity
195 Return entity-number of @var{entity}.
199 @defun mime-find-entity-from-number entity-number &optional message
201 Return entity from @var{entity-number} in @var{message}.@refill
203 If @var{message} is not specified, @code{mime-message-structure} is
208 @defun mime-find-entity-from-node-id entity-node-id &optional message
210 Return entity from @var{entity-node-id} in @var{message}.@refill
212 If @var{message} is not specified, @code{mime-message-structure} is
218 @node Entity Attributes, Entity-header, Entity hierarchy, Entity
219 @section Functions about attributes of mime-entity
221 @defun mime-entity-content-type entity
223 Return content-type of @var{entity}. (cf. @ref{mime-content-type})
227 @defun mime-entity-content-disposition entity
229 Return content-disposition of
230 @var{entity}. (cf. @ref{mime-content-disposition})
234 @defun mime-entity-filename entity
236 Return file name of @var{entity}.
240 @defun mime-entity-encoding entity &optional default-encoding
242 Return content-transfer-encoding of @var{entity}.
243 (cf. @ref{Content-Transfer-Encoding}) @refill
245 If the @var{entity} does not have Content-Transfer-Encoding field, this
246 function returns @var{default-encoding}. If it is nil, @code{"7bit"} is
247 used as default value.
251 @defun mime-entity-cooked-p entity
253 Return non-nil if contents of @var{entity} has been already
259 @node Entity-header, Entity-content, Entity Attributes, Entity
260 @section Information of entity header
262 @defun mime-fetch-field field-name &optional entity
264 Return field-body of @var{field-name} field in header of
267 The results is network representation.@refill
269 If @var{entity} is omitted, @code{mime-message-structure} is used as
270 default value.@refill
272 If @var{field-name} field is not found, this function returns
277 @defun mime-read-field field-name &optional entity
279 Parse @var{field-name} field in header of @var{entity}, and return the
282 Format of result is depended on kind of field. For non-structured
283 field, this function returns string. For structured field, it returns
284 list corresponding with structure of the field.@refill
286 Strings in the result will be converted to internal representation of
289 If @var{entity} is omitted, @code{mime-message-structure} is used as
290 default value.@refill
292 If @var{field-name} field is not found, this function returns
297 @defun mime-insert-decoded-header entity &optional invisible-fields visible-fields
299 Insert before point a decoded contents of header of @var{entity}.@refill
301 @var{invisible-fields} is list of regexps to match field-name to hide.
302 @var{visible-fields} is list of regexps to match field-name to
305 If a field-name is matched with some elements of @var{invisible-fields}
306 and matched with none of @var{visible-fields}, this function don't
312 @node Entity-content, Entity buffer, Entity-header, Entity
313 @section Contents of Entity
315 @defun mime-entity-content entity
317 Return content of @var{entity} as byte sequence.
321 @defun mime-write-entity-content entity filename
323 Write content of @var{entity} into @var{filename}.
327 @defun mime-write-entity entity filename
329 Write representation of @var{entity} into @var{filename}.
333 @defun mime-write-entity-body entity filename
335 Write body of @var{entity} into @var{filename}.
340 @node Entity buffer, mm-backend, Entity-content, Entity
341 @section Entity as buffer representation
343 @defun mime-entity-buffer entity
345 Return buffer, which contains @var{entity}.
349 @defun mime-entity-point-min entity
351 Return the start point of @var{entity} in the buffer which contains
356 @defun mime-entity-point-max entity
358 Return the end point of @var{entity} in the buffer which contains
363 @defun mime-entity-header-start entity
365 Return the start point of header of @var{entity} in the buffer which
366 contains @var{entity}.
370 @defun mime-entity-header-end entity
372 Return the end point of header of @var{entity} in the buffer which
373 contains @var{entity}.
377 @defun mime-entity-body-start entity
379 Return the start point of body of @var{entity} in the buffer which
380 contains @var{entity}.
384 @defun mime-entity-body-end entity
386 Return the end point of body of @var{entity} in the buffer which
387 contains @var{entity}.
392 @node mm-backend, , Entity buffer, Entity
393 @section Entity representations and implementations
395 @cindex entity
\e$B=hM}
\e(B method
396 @cindex representation-type
398 Entity is an abstraction. It is designed to use various data
399 representations for their purposes.@refill
401 Each entity has @strong{representation-type}. It must be specified when
402 an entity is created. (cf. @ref{Entity Creation}) @refill
404 \e$BA0@a$^$G$K=R$Y$FMh$?
\e(B entity
\e$B$KBP$9$k=hM}$O!"
\e(Bentity
\e$B$KBP$7$F$=$N=hM}$r0M
\e(B
405 \e$BMj$9$k$3$H$K$h$C$F<B8=$5$l$F$$$^$9!#
\e(BEntity
\e$B$O<+J,$N
\e(B representation-type
406 \e$B$rCN$C$F$*$j!"$=$N
\e(B representation-type
\e$B$K1~$8$F<B:]$N=hM}$r9T$&4X?t$r8F
\e(B
407 \e$B$S=P$7$^$9!#$3$N$h$&$J4X?t$r
\e(B @strong{entity
\e$B=hM}
\e(Bmethod}
\e$B$H8F$S$^$9!#$^$?!"
\e(B
408 representation-type
\e$BKh$K$3$N$h$&$J4X?t$r$^$H$a$?$b$N$r
\e(B
409 @strong{mm-backend}
\e$B$H8F$S$^$9!#
\e(B@refill
411 mm-backend
\e$B$O
\e(B representation-type
\e$B$NL>A0$N@hF,$K
\e(B @code{mm}
\e$B$H$$$&
\e(B
412 \e$B@\F,<-$rIU$1$?4X?tL>$+$i$J$k
\e(B module
\e$B$G!"$=$N
\e(B module
\e$BL>$OF1MM$K
\e(B
413 representation-type
\e$B$NL>A0$N@hF,$K
\e(B @code{mm}
\e$B$rIU$1$?$b$N$K$J$C$F
\e(B
414 \e$B$$$^$9!#$3$N
\e(B module
\e$B$O
\e(B representation-type
\e$B$N
\e(B entity
\e$B$,:G=i$K@8@.$5$l$k
\e(B
415 \e$B;~$K<+F0E*$K
\e(B require
\e$B$5$l$^$9!#
\e(B
419 * Request for entity:: Message-passing for entity
420 * mm-backend module:: How to make mm-backend
423 @node Request for entity, mm-backend module, mm-backend, mm-backend
424 @subsection Message-passing for entity
426 @defun mime-entity-send entity message &rest args
428 @var{entity}
\e$B$K
\e(B @var{message}
\e$B$rAw$k!#
\e(B@refill
430 @var{args}
\e$B$O
\e(B @var{message}
\e$B$N0z?t$G$"$k!#
\e(B
435 @node mm-backend module, , Request for entity, mm-backend
436 @subsection How to make mm-backend
438 \e$B!J$9$_$^$;$s!#$=$N$&$A=q$-$^$9
\e(B (^_^;
\e$B!K
\e(B@refill
440 \e$B!J$H$j$"$($:!"
\e(Bmm*.el
\e$B$r;29M$K$7$F$/$@$5$$!K
\e(B
443 @node Content-Type, Content-Disposition, Entity, Top
444 @chapter Information of Content-Type field
445 @cindex mime-content-type
446 @cindex Content-Type field
448 @strong{Content-Type field} is a field to indicate kind of contents or
449 data format, such as media-type (@ref{media-type}) and MIME charset. It
450 is defined in RFC 2045 (@ref{RFC 2045}).
456 Historically, Content-Type field was proposed in RFC 1049. In it,
457 Content-Type did not distinguish type and subtype, and there are no
458 mechanism to represent kind of character code like MIME charset.
462 FLIM provides parser for Content-Type field and structure
463 @strong{mime-content-type} to store information of
468 * Content-Type field:: Format of Content-Type field
469 * mime-content-type:: mime-content-type structure
470 * Content-Type parser:: Parser
471 * Content-Type utility:: Utility functions
474 @node Content-Type field, mime-content-type, Content-Type, Content-Type
475 @section Format of Content-Type field
480 Content-Type
\e$BMs$N7A<0$O0J2<$N$h$&$KDj5A$5$l$F$$$^$9!'
\e(B
483 ``Content-Type'' ``:'' @strong{type} ``/''
484 @strong{subtype} *( ``;'' @strong{parameter} )
491 Content-Type: image/jpeg
500 Content-Type: text/plain; charset=iso-2022-jp
505 \e$B$J$I$N$h$&$KMQ$$$i$l$^$9!#
\e(B
507 \e$B$3$3$G!"
\e(B`type'
\e$B$H
\e(B `subtype'
\e$B$O
\e(B entity
\e$B$N7A<0$r<($9$b$N$G!"N><T$rAm>N$7
\e(B
508 \e$B$F!"
\e(B`media-type'
\e$B$H8F$V$3$H$K$7$^$9!#>e5-$NNc$K$*$1$k
\e(B `image/jpeg'
\e$B$d
\e(B
509 `text/plain'
\e$B$O
\e(B media-type
\e$B$N#1$D$G$9!#
\e(B
515 Content-Type
\e$BMs$N$J$$
\e(B entity
\e$B$O
\e(B
519 Content-Type: text/plain; charset=us-ascii
524 \e$B$H$7$F2r<a$5$l$k!#
\e(B(cf. @ref{us-ascii})
529 @node mime-content-type, Content-Type parser, Content-Type field, Content-Type
530 @section mime-content-type structure
532 @deffn{Structure} mime-content-type
534 Content-Type
\e$BMs$N>pJs$r3JG<$9$k$?$a$N9=B$BN!#
\e(B@refill
536 \e$B$3$N9=B$BN$r;2>H$9$k$K$O
\e(B @code{mime-content-type-
\e$BMWAGL>
\e(B}
\e$B$H$$$&L>A0$N;2
\e(B
537 \e$B>H4X?t$rMQ$$$k!#
\e(B@refill
539 \e$B$3$N9=B$BN$NMWAG$O0J2<$NDL$j$G$"$k!'
\e(B
543 media-type
\e$B$N<g7?
\e(B (symbol).
546 media-type
\e$B$NI{7?
\e(B (symbol).
549 Content-Type
\e$BMs$N
\e(B parameter (
\e$BO"A[
\e(B list).
555 @defun make-mime-content-type type subtype
558 content-type
\e$B$N@8@.;R!#
\e(B
562 @defun mime-content-type-parameter content-type parameter
564 @var{content-type}
\e$B$N
\e(B @var{parameter}
\e$B$NCM$rJV$9!#
\e(B
569 @node Content-Type parser, Content-Type utility, mime-content-type, Content-Type
572 @defun mime-parse-Content-Type string
574 @var{string}
\e$B$r
\e(B content-type
\e$B$H$7$F2r@O$7$?7k2L$rJV$9!#
\e(B
578 @defun mime-read-Content-Type
580 \e$B8=:_$N
\e(B buffer
\e$B$N
\e(B Content-Type
\e$BMs$rFI$_<h$j!"2r@O$7$?7k2L$rJV$9!#
\e(B@refill
582 Content-Type
\e$BMs$,B8:_$7$J$$>l9g$O
\e(B nil
\e$B$rJV$9!#
\e(B
587 @node Content-Type utility, , Content-Type parser, Content-Type
588 @section Utility functions
590 @defun mime-type/subtype-string type &optional subtype
592 Return type/subtype string from @var{type} and @var{subtype}.
597 @node Content-Disposition, Content-Transfer-Encoding, Content-Type, Top
598 @chapter Information of Content-Disposition field
599 @cindex mime-content-disposition
601 @cindex Standards Track
602 @cindex Content-Disposition
\e$BMs
\e(B
604 @strong{Content-Disposition
\e$BMs
\e(B}
\e$B$O
\e(B entity
\e$B$NI=<($d
\e(B file
\e$BL>$J$I
\e(B
605 \e$B$NB0@-$K$J$I$K4X$9$k>pJs$r5-=R$9$k$?$a$N$b$N$G$9!#
\e(B
611 S. Dorner, K. Moore and R. Troost, ``Communicating Presentation
612 Information in Internet Messages: The Content-Disposition Header'',
613 August 1997, Standards Track.
616 FLIM
\e$B$O
\e(B Content-Disposition
\e$BMs$r9=J82r@O$9$k4X?t$H
\e(B Content-Disposition
617 \e$BMs$N2r@O7k2L$r3JG<$9$k9=B$BN
\e(B
618 @strong{mime-content-disposition}
\e$B$rDs6!$7$^$9!#
\e(B
622 * mime-content-disposition:: mime-content-disposition structure
623 * Content-Disposition parser:: Parser for Content-Disposition field
626 @node mime-content-disposition, Content-Disposition parser, Content-Disposition, Content-Disposition
627 @section mime-content-disposition structure
629 @deffn{Structure} mime-content-disposition
631 Content-Disposition
\e$BMs$N2r@O7k2L$r<}$a$k$?$a$N9=B$BN!#
\e(B@refill
633 \e$B$3$N9=B$BN$r;2>H$9$k$K$O
\e(B @code{mime-content-disposition-
\e$BMWAGL>
\e(B}
\e$B$H$$$&L>
\e(B
634 \e$BA0$N;2>H4X?t$rMQ$$$k!#
\e(B@refill
636 \e$B$3$N9=B$BN$NMWAG$O0J2<$NDL$j$G$"$k!'
\e(B
639 @item disposition-type
640 disposition-type (symbol).
643 Content-Disposition
\e$BMs$N
\e(B parameter (
\e$BO"A[
\e(B list).
649 @defun mime-content-disposition-parameter content-disposition parameter
651 @var{content-disposition}
\e$B$N
\e(B @var{parameter}
\e$B$NCM$rJV$9!#
\e(B
655 @defun mime-content-disposition-filename content-disposition
657 @var{content-disposition}
\e$B$N
\e(B filename
\e$B$NCM$rJV$9!#
\e(B
662 @node Content-Disposition parser, , mime-content-disposition, Content-Disposition
663 @section Parser for Content-Disposition field
665 @defun mime-parse-Content-Disposition string
667 @var{string}
\e$B$r
\e(B content-disposition
\e$B$H$7$F2r@O$7$?7k2L$rJV$9!#
\e(B
671 @defun mime-read-Content-Disposition
673 \e$B8=:_$N
\e(B buffer
\e$B$N
\e(B Content-Disposition
\e$BMs$rFI$_<h$j!"2r@O$7$?7k2L$rJV$9!#
\e(B
676 Content-Disposition
\e$BMs$,B8:_$7$J$$>l9g$O
\e(B nil
\e$B$rJV$9!#
\e(B
681 @node Content-Transfer-Encoding, encoded-word, Content-Disposition, Top
682 @chapter Encoding Method
683 @cindex Content-Transfer-Encoding
\e$BMs
\e(B
685 @strong{Content-Transfer-Encoding
\e$BMs
\e(B}
\e$B$O
\e(B entity
\e$B$NId9f2=K!$r5-=R$9$k$?$a
\e(B
686 \e$B$N$b$N$G$9!#
\e(B@refill
688 FLIM
\e$B$G$O
\e(B Content-Transfer-Encoding
\e$BMs$r9=J82r@O$9$k4X?t$rDs6!$7$^$9!#$3
\e(B
689 \e$B$l$i$N4X?t$O
\e(B Content-Transfer-Encoding
\e$BMs$N>pJs$OJ8;zNs$GI=8=$7$^$9!#
\e(B
692 \e$B$^$?!"
\e(BContent-Transfer-Encoding
\e$B$K4p$E$$$FId9f2=!&I|9f2=$r9T$&4X?t$bDs
\e(B
697 * Content-Transfer-Encoding parser:: Parser
698 * Region encoder/decoder:: Region encoding/decoding
699 * String encoder/decoder:: String encoding/decoding
700 * File encoder/decoder:: File encoding/decoding
703 @node Content-Transfer-Encoding parser, Region encoder/decoder, Content-Transfer-Encoding, Content-Transfer-Encoding
706 @defun mime-parse-Content-Transfer-Encoding string
708 @var{string}
\e$B$r
\e(B content-transfer-encoding
\e$B$H$7$F2r@O$7$?7k2L$rJV$9!#
\e(B
712 @defun mime-read-Content-Transfer-Encoding &optional default-encoding
714 \e$B8=:_$N
\e(B buffer
\e$B$N
\e(B Content-Transfer-Encoding
\e$BMs$rFI$_<h$j!"2r@O$7$?7k2L$r
\e(B
715 \e$BJV$9!#
\e(B@refill
717 Content-Transfer-Encoding
\e$BMs$,B8:_$7$J$$>l9g$O
\e(B@var{default-encoding}
\e$B$r
\e(B
723 @node Region encoder/decoder, String encoder/decoder, Content-Transfer-Encoding parser, Content-Transfer-Encoding
724 @section Region encoding/decoding
726 @defun mime-encode-region start end encoding
728 Encode region @var{start} to @var{end} of current buffer using
733 @defun mime-decode-region start end encoding
735 Decode region @var{start} to @var{end} of current buffer using
740 @defvar mime-encoding-method-alist
742 Alist of encoding vs. corresponding method to encode region.@refill
744 Each element looks like @code{(STRING . FUNCTION)} or @code{(STRING
745 . nil)}. @var{string} is content-transfer-encoding. @code{function} is
746 region encoder and @code{nil} means not to encode.
750 @defvar mime-decoding-method-alist
752 Alist of encoding vs. corresponding method to decode region.@refill
754 Each element looks like @code{(STRING . FUNCTION)} or @code{(STRING
755 . nil)}. @var{string} is content-transfer-encoding. @code{function} is
756 region decoder and @code{nil} means not to decode.
761 @node String encoder/decoder, File encoder/decoder, Region encoder/decoder, Content-Transfer-Encoding
762 @section String encoding/decoding
764 @defun mime-decode-string string encoding
766 @var{string}
\e$B$r
\e(B @var{encoding}
\e$B$H$7$FI|9f$7$?7k2L$rJV$7$^$9!#
\e(B
770 @defvar mime-string-decoding-method-alist
772 Alist of encoding vs. corresponding method to decode string.@refill
774 Each element looks like @code{(STRING . FUNCTION)}. STRING is
775 content-transfer-encoding. FUNCTION is string decoder.
780 @node File encoder/decoder, , String encoder/decoder, Content-Transfer-Encoding
781 @section File encoding/decoding
783 @defun mime-insert-encoded-file filename encoding
785 Insert file @var{FILENAME} encoded by @var{ENCODING} format.
789 @defun mime-write-decoded-region start end filename encoding
791 Decode and write current region encoded by @var{encoding} into
792 @var{filename}.@refill
794 @var{start} and @var{end} are buffer positions.
798 @defvar mime-file-encoding-method-alist
800 Alist of encoding vs. corresponding method to insert encoded
803 Each element looks like @code{(STRING . FUNCTION)}. STRING is
804 content-transfer-encoding. FUNCTION is function to insert encoded file.
808 @defvar mime-file-decoding-method-alist
810 Alist of encoding vs. corresponding method to write decoded region to
813 Each element looks like @code{(STRING . FUNCTION)}. STRING is
814 content-transfer-encoding. FUNCTION is function to write decoded region
820 @node encoded-word, custom, Content-Transfer-Encoding, Top
821 @chapter Network representation of header
823 @cindex Standards Track
826 encoded-word
\e$B$O
\e(B header
\e$B$GHs
\e(B ASCII (@ref{ASCII})
\e$BJ8;z$rI=8=$9$k$?$a$N7A<0
\e(B
827 \e$B$G!"
\e(B@strong{RFC 2047}
\e$B$GDj5A$5$l$F$$$^$9!#
\e(B@refill
833 K. Moore, ``MIME (Multipurpose Internet Mail Extensions) Part Three:
834 Message Header Extensions for Non-ASCII Text'', November 1996, Standards
835 Track (obsolete RFC 1521,1522,1590).
838 \e$B$^$?!"9T57$N0-$$$3$H$@$H8@$($^$9$,!"
\e(Bencoded-word
\e$B$rMQ$$$:$KHs
\e(B ASCII
839 (@ref{ASCII})
\e$BJ8;z$r
\e(B header
\e$B$KF~$l$?5-;v$bB8:_$7$^$9!#
\e(B@refill
841 FLIM
\e$B$O$3$l$i$rId9f2=!&I|9f2=$9$k5!G=$rDs6!$7$^$9!#
\e(B
845 * Header encoder/decoder:: Header encoding/decoding
848 @node Header encoder/decoder, , encoded-word, encoded-word
849 @section Header encoding/decoding
851 @defun eword-encode-header &optional code-conversion separator
853 Decode MIME encoded-words in header fields.@refill
855 If @var{code-conversion} is @code{nil}, it decodes only encoded-words.
856 If it is mime-charset, it decodes non-ASCII bit patterns as the
857 mime-charset. Otherwise it decodes non-ASCII bit patterns as the
858 default-mime-charset.@refill
860 If @var{separator} is not nil, it is used as header separator.
864 @defun eword-encode-header &optional code-conversion
866 Encode header fields to network representation, such as MIME
869 It refer variable @code{eword-field-encoding-method-alist}.
874 @node custom, Appendix, encoded-word, Top
875 @chapter Various Customization
879 MIME
\e$B4XO"5!G=$K4X$9$k
\e(B group.@refill
881 @code{mail}
\e$B$H
\e(B @code{news}
\e$B$KB0$9$k!#
\e(B
885 @defvar default-mime-charset
887 \e$BE,@Z$J
\e(B MIME charset (@ref{MIME charset})
\e$B$,8+$D$+$i$J$+$C$?>l9g$KMQ$$$i
\e(B
888 \e$B$l$k
\e(BMIME charset.@refill
890 \e$BK\Mh$O
\e(B APEL
\e$B$NJQ?t$G$"$k!#
\e(B
894 @defvar mime-temp-directory
896 MIME
\e$B5!G=$K4X$9$k<BAu$,0l;~E*$K;HMQ$9$k
\e(B file
\e$B$r:n@.$9$k
\e(B
899 \e$B4D6-JQ?t
\e(B @code{MIME_TMP_DIR}, @code{TM_TMP_DIR}, @code{TMPDIR},
900 @code{TMP}
\e$B$b$7$/$O
\e(B @code{TEMP}
\e$B$,@_Dj$5$l$F$$$?>l9g!"$=$l$r=i4|CM$H$7$F
\e(B
901 \e$BMQ$$$k!#2?$b@_Dj$5$l$F$$$J$$>l9g!"
\e(B@code{"/tmp/"}
\e$B$rMQ$$$k!#
\e(B
906 @node Appendix, Concept Index, custom, Top
912 * Bug report:: How to report bugs
913 * CVS:: CVS based development
914 * History:: History of FLIM
917 @node Glossary, Bug report, Appendix, Appendix
927 * coded character set:: Coded character set, Character code
945 @node 7bit, 8bit, Glossary, Glossary
947 @cindex 7bit (textual) string
951 @strong{7bit} means any integer between 0 .. 127.@refill
953 Any data represented by 7bit integers is called @strong{7bit data}.@refill
955 Textual string consisted of Control characters between 0 .. 31 and 127,
956 and space represented by 32, and graphic characters between 33 .. 236
957 are called @strong{7bit (textual) string}.@refill
959 Conventional Internet MTA (@ref{MTA}) can translate 7bit data, so it is
960 no need to translate by Quoted-Printable (@ref{Quoted-Printable}) or
961 Base64 (@ref{Base64}) for 7bit data.@refill
963 However if there are too long lines, it can not translate by 7bit MTA
964 even if it is 7bit data. RFC 821 (@ref{RFC 821}) and RFC 2045 (@ref{RFC 2045}) require lines in 7bit data must be less than 998 bytes. So if a
965 ``7bit data'' has a line more than 999 bytes, it is regarded as binary
966 (@ref{binary}). For example, Postscript file should be encoded by
970 @node 8bit, ASCII, 7bit, Glossary
972 @cindex 8bit (textual) string
976 @strong{8bit} means any integer between 0 .. 255.@refill
978 Any data represented by 8bit integers is called @strong{8bit data}.@refill
980 Textual string consisted of Control characters between 0 .. 31, 127, and
981 128 .. 159, and space represented by 32, and graphic characters between
982 33 .. 236 and 160 .. 255 are called @strong{8bit (textual) string}.@refill
984 For example, iso-8859-1 (@ref{iso-8859-1}) or euc-kr (@ref{euc-kr}) are
985 coded-character-set represented by 8bit textual string.@refill
987 Traditional Internet MTA (@ref{MTA}) can translate only 7bit
988 (@ref{7bit}) data, so if a 8bit data will be translated such MTA, it
989 must be encoded by Quoted-Printable (@ref{Quoted-Printable}) or Base64
990 (@ref{Base64}).@refill
992 However 8bit MTA are increasing today.@refill
994 However if there are too long lines, it can not translate by 8bit MTA
995 even if it is 8bit data. RFC 2045 (@ref{RFC 2045}) require lines in
996 8bit data must be less than 998 bytes. So if a ``8bit data'' has a line
997 more than 999 bytes, it is regarded as binary (@ref{binary}), so it must
998 be encoded by Base64 or Quoted-Printable.
1001 @node ASCII, Base64, 8bit, Glossary
1003 @cindex ANSI X3.4:1986
1007 @strong{ASCII} is a 94-character set contains primary latin characters
1008 (A-Z, a-z), numbers and some characters. It is a standard of the United
1009 States of America. It is a variant of ISO 646 (@ref{ISO 646}).
1015 ``Coded Character Set -- 7-Bit American Standard Code for Information
1016 Interchange'', ANSI X3.4:1986.
1021 @node Base64, binary, ASCII, Glossary
1026 @strong{Base64} is a transfer encoding method of MIME (@ref{MIME})
1027 defined in RFC 2045 (@ref{RFC 2045}).@refill
1029 The encoding process represents 24-bit groups of input bits as output
1030 strings of 4 encoded characters. Encoded characters represent integer 0
1031 .. 63 or @strong{pad}. Base64 data must be 4 * n bytes, so pad is used
1032 to adjust size.@refill
1034 These 65 characters are subset of all versions of ISO 646, including
1035 US-ASCII, and all versions of EBCDIC. So it is safe even if it is
1036 translated by non-Internet gateways.
1039 @node binary, coded character set, Base64, Glossary
1043 Any byte stream is called @strong{binary}.@refill
1045 It does not require structureof lines. It differs from from 8bit
1046 (@ref{8bit}).@refill
1048 In addition, if line structured data contain too long line (more than
1049 998 bytes), it is regarded as binary.
1052 @node coded character set, media-type, binary, Glossary
1053 @subsection Coded character set, Character code
1055 A set of unambiguous rules that establishes a character set and the
1056 one-to-one relationship between the characters of the set and their
1060 @node media-type, message, coded character set, Glossary
1061 @subsection media-type
1074 @strong{media-type} specifies the nature of the data in the body of MIME
1075 (@ref{MIME}) entity (@ref{entity}). It consists of @strong{type} and
1076 @strong{subtype}. It is defined in RFC 2046 (@ref{RFC 2046}).@refill
1078 Currently there are following standard primary-types:
1090 @strong{application}
1092 @strong{multipart} (@ref{multipart})
1098 And there are various subtypes, for example, application/octet-stream,
1099 audio/basic, image/jpeg, multipart/mixed (@ref{multipart/mixed}),
1100 text/plain (@ref{text/plain}), video/mpeg... @refill
1102 You can refer registered media types at MEDIA TYPES
1103 (ftp://ftp.isi.edu/in-notes/iana/assignments/media-types).@refill
1105 In addition, you can use private type or subtype using @strong{x-token},
1106 which as the prefix `x-'. However you can not use them in
1109 (cf. @ref{Content-Type field})
1113 @node message, MIME, media-type, Glossary
1116 In this document, it means mail defined in RFC 822 (@ref{RFC 822}) and
1117 news message defined in RFC 1036 (@ref{RFC 1036}).
1120 @node MIME, MIME charset, message, Glossary
1122 @cindex Multipurpose Internet Mail Extensions
1124 MIME stands for @strong{Multipurpose Internet Mail Extensions}, it is an
1125 extension for RFC 822 (@ref{RFC 822}).@refill
1127 According to RFC 2045:@refill
1129 STD 11, RFC 822, defines a message representation protocol specifying
1130 considerable detail about US-ASCII message headers, and leaves the
1131 message content, or message body, as flat US-ASCII text. This set of
1132 documents, collectively called the Multipurpose Internet Mail
1133 Extensions, or MIME, redefines the format of messages to allow for
1137 textual message bodies in character sets other than US-ASCII,
1139 an extensible set of different formats for non-textual message
1142 multi-part message bodies, and
1144 textual header information in character sets other than US-ASCII.
1148 It is defined in RFC 2045 (@ref{RFC 2045}), RFC 2046 (@ref{RFC 2046}),
1149 RFC 2047 (@ref{encoded-word}), RFC 2048 (@ref{RFC 2048}) and RFC 2049
1153 @node MIME charset, MTA, MIME, Glossary
1154 @subsection MIME charset
1156 Coded character set (@ref{coded character set}) used in Content-Type
1157 field (@ref{Content-Type field}) or charset parameter of encoded-word
1158 (@ref{encoded-word}).@refill
1160 It is defined in RFC 2045 (@ref{RFC 2045}).@refill
1162 iso-2022-jp (@ref{iso-2022-jp}) or euc-kr (@ref{euc-kr}) are kinds of
1163 it. (In this document, MIME charsets are written by small letters to
1164 distinguish graphic character set (@ref{graphic character set}). For
1165 example, ISO 8859-1 is a graphic character set, and iso-8859-1 is a MIME
1169 @node MTA, MUA, MIME charset, Glossary
1171 @cindex Message Transfer Agent
1173 @strong{Message Transfer Agent}. It means mail transfer programs
1174 (ex. sendmail) and news servers.@refill
1180 @node MUA, Quoted-Printable, MTA, Glossary
1182 @cindex Message User Agent
1184 @strong{Message User Agent}. It means mail readers and news
1191 @node Quoted-Printable, RFC 822, MUA, Glossary
1192 @subsection Quoted-Printable
1193 @cindex Quoted-Printable
1195 @strong{Quoted-Printable} is a transfer encoding method of MIME
1196 (@ref{MIME}) defined in RFC 2045 (@ref{RFC 2045}).@refill
1198 If the data being encoded are mostly US-ASCII text, the encoded form of
1199 the data remains largely recognizable by humans.@refill
1205 @node RFC 822, RFC 1036, Quoted-Printable, Glossary
1209 @cindex Internet mail
1210 @cindex Internet message
1211 @cindex message header
1213 A RFC defines format of Internet mail message, mainly @strong{message header}.
1219 news message is based on RFC 822, so @strong{Internet message} may be
1220 more suitable than @strong{Internet mail} .
1228 D. Crocker, ``Standard for the Format of ARPA Internet Text Messages'',
1229 August 1982, STD 11.
1234 @node RFC 1036, RFC 2045, RFC 822, Glossary
1235 @subsection RFC 1036
1239 A RFC defines format of USENET message. It is a subset of RFC 822
1240 (@ref{RFC 822}). It is not Internet standard, but a lot of netnews
1241 excepting Usenet uses it.
1247 M. Horton and R. Adams, ``Standard for Interchange of USENET Messages'',
1248 December 1987, (obsolete RFC 850).
1253 @node RFC 2045, RFC 2046, RFC 1036, Glossary
1254 @subsection RFC 2045
1256 @cindex Standards Track
1262 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1263 (MIME) Part One: Format of Internet Message Bodies'', November 1996,
1264 Standards Track (obsolete RFC 1521, 1522, 1590).
1269 @node RFC 2046, RFC 2048, RFC 2045, Glossary
1270 @subsection RFC 2046
1272 @cindex Standards Track
1278 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1279 (MIME) Part Two: Media Types'', November 1996, Standards Track (obsolete
1280 RFC 1521, 1522, 1590).
1285 @node RFC 2048, RFC 2049, RFC 2046, Glossary
1286 @subsection RFC 2048
1288 @cindex Standards Track
1294 N. Freed, J. Klensin and J. Postel, ``Multipurpose Internet Mail
1295 Extensions (MIME) Part Four: Registration Procedures'', November 1996,
1296 Standards Track (obsolete RFC 1521, 1522, 1590).
1301 @node RFC 2049, plain text, RFC 2048, Glossary
1302 @subsection RFC 2049
1304 @cindex Standards Track
1310 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1311 (MIME) Part Five: Conformance Criteria and Examples'', November 1996,
1312 Standards Track (obsolete RFC 1521, 1522, 1590).
1317 @node plain text, us-ascii, RFC 2049, Glossary
1318 @subsection plain text
1320 A textual data represented by only coded character set (@ref{coded character set}). It does not have information about font or
1321 typesetting. (cf. @ref{text/plain})
1325 @node us-ascii, , plain text, Glossary
1326 @subsection us-ascii
1330 A MIME charset (@ref{MIME charset}) for primary Latin script mainly
1331 written by English or other languages.@refill
1333 It is a 7bit coded character set (@ref{coded character set}) based on
1334 ISO 2022 (@ref{ISO 2022}), it contains only ASCII (@ref{ASCII}) and code
1335 extension (@ref{code extension}) is not allowed.@refill
1337 It is standard coded character set of Internet mail. If MIME charset is
1338 not specified, @strong{us-ascii} is used as default.@refill
1340 In addition, @strong{ASCII} of RFC 822 (@ref{RFC 822}) should be
1341 interpreted as us-ascii.
1344 @node Bug report, CVS, Glossary, Appendix
1345 @section How to report bugs
1346 @cindex good bug report
1348 If you write bug-reports and/or suggestions for improvement, please
1349 send them to the tm Mailing List:
1353 Japanese <bug-tm-ja@@chamonix.jaist.ac.jp>
1355 English <bug-tm-en@@chamonix.jaist.ac.jp>
1359 Notice that, we do not welcome bug reports about too old version. Bugs
1360 in old version might be fixed. So please try latest version at
1363 You should write @strong{good bug report}. If you write only ``FLIM
1364 does not work'', we can not find such situations. At least, you should
1365 write name, type, variants and version of OS, emacs, APEL, FLIM, SEMI
1366 and MUA, and setting. In addition, if error occurs, to send backtrace
1367 is very important. (cf. @ref{(emacs)Bugs}) @refill
1369 Bug may not appear only your environment, but also in a lot of
1370 environment (otherwise it might not bug). Therefor if you send mail
1371 to author directly, we must write a lot of mails. So please send mail
1372 to address for tm bugs instead of author.
1374 Via the tm ML, you can report FLIM bugs, obtain the latest release of
1375 FLIM, and discuss future enhancements to FLIM. To join the tm ML,
1376 send empty e-mail to:
1380 Japanese <tm-ja-help@@chamonix.jaist.ac.jp>
1382 English <tm-en-help@@chamonix.jaist.ac.jp>
1387 @node CVS, History, Bug report, Appendix
1388 @section CVS based development
1390 FLIM
\e$B$N
\e(B file
\e$B$O
\e(B CVS
\e$B$r;H$C$F4IM}$5$l$F$$$^$9!#$3$N$?$a!"0J2<$NJ}K!$G:G
\e(B
1391 \e$B?7$N
\e(B FLIM
\e$B$rF~<j$9$k$3$H$,$G$-$^$9!'
\e(B
1396 % cvs -d :pserver:anonymous@@chamonix.jaist.ac.jp:/hare/cvs/root \
1399 CVS password: [CR] # NULL string
1403 % cvs -d :pserver:anonymous@@chamonix.jaist.ac.jp:/hare/cvs/root \
1404 checkout [-r TAG] flim
1408 CVS
\e$B$rMQ$$$?3+H/$K;22C$7$?$$J}$O
\e(B
1412 <cvs@@chamonix.jaist.ac.jp>
1416 \e$B$^$G!"
\e(Baccount
\e$BL>$H
\e(B UNIX
\e$B$N
\e(B passwd
\e$B$HF1$87A<0$N
\e(B crypt
\e$B2=$5$l$?
\e(B password
1417 \e$B$r1h$($F8fO"Mm$/$@$5$$!#
\e(B
1420 @node History, , CVS, Appendix
1421 @section History of FLIM
1423 FLIM
\e$B$N
\e(B code
\e$B$N:G8E$NItJ,$O
\e(B
\e$B1]JB
\e(B
\e$B;LCR
\e(B
\e$B;a$,=q$$$?
\e(B @file{mime.el}
\e$B$K5/8;$7
\e(B
1424 \e$B$^$9!#$3$N>.$5$J
\e(B program
\e$B$O
\e(B Nemacs
\e$B$GF0:n$9$k
\e(B iso-2022-jp
\e$B$N
\e(B B-encoding
1425 \e$B@lMQ$N
\e(B encoded-word
\e$B$NI|9f2=%W%m%0%i%`$G$7$?!#
\e(B@refill
1427 \e$B$=$N8e!"<i2,
\e(B
\e$BCNI'
\e(B
\e$B$O
\e(B @file{mime.el}
\e$B$r85$K
\e(B@file{tiny-mime.el}
\e$B$H$$$&%W%m
\e(B
1428 \e$B%0%i%`$r=q$-$^$9!#$3$l$O!"
\e(BNemacs
\e$B$H
\e(B Mule
\e$B$GF0:n$9$k
\e(B encoded-word
\e$B$NId9f
\e(B
1429 \e$B2=!&I|9f2=%W%m%0%i%`$G$7$?!#
\e(B@file{tiny-mime.el}
\e$B$O
\e(B B-encoding
\e$B$@$1$G$J$/
\e(B
1430 Q-encoding
\e$B$b
\e(Bsupport
\e$B$7!"$^$?!"
\e(BMULE
\e$B$G07$&$3$H$,$G$-$k$5$^$6$^$J
\e(B MIME
1431 charset (@ref{MIME charset})
\e$B$rF1;~$K;H$&$3$H$,$G$-$^$7$?!#$3$N;~!"
\e(B
1432 Nemacs
\e$B$H
\e(B Mule
\e$B$NAPJ}$r
\e(B support
\e$B$9$k$?$a$KMQ$$$i$l$?%F%/%K%C%/$O8e$K
\e(B emu
1433 package
\e$B$K$^$H$a$i$l$^$9!#
\e(B@refill
1435 \e$B$3$N:"!"<i2,
\e(B
\e$BCNI'
\e(B
\e$B$O
\e(B @file{tiny-mime.el}
\e$B$r$5$^$6$^$J
\e(B MUA
\e$B$G;H$&$?$a$N@_
\e(B
1436 \e$BDj=8$bG[I[$7$F$$$^$7$?$,!"$=$l$i$O8e$K
\e(B@file{tiny-mime.el}
\e$B$H$H$b$K#1$D$N
\e(B
1437 package
\e$B$K$^$H$a$i$l!"
\e(Btm
\e$B$H$$$&L>A0$GG[I[$5$l$^$9!#
\e(B@refill
1439 \e$B<i2,
\e(B
\e$BCNI'
\e(B
\e$B$O$d$,$F!"
\e(BMIME message
\e$B$r1\Mw$9$k$?$a$N%W%m%0%i%`$G$"$k
\e(B
1440 @file{tm-body.el}
\e$B$r=q$-$^$9!#$3$l$O!"$9$0$K
\e(B@file{tm-view.el}
\e$B$H$$$&L>A0
\e(B
1441 \e$B$KJQ$o$j$^$7$?$,!"$d$,$F!"$3$l$,
\e(B@file{tiny-mime.el}
\e$B$KBe$o$C$F!"
\e(Btm
\e$B$NCf
\e(B
1442 \e$B3K$H$J$j$^$9!#
\e(B@refill
1444 @file{tm-view.el}
\e$B$OEvA3!"
\e(BContent-Transfer-Encoding
\e$B$r07$&I,MW$,$"$j$^$9!#
\e(B
1445 \e$B$3$NL\E*$N$?$a$K!"
\e(BMEL
\e$B$,@0Hw$5$l$O$8$a$^$7$?!#
\e(BBase64
\e$B$K4X$7$F$O
\e(B
1446 @file{tiny-mime.el}
\e$B$N
\e(B code
\e$B$,0\$5$l!"$^$?!"?7$?$K
\e(BQuoted-Printable
\e$B$N
\e(B
1447 code
\e$B$,DI2C$5$l$^$7$?!#$3$l$i$,
\e(B@file{mel-b.el}
\e$B$H
\e(B @file{mel-q.el}
\e$B$K$J$j
\e(B
1448 \e$B$^$7$?!#
\e(B@refill
1450 \e$B$^$?!"8e$K!"<i2,
\e(B
\e$BCNI'
\e(B
\e$B$K$h$C$F
\e(B uuencode
\e$BMQ$N
\e(B @file{mel-u.el}
\e$B$,DI2C$5$l!"
\e(B
1451 \e$B$=$N8e$K!">.NS
\e(B
\e$B=$J?
\e(B
\e$B;a$K$h$C$F
\e(B x-gzip64
\e$BMQ$N
\e(B@file{mel-g.el}
\e$B$,DI2C$5$l$^
\e(B
1452 \e$B$7$?!#
\e(B@refill
1454 tm
\e$B$G$O8e$K!"<i2,
\e(B
\e$BCNI'
\e(B
\e$B$K$h$C$F
\e(B @file{tiny-mime.el}
\e$B$N:F<BAu$,9T$o$l!"$3
\e(B
1455 \e$B$N2aDx$G!"
\e(BSTD 11
\e$B$N
\e(B parser
\e$B$,=q$+$l$^$7$?!#$3$l$O!"8=:_$N
\e(B
1456 @file{std11.el}
\e$B$KEv$?$j$^$9!#$^$?!"$3$N2aDx$G
\e(B @file{tiny-mime.el}
\e$B$OI|
\e(B
1457 \e$B9f2=$r9T$&
\e(B @file{tm-ew-d.el}
\e$B$HId9f2=$r9T$&
\e(B @file{tm-ew-e.el}
\e$B$KJ,$1$i$l
\e(B
1458 \e$B$^$7$?!#$3$NN><T$,8=:_$N
\e(B @file{eword-decode.el}
\e$B$H
\e(B
1459 @file{eword-encode.el}
\e$B$N@hAD$KEv$?$j$^$9!#
\e(B@refill
1461 \e$B8e$K!"<i2,
\e(B
\e$BCNI'
\e(B
\e$B$i$K$h$C$F
\e(B tm
\e$B$NA4LL=q$-49$(:n6H$,9T$o$l!"$3$N2aDx$G!"
\e(Btm
1462 \e$B$O
\e(B APEL, MEL, SEMI, EMH, RMAIL-MIME, Gnus-MIME
\e$B$J$I$KJ,$1$i$l$^$7$?!#$3
\e(B
1463 \e$B$N$&$A$N
\e(B MEL
\e$B$,
\e(B FLIM
\e$B$ND>@\$N@hAD$KEv$?$j$^$9!#
\e(B@refill
1465 \e$B8e$K!"
\e(BAPEL
\e$B$+$i
\e(B @file{std11.el}
\e$B$,0\$5$l!"$^$?!"
\e(B@file{mailcap.el},
1466 @file{eword-decode.el}
\e$B$*$h$S
\e(B @file{eword-encode.el}
\e$B$,
\e(B SEMI
\e$B$+$i0\$5$l!"
\e(B
1467 package
\e$B$NL>A0$,
\e(B FLIM
\e$B$H$J$j$^$9!#
\e(B@refill
1469 \e$B$3$ND>A0$+$iEDCf
\e(B
\e$BE/
\e(B
\e$B;a$,$h$j
\e(B RFC
\e$B$KCi<B$J<BAu$r=q$-;O$a!"$3$l$O!"8=:_!"
\e(B
1470 FLIM
\e$B$N;^$G$"$k
\e(B ``FLIM-FLAM''
\e$B$H$J$C$F$$$^$9!#
\e(B
1473 @node Concept Index, Function Index, Appendix, Top
1474 @chapter Concept Index
1478 @node Function Index, Variable Index, Concept Index, Top
1479 @chapter Function Index
1483 @node Variable Index, , Function Index, Top
1484 @chapter Variable Index