[blaenk]

Haven't checked this thread in a while, so I'm catching up.

Originally Posted by odamizu

Just guessing here, but they might have been MOBI rather than AZW3. I've noticed MOBI has smaller line spacing than AZW3 on all three settings.

I can confirm this. I distinctly remember noticing this when I migrated my library from old MOBI to KF8/AZW3.

Originally Posted by odamizu

Another thought I had is that only AZK (and perhaps MOBI) requires rejiggering for the enhanced typesetting to work, and for AZW3s, the enhanced typesetting is controlled entirely on the device-side. That would explain why Amazon has been rejiggering their Kindlebooks without it seeming to make any difference in the AZW3s we've seen.

This is an excellent theory, and I'm inclined to agree based on what we know so far.

Originally Posted by odamizu

@blaenk and anyone else who has a PW3:

Does the Bookerly font work with ebooks (AZW3 or MOBI) that you created with Calibre? I.e., even if you don't get improved word-spacing and hyphenation, can you still use Bookerly?

Merci, Gracias, Spasibo!

That's affirmative! I'm glad I at least have that so far, since unlike you, I _do_ really want the new typesetting! I imagine it's similar to how other kindle fonts previously worked regardless of the book, i.e. Caecilia. As far as I know, the book's font is more of the edge case.

Originally Posted by Doitsu

Did you add the following style to the main stylesheet before converting your epubs to AZW3 books:

body {
-epub-hyphens:auto; 
-webkit-hyphens:auto; 
}

Personally I added this as a global "Extra CSS" option in Calibre > Preferences > Conversion - Common Options > Look and Feel. I'm not sure if this is the correct way to do it. I have not noticed any hyphenation myself.

Originally Posted by rashkae

[...] and the body css includes -epub-hyphens: auto

This might just be clutter from poor epub being fed to amazon, (both books I sampled were from the same publisher/series) but I'm starting to suspect that the new typesetting engine is just better support for epub css (obeying smaller line heights and hyphen rules, for example) and not any kind of special flag in the book.

This is plausible.

So, since we're not sure exactly what may be the way to leverage the new type setting (if it even is possible for side-loaded books), I'm starting to convert my books in a way that I hope is compatible with it when it's enabled. In particular I'm simply adding the CSS hyphenation directives shown above as well as ticking the checkbox "Keep ligatures".

With respect to that option, however, and ligatures in general, I have a concern. I imagine since some (at least as stated by the tooltip for that checkbox) readers don't support ligatures, I wouldn't be surprised if they catered to the lowest common denominator and simply did not include ligatures. I wonder if the new typesetting can compensate for this by substituting in ligatures where appropriate, or if this is part of what the 'typesetting processing' is doing, assuming the files you guys have downloaded are not the processed ones.