Hi all I got an awesome patch from Sean few days ago that listed all the unimplemented tags in the PhD-renderer in a simple and readable manners. Turns out that there were only ~25 tags that phpdoc uses still unimplemented. During the weekend I managed to implement the all \o/ Every single tag that phpdoc uses is now implemented and PhD-renderer runs without any warnings or notices.
There is currently no known bug in PhD-renderer so if you find one then please file a bug report or at least let me know about it. I don't care how small or major the bug is, a missing whitespace or a whole page missing, let me know if you find anything. There is only one missing feature; Auto-generated (and translated) titles/inline texts. I.e. generating titles for the <warning>s, <tip>s, <abstract> elements, title for TOCs, inline text for <note>s... Running PhD to build your docbook files currently only makes sense for phpdoc as there is no generic "theme" yet, but as it is fully capable of competing with Docbook-XSL in the not-so-distant-future I'd like to do an "official release" of the PhD-render just have some "release process" and versioning in place. The plan is; Tag 0.1RC1 after adding the auto-generation of titles/inline text and release a PEAR-installable .tgz. If there are no critical bugs found within couple of weeks of the release I'd like to release 0.1-final and deploy PhD-renderer on the rsync box replacing Docbook-XSL for the phpweb and html builds. The CHM builds will continue to be built using Docbook-XSL. NOTE: I am NOT talking about deploying the proposed reference structure[1], only PhD-renderer itself. We should probably create some kind of website for PhD with some basic info about the project and a link to the .tgz.. Also, where should that website be located? http://phd.php.net? http://doc.php.net/? http://doc.php.net/wiki/phd? Ideas and volunteers appreciated :) -Hannes [1] http://news.php.net/php.doc/969378166
