David Starner wrote: But XHTML sucks for books. There's no sidenote/footnote/endnote
markups, there's no titlepage mark-up (which would make title and author automatically readable in most cases), etc.
Point well taken: I should have referred (appropriately enhanced) XHTML. I have been processing notes in some of the books (see Ivanhoe and Ballantrae). I include the inline NOTE element which, in processing, leads to end notes in XHTML and footnotes in PDF. The lack of page breaks is one of the resoundingly big negatives in HTML--particularly in generating hard copy--so we agree on that. I have tried to compensate for the lack of a title page by styling and generating a table of contents. Not up to PDF standards, but really not TOO bad. Have a look at a couple of the HTML examples. Page dimensions, particularly aspect ratios, are presently a stinker for PDF ebooks--and I hope that the area settles down SOON. But, with my scripts, it is only a problem of handling the multiple PDFs. In my setup, I can generate--and DO generate--multiple XSLT stylesheets with combinations of page dimensions and fonts, etc. So producing multiple PDFs is not the problem (it is quick and easy). What you do with 'em is the problem. Thanks for your interest, John Redmond