On Sat, Mar 1, 2008 at 11:21 AM, Richard Quadling <[EMAIL PROTECTED]> wrote: > On 01/03/2008, Edward Z. Yang <[EMAIL PROTECTED]> wrote: > > And, although we can't put a DOCTYPE in every XML document in phpdoc/, > > Why not? If it makes all the XML files closer to being well formed ... > > I would say having them well formed means a lot more tools can be used > to deal with them, especially for editing and validating. Even if 6 > minutes to configure/build is a lot better than the 1.5 hours I used > to have to wait ... (I'm on windows so this is an improvement).
I agree with Richard here. The advantages of having all files well formed XML out weight any argument I myself have tried to come up with. My initial testing of adding DTD to all book.xml files, using custom catalogs and XInclude shows no noticeable performance hit, it actually reduces the memory overhead drastically. Some of the advantages: - The PhD partial switch will be pointless as phd --docbook phpdoc/en/reference/strings/book.xml would work fine - People could use the fancy XML editors - Reduced entity magic (replaced with minor configurable per-language-catalog voodoo) - No need to run `php configure.php` more then once (even when editing or even adding files) - No need to run `php configure.php --with-lang=..` more then once (even when editing or adding files or even switching languages) - No fear about breaking translation builds when adding/removing files - We would actually be following the standards ... Long term advantages: - No need for any .in files - Each extension doc can be built/updated/distributed separately - Makes it possible to write on-the-fly-translation(and -editing) modules for phpweb (as each filename has xml:base attribute) - Makes it possible to report a bug on a specific page, down to the sentence, with a click of a mouse - In theory a phpdoc checkout would not no even be required to render the docs ... -Hannes
