Chris Jones has pointed out that the Google Summer of Code Projects for 2009 has been finalized and several PHP projects are on the list.

There's seven projects with a wide range of topics - here's the list:

• run-tests.php improvements
• Add decision and path coverage to Xdebug's code coverage instrumentation
• Bug Tracker Improvements
• PhD Improvements (Plugin System)
• Abstract Extension API and Dependency Interface
• Benchmark creation
• PhD O.E. - Online editor for the PHP Manual

You can find out more about the Google Summer of Code here.

Christian Weiske has posted a guide to generate CHM files dynamically in in a Wine instance on a machine running some form of Linux.

The only way to generate .chm files is to use Microsoft's HTML Help Compiler hhc.exe from the HTML Help Workshop. It can be downloaded free of charge from their website. While the workshop tool is a GUI application, hhc.exe can run completely without any windowing environment on a server - ideal for an headless web server like pear.php.net. I already got it running on my Linux desktop at home using Wine, so I chose to go the same way on the server.

He actually starts out the post with a brief history of some of the work that's been done on the PhD tool to incorporate things like screenshots and image support as well as improvements to character set handling.

As far as installing the Help Complier, he offers two helpful tips on things to watch for - the need for X forwarding to display the windows for the installation and a need to install some extra DLL files to correct this bug with Wine.

In this new post to her blog Elizabeth Smith takes a look at something easy you can do to help out the PHP project without ever writing a line of C code - helping the Documentation project. How, you ask? Well, if you're working with Windows, this is your lucky day. Elizabeth uses the rest of the post to show you how to install PHP, grab the phpdoc XML files from CVS and get PhD up and running.

So, you’ve decided you want to help out - where do you start? Before you can edit a file or document an extension you need to be able to build the manual to check your changes. So you need a working install of PhD. In order to accomplish this goal you’ll need three things installed and configured, which is what this article is intended to help with.

You might need to grab a few other things (like the Microsoft 2008 C++ runtime or a QA build of PHP 5.3) to get things running, but her guide - complete with screenshots - walks you through every step of the way. For those that are a bit more experienced with working with Windows & PHP, you might find the five minute install a bit faster.

Christian Weiske set out on a project - no small thing - to convert the current PEAR documentation info over to the PhD DocBook rendering system. In a new post he talks about the conversion process and some of the technology involved.

The reason for PhD to exist was that the previously used DSSSL based system was slow: a full build (all formats and all languages) took 24 hours to complete. Further, the tools the system based on were old, rusty and nobody understood why they broke on some machines, but also why they worked on other ones. Having a php-based system for PHP ensures that there is always someone around who can fix it if it's broken. This wasn't the case with the old documentation build system.

The conversion was spurred on by the fact that the PEAR documentation stopped building and more and more people were finding it hard to build on their machines too. He walks through the steps he took - installing PhD, converting over the docs to the DocBook 5 format and the first builds with the new system.

Now that at the XML was shiny, too, it was time to actually use PhD on it. The numbers were amazing: While a build for one format and one language took around 40 minutes on my system (dual core Macbook with 2GHz and 2GiB RAM), building the same with PhD takes 45 seconds!

Antony Dovgal has pointed out that the latest builds of the PHP documentation using the new PhD system have been put online.

Feel the difference:
With the old OpenJade/DocBook it took 40-60 minutes to build 'many htmls' version of the manual.
With PhD it takes less than 2 minutes to build all three formats ('phpweb', 'one big html' and 'many htmls').

You can grab the latest version of PhD to work on your very own docs either from their CVS repository or download them from the Docs section on the main PHP.net website.

Antony Dovgal has pointed out that the latest builds of the PHP documentation using the new PhD system have been put online.

Feel the difference:
With the old OpenJade/DocBook it took 40-60 minutes to build 'many htmls' version of the manual.
With PhD it takes less than 2 minutes to build all three formats ('phpweb', 'one big html' and 'many htmls').

You can grab the latest version of PhD to work on your very own docs either from their CVS repository or download them from the Docs section on the main PHP.net website.

The main PHP website has announced the release of the new documentation build system (as Hannes Magnusson mentioned previously) is ready and has been launched for testing.

The PHP documentation team is pleased to announce the initial release of the new build system that generates the PHP Manual. Written in PHP, PhD ([PH]P based [D]ocBook renderer) builds are now available for viewing at docs.php.net. Everyone is encouraged to test and use this system so that bugs will be found and squashed.

Once the new build system is stable, expect additional changes to the PHP manual that will include an improved navigation system and styling for OOP documentation.

You can use the my.php page to set it as your default mirror if you'd like to use it seamlessly.

The main PHP website has announced the release of the new documentation build system (as Hannes Magnusson mentioned previously) is ready and has been launched for testing.

The PHP documentation team is pleased to announce the initial release of the new build system that generates the PHP Manual. Written in PHP, PhD ([PH]P based [D]ocBook renderer) builds are now available for viewing at docs.php.net. Everyone is encouraged to test and use this system so that bugs will be found and squashed.

Once the new build system is stable, expect additional changes to the PHP manual that will include an improved navigation system and styling for OOP documentation.

You can use the my.php page to set it as your default mirror if you'd like to use it seamlessly.

Hannes Magnusson has bloccked about the latest release of their application, PhD (the [PH]P based [D]ocbook renderer) that builds up documentation, like that for the PHP manual.

Quick note; We released PhD0.1RC1 today o/ Building the php.net documentations has never been as easy or as fast. [...] It takes less than 2 minutes (on my two years old Precision M70 laptop) to render the entire php.net documentations in three formats.

He includes instructions on fetching the packages needed/documents to compile, modify the configuration files and installing and rendering the php.net documentation. They've also set up a special mirror of the PHP documentation with experimental builds of the docs.

Hannes Magnusson has bloccked about the latest release of their application, PhD (the [PH]P based [D]ocbook renderer) that builds up documentation, like that for the PHP manual.

Quick note; We released PhD0.1RC1 today o/ Building the php.net documentations has never been as easy or as fast. [...] It takes less than 2 minutes (on my two years old Precision M70 laptop) to render the entire php.net documentations in three formats.

He includes instructions on fetching the packages needed/documents to compile, modify the configuration files and installing and rendering the php.net documentation. They've also set up a special mirror of the PHP documentation with experimental builds of the docs.