View Single Post
Old 02-26-2012, 01:47 PM   #1
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
Posts: 1,820
Karma: 510215
Join Date: Dec 2011
Location: Midwest USA
Device: Nook STR w/Glowlight, Kindle 3g, Droid
Nook STR(&Color) Cover meta Tag

I ran across a rather irritating problem this weekend.

Nook STR (and Color from what I've read), doesn't recognize:
Code:
<meta content="coverimg" name="cover"/>
...in content.opf. It insists on having:
Code:
<meta name="cover" content="coverimg"/>
...with the name attribute first.

Sigil and apparently caliber epub->epub conversion will 'correct' the problem. But since calibre is already modifying the epub to include the current calibre cover when it sends to the device, perhaps it could insure that order in the meta tag, too?
JimmXinu is offline   Reply With Quote