W3C home > Mailing lists > Public > public-publ-wg@w3.org > July 2018

Re: Cover-image redux

From: Ric Wright <rkwright@geofx.com>
Date: Mon, 30 Jul 2018 08:52:02 -0700
To: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
CC: W3C Publishing Working Group <public-publ-wg@w3.org>
Message-ID: <D7848102.64E2C7%rkwright@geofx.com>
Agreed.  But at present there is no way (in the spec) to achieve both a
bitmap cover for the static library and also a HTML/SVG/Whatever for the
titlepage itself.  OTOH, this may not be a huge problem.  Do we really need
to be able to animate the title page?  Much more importantly, do we want to
make the spec more complex and potentially dissuade authors and RS from
using these ≥advanced≤ features (as happens today in some cases)?

IMO, we have to skate a careful line between enabling interesting use-cases
and discouraging use of EPUB because it is (or appears to be) overly


From:  Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
Date:  Friday, July 27, 2018 at 4:27 AM
To:  Ric Wright <rkwright@geofx.com>
Cc:  W3C Publishing Working Group <public-publ-wg@w3.org>
Subject:  Re: Cover-image redux
Resent-From:  <public-publ-wg@w3.org>
Resent-Date:  Fri, 27 Jul 2018 11:28:41 +0000

Hello Ric,

IMO the best way to deal with this type of use case is to also embed a
bitmap as well.

This way the author can control what shows up in the bookshelf (bitmap) as
well as what shows up in the publication itself (SVG, canvas, OpenGL).

Received on Monday, 30 July 2018 15:53:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:52:29 UTC