- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 13 Jul 2005 21:18:16 +0000 (UTC)
- To: Karl Dubost <karl@w3.org>
- Cc: www-style@w3.org
- Message-ID: <Pine.LNX.4.62.0507132111480.7450@dhalsim.dreamhost.com>
On Wed, 13 Jul 2005, Karl Dubost wrote: > > Q is unlikely to be implemented in browsers. > > What the author can do? I don't know. The XHTML2 WG decided to revamp <q> in XHTML2, changing its processing model substantially. (The WHATWG has yet to come up with a solution for how to handle <q> in HTML5, but it is a concern there too.) > 1. Use <q>« something here »</q> > Pb: Browsers usually do "" for the element q so it will give something > -> "« something here »" > > 2. Use CSS to control the rendering of q with quote > > If 2. is not implemented, we are in the case that we have now. quote is > dropped from CSS 2.1. ok. You don't need 'quotes' from CSS to do quotes on <q>, as has been pointed out. The 'quotes' feature in CSS2.1 is for much, much more complicated scenarios than <q> (e.g. getting multi-paragraphs quote typographically correct). > I then propose to coordinate with the HTML WG to "fix" HTML 4.01 and ask > browser vendors to not implement anymore the "" for q and leave freedom > to the authors. It will be a kind of pragmatic solution. Sadly, the HTML WG has, as far as I can tell, abandoned HTML. I suggest you raise your suggestion with the WHATWG, though (whatwg@whatwg.org). As far as CSS is concerned, however, I don't understand how any of this is the CSSWG's concern. 'quotes' aren't required to style <q> in HTML, so removing it doesn't change much. And we don't want to remove it anyway, we would only do so if we were required to do so in order to exit CR. I guess I don't understand why what happens with the <q> element is relevant to us. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 13 July 2005 21:18:23 UTC