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

Re: CSS Pages and Pagination (was: Prioritisation)

From: Sanders Kleinfeld <sanders@oreilly.com>
Date: Thu, 6 Aug 2015 13:31:35 -0400
Message-ID: <CAD1Cp0smbDsAFj5YQAt-Mias6rapBtQG7jUOifggpor5MUWZUw@mail.gmail.com>
To: Håkon Wium Lie <howcome@opera.com>
Cc: Daniel Glazman <daniel.glazman@disruptive-innovations.com>, public-digipub@w3.org
On Thu, Aug 6, 2015 at 11:55 AM, Håkon Wium Lie <howcome@opera.com> wrote:
> Also sprach Daniel Glazman:
>  > I choke every time I see the 16
>  > margin boxes specified in CSS Paged Media and the associated magic...
> You have repeatedly made it clear that you dislike this spec [1][2]. Others
> find it quite useful and use it to publish printed publications in
> HTML/CSS, e.g.:

Yes, just to chime in on this point, I work for a publisher that uses
XHTML5 source files in conjunction with a variety of template designs
written in CSS Paged Media to produce print-ready PDFs for > 100
frontlist titles a year. Having source files in XHTML5 format has been
a boon for us, as we can easily autogenerate both print and ebook
outputs (EPUB/MOBI) from one set of files, which makes it trivial for
us to publish updates, errata corrections, etc.

Paged Media does not yet meet every single one of our needs (e.g., we
fall back on XSLT postprocessing of XHTML to generate text nodes for
cross-reference in a more sophisticated fashion than currently
supported by CSS Generated Content for Paged Media), but it meets most
of them, and the fact that there are professional-grade tools
available that implement it (we use AntennaHouse) makes it viable to
center a print publishing program around the specification. I can't
yet say the same for any other spec.

And I'll echo Daniel and Tzviya with a big thumbs up for the excellent
work Dave Cramer and others are doing to evolve and enhance GCPM.

>   http://css4.pub/
> It's quite magical, actually :)
> The 16 margin boxes makes it possible to replicate real-world running
> headers, which can be quite complex. Here are some samples:
>   http://people.opera.com/howcome/2013/tests/css3/samples.jpg
> If you still disagree, I'd like to see the code you propose using for
> the challenge posted in [3].
>  > There is some resistance to changes there, again often for quite
>  > bad reasons. With other concepts like Templates, Regions, Shapes
>  > and Exclusions we could certainly specify much more powerful - and even
>  > simpler - page models. We need implementors for that, and that's where
>  > you all can help. The CSS WG is where it should happen.
> Or you can use Prince and AntennaHouse which already provide
> interoperable implementation of many features from Paged Media.
> [1] https://lists.w3.org/Archives/Public/www-style/2013Jan/0133.html
> [2] https://lists.w3.org/Archives/Public/www-style/2013Jan/0163.html
> [3] https://lists.w3.org/Archives/Public/www-style/2013Jan/0169.html
> Cheers,
> -h&kon
>               Håkon Wium Lie                          CTO °þe®ª
> howcome@opera.com                  http://people.opera.com/howcome
Received on Monday, 10 August 2015 06:50:13 UTC

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