On 4.10.2011 15:46, Adam Witwer wrote:
> "" Aug 1 2011 Update. I have resigned myself to the need to do some
> post-processing of HTML code after the epub is generated. ""
>
> We take this same approach at O'Reilly (using XSLT that we maintain),
> and there's no reason to think we won't have to continue to use that
> same approach with EPUB 3. Kindlegen is a black box with very limited
> parameters and logging, so we've had to figure out what input work
> best with it, and feed that input in accordingly. All of Amazon's
> tools expect the structure that Kindlegen outputs, so using some
> other tool is (like Calibre) is dangerous and can lead to
> embarrassing problems like the sample ebook being completely mangled,
> highlighting working in odd ways, and so on.
Hi Adam,
thanks for useful (albeit not very encouraging information).
Do you think that you can share back at least general patches required
for producing Kindle-friendly HTML?
Thanks,
Jirka
--
------------------------------------------------------------------
Jirka Kosek e-mail:
jirka@kosek.cz http://xmlguru.cz------------------------------------------------------------------
Professional XML consulting and training services
DocBook customization, custom XSLT/XSL-FO document processing
------------------------------------------------------------------
OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
------------------------------------------------------------------