- From: <bugzilla@jessica.w3.org>
- Date: Thu, 30 Jun 2011 23:39:18 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13105 Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xn--mlform-iua@xn--mlform-i | |ua.no --- Comment #2 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-06-30 23:39:17 UTC --- (In reply to comment #1) Regarding cramped: Firstly, if you narrow the browser window, then you get a much tidier view. (On a wide screen, the table splits into paralell columns, which makes it look cramped.) Secondly: the table lists both 'raquo' and 'raquo;' and both 'shy' and 'shy;'. It sems that all HTML4 entities are listed twice (since the closing ';' was optional in HTML4). [The table should have explained why ...] > So I dunno if this is worth the benefit. The code points are there, and that's > all that's strictly necessary. I believe it would add more than it cluttered. # Roy (Fielding) made the point once that when he searched the spec for "anhor" or "anchor element", he found nothing. To rectify this, the Editor did indeed add the word "anchor" - at least once. This simple change added a kind of conceptual link back to previous specifications of HTML. # Similarily, by adding the UNICODE names of these characters, the spec would get lots for free, as the named characters keep many charaters which either are - of have historically been considered - important to HTML. # For instance, currently, in contrast to HTML4, HTML5 does not (yet) discuss how to hyphenate. But by simply listing the Unicode names, then a search for 'hyphen' would bring up at least those hyphen characters that are mentioned in HTML4. Likewise it would also give us the names for AMPERSAND, LESS-THAN sign etc - all in one place rather than scattered around the specification. # Finally, the caption of the table states that the table "is referenced by the previous sections". Thus, it would make sense to complete it with the names, so that it became a more complete reference. E.g. if I want to know the anme of '<' and '>', then it would be more practival to look up the table rather than starting to extract the name from the HTML syntax description or some such thing. -- 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 Thursday, 30 June 2011 23:39:20 UTC