Re: CSS 3 Comments

LOL. You should see what _I_ think of first when I think of pseduo-elements. They are no where near close to what CSS says they are.

(Said in context of being an Arbortext stylesheet developer of years past…)

-J

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

[cid:A1541402-C04D-410B-BA6A-DC7B8E497ADF]

From: <Cramer>, Dave <Dave.Cramer@hbgusa.com<mailto:Dave.Cramer@hbgusa.com>>
Date: Tuesday, November 5, 2013 at 11:30 AM
To: Brady Duga <duga@google.com<mailto:duga@google.com>>, "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:31 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.

I agree that this particular discussion is out-of-scope for CSS3-text. But it's fun, even though it will lead to many opportunities for me to embarrass myself by not understanding the difference between pseudo-classes and pseudo-elements. :)



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