W3C home > Mailing lists > Public > public-digipub@w3.org > August 2015

RE: Prioritisation

From: Deborah Kaplan <dkaplan@safaribooksonline.com>
Date: Tue, 4 Aug 2015 13:21:46 -0400 (Eastern Daylight Time)
To: Dave Cramer <dauwhe@gmail.com>, "public-digipub@w3.org" <public-digipub@w3.org>
Message-ID: <alpine.WNT.2.00.1508041316580.10448@DKaplan.safarijv.com>
In academic contexts, pagination is a requirement. In the classroom, whether a student is reading an electronic version of a book or print version of the book, all students need to be able to clearly say "look at the material which you can locate in this way." With pagination in HTML, a user who is reading an Epub in an accessible reader will be able to follow along when the professor says, "turn to page 32 in the text." Whether or not the pagination is available on demand versus available by default, whether or not the text is displayed as paginated, all of these are details that can be implemented by the different reading systems as appropriate. But the information for correct pagination needs to be available in the document in order to provide the functionality.

Deborah Kaplan

On Tue, Aug 4, 2015 at 11:55 AM, Kaveh Bazargan <kaveh@rivervalleytechnologies.com> wrote:
> 
... 
> My very basic question is, why do we need to "paginate" in the browser in the first place? Why not keep the browser for reflowing and
> interactive text, which is what it is good at, and use a standard mark-up pagination system (TeX/LaTeX would be my choice) to do what
> that is good at. If another system has already solved problems like footnotes and floating figures, what exactly is the drive to reinvent
> that in the browser?
Received on Tuesday, 4 August 2015 17:24:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 August 2015 17:24:05 UTC