It would be nice if publican could do without Book_Info.xml and Revision_History.xml. The former would then be merged in the main XML document and the latter would simply not exist.
This would make it easier to use publican to generate documentation out of a random docbook file. It would also make it easier to convert an existing document to Publican.
(Bug filed as per request in <4F682EDE.5060403> on the list)
Added info_file parameter to allow overriding where to look for info fields.
Added rev_file parameter to allow overriding where to look for revision history.
Both fields go in the Publican cfg file and need the full name of the file without the path. .e.g. "test.xml" not "en-US/test.xml" not "test".
For books that don't contain a revision history at all, the new add_revision action is a quick way of getting a structure Publican will be happy with, you don't have to xi:include the new file for Publican to use it.
a8b827b..bcedf1e master -> master
1. Create new book
2. Copy XML from Revision_History.xml to the appropriate part of my test book's main XML file (starting from <appendix> and ending with </appendix>)
3. Add the following to publican.cfg: rev_file: <bookname>.xml
4. Remove Revision_History.xml and its xi:include from the book's main XML file
5. Build the book
Similar test for info_file: Success
I'm happy to verify this.