Quote:
Originally Posted by JSWolf
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 toggel Amazon added to the header.
|
I think you're right about the toggle. Just wish we could find it.
I have 13 AZW3s downloaded from Amazon into K4Mac. 7 supposedly have enhanced typesetting, 6 do not. (I say supposedly because I'm only like 95% sure K4Mac receives the same version as an eink Kindle. Does anyone know for sure?)
Of the 7 enhanced AZW3s, only 1 has CSS for hyphens.
K4Mac: When opening the enhanced AZW3s in K4Mac, the only one that shows hyphens is the one with hyphen-CSS.
K4iOS: When downloading the same titles into K4iOS (and receiving AZK? or MOBI? I'm not sure what K4iOS receives, but it's not AZW3), 6 out of 7 show hyphens, including 5 that do not have hyphen-CSS in the AZW3.
Of the 6 non-enhanced AZW3s, 1 has CSS for hyphens.
K4Mac: When opening the non-enhanced AZW3s in K4Mac, the one with hyphen-CSS has hyphens, even though it is non-enhanced. The rest have no hyphens.
K4iOS: When downloading the same titles into K4iOS, the same thing happens: if it has hyphen-CSS in the AZW3, it shows hyphens in K4iOS, even if it is non-enhanced.
Not surprisingly, my Kindle Voyage does not show hyphens for anything, regardless of CSS or enhanced typesetting. But once the updated software is released, it will be interesting to see what happens -- and until then, the above tests are somewhat flawed as it's like working with half a blindfold.