View Single Post
Old 06-06-2011, 09:13 AM   #3
terencek
Groupie
terencek ought to be getting tired of karma fortunes by now.terencek ought to be getting tired of karma fortunes by now.terencek ought to be getting tired of karma fortunes by now.terencek ought to be getting tired of karma fortunes by now.terencek ought to be getting tired of karma fortunes by now.terencek ought to be getting tired of karma fortunes by now.terencek ought to be getting tired of karma fortunes by now.terencek ought to be getting tired of karma fortunes by now.terencek ought to be getting tired of karma fortunes by now.terencek ought to be getting tired of karma fortunes by now.terencek ought to be getting tired of karma fortunes by now.
 
Posts: 170
Karma: 1010944
Join Date: Oct 2010
Location: The African bush
Device: Kindle 3
Any idea then why there might be this permissions issue stopping writing to the Calibre configurations file, and how to fix this (I'm using Windows 7)?

What I'm referring to with Calibre insisting on producing a separate cover.jpg file even when the cover is embedded in the (.mobi) output conversion, is that then loading the resulting book in its folder onto the Kindle means the device is cluttered with an unnecessary cover.jpg file for every single book, which is a waste of space.

What I am trying to do is when converting from another format (.epub, .pdf etc.) to .mobi, is avoid having Calibre creating a separate cover.jpg file which I then have to manually delete before sideloading the new book onto the device.

In a similar vein, I also can't seem to stop Calibre creating an equally unnecessary metadata.opf file for every book which is converted, which also has to be deleted before sideloading to the device
terencek is offline   Reply With Quote