On Sat, May 31, 2008 at 7:00 PM, Brett Bieber <brett.bieber@gmail.com> wrote:
> Hello
>
> On Sat, May 31, 2008 at 9:23 AM, Hannes Magnusson
> <hannes.magnusson@gmail.com> wrote:
>> Hi all
>>
>> I'd say the next task would be to check the status of the php-gtk and
>> pear docs, these are still in DocBook4? Any ETA on DB5 upgrade?
>
> I put together a script to handle the upconvert of peardoc to DB5.
> http://wiki.pear.php.net/index.php/PEARDocMoveToDocbook5#Conversion_Script
>
> So getting to DB5 is fine... the question is - where we go from there?
> I think we really need help with the build magic to get the
> .manual.xml, a minimal setup utilizing PhD, and some recommendations
> on the set/book structure we need to target.
>
> Can we use our existing build scripts to get all the way up to
> .manual.xml with the new DB5 sources? For some reason I was thinking
> we have to rewrite our entire build process.

No no. There is no need to rewrite anything.
The configure.php changes in phpdoc/ are completely separate from PhD.
All PhD needs is a file containing the XML (i.e. .manual.xml) which
can be created with PHP:
<?php
$dom = new DOMDocument();
$dom->load("manual.xml", LIBXML_NOENT | LIBXML_NSCLEAN);
$dom->xinclude();

if ($dom->validate()) {
    $dom->save(".manual.xml");
}
?>

The .manual.xml isn't technically even required for PhD, it is just faster :)

Since pear-doc is using Docbook-DSSSSL you will not be able to build
the manual after upgrading to DB5 since the DSSSL stylesheets simply
don't support it, so before you upgrade the PhD theme/stylesheet needs
to be ready.

The last step (optional) is to upgrade to set/book structure like
phpdoc/ did few weeks ago.. I don't exactly recommend you upgrade just
yet though, start small (DB5&PhD) then maybe restructure late on.


Rudy: I guess you should check out that DB5 upgrade script and produce
a .manual.xml file which you can use a test file until you've created
the theme...

-Hannes