On Tue, Aug 4, 2015 at 8:10 PM, Deborah Kaplan < dkaplan@safaribooksonline.com> wrote: ... > > There are any other number of reasons, both accessibility and design, why > rendering a paged model would be desirable. E-book versions of picture > books, for example, need visually rendered pages. > Indeed. That is an important point. But at least for me, as a person coming from the LaTeX world, in my head it seems natural to distinguish between two types of book content layouting needs for: 1. Design type books which need to be very specific about what goes on every page and where it goes. These books will be great visually, but will find it somewhat more challenging to do reflow if the user uses zoom. 2. Structured content type books which possibly need to be able to say which page number something would have been on if the page size had been the standard size, but other than that only need to follow some generally defined rules on how the content is to be laid out and therefore have much less problems doing reflow on zooming, etc. . The page float specification that I am working on [1] is trying to improve the display of the second type books: It should be possibly to say that certain figures or images should always be at the top or bottom of any page, no matter how much zoom the user uses or what the screen size is. I think that should make it possibly to switch to the second type of book layout for a lot of content that had opted for 1 before, which again should improve the reader's experience by improving reflow capabilities, etc. . That being said, for certain type books (such as photo collages, etc., the first type of book design will always be preferred, so both need to be available. [1] http://dev.w3.org/csswg/css-page-floats/
Received on Tuesday, 4 August 2015 19:34:22 UTC