Thread: calibre and the new kindle layout engine
View Single Post
Old 06-30-2015, 06:59 AM   #27
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 81,485
Karma: 150264805
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by blaenk View Post
One curiosity I have though is, if it's really that simple of a change that it requires to enable the new typesetting, then why would Amazon have to go through each book to apply this? Couldn't they just set that at the firmware level, for the system to force-apply these changes (e.g. the CSS hyphenation setting) automatically? As for the body font definitions they could simply ignore those, no? I'm not sure why they have to go through each book and make it "new typesetting enabled."
One of my Kindle eBooks that says it is typesetting enabled does not have any hyphenation commands in the CSS. That's why I think it's a toggle in the header like the TTS toggle Amazon added to the header.
Last edited by JSWolf; 06-30-2015 at 04:04 PM.
JSWolf is offline   Reply With Quote