Warning: cover not specified

Derek R · 10-30-2012, 12:34 PM

Hello, I've just downloaded Sigil 0.6.0, which is very snazzy. Creating an epub from it was not a problem. However, when I tried to convert it to a .mobi file using Kindlegen I got the faollowing warning:

Quote:

Warning(prcgen):W14016: Cover not specified

I used the 'add semantics' to specify the cover file just as I had always done in the previous version. Does anyone know what might be causing this warning in Kindlegen?

The cover does appear in Kindlegen, but I like to make sure the ebooks are formatted perfectly for the job.

I also noticed this time round that the max-width styling I had for the cover image came up as a warning:

Code:

<img alt="" src="../Images/cover.jpg" style="max-width:100%;" />

Has something changed there too?

Derek R · 10-30-2012, 12:50 PM

In case anyone else faces this issue, I have just resolved it by adding a semantic to the cover image itself, rather than just the cover.xhtml file.

lrui · 10-31-2012, 02:57 AM

Covers are defined by a meta element in the content.opf file within the metadata section. The meta element needs to have two attributes, “name” which needs to be cover and “content” which points to the id of the cover item (needs to be an image) in the manifest section.

<meta content="cover.jpg" name="cover" />

http://john.nachtimwald.com/2011/08/...ot-showing-up/

sjkramer · 10-31-2012, 11:33 AM

I often have this problem when I've changed the cover image by deleting and replacing the img file—even when everything looks absolutely correct in the content.opf file. It will resolve if I delete all instances of the cover in the meta and the guide of the opf and then reselect them in the semantics menu. I can't explain why, but doing this little dance helps.

Derek R · 11-02-2012, 03:10 AM

Yes, I've noticed that changes to the stylesheet now don't seem to take effect either unless the file is opened, edited and saved in an external editor.

meme · 11-02-2012, 04:22 AM

Quote:

Originally Posted by sjkramer

I often have this problem when I've changed the cover image by deleting and replacing the img file—even when everything looks absolutely correct in the content.opf file. It will resolve if I delete all instances of the cover in the meta and the guide of the opf and then reselect them in the semantics menu. I can't explain why, but doing this little dance helps.

As per the Sigil User Guide, covers require you to Add Semantics to both the cover HTML file and the cover image (well for Kindle anyway) as you've found out. @irui There is no need to edit the OPF as you can do this by right-clicking on the files in Sigil and using the semantic menu.

If you delete a cover image you need to re-add the semantic type of cover to the new image. The OPF data for the cover image will be deleted when you delete the cover image. This all seems to work as expected for me - if you find something inconsistent on 0.6.0 then let us know.

Quote:

Originally Posted by Derek R

Yes, I've noticed that changes to the stylesheet now don't seem to take effect either unless the file is opened, edited and saved in an external editor.

Covers have nothing to do with stylesheets. But at least for me, if I edit a CSS file in a Sigil tab and switch back to the tab for the document then the new CSS is immediately applied. There is no need to use an external editor on the CSS (although its very helpful and fast when testing style tweaks). If you find something different, please detail it here.

lrui · 11-02-2012, 05:06 AM

@meme
Some of my EPUB books couldn't display covers in my nook2, even though I
specified as cover in SIGIL, but it still didn't work. I don't know why.

So I modified the cover's metadata section in OPF and it worked.

meme · 11-02-2012, 05:44 AM

Quote:

Originally Posted by lrui

@meme
Some of my EPUB books couldn't display covers in my nook2, even though I
specified as cover in SIGIL, but it still didn't work. I don't know why.

So I modified the cover's metadata section in OPF and it worked.

It may depend on what version of Sigil you used. 0.4.0 had an issue. The current 0.6.0 versio (and I think 0.5.x) has a specific fix for the Nook for the cover metadata. Nook's apparently required (or required) you to have the metadata attribute name before the content attribute unlike other devices. When you first tag a cover with Add Semantic the attributes are put into the content.opf file in alphabetical order. However, when you save your EPUB Sigil will switch the order of the metadata to read <meta name="cover" content="cover.png" /> to accomodate the Nook's behaviour. You must save to see this, otherwise it will be listed in standard alphabetical order.

lrui · 11-02-2012, 09:34 AM

@meme

Thanks for reply, I see.
When I checked the content.opf, the cover‘s meta attribute is
<meta content="cover" name="cover" />
I changed the above attribute to
<meta content="cover.jpg" name="cover" />

I think there is nothing to do with the order.

10-31-2012, 02:57 AM	#3
lrui Enthusiast Posts: 49 Karma: 475062 Join Date: Aug 2012 Device: nook simple touch	Covers are defined by a meta element in the content.opf file within the metadata section. The meta element needs to have two attributes, “name” which needs to be cover and “content” which points to the id of the cover item (needs to be an image) in the manifest section. <meta content="cover.jpg" name="cover" /> http://john.nachtimwald.com/2011/08/...ot-showing-up/ Last edited by lrui; 10-31-2012 at 02:59 AM.

11-02-2012, 05:06 AM	#7
lrui Enthusiast Posts: 49 Karma: 475062 Join Date: Aug 2012 Device: nook simple touch	@meme Some of my EPUB books couldn't display covers in my nook2, even though I specified as cover in SIGIL, but it still didn't work. I don't know why. So I modified the cover's metadata section in OPF and it worked. Last edited by lrui; 11-02-2012 at 05:26 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Epub to Mobi using Kindle Preview - Cover warning	DTurner	Kindle Formats	3	04-10-2012 05:53 PM
Ended Sony PRS-505 SC w/ Cover and Separate Wedge Light Cover in Canada	notsure	Flea Market	2	11-13-2010 03:28 PM
Deluxe Cover - Warning	will_wiggle	iRex	7	08-28-2008 10:33 AM

10-30-2012, 12:50 PM	#2
Derek R Zealot Posts: 104 Karma: 20 Join Date: Jun 2011 Location: County Down, Northern Ireland Device: none	In case anyone else faces this issue, I have just resolved it by adding a semantic to the cover image itself, rather than just the cover.xhtml file.

10-31-2012, 11:33 AM	#4
sjkramer Connoisseur Posts: 68 Karma: 526028 Join Date: Nov 2009 Location: New York, NY Device: iphone	I often have this problem when I've changed the cover image by deleting and replacing the img file—even when everything looks absolutely correct in the content.opf file. It will resolve if I delete all instances of the cover in the meta and the guide of the opf and then reselect them in the semantics menu. I can't explain why, but doing this little dance helps.

11-02-2012, 03:10 AM	#5
Derek R Zealot Posts: 104 Karma: 20 Join Date: Jun 2011 Location: County Down, Northern Ireland Device: none	Yes, I've noticed that changes to the stylesheet now don't seem to take effect either unless the file is opened, edited and saved in an external editor.

11-02-2012, 09:34 AM	#9
lrui Enthusiast Posts: 49 Karma: 475062 Join Date: Aug 2012 Device: nook simple touch	@meme Thanks for reply, I see. When I checked the content.opf, the cover‘s meta attribute is <meta content="cover" name="cover" /> I changed the above attribute to <meta content="cover.jpg" name="cover" /> I think there is nothing to do with the order.

Advert

Advert