HTML and CSS Reference
In-Depth Information
Named
Entity
Numbered
Entity
Intended
Rendering
HTML5 Alias
Unicode Entity
Description
&
&
&
&
&
Ampersand
©
©
©
©
©
Copyright
>
>
>
>
>
Greater than
<
<
<
<
<
Less than
&quot;
&QUOT;
&#34;
&#x0022;
Double quotes
&reg;
&REG;
&#174;
&#x00AE;
®
Registration mark
&trade;
&TRADE;
&#8482;
&#x2122;
Trademark symbol
T ABLE A-1 Entities Considered Case Insensitive in HTML5
Under Internet Explorer, the rendering engine even in a strict mode will “fix” this
problem and effectively convert this into
<p> &QUOT;E; and &quot;e; </p>
while other browsers will correctly leave this mistake alone.
While it turns out that SGML (and thus traditional HTML) does allow the final
semicolon to be left off in an entity in some cases, the preceding example clearly indicates it
does not allow for that latitude in the middle of words. Just as when dealing with markup
and CSS, it is best to get syntax right rather than rely on some variable fix-up applied by a
browser's rendering engine.
There will be instances when you may get the syntax correct but the browser may not be
able to render the characters meaningfully. The reasons for nonsupport can vary and may
be because a particular font is missing or the operating environment or browser is unable to
render the character. Generally, browsers will present these failures as boxes or diamonds,
like so:
 
Search WWH ::




Custom Search