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

RE: Prioritisation

From: Deborah Kaplan <dkaplan@safaribooksonline.com>
Date: Tue, 4 Aug 2015 14:14:36 -0400 (Eastern Daylight Time)
To: "Siegman, Tzviya - Hoboken" <tsiegman@wiley.com>
cc: Dave Cramer <dauwhe@gmail.com>, "public-digipub@w3.org" <public-digipub@w3.org>
Message-ID: <alpine.WNT.2.00.1508041411210.10448@DKaplan.safarijv.com>
You're right about the terminology, Tzviya! I am intimately familiar
with CSS and page layout, and have read the working draft many times,
but because of the terminology, I assumed that the spec allowed for
linkage between the physical concept of page and the CSS-enable display
of the semantically marked up page. Reading over the specification, it
neither says that it does nor doesn't have that linkage -- I have been
making an assumption about it all this time based on the language.

Careless of me, though I certainly do wish the language did not invite
the confusion!

Deborah Kaplan

On Tue, 4 Aug 2015, Siegman, Tzviya - Hoboken wrote:

> This is why I am not a big fan of the term "pagination". Bill and Leonard responded using the term pagination to mean discrete units of display (boxes, fragments, fragementainers), similar to what is discussed in the CSS paged-media module [1]. Deborah addressed the issue of page numbering, a term that people who are not intimately familiar with CSS or page layout (and even those, like Deborah, who are) may think is what we mean when we say pagination.
> The CSS prioritization document refers to the former [2]
> [1] http://www.w3.org/TR/css3-page/
> [2] http://w3c.github.io/dpub-pagination/priorities.html#pagination
> Tzviya Siegman
> Digital Book Standards & Capabilities Lead
> Wiley
> 201-748-6884
> tsiegman@wiley.com
> -----Original Message-----
> From: Deborah Kaplan [mailto:dkaplan@safaribooksonline.com]
> Sent: Tuesday, August 04, 2015 1:22 PM
> To: Dave Cramer; public-digipub@w3.org
> Subject: RE: Prioritisation
> 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 18:16:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:34:51 UTC