If I correctly remember, we weren't using XSL because a few years ago there
wasn't any free tool good enough to handle the big php manual (it was much
slower than dsssl and often segfaulted). Nowadays this isn't the case, so we
can use both technologies. (anyway I only know dsssl and not xsl, so you are
nominated the official maintainer of such things :P)
Ah, we still don't have PDFs because there isn't still a program to convert
fo->pdf nicelly. Apache's FOP is simply too slow and needs huge amounts of
RAM.
Nuno
----- Original Message -----
Hi Derick & all
I've been looking into phpweb_xsl build the last few days and honestly
have _no_ idea why it isn't used. I dug through the archives searching
for a reason - not found anything yet.
It looks like it simply got dropped since "livedocs is around the corner".
Anyway! I made tiny adjustments to the xsl build yesterday and it
should be pretty much the same as the dssssl builds - except from only
taking little under 90minutes (per translation) rather then 24hours
and readable markup and easier and...
The only way to know for sure is trying it out, live! Featuring new
functable (Sean), image output examples and
almost-completed-"new"-docstyle (Mehdi) to boot, I hereby ask you to
rebuild all translations, starting with en, using phpweb_xsl \o/
-Hannes
