View Single Post
Old 11-21-2012, 07:39 AM   #14
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 4,814
Karma: 4461973
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW & PW2
@purplepancake:

Quote:
Originally Posted by purplepancake View Post
No, I know it isn't. ISBN are used with books and ASIN are, I believe, unique to Amazon and more commonly used on items other than books. So could there be a conflict or is it ok to have both?
Basically, what I meant was don't manually tweak the ASIN in the metadata field (exth 113) unless you know exactly what you're doing and what it entails .

Quote:
Originally Posted by purplepancake View Post
Ok - but other links on this site disagree here - but I'm happy to try it your way.
Yeah, I know, but I insist . You're welcome to check Calibre's sources to understand how it works in more details .

Quote:
Originally Posted by purplepancake View Post
Ok - so I assume that calibre produces the thumbnail? If so where is it stored/filed on the paperwhite or is it embedded in the mobi. Are you in fact calling the cover a thumbnail or is this a secondary item?
Yes, Calibre generates it from the current cover in Calibre's metadata for this book. There's actually two of them, one embedded, and one sideloaded. The one we usually care about on the PW is the external one (it's used when exth 113 is set), and is stored in system/thumbnails/ on the Touch/PaperWhite. The other one, the embedded one, is nothing new, hand has been part of the MOBI format for a good long while AFAIK. It's only used on the Touch/PW when exth 113 isn't set (ie. a file built by KindleGen, or by Calibre with the 'enable sharing' setting enabled) [no exth 113 is also what triggers the PDOC banner on the PaperWhite, even if the cdetype isn't PDOC]. In both cases, it is in fact a thumbnail, the full size cover is separate.

Quote:
Originally Posted by purplepancake View Post
As a matter of interest only, what is the difference between 'sending to' and dragging or pasting the mobi to the paperwhite, the end result is that it bypasses the Amazon servers but what else happens?
When you sideload manually, you're basically just dropping the mobi file 'as-is' straight out of the build process (be it from Calibre or KG). On the other hand, Calibre's "Send to Device" will do more than that: it will refresh the metadata (embedded cover & thumbnail included) in the file, and will also, depending on the device & settings, send some sidecar files: usually, the APNX file for the page numbers, and the external thumbnail on the Touch/PW.

Last edited by NiLuJe; 11-21-2012 at 07:42 AM.
NiLuJe is offline   Reply With Quote