Quote:
Originally Posted by odamizu
Whether or not the books had enhanced typesetting seemed irrelevant.
|
IMHO, the whole "enhanced typesetting" business is nothing but marketing hype. All they did was add a new font with better kerning and hyphenation support. Both features combined will automatically make for a more pleasant reading experience.
Quote:
Originally Posted by odamizu
After KindleUnpack-ing the books, I noticed that books with hyphenation had CSS for hyphens (i.e., -epub-hyphens:auto; -webkit-hyphens:auto) whereas books without hyphens lacked this CSS. Whether or not the books had enhanced typesetting seemed irrelevant.
|
I did some test with the 4.9.1 Kindle for iOS app and found out that sideloaded mobi6 and mobi7 files are automatically hyphenated even if the original CSS was missing -epub-hyphens:auto; -webkit-hyphens:auto entries.
OTOH, AZK (KF8/Mobi8) files required either -epub-hyphens:auto; or -webkit-hyphens:auto; entries for hyphenation.
(The new Bookerly font can be selected for both file types.)
Quote:
Originally Posted by odamizu
Though there may still be something in the opf that enables enhanced typesetting that I missed on my cursory scan. There was also nothing in the CSS (other than the hyphen code) that shouted "enhanced typesetting" to me..
|
Since Amazon has neither updated KindlePreviewer/KindleGen nor the Kindle Publishing Guidelines, it's highly unlikely that there are new "enhanced typesetting" .opf entries.
IMHO, all that Amazon needs to do enable "enhanced typesetting" for existing books is append -epub-hyphens:auto; or -webkit-hyphens:auto; entries to the main stylesheet and maybe remove/override all existing body font definitions so that books will automatically be displayed using the default Bookerly font.