UPDATE: It’s a couple of days later and today, I changed the source file to include an ISBN for the Amazon Kindle version distinct from the Smashwords version. So I suppose when I changed the cover all those hours ago, all I had to do was clear KPC’s cache by rebooting, and I wouldn’t have had to rebuild the book from scratch. And KPC picked up the new version of the book from the disk. After my obligatory apoplectic fit, I reasoned that, far from dancing to Calibre’s tune, KPC was merrily displaying its own cached data, trying to be smart, to reduce the time to load. But still, KPC was somehow picking up the old version of the book, a version which I had deleted from the disk. How could this be? I had changed it, scrubbed everything, started from scratch. Imagine my surprise when that pronoun appeared, bold as brass on my screen. Into KPC I scurried, with my fingers crossed. I went back to square one, deleted the Calibre-Kindle files from the disk, removed the book from Calibre’s library and recreated the book again. Not a big one, just a pronoun that needed to be replaced by a noun what I had written was ambiguous. Idly paging through the book, I found a typo. I deleted the four Calibre-generated files from my disk and started from scratch in Calibre again. That didn’t work either – KPC was still picking up the original cover. I started from scratch, removing the book from Calibre’s database (“library”) and rebuilding from my html file. I tried changing just the cover and re-saving the whole shebang onto the disk.

Not a huge change, but I needed to replace the book cover file with a new version. But, they make miserable dancing partners.Ī whole afternoon and half the evening I’ve spent rebuilding my latest eBook in Calibre for the Kindle. And I have nothing but admiration for my Kindle, and her close cousin, Kindle-for-PC (KPC).

When it comes to converting my text from crude html to a fully-functioning, card-carrying member of the eBook community, it does the business.

Calibre kindle css theme