Jim Adcock wrote:
But instead you blame Amazon for the fact that YOU are choosing to make files that will not work correctly on the majority of e-book readers being sold in the market. You could easily make them work if you wanted to, but you don't want them to work.
If I didn't want them to work I wouldn't generate them in the first time. To recap for the last time: 1. I do generate epub files that pass epubcheck and display correctly on ADE mobile readers. 2. Amazon provides a converter "kindlegen" that claims to convert epub files into their proprietary mobi format. 3. kindlegen fumbles the perfectly valid toc that is inside my epubs and generates a mobi file without toc (your claim). 4. You tell me that I should volunteer more unpaid time to work around a bug in Amazon's converter, reverse engineer their closed proprietary format for which they provide no documentation maybe and test it on a dozen devices that I should buy out of my own pocket. IMHO you should bugger the people that chose to make the format proprietary, to not document it in any way and on top of that release buggy converter software. Remember another textbook example: that Internet Explorer even in its 8th incarnation still does not follow w3c standards. And why is that possible? Because developers all over the world chose to work around Microsofts bugs instead of forcing them to fix their software. I'm not going down that slippery slope: If I would I'd spend more time working around other people's bugs than writing new functionality. But YOU are perfectly free to volunteer your time to save Amazon some bucks: Take my epubs, patch them, and convert them to mobis that display the toc when you hit the toc button, and redistribute them on your site. -- Marcello Perathoner webmaster@gutenberg.org