W3C home > Mailing lists > Public > www-style@w3.org > December 2013

Re: [css-regions] content/presentation separation, and regions as elements

From: Cramer, Dave <Dave.Cramer@hbgusa.com>
Date: Thu, 19 Dec 2013 22:58:38 -0500
To: Alan Stearns <stearns@adobe.com>, www-style list <www-style@w3.org>
Message-ID: <CED92754.43D61%david.cramer@hbgusa.com>
On 12/19/13 8:13 PM, "Alan Stearns" <stearns@adobe.com> wrote:

>So I wanted to note how you can use named flows to combine content and
>presentation from entirely separate files. I believe Fantasai preferred
>this approach. Combining files is a key feature of IE's current
>implementation, and one reason we added the content keyword to the

This may address some of our concerns, too. We work with HTML files that
represent book chapters. Given that the same source may end up in ebooks
as well as various print editions, we prefer to keep the source "clean"
and use different CSS files for the different presentations. Having a
separate HTML template with presentational information would allow us to
continue with the single content source without resorting to external

>I also brought up the issue of flow-from applying to elements. One thread
>of feedback we've recieved is that flow-from should only apply to
>pseudo-elements (or other CSS-generated boxes). This has never made much
>sense to me. As far as I know, content is the only property that is
>currently restricted to pseudo-elements, and we're looking to extend its
>use to elements. I believe Fantasai agreed with me that restricting a new
>property to pseudo-elements would be a bad choice.

Yep. Luckily PrinceXML ignores this restriction on the content property,
and we find it really useful to entirely replace some elements. Our source
HTML may contain "space breaks" [1] with three asterisks to indicate a
change of scene in a novel. We may replace those asterisks with some
font-based ornament or image in the printed version but not the ebook
version. That's really easy using content on the element.



This may contain confidential material. If you are not an intended recipient, please notify the sender, delete immediately, and understand that no disclosure or reliance on the information herein is permitted. Hachette Book Group may monitor email to and from our network.
Received on Friday, 20 December 2013 03:59:12 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:17 UTC