On 12/27/05, Leo Simons <[EMAIL PROTECTED]> wrote: > == Available tools == > > None of the other generally available tools satisfy all the above > requirements at the moment.
How about just plain xml and xslt? Stick a build.xml in there, but people are free to use the xslt engine of their choice. xmlproc or whatever. The only problem that seems to occur then is that you have to stick to standard xslt, and that different engines format things differently, so a noisy svn. Or just write the documentation in html. An ant script to do the search and replace for the nav bar, the header and the footer if that's what we're talking about. Write a nice css to handle the formatting. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
