20702 2013-01-18 02:40:03 +0000 named-character-references.html fakes the represenation of named character entities 2013-05-14 21:46:16 +0000 1 1 1 Unclassified HTML WG Editor tools unspecified PC All CLOSED FIXED http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#named-character-references P3 normal --- 14430 1 xn--mlform-iua eoconnor eoconnor erika.doyle mike public-html-admin public-html-wg-issue-tracking silviapfeiffer1 travil xn--mlform-iua public-html-bugzilla oldest_to_newest 81553 0 xn--mlform-iua 2013-01-18 02:40:03 +0000 ISSUE: (A) In Working Drafts up until bug 1430 was solved, the spec had represented the glyphs by using a numeric character reference. http://www.w3.org/TR/2012/WD-html5-20120329/named-character-references.html#named-character-references Example code, Aacute: <span class="glyph" title="">&#193;</span> (B) But starting with Working Draft of 25th of October 2012, the spec has started to fake it, by using self reference. http://www.w3.org/TR/2012/WD-html5-20121025/named-character-references.html#named-character-references Example code, Aacute: <span class="glyph" title="">&Aacute;</span> CONSEQUENCES OF THE BUG: * The glyph column becomes unreliable - in broken and legacy user agents, unless the parser already has a correct implementation of the named character references, one cannot trust that the character displayed is the inteded character. * Also, the WHATWG spec doesn't fake this way, and so WHATWG spec is more reliable. PROPOSAL: * Either clarify that the glyph column is not normative. * Or go back to the old solution where the glyph is referenced as a numeric character reference * Or adopt the solution in the WHATWG spec, which represents the glyph as normal (unescaped) characters 83885 1 eoconnor 2013-03-01 21:34:58 +0000 Note that this is only a problem in the multi-page spec; the single-page spec is correct. Moving to "Editor tools" component as the culprit is most probably the spec splitter. 87676 2 eoconnor 2013-05-14 18:54:33 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: https://github.com/w3c/html-tools/commit/5f9f4a20b520da183084bb6a0c28cdac869ba0cc Rationale: Fixed. 87689 3 xn--mlform-iua 2013-05-14 21:46:16 +0000 I’m relying you and David’s assessment.