W3C home > Mailing lists > Public > public-i18n-bidi@w3.org > July to September 2011

[Bug 11829] parts of default stylesheet setting unicode-bidi and direction should be normative

From: <bugzilla@jessica.w3.org>
Date: Fri, 15 Jul 2011 02:04:17 +0000
To: public-i18n-bidi@w3.org
Message-Id: <E1QhXlJ-0002xh-RI@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11829

Martin Dürst <duerst@it.aoyama.ac.jp> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |duerst@it.aoyama.ac.jp

--- Comment #11 from Martin Dürst <duerst@it.aoyama.ac.jp> 2011-07-15 02:04:16 UTC ---
(In reply to comment #9)
> I can add a normative subsection to the rendering section that applies to
> visual UAs that don't implement CSS, and says what the default rendering in
> bidi terms should be, sure.

I agree that this is the right way to go. I think this could be as simple as
saying something like "If you don't implement bidi CSS, then you still have to
implement rendering as if you implemented bidi CSS with the bidi parts from the
default stylesheet fixed.".

[In RFC 2070, we also had a way out for implementations that didn't want to
implement bidi at all; that was allowed if an implementation didn't display RTL
scripts. But I'm not sure this is still needed/appropriate.]

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 15 July 2011 02:04:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 15 July 2011 02:04:23 GMT