X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;f=mime-en.texi;h=e04f744b35de72673cd912f3840d18a4ba44804e;hb=6260b782ec94886678bc08ecf41d7fa91fa6c9c5;hp=a95ec3dd7bde51abed368fcbe0dc2c2ac48f1cc2;hpb=fdffb5370df2b02b3f9e9100519320dce1cb00fb;p=elisp%2Fflim.git

diff --git a/mime-en.texi b/mime-en.texi
index a95ec3d..e04f744 100644
--- a/mime-en.texi
+++ b/mime-en.texi
@@ -1,18 +1,19 @@
 \input texinfo.tex
+@c Generated automatically from mime-en.sgml by sinfo 3.7.
 @setfilename mime-en.info
-@settitle{FLIM 1.9 Manual about MIME Features}
+@settitle{FLIM 1.14 Reference Manual about MIME Features}
 @titlepage
-@title FLIM 1.9 Manual about MIME Features
+@title FLIM 1.14 Reference Manual about MIME Features
 @author MORIOKA Tomohiko <morioka@@jaist.ac.jp>
-@subtitle 1998/07/01
+@subtitle 1999-01-27
 @end titlepage
 @node Top, Introduction, (dir), (dir)
-@top FLIM 1.9 Manual about MIME Features
+@top FLIM 1.14 Reference Manual about MIME Features
 
 @ifinfo
 
-This file documents MIME features of FLIM, a Internet message
-parsing/encoding library for GNU Emacs.
+This file documents MIME features of FLIM, a fundamental library to
+process Internet Messages for GNU Emacsen.
 @end ifinfo
 
 @menu
@@ -24,10 +25,10 @@ parsing/encoding library for GNU Emacs.
 * Content-Transfer-Encoding::   Encoding Method
 * encoded-word::                Network representation of header
 * custom::                      Various Customization
-* Appendix::                    
-* Concept Index::               
-* Function Index::              
-* Variable Index::              
+* Appendix::
+* Concept Index::
+* Function Index::
+* Variable Index::
 @end menu
 
 @node Introduction, How to use, Top, Top
@@ -50,8 +51,6 @@ Please eval following to use MIME features provided by FLIM:
 
 @node Entity, Content-Type, How to use, Top
 @chapter Message and Entity
-@cindex node-id
-@cindex entity-number
 @cindex mime-entity
 @cindex entity
 
@@ -61,53 +60,24 @@ message or one of the parts in the body of a multipart entity.'  In this
 document, the term @strong{entity} indicates all of header fields and
 body.@refill
 
-The definition of RFC 2045 indicates that a MIME message is a tree.  An
-message is a tree, each node is an entity, like following figure.
-Namely MIME extends message to tree structure.@refill
-
-FLIM uses @strong{mime-entity} structure to represent information of
-entity.  In this document, it is called simply `mime-entity'.@refill
-
-前述のように、message 中の各 entity は木の節に当たりますが、この木には
-深さと同じ深さの中の順番に従って番号が付けることができます。即ち、
-@example
-
-                              ┌───┐
-                              │  nil │
-                              └─┬─┘
-              ┌─────────┼─────────┐
-            ┌┴┐              ┌┴┐              ┌┴┐
-            │０│              │１│              │２│
-            └┬┘              └┬┘              └┬┘
-              │        ┌────┼────┐        │
-          ┌─┴─┐┌─┴─┐┌─┴─┐┌─┴─┐┌─┴─┐
-          │ ０.０││ １.０││ １.１││ １.２││ ２.０│
-          └───┘└───┘└───┘└───┘└───┘
-@end example
-
-@noindent
-のように深さ n の節には長さ n の整数列の節番号が振れます。これ
-を @strong{entity-number} と呼びます。entity-number は S 式と
-しては @code{(1 2 3)} のような整数のリストとして表現されます。
+The definition of RFC 2045 indicates that a MIME message is a tree, and
+each node of the tree is an entity.  Namely MIME extends message to tree
+structure.@refill
 
-mime-entity では、これと同様の @strong{node-id} を用います。node-id はちょ
-うど entity-number を逆にしたリストで、entity-number 1.2.3 に対応する 
-node-id は @code{(3 2 1)} です。@refill
-
-前述のように、MIME message は entity を単位とした木構造になっているので、
-この根である message 全体も mime-entity で表現することができ、buffer
-local 変数 @code{mime-message-structure} に格納することにします。
-そして、entity-number や node-id を用いることで 
-@code{mime-message-structure} における entity の相対的な位置関係を
-扱うことができます。
+FLIM uses @strong{mime-entity} structure to represent
+information of entity.  In this document, it is called simply
+`mime-entity'.
 
 
 @menu
 * Entity creation::             Functions to create mime-entity
 * Entity hierarchy::            Features about message tree
+* Entity Search::               Find Entity
 * Entity Attributes::           Functions about attributes of mime-entity
 * Entity-header::               Information of entity header
+* entity formatting::           Text presentation of entity
 * Entity-content::              Contents of Entity
+* Entity-network-representation::  Network representation of Entity
 * Entity buffer::               Entity as buffer representation
 * mm-backend::                  Entity representations and implementations
 @end menu
@@ -140,8 +110,55 @@ mime-entity. (cf. @ref{mm-backend}) Default value is @var{buffer}.
 
 
 
-@node Entity hierarchy, Entity Attributes, Entity creation, Entity
+@node Entity hierarchy, Entity Search, Entity creation, Entity
 @section Features about message tree
+@cindex node-id
+@cindex entity-number
+@cindex message
+@cindex root-entity
+
+Structure of a MIME message is tree.@refill
+
+In the tree, root node is the entity indicates all of the message.  In
+this document, it is called @strong{root-entity} or @strong{message}.
+In FLIM, it is indicated by buffer local variable
+@code{mime-message-structure}.@refill
+
+Each entity except root-entity has a parent.  An entity may have
+children.  We can indicate an entity by relative position from a base
+entity, based on the parent-child relationship.@refill
+
+In addition, we can indicate an entity by absolute position of the
+message.@refill
+
+Each entity, which is a node of the tree, can be numbered by
+depth and left-to-right order of the depth.
+@example
+
+                              +-------+
+                              |  nil  |
+                              +---+---+
+              +-------------------+-------------------+
+            +-+-+               +-+-+               +-+-+
+            | 0 |               | 1 |               | 2 |
+            +-+-+               +-+-+               +-+-+
+              |         +---------+---------+         |
+           +--+--+   +--+--+   +--+--+   +--+--+   +--+--+
+           | 0.0 |   | 1.0 |   | 1.1 |   | 1.2 |   | 2.0 |
+           +-----+   +-----+   +-----+   +-----+   +-----+
+@end example
+
+Namely, if depth of a node is n, the node has a node-number, which is
+consists of n integers.  In this document, it is called
+@strong{entity-number}.  An entity-number is represented by list of
+integer, like @code{(1 2 3)}.@refill
+
+mime-entity has also @strong{node-id}.  A node-id is represented by
+reversed list of entity-number.  For example, node-id corresponding with
+1.2.3 is @code{(3 2 1)}.@refill
+
+Each entity can be indicated by entity-number or node-id in
+@code{mime-message-structure}.
 
 @defvar mime-message-structure
 
@@ -182,6 +199,10 @@ Return entity-number of @var{entity}.
 @end defun
 
 
+
+@node Entity Search, Entity Attributes, Entity hierarchy, Entity
+@section Find Entity
+
 @defun mime-find-entity-from-number entity-number  &optional  message
 
 Return entity from @var{entity-number} in @var{message}.@refill
@@ -200,8 +221,17 @@ used.
 @end defun
 
 
+@defun mime-find-entity-from-content-id cid  &optional  message
+
+Return entity from @var{cid} in @var{message}.@refill
+
+If @var{message} is not specified, @code{mime-message-structure} is
+used.
+@end defun
+
+
 
-@node Entity Attributes, Entity-header, Entity hierarchy, Entity
+@node Entity Attributes, Entity-header, Entity Search, Entity
 @section Functions about attributes of mime-entity
 
 @defun mime-entity-content-type entity
@@ -242,7 +272,7 @@ code-converted.
 
 
 
-@node Entity-header, Entity-content, Entity Attributes, Entity
+@node Entity-header, entity formatting, Entity Attributes, Entity
 @section Information of entity header
 
 @defun mime-fetch-field field-name  &optional  entity
@@ -280,7 +310,11 @@ If @var{field-name} field is not found, this function returns
 @end defun
 
 
-@defun mime-insert-decoded-header entity  &optional  invisible-fields visible-fields
+
+@node entity formatting, Entity-content, Entity-header, Entity
+@section Text presentation of entity
+
+@defun mime-insert-header entity  &optional  invisible-fields visible-fields
 
 Insert before point a decoded contents of header of @var{entity}.@refill
 
@@ -290,12 +324,36 @@ hide.@refill
 
 If a field-name is matched with some elements of @var{invisible-fields}
 and matched with none of @var{visible-fields}, this function don't
-insert the field.
+insert the field.@refill
+
+Each encoded-word (@ref{encoded-word}) in the header is decoded.  ``Raw
+non us-ascii characters'' are also decoded as
+@code{default-mime-charset}.
 @end defun
 
 
+@defun mime-insert-text-content entity
+
+Insert before point a contents of @var{entity} as text entity.@refill
+
+Contents of the @var{entity} are decoded as MIME charset (@ref{MIME charset}).  If the @var{entity} does not have charset parameter of
+Content-Type field, @code{default-mime-charset} is used as default
+value.
+@end defun
+
+
+@defvar default-mime-charset
 
-@node Entity-content, Entity buffer, Entity-header, Entity
+Symbol to indicate default value of MIME charset (@ref{MIME charset}).@refill
+
+It is used when MIME charset is not specified.@refill
+
+It is originally variable of APEL.
+@end defvar
+
+
+
+@node Entity-content, Entity-network-representation, entity formatting, Entity
 @section Contents of Entity
 
 @defun mime-entity-content entity
@@ -304,12 +362,28 @@ Return content of @var{entity} as byte sequence.
 @end defun
 
 
+@defun mime-insert-entity-content entity
+
+Insert content of @var{entity} at point.
+@end defun
+
+
 @defun mime-write-entity-content entity filename
 
 Write content of @var{entity} into @var{filename}.
 @end defun
 
 
+
+@node Entity-network-representation, Entity buffer, Entity-content, Entity
+@section Network representation of Entity
+
+@defun mime-insert-entity entity
+
+Insert header and body of @var{entity} at point.
+@end defun
+
+
 @defun mime-write-entity entity filename
 
 Write representation of @var{entity} into @var{filename}.
@@ -323,7 +397,7 @@ Write body of @var{entity} into @var{filename}.
 
 
 
-@node Entity buffer, mm-backend, Entity-content, Entity
+@node Entity buffer, mm-backend, Entity-network-representation, Entity
 @section Entity as buffer representation
 
 @defun mime-entity-buffer entity
@@ -378,33 +452,30 @@ contains @var{entity}.
 @node mm-backend,  , Entity buffer, Entity
 @section Entity representations and implementations
 @cindex mm-backend
-@cindex entity 処理 method
+@cindex entity processing method
 @cindex representation-type
 
-Entity は抽象化されたデータ表現で、実際のデータ表現としては用途に応じて
-さまざまなものが利用できるように設計されています。@refill
+Entity is an abstraction.  It is designed to use various data
+representations for their purposes.@refill
 
-ここで、entity がどういう種類の表現を行っているかを示すのが
-@strong{representation-type} で、entity を生成する時にはこれを指定します。
-(cf. @ref{Entity Creation}) @refill
+Each entity has @strong{representation-type}.  It must be specified when
+an entity is created. (cf. @ref{Entity Creation}) @refill
 
-前節までに述べて来た entity に対する処理は、entity に対してその処理を依
-頼することによって実現されています。Entity は自分の representation-type 
-を知っており、その representation-type に応じて実際の処理を行う関数を呼
-び出します。このような関数を @strong{entity 処理method} と呼びます。また、
-representation-type 毎にこのような関数をまとめたものを 
-@strong{mm-backend} と呼びます。@refill
+Functions about entity are implemented by request processing to the
+entity.  Each entity knows its representation-type.  Each entity calls
+processing function corresponding with the representation-type.  Such
+kind of function is called @strong{entity processing method}.  A module,
+consists of them corresponding with a representation-type, is called
+@strong{mm-backend}.@refill
 
-mm-backend は representation-type の名前の先頭に @code{mm} という
-接頭辞を付けた関数名からなる module で、その module 名は同様に
-representation-type の名前の先頭に @code{mm} を付けたものになって
-います。この module は representation-type の entity が最初に生成される
-時に自動的に require されます。
+Module name of each mm-backend consists of the prefix @code{mm}
+and its representation-type.  The module is required automatically
+when its entity is created at first.
 
 
 @menu
 * Request for entity::          Message-passing for entity
-* mm-backend module::           How to make mm-backend
+* mm-backend module::           Definition of mm-backend
 @end menu
 
 @node Request for entity, mm-backend module, mm-backend, mm-backend
@@ -412,19 +483,49 @@ representation-type の名前の先頭に @code{mm} を付けたものになって
 
 @defun mime-entity-send entity message  &rest  args
 
-@var{entity} に @var{message} を送る。@refill
+Send @var{message} to @var{entity} with @var{args}, and return the
+result.@refill
 
-@var{args} は @var{message} の引数である。
+@var{args} is arguments of the @var{message}.
 @end defun
 
 
 
 @node mm-backend module,  , Request for entity, mm-backend
-@subsection How to make mm-backend
+@subsection Definition of mm-backend
+
+@defmac mm-define-backend type &optional  parents
+
+Define @var{type} as a mm-backend.@refill
+
+If @var{PARENTS} is specified, @var{type} inherits parents.  Each parent
+must be representation-type.@refill
+
+Example:@refill
+
+@lisp
+(mm-define-backend chao (generic))
+@end lisp
+@end defmac
 
-（すみません。そのうち書きます (^_^;）@refill
 
-（とりあえず、mm*.el を参考にしてください）
+@defmac mm-define-method name args  &rest  body
+
+Define @var{name} as a method function of (nth 1 (car @var{args}))
+backend.@refill
+
+@var{args} is like an argument list of lambda, but (car @var{args}) must
+be specialized parameter.  (car (car @var{args})) is name of variable
+and (nth 1 (car @var{args})) is name of backend
+(representation-type).@refill
+
+Example:@refill
+
+@lisp
+(mm-define-method entity-cooked-p ((entity chao)) nil)
+@end lisp
+@end defmac
+
 
 
 @node Content-Type, Content-Disposition, Entity, Top
@@ -464,14 +565,14 @@ Content-Type field.
 @cindex subtype
 @cindex type
 
-Content-Type 欄の形式は以下のように定義されています：
+Format of Content-Type field is defined as follows:
 
 @quotation
 ``Content-Type'' ``:'' @strong{type} ``/''
 @strong{subtype} *( ``;'' @strong{parameter} )
 @end quotation
 
-例えば、
+For example:
 
 @quotation
 @example
@@ -479,8 +580,6 @@ Content-Type: image/jpeg
 @end example
 @end quotation
 
-@noindent
-や
 
 @quotation
 @example
@@ -488,18 +587,16 @@ Content-Type: text/plain; charset=iso-2022-jp
 @end example
 @end quotation
 
-@noindent
-などのように用いられます。
-
-ここで、`type' と `subtype' は entity の形式を示すもので、両者を総称し
-て、`media-type' と呼ぶことにします。上記の例における `image/jpeg' や
-`text/plain' は media-type の１つです。
+`type' and `subtype' indicate format of an entity.  In this document,
+pair of them is called `media-type'.  `image/jpeg' or `text/plain' is
+a media-type.
 
 @noindent
 @strong{[Memo]}
 @quotation
 
-Content-Type 欄のない entity は
+If an entity does not have Content-Type field, it is regarded as
+following:
 
 @quotation
 @example
@@ -508,7 +605,7 @@ Content-Type: text/plain; charset=us-ascii
 @end quotation
 
 @noindent
-として解釈される。(cf. @ref{us-ascii})
+(cf. @ref{us-ascii})
 @end quotation
 
 
@@ -518,22 +615,23 @@ Content-Type: text/plain; charset=us-ascii
 
 @deffn{Structure} mime-content-type
 
-Content-Type 欄の情報を格納するための構造体。@refill
+Structure to store information of a Content-Type field.@refill
 
-この構造体を参照するには @code{mime-content-type-要素名} という名前の参
-照関数を用いる。@refill
+Applications should use reference functions
+@code{mime-content-type-SLOT} to refer information of the
+structure.@refill
 
-この構造体の要素は以下の通りである：
+Slots of the structure are following:
 
 @table @var
 @item primary-type
-media-type の主型 (symbol).
+primary type of media-type (symbol).
 
 @item subtype
-media-type の副型 (symbol).
+subtype of media-type (symbol).
 
 @item parameters
-Content-Type 欄の parameter (連想 list).
+parameters of Content-Type field (association-list).
 
 @end table
 @end deffn
@@ -542,13 +640,13 @@ Content-Type 欄の parameter (連想 list).
 @defun make-mime-content-type type subtype
 	   &optional  parameters
 
-content-type の生成子。
+Constructor of content-type.
 @end defun
 
 
 @defun mime-content-type-parameter content-type parameter
 
-@var{content-type} の @var{parameter} の値を返す。
+Return value of @var{parameter} of @var{content-type}.
 @end defun
 
 
@@ -558,15 +656,17 @@ content-type の生成子。
 
 @defun mime-parse-Content-Type string
 
-@var{string} を content-type として解析した結果を返す。
+Parse @var{string} as a field-body of Content-Type field, and return the
+result as mime-content-type (@ref{mime-content-type}) structure.
 @end defun
 
 
 @defun mime-read-Content-Type
 
-現在の buffer の Content-Type 欄を読み取り、解析した結果を返す。@refill
+Parse Content-Type field of the current buffer, and return the result as
+mime-content-type (@ref{mime-content-type}) structure.@refill
 
-Content-Type 欄が存在しない場合は nil を返す。
+Return @code{nil} if Content-Type field is not found.
 @end defun
 
 
@@ -586,10 +686,11 @@ Return type/subtype string from @var{type} and @var{subtype}.
 @cindex mime-content-disposition
 @cindex RFC 2183
 @cindex Standards Track
-@cindex Content-Disposition 欄
+@cindex Content-Disposition field
 
-@strong{Content-Disposition 欄} は entity の表示や file 名など
-の属性になどに関する情報を記述するためのものです。
+@strong{Content-Disposition field} is an optional field to
+specify presentation of an entity or attributes of an entity, such as
+file name.
 
 
 @noindent
@@ -600,9 +701,9 @@ Information in Internet Messages: The Content-Disposition Header'',
 August 1997, Standards Track.
 @end quotation
 
-FLIM は Content-Disposition 欄を構文解析する関数と Content-Disposition 
-欄の解析結果を格納する構造体 
-@strong{mime-content-disposition} を提供します。
+FLIM provides parser for Content-Disposition field and structure
+@strong{mime-content-disposition} to store information of
+Content-Disposition field.
 
 
 @menu
@@ -615,19 +716,21 @@ FLIM は Content-Disposition 欄を構文解析する関数と Content-Dispositi
 
 @deffn{Structure} mime-content-disposition
 
-Content-Disposition 欄の解析結果を収めるための構造体。@refill
+Structure to store information of a Content-Disposition field.@refill
 
-この構造体を参照するには @code{mime-content-disposition-要素名} という名
-前の参照関数を用いる。@refill
+Applications should use reference functions
+@code{mime-content-disposition-SLOT} to refer information of the
+structure.@refill
 
-この構造体の要素は以下の通りである：
+Slots of the structure are following:
 
 @table @var
 @item disposition-type
 disposition-type (symbol).
 
 @item parameters
-Content-Disposition 欄の parameter (連想 list).
+parameters of Content-Disposition field
+(association-list).
 
 @end table
 @end deffn
@@ -635,13 +738,13 @@ Content-Disposition 欄の parameter (連想 list).
 
 @defun mime-content-disposition-parameter content-disposition parameter
 
-@var{content-disposition} の @var{parameter} の値を返す。
+Return value of @var{parameter} of @var{content-disposition}.
 @end defun
 
 
 @defun mime-content-disposition-filename content-disposition
 
-@var{content-disposition} の filename の値を返す。
+Return filename of @var{content-disposition}.
 @end defun
 
 
@@ -651,64 +754,69 @@ Content-Disposition 欄の parameter (連想 list).
 
 @defun mime-parse-Content-Disposition string
 
-@var{string} を content-disposition として解析した結果を返す。
+Parse @var{string} as field-body of Content-Disposition field, and
+return the result as mime-content-disposition
+(@ref{mime-content-disposition}) structure.
 @end defun
 
 
 @defun mime-read-Content-Disposition
 
-現在の buffer の Content-Disposition 欄を読み取り、解析した結果を返す。
-@refill
+Parse Content-Disposition field of the current buffer, and return the
+result as mime-content-disposition (@ref{mime-content-disposition})
+structure.@refill
 
-Content-Disposition 欄が存在しない場合は nil を返す。
+Return @code{nil} if Content-Disposition field is not found.
 @end defun
 
 
 
 @node Content-Transfer-Encoding, encoded-word, Content-Disposition, Top
 @chapter Encoding Method
-@cindex Content-Transfer-Encoding 欄
+@cindex Content-Transfer-Encoding field
 
-@strong{Content-Transfer-Encoding 欄} は entity の符号化法を記述するため
-のものです。@refill
+@strong{Content-Transfer-Encoding field} is a header field to indicate
+body encoding of a entity.@refill
 
-FLIM では Content-Transfer-Encoding 欄を構文解析する関数を提供します。こ
-れらの関数は Content-Transfer-Encoding 欄の情報は文字列で表現します。
-@refill
+FLIM provides parser functions for Content-Transfer-Encoding field.
+They represent information of Content-Transfer-Encoding field as
+string.@refill
 
-また、Content-Transfer-Encoding に基づいて符号化・復号化を行う関数も提
-供されます。
+In addition, FLIM provides encoder/decoder functions by
+Content-Transfer-Encoding.
 
 
 @menu
 * Content-Transfer-Encoding parser::  Parser
-* Region encoder/decoder::      Region encoding/decoding
-* String encoder/decoder::      String encoding/decoding
-* File encoder/decoder::        File encoding/decoding
+* encoder/decoder::             Encoder/decoder
+* Encoding information::        Other utilities
+* mel-backend::                 How to write encoder/decoder module
+* generic function for mel-backend::  How to add encoding/decoding service
 @end menu
 
-@node Content-Transfer-Encoding parser, Region encoder/decoder, Content-Transfer-Encoding, Content-Transfer-Encoding
+@node Content-Transfer-Encoding parser, encoder/decoder, Content-Transfer-Encoding, Content-Transfer-Encoding
 @section Parser
 
 @defun mime-parse-Content-Transfer-Encoding string
 
-@var{string} を content-transfer-encoding として解析した結果を返す。
+Parse @var{string} as a field-body of Content-Transfer-Encoding field,
+and return the result.
 @end defun
 
 
 @defun mime-read-Content-Transfer-Encoding &optional default-encoding
 
-現在の buffer の Content-Transfer-Encoding 欄を読み取り、解析した結果を
-返す。@refill
+Parse Content-Transfer-Encoding field of the current buffer, and return
+the result.@refill
 
-Content-Transfer-Encoding 欄が存在しない場合は@var{default-encoding} を
-返す。
+Return @var{default-encoding} if Content-Transfer-Encoding field is not
+found.  If it is not specified, @code{nil} is used as the default value.
 @end defun
 
 
 
-@node Region encoder/decoder, String encoder/decoder, Content-Transfer-Encoding parser, Content-Transfer-Encoding
-@section Region encoding/decoding
+@node encoder/decoder, Encoding information, Content-Transfer-Encoding parser, Content-Transfer-Encoding
+@section Encoder/decoder
 
 @defun mime-encode-region start end encoding
 
@@ -724,83 +832,124 @@ Decode region @var{start} to @var{end} of current buffer using
 @end defun
 
 
-@defvar mime-encoding-method-alist
-
-Alist of encoding vs. corresponding method to encode region.@refill
 
-Each element looks like @code{(STRING . FUNCTION)} or @code{(STRING
-. nil)}.  @var{string} is content-transfer-encoding.  @code{function} is
-region encoder and @code{nil} means not to encode.
-@end defvar
+@defun mime-decode-string string encoding
 
+Decode @var{string} which is encoded in @var{encoding}, and return the
+result.
+@end defun
 
-@defvar mime-decoding-method-alist
 
-Alist of encoding vs. corresponding method to decode region.@refill
 
-Each element looks like @code{(STRING . FUNCTION)} or @code{(STRING
-. nil)}.  @var{string} is content-transfer-encoding.  @code{function} is
-region decoder and @code{nil} means not to decode.
-@end defvar
+@defun mime-insert-encoded-file filename encoding
 
+Insert file @var{FILENAME} encoded by @var{ENCODING} format.
+@end defun
 
 
-@node String encoder/decoder, File encoder/decoder, Region encoder/decoder, Content-Transfer-Encoding
-@section String encoding/decoding
+@defun mime-write-decoded-region start end filename encoding
 
-@defun mime-decode-string string encoding
+Decode and write current region encoded by @var{encoding} into
+@var{filename}.@refill
 
-@var{string} を @var{encoding} として復号した結果を返します。
+@var{start} and @var{end} are buffer positions.
 @end defun
 
 
-@defvar mime-string-decoding-method-alist
 
-Alist of encoding vs. corresponding method to decode string.@refill
+@node Encoding information, mel-backend, encoder/decoder, Content-Transfer-Encoding
+@section Other utilities
 
-Each element looks like @code{(STRING . FUNCTION)}.  STRING is
-content-transfer-encoding.  FUNCTION is string decoder.
-@end defvar
+@defun mime-encoding-list &optional  SERVICE
+
+Return list of Content-Transfer-Encoding.@refill
 
+If @var{service} is specified, it returns available list of
+Content-Transfer-Encoding for it.
+@end defun
 
 
-@node File encoder/decoder,  , String encoder/decoder, Content-Transfer-Encoding
-@section File encoding/decoding
+@defun mime-encoding-alist &optional  SERVICE
 
-@defun mime-insert-encoded-file filename encoding
+Return table of Content-Transfer-Encoding for completion.@refill
 
-Insert file @var{FILENAME} encoded by @var{ENCODING} format.
+If @var{service} is specified, it returns available list of
+Content-Transfer-Encoding for it.
 @end defun
 
 
-@defun mime-write-decoded-region start end filename encoding
 
-Decode and write current region encoded by @var{encoding} into
-@var{filename}.@refill
+@node mel-backend, generic function for mel-backend, Encoding information, Content-Transfer-Encoding
+@section How to write encoder/decoder module
 
-@var{start} and @var{end} are buffer positions.
-@end defun
+@defmac mel-define-method name args  &rest  body
 
+Define @var{name} as a method function of (nth 1 (car (last
+@var{args}))) backend.@refill
 
-@defvar mime-file-encoding-method-alist
+@var{args} is like an argument list of lambda, but (car (last
+@var{args})) must be specialized parameter.  (car (car (last
+@var{args}))) is name of variable and (nth 1 (car (last @var{args}))) is
+name of backend (encoding).@refill
 
-Alist of encoding vs. corresponding method to insert encoded
-file.@refill
+Example:@refill
 
-Each element looks like @code{(STRING . FUNCTION)}.  STRING is
-content-transfer-encoding.  FUNCTION is function to insert encoded file.
-@end defvar
+@lisp
+(mel-define-method mime-write-decoded-region (start end filename
+						    (nil "base64"))
+  "Decode and write current region encoded by base64 into FILENAME.
+START and END are buffer positions."
+  (interactive
+   (list (region-beginning) (region-end)
+	 (read-file-name "Write decoded region to file: ")))
+  (let ((str (buffer-substring start end)))
+    (with-temp-buffer
+      (insert (decode-base64-string str))
+      (write-region-as-binary (point-min) (point-max) filename)
+      )))
+@end lisp
+@end defmac
 
 
-@defvar mime-file-decoding-method-alist
+@defmac mel-define-method-function spec function
 
-Alist of encoding vs. corresponding method to write decoded region to
-file.@refill
+Set @var{spec}'s function definition to @var{function}.@refill
 
-Each element looks like @code{(STRING . FUNCTION)}.  STRING is
-content-transfer-encoding.  FUNCTION is function to write decoded region
-to file.
-@end defvar
+First element of @var{spec} is service.@refill
+
+Rest of @var{args} is like an argument list of lambda, but (car (last
+@var{args})) must be specialized parameter.  (car (car (last
+@var{args}))) is name of variable and (nth 1 (car (last @var{args}))) is
+name of backend (encoding).@refill
+
+Example:@refill
+
+@lisp
+(mel-define-method-function (mime-encode-string string (nil "base64"))
+			    'encode-base64-string)
+@end lisp
+@end defmac
+
+
+
+@node generic function for mel-backend,  , mel-backend, Content-Transfer-Encoding
+@section How to add encoding/decoding service
+
+@defmac mel-define-service name &optional  args doc-string
+
+Define @var{name} as a service for Content-Transfer-Encodings.@refill
+
+If @var{args} is specified, @var{name} is defined as a generic function
+for the service.@refill
+
+Example:@refill
+
+@lisp
+(mel-define-service encoded-text-encode-string (string encoding)
+  "Encode STRING as encoded-text using ENCODING.
+ENCODING must be string.")
+@end lisp
+@end defmac
 
 
 
@@ -808,10 +957,11 @@ to file.
 @chapter Network representation of header
 @cindex RFC 2047
 @cindex Standards Track
+@cindex encoded-word
 @cindex RFC 2047
 
-encoded-word は header で非 ASCII (@ref{ASCII}) 文字を表現するための形式
-で、@strong{RFC 2047} で定義されています。@refill
+@strong{RFC 2047} defines the @strong{encoded-word} which is a format to
+represent non-ASCII (@ref{ASCII}) characters in a header.@refill
 
 
 @noindent
@@ -822,10 +972,14 @@ Message Header Extensions for Non-ASCII Text'', November 1996, Standards
 Track (obsolete RFC 1521,1522,1590).
 @end quotation
 
-また、行儀の悪いことだと言えますが、encoded-word を用いずに非 ASCII
-(@ref{ASCII}) 文字を header に入れた記事も存在します。@refill
+The encoded-word is the only valid format to represent non-ASCII
+(@ref{ASCII}) characters in a header, but there are also invalid styles.
+Such kinds of evil messages represent non-ASCII (@ref{ASCII}) characters
+in headers without encoded-words (it is called "raw" non-ASCII
+(@ref{ASCII}) characters).@refill
 
-FLIM はこれらを符号化・復号化する機能を提供します。
+FLIM provides encoding/decoding features of both encoded-word and
+invalid "raw" non-ASCII (@ref{ASCII}) characters.
 
 
 @menu
@@ -835,16 +989,17 @@ FLIM はこれらを符号化・復号化する機能を提供します。
 @node Header encoder/decoder,  , encoded-word, encoded-word
 @section Header encoding/decoding
 
-@defun eword-encode-header &optional  code-conversion separator
+@defun eword-decode-header &optional  code-conversion separator
 
 Decode MIME encoded-words in header fields.@refill
 
-If @var{code-conversion} is @code{nil}, it decodes only encoded-words.
-If it is mime-charset, it decodes non-ASCII bit patterns as the
-mime-charset.  Otherwise it decodes non-ASCII bit patterns as the
-default-mime-charset.@refill
+If @var{code-conversion} is @code{nil}, only encoded-words are decoded.
+If @var{code-conversion} is a MIME charset (@ref{MIME charset}),
+non-ASCII bit patterns are decoded as the MIME charset.  Otherwise
+non-ASCII bit patterns are decoded as the
+@code{default-mime-charset}. (cf. @ref{entity formatting}) @refill
 
-If @var{separator} is not nil, it is used as header separator.
+If @var{separator} is not @code{nil}, it is used as header separator.
 @end defun
 
 
@@ -853,41 +1008,39 @@ If @var{separator} is not nil, it is used as header separator.
 Encode header fields to network representation, such as MIME
 encoded-word.@refill
 
-It refer variable @code{eword-field-encoding-method-alist}.
+Each field is encoded as corresponding method specified by variable
+@code{mime-field-encoding-method-alist}.
 @end defun
 
 
+@defvar mime-field-encoding-method-alist
 
-@node custom, Appendix, encoded-word, Top
-@chapter Various Customization
-
-@deffn{group} mime
-
-MIME 関連機能に関する group.@refill
-
-@code{mail} と @code{news} に属する。
-@end deffn
+Association list to specify field encoding method.  Each element looks
+like (FIELD . METHOD).@refill
 
+If METHOD is @code{mime}, the FIELD will be encoded into MIME format
+(encoded-word).@refill
 
-@defvar default-mime-charset
+If METHOD is @code{nil}, the FIELD will not be encoded.@refill
 
-適切な MIME charset (@ref{MIME charset}) が見つからなかった場合に用いら
-れるMIME charset.@refill
+If METHOD is a MIME charset, the FIELD will be encoded as the charset
+when it must be convert into network-code.@refill
 
-本来は APEL の変数である。
+Otherwise the FIELD will be encoded as variable
+@code{default-mime-charset} when it must be convert into network-code.
 @end defvar
 
 
-@defvar mime-temp-directory
 
-MIME 機能に関する実装が一時的に使用する file を作成する 
-directory.@refill
+@node custom, Appendix, encoded-word, Top
+@chapter Various Customization
+
+@deffn{group} mime
 
-環境変数 @code{MIME_TMP_DIR}, @code{TM_TMP_DIR}, @code{TMPDIR},
-@code{TMP} もしくは @code{TEMP} が設定されていた場合、それを初期値として
-用いる。何も設定されていない場合、@code{"/tmp/"} を用いる。
-@end defvar
+The group associated with functions related to MIME.@refill
 
+It belongs to @code{mail} and @code{news}.
+@end deffn
 
 
 @node Appendix, Concept Index, custom, Top
@@ -1333,13 +1486,13 @@ interpreted as us-ascii.
 @cindex good bug report
 
 If you write bug-reports and/or suggestions for improvement, please
-send them to the tm Mailing List:
+send them to the EMACS-MIME Mailing List:
 
 @itemize @bullet
 @item
- Japanese <bug-tm-ja@@chamonix.jaist.ac.jp>
+ English <emacs-mime-en@@m17n.org>
 @item
- English <bug-tm-en@@chamonix.jaist.ac.jp>
+ Japanese <emacs-mime-ja@@m17n.org>
 @end itemize
 
 
@@ -1356,17 +1509,17 @@ is very important. (cf. @ref{(emacs)Bugs}) @refill
 Bug may not appear only your environment, but also in a lot of
 environment (otherwise it might not bug).  Therefor if you send mail
 to author directly, we must write a lot of mails.  So please send mail
-to address for tm bugs instead of author.
+to address for EMACS-MIME Mailing List instead of author.
 
-Via the tm ML, you can report FLIM bugs, obtain the latest release of
-FLIM, and discuss future enhancements to FLIM.  To join the tm ML,
-send empty e-mail to:
+Via the EMACS-MIME ML, you can report FLIM bugs, obtain the latest
+release of FLIM, and discuss future enhancements to FLIM.  To join the
+EMACS-MIME ML, send an empty e-mail to:
 
 @itemize @bullet
 @item
- Japanese <tm-ja-help@@chamonix.jaist.ac.jp>
+ English  <emacs-mime-en-ctl@@m17n.org>
 @item
- English  <tm-en-help@@chamonix.jaist.ac.jp>
+ Japanese <emacs-mime-ja-ctl@@m17n.org>
 @end itemize
 
 
@@ -1374,40 +1527,39 @@ send empty e-mail to:
 @node CVS, History, Bug report, Appendix
 @section CVS based development
 
-FLIM の file は CVS を使って管理されています。このため、以下の方法で最
-新の FLIM を入手することができます：
+Files in FLIM are managed under CVS. Therefore you can obtain the
+newest FLIM by the following method.
 
 @example
 (0) cvs login
 
-    % cvs -d :pserver:anonymous@@chamonix.jaist.ac.jp:/hare/cvs/root \
-	login
+    % cvs -d :pserver:anonymous@@cvs.m17n.org:/cvs/root login
 
     CVS password: [CR] # NULL string
 
 (1) checkout
 
-    % cvs -d :pserver:anonymous@@chamonix.jaist.ac.jp:/hare/cvs/root \
+    % cvs -d :pserver:anonymous@@cvs.m17n.org:/cvs/root checkout
 	checkout [-r TAG] flim
 @end example
 
 
-CVS を用いた開発に参加したい方は
+If you would like to join CVS based development, please send mail to
 
 @itemize @bullet
 @item
- <cvs@@chamonix.jaist.ac.jp>
+ <cvs@@cvs.m17n.org>
 @end itemize
 
 @noindent
-まで、account 名と UNIX の passwd と同じ形式の crypt 化された password
-を沿えて御連絡ください。
+with your account name and your public key for ssh.
+cvsroot is :ext:cvs@@cvs.m17n.org:/cvs/root.
 
 
 @node History,  , CVS, Appendix
 @section History of FLIM
 
-FLIM の code の最古の部分は 榎並 嗣智 氏が書いた @file{mime.el}に起源し
+FLIM の code の最古の部分は 榎並 嗣智 氏が書いた @file{mime.el} に起源し
 ます。この小さな program は Nemacs で動作する iso-2022-jp の B-encoding 
 専用の encoded-word の復号化プログラムでした。@refill
 
@@ -1451,7 +1603,7 @@ tm では後に、守岡 知彦 によって @file{tiny-mime.el} の再実����後に、APEL から @file{std11.el} が移され、また、@file{mailcap.el},
 @file{eword-decode.el} および @file{eword-encode.el} が SEMI から移され、
-package の名前が FLIMとなります。@refill
+package の名前が FLIM となります。@refill
 
 この直前から田中 哲 氏がより RFC に忠実な実装を書き始め、これは、現在、
 FLIM の枝である ``FLIM-FLAM'' となっています。