Re: [STATUS]

In article <97080717493881@decus.org> you wrote:

> I suspect that a lot of the people on this list aren't familiar with

> If there *are* any here that fall into that category, may I suggest

I don't want to run the same voting procedures, but STATUS messages are ok because we need to know what the current state is. At least initially when we have to make some important decisions. Here infos are needed on alternatives to make good decisions. But the hint to dev.apache.org is good. Thanks Ken. Please members on apache-docs read also the ideas expressed there.

> That said..

> I don't much care what the base format of the documentation is as

> o it can be maintained with a text editor on a dumb terminal

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related httpd.apache.org Links announce bugs cvs dev docs gui-dev modproxy-dev packagers testers Request more information about Pantek

Provided both by SGML-Tools and SDF. These two points are also one of my important wishes. I really want to enhance point two:

       o the (or a) freely-available backend produces HTML with which I'm happy

Because FrameMaker or WinWord for the Postscript format is not an option for us, I think. That's why the author of SDF currently tries to provide us with a better solution.

> I'd rather not install another ten tons of cruft.. er,

Correct, Perl rocks. And this is why I also like both SGML-Tools and SDF. Both are written mainly in Perl and can be easily ported. And both are a little bit like "closed world approach", i.e. mainly we just need this package for HTML generation. Only TeX is needed for Postscript, etc.

>[...]

>     One nice thing about the current arrangement is that the HTML files



Correct, currently we login to taz and do just a "cvs update ...." to bring
the webserver areas up-to-date. Ok with a meta-language we need one step more,
but that should be no problem.

>     Also, I'm already working on the FAQ and making it

Yes, I'm currently only started a test for the Apache Handbook. The same approach can be done for the Apache FAQ similar to the FreeBSD FAQ. But this is not directly news.answers-ready.

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com