Remove confusing "single C char locales" phrase; arguments to these
functions and must now be either an unsigned char or EOF, regardless of
locale.

Sort sections.

Re-word compatibility section, taking care to use the word "obsolete" to
describe the 4.4BSD extension of accepting characters (runes) outside of
the range of unsigned char.

Re-word the COMPATIBILITY section, taking care to use the word "deprecated"
to describe the 4.4BSD extension of accepting arguments outside the range
of unsigned char. This gives us freedom to remove

Re-word the COMPATIBILITY section, taking care to use the word "deprecated"
to describe the 4.4BSD extension of accepting arguments outside the range
of unsigned char. This gives us freedom to remove this extension when we
remove the <rune.h> interface in FreeBSD 6.

show more ...

mdoc(7) police: "The .Fn function".

Add a note to the Compatiblity section suggesting that these functions
only be used for byte values. Add cross-references to the wide-char
counterparts.

mdoc(7) police: don't you notice the warnings?

Restore C99 standard conformance information, isblank() _is_ in final
standard document

Pointed by: "Jacques A. Vidrine" <n@nectar.cc>

Removed assertion that isblank() conforms to C90 too. This assertion
is correct but less than useful. There is some uncertainty about whether
isblank() is in C99, but it is certainly not in C90. I

Removed assertion that isblank() conforms to C90 too. This assertion
is correct but less than useful. There is some uncertainty about whether
isblank() is in C99, but it is certainly not in C90. It just conforms
to C89 because it is a conforming extension.

show more ...

Remove assertion that isblank() is in C99, pointed out by ache.

From the PR:

1. ctype.h defines digittoint(), isnumber() and ishexnmber(), yet
they are not documented in any of the manpages.

2. The ctype manpage references a non-existent

From the PR:

1. ctype.h defines digittoint(), isnumber() and ishexnmber(), yet
they are not documented in any of the manpages.

2. The ctype manpage references a non-existent manpage for
digittoint().

3. The isascii() manpage claims it is standards compliant, when
it isn't.

4. isblank() claims it is _not_ standards compliant, when it
is.

Fix by including the appropriate .Nm entries, and with a new digittoint.3
page.

PR: docs/26451
Submitted by: Adrian Filipi-Martin <adrian@ubergeeks.com>

show more ...

Clarify isblank range

mdoc(7) police: Use the new .In macro for #include statements.

Introduce ".Lb" macro to libc manpages.

More libraries manpages updates following.

Add comment after locales
Use .Li for type

Suggested-by: sheldonh

Better wording according to multibyte(3)
Better man formatting
Add reference to multibyte(3)

Describe valid argument domain for 8-bit wide locales to prevent common error
calling ctype functions with signed char as an argument.

$Id$ -> $FreeBSD$

Add $Id$, to make it simpler for members of the translation teams to
track.

The $Id$ line is normally at the bottom of the main comment block in the
man page, separated from the rest of the manpage

Add $Id$, to make it simpler for members of the translation teams to
track.

The $Id$ line is normally at the bottom of the main comment block in the
man page, separated from the rest of the manpage by an empty comment,
like so;

.\" $Id$
.\"

If the immediately preceding comment is a @(#) format ID marker than the
the $Id$ will line up underneath it with no intervening blank lines.
Otherwise, an additional blank line is inserted.

Approved by: bde

show more ...

Don't use literal semicolons in .Fn macro invocations.

BSD 4.4 Lite Lib Sources