GNU bug report logs -
#6283
doc/lispref/searching.texi reference to octal code `0377' correct?
Previous Next
Reported by: MON KEY <monkey <at> sandpframing.com>
Date: Thu, 27 May 2010 17:29:02 UTC
Severity: minor
Done: Chong Yidong <cyd <at> stupidchicken.com>
Bug is archived. No further changes may be made.
Full log
Message #35 received at 6283 <at> debbugs.gnu.org (full text, mbox):
> Date: Mon, 31 May 2010 10:45:59 -0400
> From: MON KEY <monkey <at> sandpframing.com>
> Cc: 6283 <at> debbugs.gnu.org
>
> Noticed this morning the following section of the manual which
> references hex values in radian notation:
>
> ,---- (info "(elisp)Coding Systems")
> |
> | The result of encoding, and the input to decoding, are not ordinary
> | text. They logically consist of a series of byte values; that is, a
> | series of ASCII and eight-bit characters. In unibyte buffers and
> | strings, these characters have codes in the range 0 through #xFF
> | (255). In a multibyte buffer or string, eight-bit characters have
> | character codes higher than #xFF (*note Text Representations::), but
> | Emacs transparently converts them to their single-byte values when you
> | encode or decode such text.
> |
> `----
>
> This is, I believe an example of contradictory convention in the manual.
Please be more specific, because I don't see any contradictions here.
Overloaded terminology, maybe, but not contradictions.
This bug report was last modified 15 years and 42 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.