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

Re: Prioritisation

From: Dave Cramer <dauwhe@gmail.com>
Date: Tue, 4 Aug 2015 12:31:31 -0400
Message-ID: <CADxXqOwpM7JFmpjxS174rQOM8DS=Re7RrgbSJYJNwekCZRG1XA@mail.gmail.com>
Cc: public-digipub@w3.org
On Tue, Aug 4, 2015 at 11:55 AM, Kaveh Bazargan <
kaveh@rivervalleytechnologies.com> wrote:

> Forgive me for a very basic question, but it is a devil's advocate type of
> question. And if this is not the place to ask this perhaps you can direct
> me to any relevant discussions.
>
> 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?
>
> Again, apologies if the answer is really obvious!!
>
> Regards
> Kaveh
>
>
>
I find that reading long-form content is easier if that content is
paginated [1]. Much of the reading we do is now on screens, and HTML+CSS is
a very nice way of rendering content that can adapt to a variety of screen
sizes and types, not to mention the personal needs of the reader. So I
think it would be tremendously valuable to have the ability to paginate in
the browser, thus combining some of the design capabilities of print with
the flexibility and ubiquity of the web. This would make it easier to
develop ebook reading systems and give browser users more choice in how
they read, while preserving the accessibility advantages of the web.

Regards,

Dave

[1]
http://www.clickhole.com/blogpost/time-i-spent-commercial-whaling-ship-totally-chang-768
Received on Tuesday, 4 August 2015 16:31:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 August 2015 16:32:00 UTC