In article <[EMAIL PROTECTED]>, Oliver Scholz <[EMAIL PROTECTED]> writes:
> I just noticed a minor mistake in lispref/nonascii.texi. Minor, but it
> might confuse people who try to understand the meaning of the various
> encoding/decoding functions:
You are right. I've just installed your change.
---
Kenichi Handa
[EMAIL PROTECTED]
> Index: lispref/nonascii.texi
> ===================================================================
> RCS file: /cvsroot/emacs/emacs/lispref/nonascii.texi,v
> retrieving revision 1.54
> diff -u -r1.54 nonascii.texi
> --- lispref/nonascii.texi 6 Feb 2006 11:55:10 -0000 1.54
> +++ lispref/nonascii.texi 14 May 2006 21:32:03 -0000
> @@ -1174,7 +1174,7 @@
> @code{no-conversion}.
> Here are the functions to perform explicit encoding or decoding. The
> -decoding functions produce sequences of bytes; the encoding functions
> +encoding functions produce sequences of bytes; the decoding functions
> are meant to operate on sequences of bytes. All of these functions
> discard text properties.
> The standard in Emacs w.r.t. the use of the words "decoding" and
> "encoding" is as follows:
> decoding: stream (file or process output) ==> internal representation
> encoding: internal representation ==> stream
> Or in other words:
> decoding: sequence of bytes ==> sequence of characters
> encoding: sequence of characters ==> sequence of bytes
> The documentation for the functions below the cited pararagraph
> (`encode-coding-region' and others) conform to this.
> Oliver
> --
> Oliver Scholz 25 Floréal an 214 de la Révolution
> Ostendstr. 61 Liberté, Egalité, Fraternité!
> 60314 Frankfurt a. M.
> _______________________________________________
> emacs-pretest-bug mailing list
> [email protected]
> http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
