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
58 According to RFC 2045 (@ref{RFC 2045}), `The term ``entity'', refers
59 specifically to the MIME-defined header fields and contents of either a
60 message or one of the parts in the body of a multipart entity.' In this
61 document, the term @strong{entity} indicates all of header fields and
64 The definition of RFC 2045 indicates that a MIME message is a tree. An
65 message is a tree, each node is an entity, like following figure.
66 Namely MIME extends message to tree structure.@refill
68 FLIM uses @strong{mime-entity} structure to represent information of
69 entity. In this document, it is called simply `mime-entity'.@refill
71 \e$BA0=R$N$h$&$K!"
\e(Bmessage
\e$BCf$N3F
\e(B entity
\e$B$OLZ$N@a$KEv$?$j$^$9$,!"$3$NLZ$K$O
\e(B
72 \e$B?<$5$HF1$8?<$5$NCf$N=gHV$K=>$C$FHV9f$,IU$1$k$3$H$,$G$-$^$9!#B($A!"
\e(B
76 \e$B("
\e(B nil
\e$B("
\e(B
78 \e$B(#(!(!(!(!(!(!(!(!(!(+(!(!(!(!(!(!(!(!(!($
\e(B
79 \e$B(#(*($
\e(B
\e$B(#(*($
\e(B
\e$B(#(*($
\e(B
80 \e$B("#0("
\e(B
\e$B("#1("
\e(B
\e$B("#2("
\e(B
81 \e$B(&(((%
\e(B
\e$B(&(((%
\e(B
\e$B(&(((%
\e(B
82 \e$B("
\e(B
\e$B(#(!(!(!(!(+(!(!(!(!($
\e(B
\e$B("
\e(B
83 \e$B(#(!(*(!($(#(!(*(!($(#(!(*(!($(#(!(*(!($(#(!(*(!($
\e(B
84 \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
85 \e$B(&(!(!(!(%(&(!(!(!(%(&(!(!(!(%(&(!(!(!(%(&(!(!(!(%
\e(B
89 \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
90 \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
91 \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
93 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
94 \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
95 node-id
\e$B$O
\e(B @code{(3 2 1)}
\e$B$G$9!#
\e(B@refill
97 \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
98 \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
99 local
\e$BJQ?t
\e(B @code{mime-message-structure}
\e$B$K3JG<$9$k$3$H$K$7$^$9!#
\e(B
100 \e$B$=$7$F!"
\e(Bentity-number
\e$B$d
\e(B node-id
\e$B$rMQ$$$k$3$H$G
\e(B
101 @code{mime-message-structure}
\e$B$K$*$1$k
\e(B entity
\e$B$NAjBPE*$J0LCV4X78$r
\e(B
102 \e$B07$&$3$H$,$G$-$^$9!#
\e(B
106 * Entity creation:: Functions to create mime-entity
107 * Entity hierarchy:: Features about message tree
108 * Entity Attributes:: Functions about attributes of mime-entity
109 * Entity-header:: Information of entity header
110 * Entity-content:: Contents of Entity
111 * Entity buffer:: Entity as buffer representation
112 * mm-backend:: Entity representations and implementations
115 @node Entity creation, Entity hierarchy, Entity, Entity
116 @section Functions to create mime-entity
118 @defun mime-open-entity &optional type location
120 Open an entity and return it.@refill
122 @var{type} is representation-type. (cf. @ref{mm-backend}) @refill
124 @var{location} is location of entity. Specification of it is depended
125 on representation-type.
129 @defun mime-parse-buffer &optional buffer type
131 Parse @var{buffer} as message, and set the result to buffer local
132 variable @code{mime-message-structure} of @var{buffer} as
135 If @var{buffer} is omitted, current buffer is used.@refill
137 @var{type} is representation-type of created
138 mime-entity. (cf. @ref{mm-backend}) Default value is @var{buffer}.
143 @node Entity hierarchy, Entity Attributes, Entity creation, Entity
144 @section Features about message tree
146 @defvar mime-message-structure
148 Buffer local variable to store mime-entity structure of message.
152 @defun mime-entity-children entity
154 Return list of entities included in the @var{entity}.
158 @defun mime-entity-parent entity &optional message
160 Return parent entity of the @var{entity}.@refill
162 If @var{message} is specified, it is regarded as root instead of
163 @code{mime-message-structure}.
167 @defun mime-root-entity-p entity
169 Return non-@code{nil} if @var{entity} is root entity (message).
173 @defun mime-entity-node-id entity
175 Return node-id of @var{entity}.
179 @defun mime-entity-number entity
181 Return entity-number of @var{entity}.
185 @defun mime-find-entity-from-number entity-number &optional message
187 Return entity from @var{entity-number} in @var{message}.@refill
189 If @var{message} is not specified, @code{mime-message-structure} is
194 @defun mime-find-entity-from-node-id entity-node-id &optional message
196 Return entity from @var{entity-node-id} in @var{message}.@refill
198 If @var{message} is not specified, @code{mime-message-structure} is
204 @node Entity Attributes, Entity-header, Entity hierarchy, Entity
205 @section Functions about attributes of mime-entity
207 @defun mime-entity-content-type entity
209 Return content-type of @var{entity}. (cf. @ref{mime-content-type})
213 @defun mime-entity-content-disposition entity
215 Return content-disposition of
216 @var{entity}. (cf. @ref{mime-content-disposition})
220 @defun mime-entity-filename entity
222 Return file name of @var{entity}.
226 @defun mime-entity-encoding entity &optional default-encoding
228 Return content-transfer-encoding of @var{entity}.
229 (cf. @ref{Content-Transfer-Encoding}) @refill
231 If the @var{entity} does not have Content-Transfer-Encoding field, this
232 function returns @var{default-encoding}. If it is nil, @code{"7bit"} is
233 used as default value.
237 @defun mime-entity-cooked-p entity
239 Return non-nil if contents of @var{entity} has been already
245 @node Entity-header, Entity-content, Entity Attributes, Entity
246 @section Information of entity header
248 @defun mime-fetch-field field-name &optional entity
250 Return field-body of @var{field-name} field in header of
253 The results is network representation.@refill
255 If @var{entity} is omitted, @code{mime-message-structure} is used as
256 default value.@refill
258 If @var{field-name} field is not found, this function returns
263 @defun mime-read-field field-name &optional entity
265 Parse @var{field-name} field in header of @var{entity}, and return the
268 Format of result is depended on kind of field. For non-structured
269 field, this function returns string. For structured field, it returns
270 list corresponding with structure of the field.@refill
272 Strings in the result will be converted to internal representation of
275 If @var{entity} is omitted, @code{mime-message-structure} is used as
276 default value.@refill
278 If @var{field-name} field is not found, this function returns
283 @defun mime-insert-decoded-header entity &optional invisible-fields visible-fields
285 Insert before point a decoded contents of header of @var{entity}.@refill
287 @var{invisible-fields} is list of regexps to match field-name to hide.
288 @var{visible-fields} is list of regexps to match field-name to
291 If a field-name is matched with some elements of @var{invisible-fields}
292 and matched with none of @var{visible-fields}, this function don't
298 @node Entity-content, Entity buffer, Entity-header, Entity
299 @section Contents of Entity
301 @defun mime-entity-content entity
303 Return content of @var{entity} as byte sequence.
307 @defun mime-write-entity-content entity filename
309 Write content of @var{entity} into @var{filename}.
313 @defun mime-write-entity entity filename
315 Write representation of @var{entity} into @var{filename}.
319 @defun mime-write-entity-body entity filename
321 Write body of @var{entity} into @var{filename}.
326 @node Entity buffer, mm-backend, Entity-content, Entity
327 @section Entity as buffer representation
329 @defun mime-entity-buffer entity
331 Return buffer, which contains @var{entity}.
335 @defun mime-entity-point-min entity
337 Return the start point of @var{entity} in the buffer which contains
342 @defun mime-entity-point-max entity
344 Return the end point of @var{entity} in the buffer which contains
349 @defun mime-entity-header-start entity
351 Return the start point of header of @var{entity} in the buffer which
352 contains @var{entity}.
356 @defun mime-entity-header-end entity
358 Return the end point of header of @var{entity} in the buffer which
359 contains @var{entity}.
363 @defun mime-entity-body-start entity
365 Return the start point of body of @var{entity} in the buffer which
366 contains @var{entity}.
370 @defun mime-entity-body-end entity
372 Return the end point of body of @var{entity} in the buffer which
373 contains @var{entity}.
378 @node mm-backend, , Entity buffer, Entity
379 @section Entity representations and implementations
381 @cindex entity
\e$B=hM}
\e(B method
382 @cindex representation-type
384 Entity
\e$B$OCj>]2=$5$l$?%G!<%?I=8=$G!"<B:]$N%G!<%?I=8=$H$7$F$OMQES$K1~$8$F
\e(B
385 \e$B$5$^$6$^$J$b$N$,MxMQ$G$-$k$h$&$K@_7W$5$l$F$$$^$9!#
\e(B@refill
387 \e$B$3$3$G!"
\e(Bentity
\e$B$,$I$&$$$&<oN`$NI=8=$r9T$C$F$$$k$+$r<($9$N$,
\e(B
388 @strong{representation-type}
\e$B$G!"
\e(Bentity
\e$B$r@8@.$9$k;~$K$O$3$l$r;XDj$7$^$9!#
\e(B
389 (cf. @ref{Entity Creation}) @refill
391 \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
392 \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
393 \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
394 \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
395 representation-type
\e$BKh$K$3$N$h$&$J4X?t$r$^$H$a$?$b$N$r
\e(B
396 @strong{mm-backend}
\e$B$H8F$S$^$9!#
\e(B@refill
398 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
399 \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
400 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
401 \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
402 \e$B;~$K<+F0E*$K
\e(B require
\e$B$5$l$^$9!#
\e(B
406 * Request for entity:: Message-passing for entity
407 * mm-backend module:: How to make mm-backend
410 @node Request for entity, mm-backend module, mm-backend, mm-backend
411 @subsection Message-passing for entity
413 @defun mime-entity-send entity message &rest args
415 @var{entity}
\e$B$K
\e(B @var{message}
\e$B$rAw$k!#
\e(B@refill
417 @var{args}
\e$B$O
\e(B @var{message}
\e$B$N0z?t$G$"$k!#
\e(B
422 @node mm-backend module, , Request for entity, mm-backend
423 @subsection How to make mm-backend
425 \e$B!J$9$_$^$;$s!#$=$N$&$A=q$-$^$9
\e(B (^_^;
\e$B!K
\e(B@refill
427 \e$B!J$H$j$"$($:!"
\e(Bmm*.el
\e$B$r;29M$K$7$F$/$@$5$$!K
\e(B
430 @node Content-Type, Content-Disposition, Entity, Top
431 @chapter Information of Content-Type field
432 @cindex mime-content-type
433 @cindex Content-Type field
435 @strong{Content-Type field} is a field to indicate kind of contents or
436 data format, such as media-type (@ref{media-type}) and MIME charset. It
437 is defined in RFC 2045 (@ref{RFC 2045}).
443 Historically, Content-Type field was proposed in RFC 1049. In it,
444 Content-Type did not distinguish type and subtype, and there are no
445 mechanism to represent kind of character code like MIME charset.
449 FLIM provides parser for Content-Type field and structure
450 @strong{mime-content-type} to store information of
455 * Content-Type field:: Format of Content-Type field
456 * mime-content-type:: mime-content-type structure
457 * Content-Type parser:: Parser
458 * Content-Type utility:: Utility functions
461 @node Content-Type field, mime-content-type, Content-Type, Content-Type
462 @section Format of Content-Type field
467 Content-Type
\e$BMs$N7A<0$O0J2<$N$h$&$KDj5A$5$l$F$$$^$9!'
\e(B
470 ``Content-Type'' ``:'' @strong{type} ``/''
471 @strong{subtype} *( ``;'' @strong{parameter} )
478 Content-Type: image/jpeg
487 Content-Type: text/plain; charset=iso-2022-jp
492 \e$B$J$I$N$h$&$KMQ$$$i$l$^$9!#
\e(B
494 \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
495 \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
496 `text/plain'
\e$B$O
\e(B media-type
\e$B$N#1$D$G$9!#
\e(B
502 Content-Type
\e$BMs$N$J$$
\e(B entity
\e$B$O
\e(B
506 Content-Type: text/plain; charset=us-ascii
511 \e$B$H$7$F2r<a$5$l$k!#
\e(B(cf. @ref{us-ascii})
516 @node mime-content-type, Content-Type parser, Content-Type field, Content-Type
517 @section mime-content-type structure
519 @deffn{Structure} mime-content-type
521 Content-Type
\e$BMs$N>pJs$r3JG<$9$k$?$a$N9=B$BN!#
\e(B@refill
523 \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
524 \e$B>H4X?t$rMQ$$$k!#
\e(B@refill
526 \e$B$3$N9=B$BN$NMWAG$O0J2<$NDL$j$G$"$k!'
\e(B
530 media-type
\e$B$N<g7?
\e(B (symbol).
533 media-type
\e$B$NI{7?
\e(B (symbol).
536 Content-Type
\e$BMs$N
\e(B parameter (
\e$BO"A[
\e(B list).
542 @defun make-mime-content-type type subtype
545 content-type
\e$B$N@8@.;R!#
\e(B
549 @defun mime-content-type-parameter content-type parameter
551 @var{content-type}
\e$B$N
\e(B @var{parameter}
\e$B$NCM$rJV$9!#
\e(B
556 @node Content-Type parser, Content-Type utility, mime-content-type, Content-Type
559 @defun mime-parse-Content-Type string
561 @var{string}
\e$B$r
\e(B content-type
\e$B$H$7$F2r@O$7$?7k2L$rJV$9!#
\e(B
565 @defun mime-read-Content-Type
567 \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
569 Content-Type
\e$BMs$,B8:_$7$J$$>l9g$O
\e(B nil
\e$B$rJV$9!#
\e(B
574 @node Content-Type utility, , Content-Type parser, Content-Type
575 @section Utility functions
577 @defun mime-type/subtype-string type &optional subtype
579 Return type/subtype string from @var{type} and @var{subtype}.
584 @node Content-Disposition, Content-Transfer-Encoding, Content-Type, Top
585 @chapter Information of Content-Disposition field
586 @cindex mime-content-disposition
588 @cindex Standards Track
589 @cindex Content-Disposition
\e$BMs
\e(B
591 @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
592 \e$B$NB0@-$K$J$I$K4X$9$k>pJs$r5-=R$9$k$?$a$N$b$N$G$9!#
\e(B
598 S. Dorner, K. Moore and R. Troost, ``Communicating Presentation
599 Information in Internet Messages: The Content-Disposition Header'',
600 August 1997, Standards Track.
603 FLIM
\e$B$O
\e(B Content-Disposition
\e$BMs$r9=J82r@O$9$k4X?t$H
\e(B Content-Disposition
604 \e$BMs$N2r@O7k2L$r3JG<$9$k9=B$BN
\e(B
605 @strong{mime-content-disposition}
\e$B$rDs6!$7$^$9!#
\e(B
609 * mime-content-disposition:: mime-content-disposition structure
610 * Content-Disposition parser:: Parser for Content-Disposition field
613 @node mime-content-disposition, Content-Disposition parser, Content-Disposition, Content-Disposition
614 @section mime-content-disposition structure
616 @deffn{Structure} mime-content-disposition
618 Content-Disposition
\e$BMs$N2r@O7k2L$r<}$a$k$?$a$N9=B$BN!#
\e(B@refill
620 \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
621 \e$BA0$N;2>H4X?t$rMQ$$$k!#
\e(B@refill
623 \e$B$3$N9=B$BN$NMWAG$O0J2<$NDL$j$G$"$k!'
\e(B
626 @item disposition-type
627 disposition-type (symbol).
630 Content-Disposition
\e$BMs$N
\e(B parameter (
\e$BO"A[
\e(B list).
636 @defun mime-content-disposition-parameter content-disposition parameter
638 @var{content-disposition}
\e$B$N
\e(B @var{parameter}
\e$B$NCM$rJV$9!#
\e(B
642 @defun mime-content-disposition-filename content-disposition
644 @var{content-disposition}
\e$B$N
\e(B filename
\e$B$NCM$rJV$9!#
\e(B
649 @node Content-Disposition parser, , mime-content-disposition, Content-Disposition
650 @section Parser for Content-Disposition field
652 @defun mime-parse-Content-Disposition string
654 @var{string}
\e$B$r
\e(B content-disposition
\e$B$H$7$F2r@O$7$?7k2L$rJV$9!#
\e(B
658 @defun mime-read-Content-Disposition
660 \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
663 Content-Disposition
\e$BMs$,B8:_$7$J$$>l9g$O
\e(B nil
\e$B$rJV$9!#
\e(B
668 @node Content-Transfer-Encoding, encoded-word, Content-Disposition, Top
669 @chapter Encoding Method
670 @cindex Content-Transfer-Encoding
\e$BMs
\e(B
672 @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
673 \e$B$N$b$N$G$9!#
\e(B@refill
675 FLIM
\e$B$G$O
\e(B Content-Transfer-Encoding
\e$BMs$r9=J82r@O$9$k4X?t$rDs6!$7$^$9!#$3
\e(B
676 \e$B$l$i$N4X?t$O
\e(B Content-Transfer-Encoding
\e$BMs$N>pJs$OJ8;zNs$GI=8=$7$^$9!#
\e(B
679 \e$B$^$?!"
\e(BContent-Transfer-Encoding
\e$B$K4p$E$$$FId9f2=!&I|9f2=$r9T$&4X?t$bDs
\e(B
684 * Content-Transfer-Encoding parser:: Parser
685 * Region encoder/decoder:: Region encoding/decoding
686 * String encoder/decoder:: String encoding/decoding
687 * File encoder/decoder:: File encoding/decoding
690 @node Content-Transfer-Encoding parser, Region encoder/decoder, Content-Transfer-Encoding, Content-Transfer-Encoding
693 @defun mime-parse-Content-Transfer-Encoding string
695 @var{string}
\e$B$r
\e(B content-transfer-encoding
\e$B$H$7$F2r@O$7$?7k2L$rJV$9!#
\e(B
699 @defun mime-read-Content-Transfer-Encoding &optional default-encoding
701 \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
702 \e$BJV$9!#
\e(B@refill
704 Content-Transfer-Encoding
\e$BMs$,B8:_$7$J$$>l9g$O
\e(B@var{default-encoding}
\e$B$r
\e(B
710 @node Region encoder/decoder, String encoder/decoder, Content-Transfer-Encoding parser, Content-Transfer-Encoding
711 @section Region encoding/decoding
713 @defun mime-encode-region start end encoding
715 Encode region @var{start} to @var{end} of current buffer using
720 @defun mime-decode-region start end encoding
722 Decode region @var{start} to @var{end} of current buffer using
727 @defvar mime-encoding-method-alist
729 Alist of encoding vs. corresponding method to encode region.@refill
731 Each element looks like @code{(STRING . FUNCTION)} or @code{(STRING
732 . nil)}. @var{string} is content-transfer-encoding. @code{function} is
733 region encoder and @code{nil} means not to encode.
737 @defvar mime-decoding-method-alist
739 Alist of encoding vs. corresponding method to decode region.@refill
741 Each element looks like @code{(STRING . FUNCTION)} or @code{(STRING
742 . nil)}. @var{string} is content-transfer-encoding. @code{function} is
743 region decoder and @code{nil} means not to decode.
748 @node String encoder/decoder, File encoder/decoder, Region encoder/decoder, Content-Transfer-Encoding
749 @section String encoding/decoding
751 @defun mime-decode-string string encoding
753 @var{string}
\e$B$r
\e(B @var{encoding}
\e$B$H$7$FI|9f$7$?7k2L$rJV$7$^$9!#
\e(B
757 @defvar mime-string-decoding-method-alist
759 Alist of encoding vs. corresponding method to decode string.@refill
761 Each element looks like @code{(STRING . FUNCTION)}. STRING is
762 content-transfer-encoding. FUNCTION is string decoder.
767 @node File encoder/decoder, , String encoder/decoder, Content-Transfer-Encoding
768 @section File encoding/decoding
770 @defun mime-insert-encoded-file filename encoding
772 Insert file @var{FILENAME} encoded by @var{ENCODING} format.
776 @defun mime-write-decoded-region start end filename encoding
778 Decode and write current region encoded by @var{encoding} into
779 @var{filename}.@refill
781 @var{start} and @var{end} are buffer positions.
785 @defvar mime-file-encoding-method-alist
787 Alist of encoding vs. corresponding method to insert encoded
790 Each element looks like @code{(STRING . FUNCTION)}. STRING is
791 content-transfer-encoding. FUNCTION is function to insert encoded file.
795 @defvar mime-file-decoding-method-alist
797 Alist of encoding vs. corresponding method to write decoded region to
800 Each element looks like @code{(STRING . FUNCTION)}. STRING is
801 content-transfer-encoding. FUNCTION is function to write decoded region
807 @node encoded-word, custom, Content-Transfer-Encoding, Top
808 @chapter Network representation of header
810 @cindex Standards Track
813 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
814 \e$B$G!"
\e(B@strong{RFC 2047}
\e$B$GDj5A$5$l$F$$$^$9!#
\e(B@refill
820 K. Moore, ``MIME (Multipurpose Internet Mail Extensions) Part Three:
821 Message Header Extensions for Non-ASCII Text'', November 1996, Standards
822 Track (obsolete RFC 1521,1522,1590).
825 \e$B$^$?!"9T57$N0-$$$3$H$@$H8@$($^$9$,!"
\e(Bencoded-word
\e$B$rMQ$$$:$KHs
\e(B ASCII
826 (@ref{ASCII})
\e$BJ8;z$r
\e(B header
\e$B$KF~$l$?5-;v$bB8:_$7$^$9!#
\e(B@refill
828 FLIM
\e$B$O$3$l$i$rId9f2=!&I|9f2=$9$k5!G=$rDs6!$7$^$9!#
\e(B
832 * Header encoder/decoder:: Header encoding/decoding
835 @node Header encoder/decoder, , encoded-word, encoded-word
836 @section Header encoding/decoding
838 @defun eword-encode-header &optional code-conversion separator
840 Decode MIME encoded-words in header fields.@refill
842 If @var{code-conversion} is @code{nil}, it decodes only encoded-words.
843 If it is mime-charset, it decodes non-ASCII bit patterns as the
844 mime-charset. Otherwise it decodes non-ASCII bit patterns as the
845 default-mime-charset.@refill
847 If @var{separator} is not nil, it is used as header separator.
851 @defun eword-encode-header &optional code-conversion
853 Encode header fields to network representation, such as MIME
856 It refer variable @code{eword-field-encoding-method-alist}.
861 @node custom, Appendix, encoded-word, Top
862 @chapter Various Customization
866 MIME
\e$B4XO"5!G=$K4X$9$k
\e(B group.@refill
868 @code{mail}
\e$B$H
\e(B @code{news}
\e$B$KB0$9$k!#
\e(B
872 @defvar default-mime-charset
874 \e$BE,@Z$J
\e(B MIME charset (@ref{MIME charset})
\e$B$,8+$D$+$i$J$+$C$?>l9g$KMQ$$$i
\e(B
875 \e$B$l$k
\e(BMIME charset.@refill
877 \e$BK\Mh$O
\e(B APEL
\e$B$NJQ?t$G$"$k!#
\e(B
881 @defvar mime-temp-directory
883 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
886 \e$B4D6-JQ?t
\e(B @code{MIME_TMP_DIR}, @code{TM_TMP_DIR}, @code{TMPDIR},
887 @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
888 \e$BMQ$$$k!#2?$b@_Dj$5$l$F$$$J$$>l9g!"
\e(B@code{"/tmp/"}
\e$B$rMQ$$$k!#
\e(B
893 @node Appendix, Concept Index, custom, Top
899 * Bug report:: How to report bugs
900 * CVS:: CVS based development
901 * History:: History of FLIM
904 @node Glossary, Bug report, Appendix, Appendix
914 * coded character set:: Coded character set, Character code
932 @node 7bit, 8bit, Glossary, Glossary
934 @cindex 7bit (textual) string
938 @strong{7bit} means any integer between 0 .. 127.@refill
940 Any data represented by 7bit integers is called @strong{7bit data}.@refill
942 Textual string consisted of Control characters between 0 .. 31 and 127,
943 and space represented by 32, and graphic characters between 33 .. 236
944 are called @strong{7bit (textual) string}.@refill
946 Conventional Internet MTA (@ref{MTA}) can translate 7bit data, so it is
947 no need to translate by Quoted-Printable (@ref{Quoted-Printable}) or
948 Base64 (@ref{Base64}) for 7bit data.@refill
950 However if there are too long lines, it can not translate by 7bit MTA
951 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
952 ``7bit data'' has a line more than 999 bytes, it is regarded as binary
953 (@ref{binary}). For example, Postscript file should be encoded by
957 @node 8bit, ASCII, 7bit, Glossary
959 @cindex 8bit (textual) string
963 @strong{8bit} means any integer between 0 .. 255.@refill
965 Any data represented by 8bit integers is called @strong{8bit data}.@refill
967 Textual string consisted of Control characters between 0 .. 31, 127, and
968 128 .. 159, and space represented by 32, and graphic characters between
969 33 .. 236 and 160 .. 255 are called @strong{8bit (textual) string}.@refill
971 For example, iso-8859-1 (@ref{iso-8859-1}) or euc-kr (@ref{euc-kr}) are
972 coded-character-set represented by 8bit textual string.@refill
974 Traditional Internet MTA (@ref{MTA}) can translate only 7bit
975 (@ref{7bit}) data, so if a 8bit data will be translated such MTA, it
976 must be encoded by Quoted-Printable (@ref{Quoted-Printable}) or Base64
977 (@ref{Base64}).@refill
979 However 8bit MTA are increasing today.@refill
981 However if there are too long lines, it can not translate by 8bit MTA
982 even if it is 8bit data. RFC 2045 (@ref{RFC 2045}) require lines in
983 8bit data must be less than 998 bytes. So if a ``8bit data'' has a line
984 more than 999 bytes, it is regarded as binary (@ref{binary}), so it must
985 be encoded by Base64 or Quoted-Printable.
988 @node ASCII, Base64, 8bit, Glossary
990 @cindex ANSI X3.4:1986
994 @strong{ASCII} is a 94-character set contains primary latin characters
995 (A-Z, a-z), numbers and some characters. It is a standard of the United
996 States of America. It is a variant of ISO 646 (@ref{ISO 646}).
1002 ``Coded Character Set -- 7-Bit American Standard Code for Information
1003 Interchange'', ANSI X3.4:1986.
1008 @node Base64, binary, ASCII, Glossary
1013 @strong{Base64} is a transfer encoding method of MIME (@ref{MIME})
1014 defined in RFC 2045 (@ref{RFC 2045}).@refill
1016 The encoding process represents 24-bit groups of input bits as output
1017 strings of 4 encoded characters. Encoded characters represent integer 0
1018 .. 63 or @strong{pad}. Base64 data must be 4 * n bytes, so pad is used
1019 to adjust size.@refill
1021 These 65 characters are subset of all versions of ISO 646, including
1022 US-ASCII, and all versions of EBCDIC. So it is safe even if it is
1023 translated by non-Internet gateways.
1026 @node binary, coded character set, Base64, Glossary
1030 Any byte stream is called @strong{binary}.@refill
1032 It does not require structureof lines. It differs from from 8bit
1033 (@ref{8bit}).@refill
1035 In addition, if line structured data contain too long line (more than
1036 998 bytes), it is regarded as binary.
1039 @node coded character set, media-type, binary, Glossary
1040 @subsection Coded character set, Character code
1042 A set of unambiguous rules that establishes a character set and the
1043 one-to-one relationship between the characters of the set and their
1047 @node media-type, message, coded character set, Glossary
1048 @subsection media-type
1061 @strong{media-type} specifies the nature of the data in the body of MIME
1062 (@ref{MIME}) entity (@ref{entity}). It consists of @strong{type} and
1063 @strong{subtype}. It is defined in RFC 2046 (@ref{RFC 2046}).@refill
1065 Currently there are following standard primary-types:
1077 @strong{application}
1079 @strong{multipart} (@ref{multipart})
1085 And there are various subtypes, for example, application/octet-stream,
1086 audio/basic, image/jpeg, multipart/mixed (@ref{multipart/mixed}),
1087 text/plain (@ref{text/plain}), video/mpeg... @refill
1089 You can refer registered media types at MEDIA TYPES
1090 (ftp://ftp.isi.edu/in-notes/iana/assignments/media-types).@refill
1092 In addition, you can use private type or subtype using @strong{x-token},
1093 which as the prefix `x-'. However you can not use them in
1096 (cf. @ref{Content-Type field})
1100 @node message, MIME, media-type, Glossary
1103 In this document, it means mail defined in RFC 822 (@ref{RFC 822}) and
1104 news message defined in RFC 1036 (@ref{RFC 1036}).
1107 @node MIME, MIME charset, message, Glossary
1109 @cindex Multipurpose Internet Mail Extensions
1111 MIME stands for @strong{Multipurpose Internet Mail Extensions}, it is an
1112 extension for RFC 822 (@ref{RFC 822}).@refill
1114 According to RFC 2045:@refill
1116 STD 11, RFC 822, defines a message representation protocol specifying
1117 considerable detail about US-ASCII message headers, and leaves the
1118 message content, or message body, as flat US-ASCII text. This set of
1119 documents, collectively called the Multipurpose Internet Mail
1120 Extensions, or MIME, redefines the format of messages to allow for
1124 textual message bodies in character sets other than US-ASCII,
1126 an extensible set of different formats for non-textual message
1129 multi-part message bodies, and
1131 textual header information in character sets other than US-ASCII.
1135 It is defined in RFC 2045 (@ref{RFC 2045}), RFC 2046 (@ref{RFC 2046}),
1136 RFC 2047 (@ref{encoded-word}), RFC 2048 (@ref{RFC 2048}) and RFC 2049
1140 @node MIME charset, MTA, MIME, Glossary
1141 @subsection MIME charset
1143 Coded character set (@ref{coded character set}) used in Content-Type
1144 field (@ref{Content-Type field}) or charset parameter of encoded-word
1145 (@ref{encoded-word}).@refill
1147 It is defined in RFC 2045 (@ref{RFC 2045}).@refill
1149 iso-2022-jp (@ref{iso-2022-jp}) or euc-kr (@ref{euc-kr}) are kinds of
1150 it. (In this document, MIME charsets are written by small letters to
1151 distinguish graphic character set (@ref{graphic character set}). For
1152 example, ISO 8859-1 is a graphic character set, and iso-8859-1 is a MIME
1156 @node MTA, MUA, MIME charset, Glossary
1158 @cindex Message Transfer Agent
1160 @strong{Message Transfer Agent}. It means mail transfer programs
1161 (ex. sendmail) and news servers.@refill
1167 @node MUA, Quoted-Printable, MTA, Glossary
1169 @cindex Message User Agent
1171 @strong{Message User Agent}. It means mail readers and news
1178 @node Quoted-Printable, RFC 822, MUA, Glossary
1179 @subsection Quoted-Printable
1180 @cindex Quoted-Printable
1182 @strong{Quoted-Printable} is a transfer encoding method of MIME
1183 (@ref{MIME}) defined in RFC 2045 (@ref{RFC 2045}).@refill
1185 If the data being encoded are mostly US-ASCII text, the encoded form of
1186 the data remains largely recognizable by humans.@refill
1192 @node RFC 822, RFC 1036, Quoted-Printable, Glossary
1196 @cindex Internet mail
1197 @cindex Internet message
1198 @cindex message header
1200 A RFC defines format of Internet mail message, mainly @strong{message header}.
1206 news message is based on RFC 822, so @strong{Internet message} may be
1207 more suitable than @strong{Internet mail} .
1215 D. Crocker, ``Standard for the Format of ARPA Internet Text Messages'',
1216 August 1982, STD 11.
1221 @node RFC 1036, RFC 2045, RFC 822, Glossary
1222 @subsection RFC 1036
1226 A RFC defines format of USENET message. It is a subset of RFC 822
1227 (@ref{RFC 822}). It is not Internet standard, but a lot of netnews
1228 excepting Usenet uses it.
1234 M. Horton and R. Adams, ``Standard for Interchange of USENET Messages'',
1235 December 1987, (obsolete RFC 850).
1240 @node RFC 2045, RFC 2046, RFC 1036, Glossary
1241 @subsection RFC 2045
1243 @cindex Standards Track
1249 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1250 (MIME) Part One: Format of Internet Message Bodies'', November 1996,
1251 Standards Track (obsolete RFC 1521, 1522, 1590).
1256 @node RFC 2046, RFC 2048, RFC 2045, Glossary
1257 @subsection RFC 2046
1259 @cindex Standards Track
1265 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1266 (MIME) Part Two: Media Types'', November 1996, Standards Track (obsolete
1267 RFC 1521, 1522, 1590).
1272 @node RFC 2048, RFC 2049, RFC 2046, Glossary
1273 @subsection RFC 2048
1275 @cindex Standards Track
1281 N. Freed, J. Klensin and J. Postel, ``Multipurpose Internet Mail
1282 Extensions (MIME) Part Four: Registration Procedures'', November 1996,
1283 Standards Track (obsolete RFC 1521, 1522, 1590).
1288 @node RFC 2049, plain text, RFC 2048, Glossary
1289 @subsection RFC 2049
1291 @cindex Standards Track
1297 N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
1298 (MIME) Part Five: Conformance Criteria and Examples'', November 1996,
1299 Standards Track (obsolete RFC 1521, 1522, 1590).
1304 @node plain text, us-ascii, RFC 2049, Glossary
1305 @subsection plain text
1307 A textual data represented by only coded character set (@ref{coded character set}). It does not have information about font or
1308 typesetting. (cf. @ref{text/plain})
1312 @node us-ascii, , plain text, Glossary
1313 @subsection us-ascii
1317 A MIME charset (@ref{MIME charset}) for primary Latin script mainly
1318 written by English or other languages.@refill
1320 It is a 7bit coded character set (@ref{coded character set}) based on
1321 ISO 2022 (@ref{ISO 2022}), it contains only ASCII (@ref{ASCII}) and code
1322 extension (@ref{code extension}) is not allowed.@refill
1324 It is standard coded character set of Internet mail. If MIME charset is
1325 not specified, @strong{us-ascii} is used as default.@refill
1327 In addition, @strong{ASCII} of RFC 822 (@ref{RFC 822}) should be
1328 interpreted as us-ascii.
1331 @node Bug report, CVS, Glossary, Appendix
1332 @section How to report bugs
1333 @cindex good bug report
1335 If you write bug-reports and/or suggestions for improvement, please
1336 send them to the tm Mailing List:
1340 Japanese <bug-tm-ja@@chamonix.jaist.ac.jp>
1342 English <bug-tm-en@@chamonix.jaist.ac.jp>
1346 Notice that, we do not welcome bug reports about too old version. Bugs
1347 in old version might be fixed. So please try latest version at
1350 You should write @strong{good bug report}. If you write only ``FLIM
1351 does not work'', we can not find such situations. At least, you should
1352 write name, type, variants and version of OS, emacs, APEL, FLIM, SEMI
1353 and MUA, and setting. In addition, if error occurs, to send backtrace
1354 is very important. (cf. @ref{(emacs)Bugs}) @refill
1356 Bug may not appear only your environment, but also in a lot of
1357 environment (otherwise it might not bug). Therefor if you send mail
1358 to author directly, we must write a lot of mails. So please send mail
1359 to address for tm bugs instead of author.
1361 Via the tm ML, you can report FLIM bugs, obtain the latest release of
1362 FLIM, and discuss future enhancements to FLIM. To join the tm ML,
1363 send empty e-mail to:
1367 Japanese <tm-ja-help@@chamonix.jaist.ac.jp>
1369 English <tm-en-help@@chamonix.jaist.ac.jp>
1374 @node CVS, History, Bug report, Appendix
1375 @section CVS based development
1377 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
1378 \e$B?7$N
\e(B FLIM
\e$B$rF~<j$9$k$3$H$,$G$-$^$9!'
\e(B
1383 % cvs -d :pserver:anonymous@@chamonix.jaist.ac.jp:/hare/cvs/root \
1386 CVS password: [CR] # NULL string
1390 % cvs -d :pserver:anonymous@@chamonix.jaist.ac.jp:/hare/cvs/root \
1391 checkout [-r TAG] flim
1395 CVS
\e$B$rMQ$$$?3+H/$K;22C$7$?$$J}$O
\e(B
1399 <cvs@@chamonix.jaist.ac.jp>
1403 \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
1404 \e$B$r1h$($F8fO"Mm$/$@$5$$!#
\e(B
1407 @node History, , CVS, Appendix
1408 @section History of FLIM
1410 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
1411 \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
1412 \e$B@lMQ$N
\e(B encoded-word
\e$B$NI|9f2=%W%m%0%i%`$G$7$?!#
\e(B@refill
1414 \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
1415 \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
1416 \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
1417 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
1418 charset (@ref{MIME charset})
\e$B$rF1;~$K;H$&$3$H$,$G$-$^$7$?!#$3$N;~!"
\e(B
1419 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
1420 package
\e$B$K$^$H$a$i$l$^$9!#
\e(B@refill
1422 \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
1423 \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
1424 package
\e$B$K$^$H$a$i$l!"
\e(Btm
\e$B$H$$$&L>A0$GG[I[$5$l$^$9!#
\e(B@refill
1426 \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
1427 @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
1428 \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
1429 \e$B3K$H$J$j$^$9!#
\e(B@refill
1431 @file{tm-view.el}
\e$B$OEvA3!"
\e(BContent-Transfer-Encoding
\e$B$r07$&I,MW$,$"$j$^$9!#
\e(B
1432 \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
1433 @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
1434 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
1435 \e$B$^$7$?!#
\e(B@refill
1437 \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
1438 \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
1439 \e$B$7$?!#
\e(B@refill
1441 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
1442 \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
1443 @file{std11.el}
\e$B$KEv$?$j$^$9!#$^$?!"$3$N2aDx$G
\e(B @file{tiny-mime.el}
\e$B$OI|
\e(B
1444 \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
1445 \e$B$^$7$?!#$3$NN><T$,8=:_$N
\e(B @file{eword-decode.el}
\e$B$H
\e(B
1446 @file{eword-encode.el}
\e$B$N@hAD$KEv$?$j$^$9!#
\e(B@refill
1448 \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
1449 \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
1450 \e$B$N$&$A$N
\e(B MEL
\e$B$,
\e(B FLIM
\e$B$ND>@\$N@hAD$KEv$?$j$^$9!#
\e(B@refill
1452 \e$B8e$K!"
\e(BAPEL
\e$B$+$i
\e(B @file{std11.el}
\e$B$,0\$5$l!"$^$?!"
\e(B@file{mailcap.el},
1453 @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
1454 package
\e$B$NL>A0$,
\e(B FLIM
\e$B$H$J$j$^$9!#
\e(B@refill
1456 \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
1457 FLIM
\e$B$N;^$G$"$k
\e(B ``FLIM-FLAM''
\e$B$H$J$C$F$$$^$9!#
\e(B
1460 @node Concept Index, Function Index, Appendix, Top
1461 @chapter Concept Index
1465 @node Function Index, Variable Index, Concept Index, Top
1466 @chapter Function Index
1470 @node Variable Index, , Function Index, Top
1471 @chapter Variable Index