(find-operation-coding-system): Describe the new

argument format (FILENAME . BUFFER).

2 files changed, 13 insertions, 0 deletions

diff --git a/lispref/ChangeLog b/lispref/ChangeLog
index 7db6cb47e63..2e20af7fc78 100644
--- a/lispref/ChangeLog
+++ b/lispref/ChangeLog
@@ -1,3 +1,8 @@
+2006-05-29  Kenichi Handa  <handa@m17n.org>
+
+        * nonascii.texi (find-operation-coding-system): Describe the new
+        argument format (FILENAME . BUFFER).
+
 2006-05-28  Richard Stallman  <rms@gnu.org>
 
         * tips.texi (Coding Conventions): Better explain reasons not to
diff --git a/lispref/nonascii.texi b/lispref/nonascii.texi
index 0f4a70404af..d9050de33fc 100644
--- a/lispref/nonascii.texi
+++ b/lispref/nonascii.texi
@@ -1116,6 +1116,14 @@ or port number.
 Depending on @var{operation}, this function looks up the target in
 @code{file-coding-system-alist}, @code{process-coding-system-alist},
 or @code{network-coding-system-alist}.
+
+If @var{operation} is @code{insert-file-contents}, the argument
+corresponding to the target may be a cons cell of the form
+@code{(@var{filename} . @code{buffer})}).  In that case,
+@code{filename} is a file name to look up, and @code{buffer} is a
+buffer that already contains the file (but not yet decoded).  A
+function specified in @code{file-coding-system-alist} must pay
+attention to this format of the target.
 @end defun
 
 @node Specifying Coding Systems