Jared Williams escreveu:
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.I'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 alot.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 :)
I litle hack.It removes comments in XML, but resolves all XML entities without modifications to make all xml files "standalone"
[EMAIL PROTECTED]:~/projects/cvs.php.net/phpdoc/scripts$ time php5 prepare_livedocs.php
Chunk: dotnet.intro Only a example file real 0m46.695s user 0m8.890s sys 0m2.879s [EMAIL PROTECTED]:~/projects/cvs.php.net/phpdoc/scripts$ ls ../livedocsxml/ dotnet.intro.xml [EMAIL PROTECTED]:~/projects/cvs.php.net/phpdoc/scripts$ []s André AE
<?xml version="1.0"?> <section id="dotnet.intro"> <title>Introduction</title> <warning><simpara>This extension is <emphasis>EXPERIMENTAL</emphasis>. The behaviour of this extension -- including the names of its functions and anything else documented about this extension -- may change without notice in a future release of PHP. Use this extension at your own risk.</simpara></warning> </section>
prepare_livedocs.php
Description: application/php
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
