W3C home > Mailing lists > Public > www-style@w3.org > April 2011

RE: [css3-text] Hanging punctuation for Roman (was script-specific functionality

From: Koji Ishii <kojiishi@gluesoft.co.jp>
Date: Fri, 8 Apr 2011 02:14:46 -0400
To: Ambrose LI <ambrose.li@gmail.com>
CC: Alan Stearns <stearns@adobe.com>, Håkon Wium Lie <howcome@opera.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <A592E245B36A8949BDB0A302B375FB4E0AB3D55A98@MAILR001.mail.lan>
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?


-----Original Message-----
From: Ambrose LI [mailto:ambrose.li@gmail.com] 
Sent: Friday, April 08, 2011 3:03 PM
To: Koji Ishii
Cc: Alan Stearns; Håkon Wium Lie; www-style@w3.org
Subject: Re: [css3-text] Hanging punctuation for Roman (was script-specific functionality

2011/4/8 Koji Ishii <kojiishi@gluesoft.co.jp>:
> I understand Wikipedia is incorrect. But even if it exists, doesn't 
> the fact that at least two major applications in the world not 
> supporting the feature indicate that it's not very important to put 
> into CSS3?


In fact, one of my biggest complaints about InDesign is the lack of support of hanging punctuation.

A lot of CSS3 initiatives are already way far ahead of Word and InDesign (which, btw, does not even support RTL languages properly except in the special ME versions). It makes absolutely no sense to remove a valid feature from CSS just because other software have not yet caught up with CSS.


my thoughts on HTML5: http://goo.gl/vhv5F + http://goo.gl/leonq (thanks and no thanks)
Received on Friday, 8 April 2011 06:16:52 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:45 UTC