Re: [docbook-apps] Producing Open Source Software

[Richard Quadling <rquadling@googlemail.com>]

2009/3/6 DavePawson <davep@dpawson.co.uk>:
> Richard Quadling wrote:
>
>> The same tools are now also building the PEAR documentation (PEAR -
>> PHP Extension and Application Repository pear.php.net).
>>
>> Same tools and 2 significant DocBook projects. All done in a fraction
>> of the time it took for the OpenJade tools.
>
> Have you tried building with XSLT? Comparison with OpenJade is
> hardly valid today Richard?
>
> You don't describe the transformation tools you use, just 'use PHP'?
> How do you use PHP to get from docbook  XML to say, PDF?
>
>
>
>
> regards
>
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> http://www.dpawson.co.uk
>

The first step we do is to convert the thousands of XML files into a
single xml file. This is done using a PHP extension based upon libxml.
In essence it is nothing more than a concatenation process which
expands entities. For the 12,500 files, this takes around 1 minute on
my slow machine.

The second step is to use PhD. PhD is a PHP based DocBook5 converter.
We currently support 3 major output formats - xhtml, pdf and manpage.

These formats are used to produce many different types of documentation ...

xhtml:
        phpweb - suitable for php.net web sites documentation sections.
        chunkedhtml - many HTML pages suitable for offline reading
with no additional elements.
        bightml - 1 giant HTML file.
        chmsource - many HTML files configured to work with
Microsoft's HTML Help Compiler.
        phpkdevelop - don't know - not used.
        howto - the how to use PhD.
        pearweb - same as phpweb but for the PEAR documentation and style.
        pearbightml - same as bightml but for the PEAR documentation and style.
        pearchunkedhtml - same as chunkdedhtml but for the PEAR
documentation and style.
        pearchm - same as chmsource but for the PEAR documentation and style.
manpage:
        phpfunctions
pdf:
        phppdf
        phpbigpdf

As I understand it, the manpage output is all plain text. The PDF
output is handled by another PHP extension called haru (I believe -
again not used by me so not really followed it through to completion).

I create the phpweb, chmsource, chunkedhtml, pearweb, pearchm in
around 10 mins in total.




OpenJade may not have been right then. I know that the dssssl files
were there and xslt files. In either case, the precompiled binaries
used to take hours to run.

Richard.
-- 
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"