W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2010

[Bug 10807] i18n comment 1 : new attribute: ubi

From: <bugzilla@jessica.w3.org>
Date: Tue, 12 Oct 2010 10:34:28 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P5cBg-0002Tz-Q7@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10807

--- Comment #7 from Maciej Stachowiak <mjs@apple.com> 2010-10-12 10:34:28 UTC ---
(In reply to comment #6)
> Wouldn't it be better to use an element, like <bdo>? <bdi> or something (Bi Di
> Isolate)?

<bdo> doesn't actually do anything by itself, it only sets "unicode-bidi:
bidi-override" if dir is set. From the HTML5 rendering section (which I think
roughly matches what browsers do):

bdo[dir=ltr], bdo[dir=rtl] { unicode-bidi: bidi-override; } /* case-insensitive
*/

The proposal for ubi/bdi/whatever is that it should force unicode-bidi: isolate
regardless of dir setting (or, if set to "off", force it off, but I'm not sure
how that would work with the CSS model). So it's not really parallel to <bdo>,
as proposed.

I'm mildly skeptical of using an element, because, as I mentioned in an earlier
comment, there are 5 unicode-bidi values currently specified, maybe more in the
future. Adding an element for each does not seem like a winning strategy
long-term.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 12 October 2010 10:34:31 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:59 UTC