Facing 'such a long toolchain', I was wandering why there's such a grey corner in the boost world. :-) And, meanwhile, I'm humble with lack of the experience of doc-making.
Hearing what you've said, I feel now much more relaxed. :-)
I have experience of Doxygen, Ghostscript(a long time ago), am aware of that MikTeX is an implementaion of the famous system LaTEX by Knuth (or I'm wrong?). But I'm quite unfamilar with other stuffs, such as XSL style sheete, DocBook DTD, Iconv, libXslt, and so much.
Perhaps finally I want to make clear that what raw materials, say scripts in code or elsewhere, through what workflow, are rendered to become a pdf file.
The transforms are: quickbook -> BoostBook XML Doxygen -> Doxygen XML -> BoostBookXML BoostBook XML -> Docbook XML DocBook XML -> HTML DocBook XML -> FO XML -> PDF or PS
Thanks for your help. And one more question: Is it possible to make _one_ pdf doc file for all of the boost packages by one run? yes or no? :-)
Well if you want it in black and white like that, then no :-( In any case it's unlikely that a build of everything is what you really want: it would be one huge PDF!!! To build a PDF for library X, then cd into libs/X/doc and do a: bjam pdf start with something small and easy like static_assert, or else there's a "test everything" project in doc/test. Also note that not all Boost libraries are documented with quickbook/boostbook/docbook so your mileage may vary. John.