> This seems like something I could do. Could you please provide more > detail on what exactly needs to be done? For example, do we want to have > each configure option in it's own html file a la php.net's documentation
I guess that's certainly a possibility--I think the original idea was that we'd keep an attrs.html for backwards-URL compatibility, but we'd have a few "category" pages. Certainly we could do both--have a "category" index and then separate pages for each attribute. But I think in some cases, it's useful to show examples in the documentation of using multiple related attributes together. > Also, what version of htdig et al are we preparing this documentation > for? 3.2.x. The defaults.cc file (or defaults.xml file, if you've been following that) has a "category" field like "File Layout" or "Indexing" that should be a separate page. -Geoff ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ htdig-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/htdig-dev
