- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 10 Jul 2008 11:03:26 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5852 Summary: Incorporate Entity Reference Table into Authoring Guide Product: HTML WG Version: unspecified Platform: PC OS/Version: All Status: ASSIGNED Severity: normal Priority: P2 Component: Developer's Guide AssignedTo: lachlan.hunt@lachy.id.au ReportedBy: lachlan.hunt@lachy.id.au QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html@w3.org Obviously, the way this is listed in the HTML5 spec is aimed at implementers, and is totally unusable by authors. This will need significant imporovement for the authoring guide. Things to do before this can be done: * Work out what information is useful for authors - Entity Ref (&foo;) - Equivalent Hexadecimal reference (�) - Equivalent Decimal Reference (�) - Name of character - Image of character (especially in cases where the user may not have appropriate fonts avaialable) - Human readable description - Links to related characters * Provide some way to quickly and easily search or filter the list. * Should it be broken into some sort of categories? If so, how? * Should authors be able to show and hide interesting/uninteresting colums? * It might also be useful to indicate which entities will still work without the trailing semicolon, even though that's non-conforming in HTML5. Here are some existing tables covering HTML4 entity references. http://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references http://www.cookwood.com/html/extras/entities.html http://www.digitalmediaminute.com/reference/entity/index.php The wikipedia table contains additional info about which standard and DTD it was introduced in. That stuff isn't really relevant to HTML5. The digitalmediaminute page takes an interesting approach, instead of a traditional table layout. Additional feature requests and suggestions welcome. -- 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, 10 July 2008 11:04:01 UTC