Quote:
Originally Posted by chaley
AFAIK the carousel gets its image from one of two places: the book itself or an amazon web server if the Fire knows that the book is a really-true amazon-purchased book. The cover stored in CC plays no role at all.
|
thanks, i thought so. I was going to force a test case by creating an azw and then updating to a completely different cover via calibre add metadata but i think you've saved me the hassle.
I may still do that test, but we are expecting to see that CC shelf gets the latest calibre metadata cover, kindle fire carousel and book tab view gets whatever is inside of azw.
i also found when messing with cover sizes yesterday that KF likes to cache images, so it's sometimes necessary to reboot it, in between delete book, re-download book , for a fair test of cover imaging same book. otherwise it tried to use its cached image.
it is yet another example of me thinking
hey maybe this built in kindle reader is not so bad after all, then it pops up a fresh annoyance & I go back to mantano again!
A bit off topic but in that same book, the text looked way small in kinlde reader. checking the css, it had font size 1.2 in main calibre class, font size 0.83333 in body text.. in most readers those two cancel each other out [1.2 * 0.833333=1 ], but kindle seems to only look at the body text size.
after zapping both declarations, the epub was unchanged & the azw was well beahved.