Kindle Paperwhite 2-Voyage Software Update 5.6.5

[charleski]

I see someone asked above about the differences between the LCD and eInk versions of Bookerly. Since I got access to both I took a look. There are some very minor changes in the base contour of the glyphs:

but the main change is in the hinting used, with the eInk version hinted to render much bolder:


Speaking about hinting, I tried adding malformed hints to Fontin which would distort the characters. On ADE you can just see the effects of the bad hinting, but I couldn't see any change in rendering on the Kindle, meaning that (as we should expect by now) the Kindle doesn't use hinting on embedded fonts (example pics attached below).

On a 300dpi device this isn't a big deal. Anyone who's bought an ePub where the publisher's lazily embedded Charis to cover all the glyphs will know that bad hinting is worse than no hinting -- Charis is notorious for its badly-speced alignment zones that cause cobblestoning.

[Edit]After posting this I realised I'd been using a font with CFF outlines and Type1 hinting for the test of embedded font hinting, so went back and manipulated a different font that used TrueType (quadratic) outlines and TT hinting (which is completely different). This did show a difference, indicating that the hinting engine is not actually turned off for embedded fonts, but only works for those with TT contours. In retrospect, given the differences shown above, I should have tried this initially.

[Dr. Drib]

Moderator Notice

charleski
Please take a few moments to read our Posting Guidelines, in particular the part about the maximum image size allowed (600x600 pixels). Images that violate those guidelines will be deleted.

It is every member's responsibility to read our Posting Guidelines and follow them.

Thanks.

[adamselene]

I did some research today on ligatures with KF8 and older Kindles.

There is specific code in kindlegen to expand precomposed ligatures back to their constituent letters. This is sort of obnoxious, but is probably due to the fact that older Kindles (note: I only tested on a Touch, but I assume it's true of all older devices) render them horribly—it looks like they're using a fallback font that's completely different from Caecilia.

However, if you want to use precomposed ligatures (Unicode code points FB00-FB04) in your KF8 files, there are two options:

1) Use Calibre. It has a checkbox to turn off ligature expansion, and Just Works. (However, I didn't like using Calibre, because it doesn't use HUFF/CDIC compression, and ignores the Adobe page-map, making its own instead.)

2) Binary patch kindlegen. Ultimately, it just has a simple table of ligatures. E.g., in 0208-797bf75, it starts here:

0x88875c0: 0x00000132 0x08887e48 0x00000002 0x00000133
0x88875d0: 0x088d5548 0x00000002 0x000001c7 0x08887e4b
0x88875e0: 0x00000002 0x000001c8 0x08887e4e 0x00000002
0x88875f0: 0x000001c9 0x08887e51 0x00000002 0x000001ca

The format is simple: triplets of UTF-16 code point, string pointer, string length. The interesting part of the standard ligatures is here:

0x8887698: 0x0000fb00 0x0888f0ba 0x00000002 0x0000fb01
0x88876a8: 0x0888dc45 0x00000002 0x0000fb02 0x08887e6e
0x88876b8: 0x00000002 0x0000fb03 0x08887e69 0x00000003
0x88876c8: 0x0000fb04 0x08887e6d 0x00000003

Replace the code points with something innocuous (I used 0xebcd), and voila, it now outputs the ligatures. You'll also now see this in the informational output:

Info(prcgen):I1046: Found UNICODE range: Alphabetic Presentation Forms [FB00..FB4F]

This is really only good for Paperwhites (back to 1st gen) and Voyage, but hey, that works for me!

Addendum: The precomposed ligatures also display fine in current K4PC (both Georgia and Bookerly). It's worth noting that searching for a word with one of these characters in K4PC is wonky (you have to enter the ligature character itself), but it seems to work fine on the hardware.

Further addendum: In case it isn't obvious, most EPUB books do not contain precomposed ligatures, instead relying on the rendering system and the font to build ligatures automatically. You will have to edit the ebook contents to use them. This seems to follow Amazon's general trend of not using any of the bytecode stuff in OpenType.

[charleski]

Just when you thought things couldn't get stranger ...

Here's an example of an fi ligature turning up in a footnote of a sideloaded AZW3 book. I've checked the source epub and it is definitely not hard-coded. I exploded the converted AZW3 and it's not hard-coded there either. Unfortunately so far I've been unable to replicate this in a test book.

(The book was passed through Hyphenate This! which explains the first word.)

[cerem0ny]

Wow, there's some intense detective work going on around these parts lol...
Can one of you typesetting geniuses just haxx0r the Android app for me and make the typesetting features available on there? I have a feeling I'll be checking and rechecking all my books on my Galaxy tab in my grave!!!
Hurry up Amazon!

[JSWolf]

Originally Posted by cerem0ny

Wow, there's some intense detective work going on around these parts lol...
Can one of you typesetting geniuses just haxx0r the Android app for me and make the typesetting features available on there? I have a feeling I'll be checking and rechecking all my books on my Galaxy tab in my grave!!!
Hurry up Amazon!

The answer to the Android Kindle app being hacked to support KFX is a huge NO!