Re: CSS 3 Comments

I would agree with the statement about considering different margins based on page-facing… But does page-facing really apply in the digital/mobile world anymore?

Just as we no longer talk about recto/verso, I’m wondering how relevant the concept of the page spread will be going forward (obviously, it’s still highly relevant right now).

Clearly, we will need these typographic components to do print composition from CSS, so it’s a good idea to make sure the CSS WG is aware of these print requirements if they expect CSS to be used for print output going forward.

I also like Dave’s idea regarding controlling some of the finer points of typography with pseudo-elements. I think there are many places in print typography where we could more easily control the CSS via pseudo elements than on web pages.

What I’d really like to see is a way of building pseudo elements and other selectors into generated text before and after selectors in CSS. There are a lot of programmatic things that can be done in stylesheets with generated text, IMHO.

But this is deviating a bit from the CSS text processing discussion…

I return you to the topic at hand now that I’ve had my $.02. ;)

Jean Kaplansky
Solutions Architect
Aptara, Inc.
Email: jean.kaplansky@aptaracorp.com<mailto:jean.kaplansky@aptaracorp.com>
Skype: JeanKaplansky
Mobile: 518 487 9670

[cid:AF9FE70F-0840-430C-9B68-39A246BF6DAB]

From: Brady Duga <duga@google.com<mailto:duga@google.com>>
Date: Tuesday, November 5, 2013 at 11:25 AM
To: "Cramer, Dave" <Dave.Cramer@hbgusa.com<mailto:Dave.Cramer@hbgusa.com>>
Cc: Éric Aubourg <eric@aubourg.net<mailto:eric@aubourg.net>>, W3C Public Digital Publishing IG Mailing List <public-digipub-ig-comment@w3.org<mailto:public-digipub-ig-comment@w3.org>>
Subject: Re: CSS 3 Comments
Resent-From: <public-digipub-ig-comment@w3.org<mailto:public-digipub-ig-comment@w3.org>>
Resent-Date: Tuesday, November 5, 2013 at 11:26 AM

I was also thinking about different margins based on page-facing. Do we need to target new, left and right pages? Or even/odd pages? Seems like this is a complex enough discussion to avoid in LC comments.


On Tue, Nov 5, 2013 at 8:14 AM, Cramer, Dave <Dave.Cramer@hbgusa.com<mailto:Dave.Cramer@hbgusa.com>> wrote:
On 11/5/13 10:59 AM, "Brady Duga" <duga@google.com<mailto:duga@google.com>> wrote:

I'm not sure I would request the different indent behavior after a break without first understanding if this different rendering is limited to just indents. Are there other styles that might be different at a page boundary? Could there be even/odd differences, or two-up facing page changes? While it might be the correct solution, I think it is a bit hasty to rush one of our use cases into a requested solution. I would argue we leave it off this list, but defer issues about styling changes based on page to our face-to-face discussion with the CSS wg.

+1 to the various other comments, though.

I'm starting to think that some positional pseudo-elements would address lots of these issues:

p::top-of-page { text-indent: 0; }

This might help with something I mentioned in the pagination doc—space breaks that fall at the top/bottom of the page often require ornaments/asterisks:

div.spacebreak::bottom-of-page p { content: '*  *  *'; }


Dave



________________________________
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.