AuroraMiddleware/glibc
1
0
Fork 0
mirror of https://sourceware.org/git/glibc.git synced 2024-12-22 10:50:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update.

Browse Source 
1999-10-05  Andreas Jaeger  <aj@suse.de>

	* manual/message.texi (The message catalog files): Fix description
	to match gencat implementation and Unix98: Message fields are
	separated by a single blank space.

1999-10-05  Andreas Jaeger  <aj@suse.de>

	* manual/string.texi (Search Functions): Add missing end for
	memrchr description.
This commit is contained in:
Ulrich Drepper 1999-10-05 15:26:17 +00:00
parent 479620b96e
commit a2d6361225
3 changed files with 13 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
ChangeLog
View File

@ -1,3 +1,14 @@
1999-10-05 Andreas Jaeger <aj@suse.de>
* manual/message.texi (The message catalog files): Fix description
to match gencat implementation and Unix98: Message fields are
separated by a single blank space.
1999-10-05 Andreas Jaeger <aj@suse.de>
* manual/string.texi (Search Functions): Add missing end for
memrchr description.
1999-10-04 Ulrich Drepper <drepper@cygnus.com>
* malloc/memprof.sh: Various small cleanups. Add short options.

6
manual/message.texi
View File

@ -374,7 +374,7 @@ be escaped using the backslash (i.e., @code{\"} must be written).
@item
Any other line must start with a number or an alphanumeric identifier
(with the underscore character included). The following characters
(starting at the first non-whitespace character) will form the string
(starting after the first whitespace character) will form the string
which gets associated with the currently selected set and the message
number represented by the number and identifier respectively.
@ -390,10 +390,6 @@ identifiers will be explained below (@pxref{Common Usage}). There is
one limitation with the identifier: it must not be @code{Set}. The
reason will be explained below.
Please note that you must use a quoting character if a message contains
leading whitespace. Since one cannot guarantee this never happens it is
probably a good idea to always use quoting.
The text of the messages can contain escape characters. The usual bunch
of characters known from the @w{ISO C} language are recognized
(@code{\n}, @code{\t}, @code{\v}, @code{\b}, @code{\r}, @code{\f},

1
manual/string.texi
View File

@ -1068,6 +1068,7 @@ located byte, or a null pointer if no match was found.
The function @code{memrchr} is like @code{memchr}, except that it searches
backwards from the end of the block defined by @var{block} and @var{size}
(instead of forwards from the front).
@end deftypefun
@comment string.h
@comment ISO