This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 5852 - Incorporate Entity Reference Table into Authoring Guide
Summary: Incorporate Entity Reference Table into Authoring Guide
Status: NEW
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 Reference (editor: Lachlan Hunt) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Lachlan Hunt
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2008-07-10 11:03 UTC by Lachlan Hunt
Modified: 2015-10-05 00:56 UTC (History)
5 users (show)

See Also:


Description Lachlan Hunt 2008-07-10 11:03:26 UTC
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.

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.
Comment 1 Lachlan Hunt 2008-07-19 21:03:34 UTC
Initial draft created. (See URL)

Contains several known bugs:

* Major layout bugs in Opera, minor bugs with Firefox
* Doesn't handle characters with either long or many named character references well
* Will need to provide images of glyphs, most system fonts still lack too many (or provide the wrong glyphs for some characters!)
* Need to add Unicode Category selection and filtering support
Comment 3 Simon Pieters 2008-07-22 09:08:49 UTC
I would prefer if the leading zeros were dropped in the hex NCR and that the NCRs were always visible -- not just on hover (I think the hover effect is a bit annoying). I'd also like to have the Unicode name of the character visible so that I can search the page using my browser search feature.