View Single Post
Old 04-24-2012, 02:43 PM   #350
jhowell
Groupie
jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.
 
jhowell's Avatar
 
Posts: 192
Karma: 59999
Join Date: Nov 2011
Location: Florida
Device: iPad 2, Kinde PW II
I agree that it would not be appropriate for an unpack tool to generate new xhtml for the cover and handling it via metadata is the most sensible thing to do. That said, the full-size cover images in the KF8 files I have unpacked to EPUB are manifested, but not explicitly indicated as being a cover in the OPF. I suggest adding a name=”cover” meta tag (as per Amazon) and/or cover-image property (as per EPUB-3).

ETA: Ooops, my bad.. The cover meta tag IS present in the unpacked files. Never mind.

Last edited by jhowell; 04-24-2012 at 02:50 PM. Reason: Correction
jhowell is offline   Reply With Quote