Ciao Neal and everyone!
Hmm. XSLT is useable from Python. Python is very easy to learn.
Yep, you just preceeded me. I was thinking of Python as well (even though I
am a newbie with it).
I have done it in PHP as well, but we need an XSLT engine (I think I used
Sablotron's one). Is it easy
I'll admit I haven't been following this thread to closely... so bear with
me if this is something already coverd ;-)
Hmm. XSLT is useable from Python. Python is very easy to learn.
It may be easier to use Python + XSLT to parse the defaults.xml into
attrs.html for the site.
I've used XSLT
Just to butt in.. I have to agree wholeheartedly with what Gilles is saying
below.
Off line generation,, Good idea. Generation at each site. Difficult.
2) There's a learning curve associated with maintaining PHP files (one I
haven't personally climbed yet). It's probably safe to say that
I agree too. It just makes it easier to mirror AND the documentation
could be accessed without having to have a web server (via the file
system and a browser).
Perhaps the only real advantage of using PHP is XSLT, but even that can
be a one-time experience...
I continue to look for Brian
According to Ted Stresen-Reuter:
I've reviewed, briefly, both files mentioned. I'm not sure what they're
purpose is in terms of the whole project (I've been following the
discussion, but not closely - seems like these are default values for
every attribute based on the name), but it seems
All good arguments for automating the production of flat files and, for
the time being, leaving the 404 error page as is.
Furthermore, perhaps the best solution is to add the creation of the
html documentation to Brian White's scripts. I'll take a look at them
(if someone can point me to their
