summaryrefslogtreecommitdiffstats
path: root/lib/libc/locale/isascii.3
Commit message (Collapse)AuthorAgeFilesLines
* Per Regents of the University of Calfornia letter, remove advertisingimp2007-01-091-4/+0
| | | | | | clause. # If I've done so improperly on a file, please let me know.
* Add a note to the Compatiblity section suggesting that these functionstjr2002-10-061-1/+2
| | | | | only be used for byte values. Add cross-references to the wide-char counterparts.
* From the PR:nik2002-01-091-5/+0
| | | | | | | | | | | | | | | | | | | | 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>
* mdoc(7) police: Use the new .In macro for #include statements.ru2001-10-011-1/+1
|
* Remove whitespace at EOL.dd2001-07-151-1/+1
|
* .St -ansiC -> .St -isoCru2001-02-261-1/+1
|
* Introduce ".Lb" macro to libc manpages.phantom2000-04-211-0/+2
| | | | More libraries manpages updates following.
* Back out valid argument domain change - sneak to this function by error.ache2000-03-281-4/+2
| | | | | Reword test condition better. Previous variant was true for negative characters too.
* Describe valid argument domain for 8-bit wide locales to prevent common errorache2000-03-281-0/+2
| | | | calling ctype functions with signed char as an argument.
* Although it should be obvious that the 3-digit numeric values of thesheldonh2000-01-191-1/+1
| | | | | characters shown are octal, state this explicitly for the easily misled.
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* Add $Id$, to make it simpler for members of the translation teams tonik1999-07-121-0/+1
| | | | | | | | | | | | | | | | | 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
* Don't use literal semicolons in .Fn macro invocations.bde1997-04-131-1/+1
|
* BSD 4.4 Lite Lib Sourcesrgrimes1994-05-271-0/+58
OpenPOWER on IntegriCloud