to the NOTES section, and add references to the functions mentioned
(and perhaps a few more).

Update docs.

American variants.

it as well, especially in apps.c.

doesn't quite work on WinNT 4 earlier than SP6.  It works fine on
Windows 98 and Windows 2000.

I'm disabling it for now.  What's really needed is some kind of check
to see if GetCursorInfo is safe to call, or alternatively, GetCursor
or GetCursorPos could be used, according to Jeffrey.

This will also make it much simpler to generate softlinks name like
each function to man-pages containing the info.

which is redundant.  They are now in their own document.

Also, in the name section, all the functions described shoud be
enumerated.  This will also make it much simpler to generate softlinks
name like each function to man-pages containing the info.

which is redundant.  Instead, move them to their own page.

This combines several manual pages provided by
Lutz Jaenicke <Lutz.Jaenicke@aet.TU-Cottbus.DE>,
various comments by Bodo to the lists and a bit
of source examination by me.

sign.

indent there, especially since the pod2* scripts will regard that as
preformated text.  In one case, indent a code section one step.

for a few BIO routines.
Submitted by Lutz Jaenicke <Lutz.Jaenicke@aet.TU-Cottbus.DE>

Submitted by NAKAJI Hiroyuki <nakaji@tutrp.tut.ac.jp>

indent there, especially since the pod2* scripts will regard that as
preformated text.  In one case, indent a code section one step.

no way to make sure GetCursorInfo will give us a valid answer.