preprocess script & XHTML

[Gerald Pfeifer]

On Fri, 28 Mar 2003, Andrea Bocci wrote:
> I've finally found the time to put together a modified preprocess script
> that also validates the pages for xhtml compliance after updating them,
> and generates a final report with the status of all the gcc pages.

Ah, that's nice.  Do you have that on the web somewhere for the
gcc.gnu.org pages, so that we can use it right away?

> The validation engine I've used is the WDG validator
> (<http://www.htmlhelp.com/tools/validator/>), the installation has been
> pretty straightforward following their instructions for offline
> validation. I can change the script to use the online W3C validator if
> you prefer, so no local sotware would be needed, but that can be quite
> slower.

If you don't mind, I'd like to give that a try, because that's the
validator we are currently using, so people are familiar with it, and
that way, developers can use this very nice feature without having to
install the WDG validator.

> I've also made some minor changes here and there to the preprocess
> script so some more files are recognized (ie. no warning generated) and
> a couple of files needed to build the final pages are not copied over
> (style.mhtml, searchbox.ihtml).
> [...]
> I know these should go in a separate patch, but I made them along the rest,
> not intentionally :-)

No problem! I have extracted the .ico and .ihtml/.mhtml parts and will
commit them separately (see below).

Concerning the main change, I hope you don't mind, but I believe a bit
of documentation (in form of comments) is needed.

Also, could we make this verification a (command-line) option, which at
least in the beginning defaults to off?

Perhaps we can then avoid some of the new functions, by having the
existing ones check for a global flag and perform the check only if that
is set? What do you think?


Gerald
-- 
Gerald "Jerry"   pfeifer@dbai.tuwien.ac.at   http://www.pfeifer.com/gerald/