The EPUB standard does not address covers. Basically, the first item in the spine is rendered at a "screenfull" typically 600x800 size and used as a cover. However, an informal best practice when creating EPUB covers is if the cover is raster image based to link to the actual raster image via the <meta> tag.
So to summarize, inserting a cover needs the following: 1) Create a wrapper html file and add it to the manifest. Add a reference to the wrapper html as the first item in the <spine>. The wrapper will point to the actual image file (say cover.jpg). 2) Add cover.jpg to the manifest and add the <meta> element that links to it. Examples are in the sub class I linked to above. On Jul 29, 3:19 pm, rolmei <[email protected]> wrote: > On 27 Jul., 17:01, Kovid <[email protected]> wrote: > > > It would be nice to have support for <dc:date> in the OPF metadata and > > a cover. Both of these are implemented in the EpubBuilder sub class > > here: > > http://bazaar.launchpad.net/~kovid/calibre/trunk/annotate/head:/src/c... > > > Unfortunately I don't have the time to create a patch against epub.py > > in the sphinx trunk, hence the hackish subclassing > > Hi, > I'll work on it. > The dc:date part is easy. > > For the cover I first have to find the best and most flexible > solution. > Some sources link to a bitmap in the meta cover attribute, > but also add a html file that embeds the image. Is that necessary? > Has this html file to be added to the spine and reference sections? > Your approach is to link to the html file from the meta cover > attribute. > I'll try to figure it out. > Maybe you could give some feedback. > > Thanks, > Roland -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
