The file will be more exciting once there is actual documentation of course. I might put some of the existing docs on modules and tuning in for now.
James - thanks for pointing out that concern. It is how all the CHM files I checked operate, so I'm assuming it is a MS design decision and not a bug in my file. (If you are arrowing down the list, the system would have to load each of the possibly screenshot-intensive pages...) I don't really know what I'm talking about here, but I'd guess the Window-Eyes set files etc. for web browsers are better than those for Windows help files, so visually impaired users might find it easier to navigate a plain HTML version anyway. Roberto - I'm calling the Cygwin groff. I hope that answers your first point. :-) You can do the HTML conversion alone with a short line in bash, so scheduling something like that on an AOLserver site should be easy. You can download a CHM compiler from Microsoft. It needs HTML-formatted source files, an HTML-formatted table-of-contents, and a text file describing the options. I just hacked up a TCL script to generate the two needed files from a directory listing. I'd be happy to rerun it for a particular release or I could probably schedule it to build an up-to-date version every night or something. Thanks for the feedback, Jamie At 09:13 PM 9/25/2002 +0000, Scott Goodwin wrote: >I *LIKE* it. Give fast access to the commands; better then waiting for >the web page. > >Too bad I'm switching (to an iMac). I'll still use it at work, however. > >/s. > > >On Wed, 25 Sep 2002 18:56:26 +0100, "Jamie Rasmussen" ><[EMAIL PROTECTED]> said: > > If you use a Windows desktop or server, I've converted > > the 3.5 docs to HTML with groff and then into Windows > > HTMLHelp format. Sample available at > > http://empoweringminds.mle.ie/temp/aolserver.chm > > > > Jamie > > > > > > At 12:35 AM 9/25/2002 -0400, you wrote: > > >All, please be sure to take a look at the README included with > > >AOLserver 3.5. It should hopefully answer a number of questions I've > > >seen asked recently. > > > > > >- Nathan > > > > > >2. Documentation > > >---------------- > > > > > >Documentation is available in the "doc" subdirectory of this release. > > >It contains of Unix-style reference manual entries for AOLserver. > > >Files with extension ".1" are for programs (for example, nsd.1); files > > >with extension ".3" are for C library procedures; and files with > > >extension ".n" describe Tcl commands. The file "doc/nsd.1" gives a > > >quick summary of the AOLserver configuration. To view any of the man > > >pages on Unix, cd to the "doc" directory and invoke your favorite > > >variant of troff using the normal -man macros, for example: > > > > > > groff -Tascii -man nsd.1 | more > > > > > >Conversion to HTML may be possible with: > > > > > > groff -Thtml -man nsd.1 > nsd.html > > > > > >If AOLserver has been installed correctly and your "man" program > > >supports it, you should be able to access the AOLserver manual entries > > >using the normal "man" mechanisms, such as > > > > > > man -M /usr/local/aolserver/man nsd > > > > > >On Tuesday, September 24, 2002, at 08:05 PM, Patrick Spence wrote: > > > > > >>I certainly hope someone can do this because MAN pages are NOT a viable > > >>solution for some of us. I don't want to have to SSH into my server > > >>just to > > >>read the docs.. a web interface is MUCH easier to work > > >>with...especially > > >>since I do all my work remote.. > > > >-- > Scott Goodwin > [EMAIL PROTECTED] > http://scottg.net
