Quote:
Originally Posted by jackie_w
... the presence or absence of hyphenation css in the azw3 itself may not be the controlling factor. To use the Kobo as an example ... overriding css file built into the firmware. It's how the customisation of font, size, line-spacing, margins, font weight is handled. Maybe the hyphenation css will be placed in a similar Kindle css override file.
|
At this point I'm kind of thinking CSS inside the book is not the controlling factor. I suppose there might be an overriding CSS file in the firmware, but if the controlling factor is device-side, why would Amazon have to re-process all their ebooks? Unless the overriding CSS file is a totally new thing and they need to add something to the Kindlebooks so they'll recognize it? This really is quite mystifying.
Quote:
Originally Posted by jhowell
Amazon knows for which device a copy is being downloaded and can deliver different versions of books depending on the capabilities of that device. Once someone has both a PW3 and a slightly older device it would be interesting to download the same book to both and see what, if anything, is different between them.
|
Agreed. This is my concern with all my tests -- that the AZW3s I'm downloading via K4Mac don't actually have the enhanced code because K4Mac doesn't support enhanced typesetting yet.
Quote:
Originally Posted by Doitsu
You can extract the header information with DumpMobiHeader_v019.py ...
|
Thanks! I just tried it, then ran "diff" to compare the two log files. I then ran diff to compare everything in the OEBPS folder, including the CSS and OPF files.
Sadly, I don't think it shed any light on this puzzle. The only difference between the files was in the "Watermark (hex)" content: the numbers were different. Everything else was the same. However, I think (but am not positive) that the watermark changes with every download, in which case it would be expected that they would be different, and this finding is not significant.
Also, I'm not sure what the "Watermark (hex)" content is -- is it DRM-related?
I'm now thinking the AZW3s I'm getting via K4Mac are not in fact enhanced, and as jhowell points out, we need an enhanced AZW3 being downloaded to a PW3 to really figure this out.