14430 2011-10-11 16:12:19 +0000 Incorrect or inconsistent glyph values for &rang; and &lang; 2013-05-14 21:46:00 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other CLOSED FIXED https://www.w3.org/Bugs/Public/show_bug.cgi?id=12539 https://www.w3.org/Bugs/Public/show_bug.cgi?id=18232 http://www.w3.org/TR/html5/named-character-references#entity-rang P3 normal --- 19489 20702 1 xn--mlform-iua eoconnor eoconnor ian mike public-html-admin public-html-wg-issue-tracking xn--mlform-iua public-html-bugzilla oldest_to_newest 58059 0 xn--mlform-iua 2011-10-11 16:12:19 +0000 * The 'Glyph' column for for &rang; contains 〉 whereas the 'Character(s)' column says that &rang; has been redefined since HTML4 and is now pointing to ⟩/⟩ And ditto: * The 'Glyph' column for for &lang; contains 〈 whereas the 'Character(s)' column says that &lang; has been redefined since HTML4 and is now pointing to ⟨/⟨ Or to quote the source code in the spec: <tr id="entity-rang"> <td> <code title="">rang;</code> </td> <td> U+027E9 </td> <td> <span class="glyph" title="">〉</span> </td> </tr> <tr id="entity-lang"> <td> <code title="">lang;</code> </td> <td> U+027E8 </td> <td> <span class="glyph" title="">〈</span> </td> </tr> Btw, you might also want to see bug 14429 58678 1 ian 2011-10-21 22:53:03 +0000 That's a bug in the preprocessor's parser, I think. 63196 2 ian 2012-01-27 18:26:52 +0000 Is this still broken? 64826 3 xn--mlform-iua 2012-03-01 16:28:16 +0000 (In reply to comment #2) > Is this still broken? Yes, it is still broken. Tested today. 70272 4 contributor 2012-07-18 07:14:57 +0000 This bug was cloned to create bug 17902 as part of operation convergence. 73377 5 eoconnor 2012-09-06 23:28:50 +0000 Looks like this has been fixed. 73383 6 xn--mlform-iua 2012-09-06 23:51:59 +0000 How did you verify that it worked? This is how I verified that it did not work: 1) Search for the cell with the text U+27E9 2) Double click on the cell just to the right of that cell, in order to select its content 3) Copy (Cmd+C on a Mac) 4) Open UnicodeChecker (http://earthlingsoft.net/UnicodeChecker/) 5) Pay Shareware fee to the developer 6) Paste the character you coped into UnicodeChecker 7) Delete the extra space that you proably copied 8) Check the result. RESULT: I get 'RIGHT-POINTING ANGLE BRACKET'/U+232A It should have been: 'MATHEMATICAL RIGHT ANGLE BRACKET'/U+27E9 Sorry. Still broken. 75185 7 eoconnor 2012-10-03 01:19:00 +0000 Will address this and <https://www.w3.org/Bugs/Public/show_bug.cgi?id=18232> at the same time. 76178 8 eoconnor 2012-10-12 21:54:46 +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/commit/573ee3cd9b07533b66ff6fa6ca8b6eaf2a27d8bf Rationale: Fixed. 76193 9 xn--mlform-iua 2012-10-12 22:57:09 +0000 Looked at spec, and it does indeed seem to be corrected now. 81554 10 xn--mlform-iua 2013-01-18 02:42:31 +0000 (In reply to comment #9) > Looked at spec, and it does indeed seem to be corrected now. Since I suspect that bug 20702 is a result of how this bug was solved, I am opening this bug again, so that we can verify - once bug 20702 is solved, that this bug remains solved even then. 83057 11 eoconnor 2013-02-12 22:29:10 +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: Additional Information Needed Change Description: No spec change. Rationale: Resolving as REMIND so that we'll look at this again after bug 20702 is taken care of. 87681 12 eoconnor 2013-05-14 20:42:48 +0000 Reopening, as bug 20702 has been fixed. I'll resolve this once I've verified that the 5.1 nightly on w3.org doesn't exhibit this problem. 87687 13 eoconnor 2013-05-14 21:14:47 +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: Fix verified by David Carlisle in bug 12539 comment 20. 87688 14 xn--mlform-iua 2013-05-14 21:46:00 +0000 I’m relying you and David’s assessment.