StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I needed an XML validation of potentially HTML 5. HTML 4 and XHTML only had a mediocre 250 or so entities, while the current draft (January 2012) has more than 2000.</p> <pre><code>GET 'http://www.w3.org/TR/html5-author/named-character-references.html' | xmllint --html --xmlout --format --noent - | egrep '<code|<span.*glyph' | # get only the bits we're interested in sed -e 's/.*">/__/' | # Add some "__" markers to make e.g. whitespace sed -e 's/<.*/__/' | # entities work with xargs sed 's/"/\&quot;/' | # xmllint output contains " which messes up xargs sed "s/'/\&apos;/" | # ditto apostrophes. Make them HTML entities instead. xargs -n 2 echo | # Put the entity names and values on one line sed 's/__/<!ENTITY /' | # Make a DTD sed 's/;__/ /' | sed 's/ __/"/' | sed 's/__$/">/' | egrep -v '\bapos\b|\bquot\b|\blt\b|\bgt\b|\bamp\b' # remove XML entities. </code></pre> <p>You end up with a file containing 2114 entities.</p> <pre><code><!ENTITY AElig "&#xC6;"> <!ENTITY Aacute "&#xC1;"> <!ENTITY Abreve "&#x102;"> <!ENTITY Acirc "&#xC2;"> <!ENTITY Acy "&#x410;"> <!ENTITY Afr "&#x1D504;"> </code></pre> <p>Plugging this into an XML parser should allow the XML parser to resolve these character entities.</p> <p><em>Update October 2012</em>: Since the working draft now has a JSON file (yes, I'm still using regular expressions) I worked it down to a single sed:</p> <pre><code>curl -s 'http://www.w3.org/TR/html5-author/entities.json' | sed -n '/^ "&/s/"&\([^;"]*\)[^0-9]*\[\([0-9]*\)\].*/<!ENTITY \1 "\&#\2;">/p' | uniq </code></pre> <p>Of course a javascript equivalent would be a lot more robust, but not everyone has node installed. Everyone has sed, right? Random sample output:</p> <pre><code><!ENTITY subsetneqq "&#10955;"> <!ENTITY subsim "&#10951;"> <!ENTITY subsub "&#10965;"> <!ENTITY subsup "&#10963;"> <!ENTITY succapprox "&#10936;"> <!ENTITY succ "&#8827;"> </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload