> Most of these build logs look bogus. The problem isn't > in the xml (imho) but I don't know where it is. All this > used to work just fine, now all of sudden build logs show > every single xml file to be full of errors? Strangly when > langs are missing files and fallback on /en/, they (all the > /en/) show the bogus errors... Please explain what we > can do as fixing xml syntax doesn't look like a required > task. I can't make any sense of this, it must be something > simple.
Hm, I guess this build errors are the result of introducing seperate ini.xml and constants.xml files for extentensions in the en-tree. As example the fr Manual: /usr/bin/nsgmls:/local/mirrors/phpdoc/fr/reference/apache/ini.xml:63:19:E: ID "ini.engine" already defined /usr/bin/nsgmls:/local/mirrors/phpdoc/fr/chapters/config.xml:256:24: ID "ini.engine" first defined here Because the moved ini.settings are no longer in /en/chapters/config.xml, fr updated apache/ini.xml but didn't delete the ini-setting from /en/chapters/config.xml or update the whole, restructerd config.xml. Amother "good" guess is, their language-snippets.ent is not uptodate, which means they are using undefined entities. In this case there is no fallback to en/language-snippets.ent. The "character data is not allowed here" error is the result. In most cases the xml looks right. Regards Friedhelm Betz -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
