3) The generated html files are a bit (to say the least) messy and heard to read. Is it possible to either 1) generate more tidy html, or 2) use tidy in the tool chain after generating html?
1) is a question for XSLT experts
There's a DocBook parameter to do this. I've just turned it on and checked the result in; the HTML looks a bit nicer now (albeit not perfect).
2) is not easy either because Boost.Build has no idea what files XSTL will
produce so can't schedule tidy run. You might be better of running tidy
separately, sorry :-(
Well, we know the name when the drop a single .html file (of course); for multiple html files there is the manifest, that could presumably be read to determine what to tidy.
4) Is it possible to specify a different CSS?
http://www.sagehill.net/docbookxsl/UsingCSS.html
says the html.stylesheet parameter can be used.
I'm not totally thrilled about this, because part of the reason for BoostBook was so that Boost documentation could have a common look and feel. Did you want to change the default CSS?
5) Why is: <emphasis role="underline">underline</emphasis> not rendered correctly? See http://tinyurl.com/5otwq under FontStyles.
That's not what I see in HTML, it has:
<span class="underline">underline</span>
and the ".underline" class is not defined in CSS. When I add
span.underline { text-decoration: underline; }
to CSS, it works.
Feel free to check in that change.
Doug
------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Boost-docs mailing list [EMAIL PROTECTED] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
