On 6/6/07, John Maddock <[EMAIL PROTECTED]> wrote: > Matias Capeletto wrote: > > Which is the rationale of this decision? > > IMHO css layout and admonitions images must be the same because it is > > one book, but I do not understand the imposition of a general chunk > > layout. Many libs docs are design for a particular chunk layout. > > Agree 100%, but if the docs are built as one "book" then that means they are > built as a single XML file: the docbook xml generated for your lib gets > included by the master XML document, and that's what gets chunked. You can > have you're own chunk settings, but then you have to be in a separate > "book". Incidently, the current system doesn't scale at all well: it takes > a fearsomely long time to build in the doc directory: if you're just trying > to test a minor change it's no fun at all :-(
Yes, and there are tons of warning and errors in library docs. Two things. First, I really think we should treat .qbk files with the same diligence we treat our source code. That means taking the time to eliminated all the warnings. A general build, must be a clean build to be successful. Second, Is there a way in which each library generate a .xml and a script join them together to build the general docs? Best regards Matias ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
