- From: Ambrose LI <ambrose.li@gmail.com>
- Date: Fri, 8 Apr 2011 02:23:26 -0400
- To: Koji Ishii <kojiishi@gluesoft.co.jp>
- Cc: Alan Stearns <stearns@adobe.com>, Håkon Wium Lie <howcome@opera.com>, "www-style@w3.org" <www-style@w3.org>
2011/4/8 Koji Ishii <kojiishi@gluesoft.co.jp>: > It's not CSS WG who makes the final call; it's browser > vendors. My point is that if a feature didn't qualify for > Adobe/Microsoft to pay the development cost for it, how could > it qualify for two or more browser vendors? > > We could try if you insist though. We could put it in to the > spec, ask browser vendors to see it, and it'll make into the > final spec if two or more vendors think it's important enough > to pay the development cost. > > If you want to take this way, can you please tell me > the expected behavior then? I don't have professional > typographic knowledge for Roman typography as I do for > Japanese typography. > > I suppose it's very similar to 'allow-end' value, except that > code points allowed to hang is different. Is this correct? Do > you know list of code points allowed to hang in that case? Do > you allow, for instance, closing parenthesis to hang? OK, if this is the case then just ignore my comments and see what others say. But if we defer it to CSS4 (or later), just make it clear that its removal from CSS3 is due to cost concerns and not because it is “incorrect”. This need to be made very clear: It is very misleading and wrong to state that Roman hanging punctuation on the right edge does not exist. -- cheers, -ambrose my thoughts on HTML5: http://goo.gl/vhv5F + http://goo.gl/leonq (thanks and no thanks)
Received on Friday, 8 April 2011 06:24:04 UTC