W3C home > Mailing lists > Public > www-style@w3.org > November 2003

Re: [CSS2.1] Text 16.6.2 Bidirectionality with Whitespace Collapsing

From: Tex Texin <tex@i18nguy.com>
Date: Wed, 05 Nov 2003 03:10:54 -0500
Message-ID: <3FA8B08E.E49E5B27@i18nguy.com>
To: fantasai <fantasai@escape.com>
Cc: www-style@w3.org, W3c I18n Group <w3c-i18n-ig@w3.org>

I think I agree with these comments, but I am asking the i18n group to comment.

The FAQ that the GEO group wrote on this suggested "remove all space before the
end tag of the inline element, or remove the dir attribute (if appropriate)."

Here it makes sense to remove unnecessary embedding, not to remove explicit
overrides.
Also, the key impact is on spaces before end tags, not beginning spaces.

http://www.w3.org/International/questions/qa-bidi-space.html
tex


fantasai wrote:
> 16.6.2 Bidirectionality with Whitespace Collapsing
> http://www.w3.org/TR/2003/WD-CSS21-20030915/text.html#q9
> 
> # This is best avoided by using the natural bidirectionality of characters
> # instead of explicit embedding levels.
> 
> It's not always possible to rely on implicit bidi, which is why we *have*
> embedding levels. You shouldn't discourage their use like this. The problem
> is best avoided by keeping start and end tags close to the text: by not
> putting spaces at the start and end of inline elements.
> 
> ~fantasai

-- 
-------------------------------------------------------------
Tex Texin   cell: +1 781 789 1898   mailto:Tex@XenCraft.com
Xen Master                          http://www.i18nGuy.com
                         
XenCraft		            http://www.XenCraft.com
Making e-Business Work Around the World
-------------------------------------------------------------
Received on Wednesday, 5 November 2003 03:11:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:25 GMT