Re: RE: [PHP-DEV] RE: [PHP-DOC] Re: [PHP-DEV] Summer of Code
| From: | André Luis Ferreira da Silva Bacci | Date: | Mon, 17 Apr 2006 02:38:12 +0000 |
| Subject: | Re: RE: [PHP-DEV] RE: [PHP-DOC] Re: [PHP-DEV] Summer of Code | ||
| References: | 1 | Groups: | php.doc php.internals |
| Request: | Send a blank email to phpdoc+get-969372702@lists.php.net to get a copy of this message | ||
Jared Williams escreveu:
I litle hack. It removes comments in XML, but resolves all XML entities without modifications to make all xml files "standalone" andre@macrossv:~/projects/cvs.php.net/phpdoc/scripts$ time php5 prepare_livedocs.php Chunk: dotnet.intro Only a example fileI'm not sure what you mean by end-user experience. Xinclude is just another mechanism for including a file in xml. Livedocs currently has todo a fair bit of work dealing with entities. Making each of the .xml files standalone would simplify it a lot. I did attempt to write a custom user stream that injected entity definitions into an xml file, so you could load a raw page of the manual directly into a DOMDocument and apply a xsl transform. Didn't have enough time/patience to get it working tho :)How about moving away from using system entities to construct the manual and using Xinclude instead? (See the mysql refmanual docbooksources) This would make the base pages independent fromeach other, and loadable into a DOMDocument, which could be transformed with xslt. for what it's worth: my end-user experience of (and that of pretty much everyone in php-land I work with/ speak to) is that the mysql docs are a dog to work with and the the php docs are in comparison a delight.
real 0m46.695s user 0m8.890s sys 0m2.879sandre@macrossv:~/projects/cvs.php.net/phpdoc/scripts$ ls ../livedocsxml/ dotnet.intro.xml andre@macrossv:~/projects/cvs.php.net/phpdoc/scripts$ []s André AE