But what is the internal format for the Kindle and MOBI? Does the Kindle or
the Fire support /any/ of the new features of HTML 5? What I think "we" are talking about is heading towards XHMTL5, which is compatible with KF8 (Mobi Version 8) and which will be compatible with EPUB3. By writing code that the tools can accept "directly" and which display correctly on current browsers, then we can reduce the amount of rewriting that Marcello has to do. Or that other tools have to do. And hopefully start heading in a direction where the EPUB and the MOBI that PG posts renders much more similar to how the HTML that PG posts renders, with the PG EPUB and the PG MOBI showing much less frequent "broken parts" -- which happens more often than not nowadays. New HTML5 Elements which seem useful to the PG cause which Amazon says the new Kindlegen (and KFire) supports: wbr section article aside hgroup header footer figure figcaption mark I haven't done an "all points test" yet on the new kindlegen to see how it actually implements this stuff. See http://www.amazon.com/gp/feature.html?ie=UTF8&docId=1000729901
We all know that internally the Kindle supports only a slight variation of HTML 3.2.
Not sure what "we all know." Are you saying Kindle Fire is only internally HTML 3.2? Are you saying KF8 is only internally HTML 3.2? Agreed that the new kindlegen *does not* seem to "magically" fix all the limitations of the older generations of Kindle. Most notably the paragraph top-margin/bottom-margin problem which keeps killing so many of the PG MOBI files remains on older Kindles even using the new kindlegen. See also: http://www.w3.org/TR/html5-diff/