@dwanthny: well, I can't attest to the archaic-ness of mobi's standard :-)... though if you can store an image and then display it - it would seem to me to operate based on rules that should allow the same to be removed and any offsets adjusted. My understanding is that the "cover" image can be stuck into a mobi file in one of several ways - one where it is identified in some header data as "the" cover image, with associated offsets, etc... vs the other way (which I think you alluded to) being just "an" image like any other referenced in the actual HTML of the book content - like any other chapter header images and other in-story images.
re: that last - I dabbled with the "Remove first image" option you mentioned, but it appears I have some mobi files that have the cover image listed OTHER than as the first image, etc... Sigh.
At this point - from a workflow perspective, the most consistently useful method for me is to just convert to html, clean out any references to any existing cover image, then re-convert to mobi (and epub as well for that matter). Since I "am" converting to epub now as well - I'll see if converting straight to epub first instead of html, then making my mods in sigil, then final convert from epub to mobi works ok (ta dwig)...
Thanks all for the thoughts and information - you guys are quite responsive and welcoming to newcomers. Much appreciated!
|