bug-glibc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

small bug in glibc-doc


From: Petr Nekula
Subject: small bug in glibc-doc
Date: Wed, 12 Mar 2003 11:00:45 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1

Hi,

I have found one very small and really only cosmetical bug in glibc-documentation. I'm sending a patch against 2.3.1 release.

Bye

Petr Nekula
address@hidden

diff -urN glibc-2.3.1/manual/libc.info-8 glibc-2.3.1-modified/manual/libc.info-8
--- glibc-2.3.1/manual/libc.info-8      2002-10-11 06:21:52.000000000 +0200
+++ glibc-2.3.1-modified/manual/libc.info-8     2003-03-12 10:48:37.000000000 
+0100
@@ -353,12 +353,6 @@
      Each byte is treated separately.  The function is not
      locale-dependent.
 
-     Note that "character" is here used in the sense of byte.  In a
-     string using a multibyte character encoding (abstract) character
-     consisting of more than one byte are not treated as an entity.
-     Each byte is treated separately.  The function is not
-     locale-dependent.
-
  - Function: wchar_t * wcstok (wchar_t *NEWSTRING, const char
           *DELIMITERS)
      A string can be split into tokens by making a series of calls to
diff -urN glibc-2.3.1/manual/string.texi glibc-2.3.1-modified/manual/string.texi
--- glibc-2.3.1/manual/string.texi      2001-11-05 21:54:05.000000000 +0100
+++ glibc-2.3.1-modified/manual/string.texi     2003-03-12 10:49:19.000000000 
+0100
@@ -1964,11 +1964,6 @@
 using a multibyte character encoding (abstract) character consisting of
 more than one byte are not treated as an entity.  Each byte is treated
 separately.  The function is not locale-dependent.
-
-Note that ``character'' is here used in the sense of byte.  In a string
-using a multibyte character encoding (abstract) character consisting of
-more than one byte are not treated as an entity.  Each byte is treated
-separately.  The function is not locale-dependent.
 @end deftypefun
 
 @comment wchar.h

reply via email to

[Prev in Thread] Current Thread [Next in Thread]