> > The build fails, guaranteed, if the translation is not up2date with > > the reference.xml split due to duplicated IDs. > > These duplicated IDs are caused by the new "root/container" file, > > book.xml (since all extensions are now <book>s), which includes a > > setup.xml <chapter> file (containing the > > installation+configuration+requirements <section>s). > > Then the reference.xml file will be included which (unless it is > > up2date) again defines the same sections, causing duplicated IDs. > > Furthermore, the constant sections are now <chapter>s, not <section>s > > and the document will therefor not validate. > > > So: > 1. There is a new file, book.xml. This is the main file for each extension.
Correct. This file contains "entity includes" to reference.xml, setup.xml, constants.xml and any other appendices/articles/chapters (such as in-dept explainations, usage examples...) (See the first "example" on http://doc.php.net/wiki/skeletons) > 2. There is a new file, setup.xml. It have howto install and setup a > extension. Correct. That file contains for sections (all of them _must_ exist, in this order): requirements, installation, configuration and resources. (See '<chapter xml:id="extname.setup"...' in the skeleton) > 3. The reference.xml will contain samples and this kind about a > extension. The setup and what is an extension will go to the files above. Almost. reference.xml contains in most cases no content (except for an entity referring to the functions). In the rare cases it does its mostly "see also the foo function in the bar extension" sections. (See ' <reference xml:id="functions.extname"...' in the skeleton) Examples, detailed information and long notes have all been moved to its own chapters/articles/appendixes (which are referred to from book.xml). > 3. The file functions.xml is now entities.functions.xml. Is a simple > rename or there is other change? The file is autogenerated. I have already updated all the entities (I hope) in all translations so there is nothing you need to do here. If anyone is interested, here are the steps we took to upgrade en; http://doc.php.net/wiki/skeletons/convert > > [1] With the exception of the pt-br translation, as there was/is a > > typo(I assume) in the mailinglist name causing the mail to be sent out > > to non-existing-mailinglist. > > > I will look at this. The mailing list is not [EMAIL PROTECTED] ? Right, the mailinglist list is [EMAIL PROTECTED], but the mails were sent to [EMAIL PROTECTED] (which doesn't exist). This should be solved now afaik. -Hannes
