- From: <bugzilla@jessica.w3.org>
- Date: Wed, 29 Sep 2010 12:54:19 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10816 Summary: i18n comment 11 : default ignorable code points Product: HTML WG Version: unspecified Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: public-i18n-bidi@w3.org QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org, public-i18n-bidi@w3.org Comment from the i18n review of: http://dev.w3.org/html5/spec/ Comment 11 At http://www.w3.org/International/reviews/html5-bidi/ Editorial/substantive: S Tracked by: AL Location in reviewed document: undefined [http://dev.w3.org/html5/spec/spec.html#contents] Comment:The HTML specification should require user agents to implement the Unicode spec re Default Ignorable Code Points (Unicode Standard version 5.2, Chapter 5 (http://unicode.org/versions/Unicode5.2.0/ch05.pdf), section 5.21), including never displaying the directional formatting characters (LRM, RLM, LRE, RLE, LRO, RLO, and PDF) inappropriately (e.g. as empty boxes or advance widths) even if the underlying platform does not handle them properly. In particular, this must be the case for script dialog text, page titles, and tooltips. Currently, directional formatting characters are most often displayed inappropriately in these context, since user agents mostly rely on the operating system to display the text in these contexts correctly, which does not happen because most LTR users' machines do not have RTL characters support installed. As a result, web applications are unable to use directional formatting characters around LTR text to make sure it is displayed correctly in an RTL context, since doing so will make it display incorrectly in the far more common LTR context. -- 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 Wednesday, 29 September 2010 12:54:22 UTC