REC-html32-19970114 122 KB

Raw Blame History Permalink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<title>HTML 3.2 Reference Specification</title>
<body bgcolor="#FFF6F0"
 background="recbg.jpg"
 text="#000000"
 link="#C00000"
 vlink="#800000" alink="#FF00FF">
<!--basefont size=3-->
<h2 align=right><A HREF="http://www.w3.org/"><img align=left border=0 alt="W3C:"
width=72 height=48
src="http://www.w3.org/pub/WWW/Icons/WWW/w3c_home"></A>
REC-html32</h2>

<h1 align=center>HTML 3.2 Reference Specification</h1>

<h3 align=center>W3C Recommendation <i>14-Jan-1997</i></h3>

<p>Author: <i><a href="http://www.w3.org/People/Raggett">Dave Raggett</a></i>
<tt>&lt;<a href="mailto:dsr@w3.org">dsr@w3.org</a>&gt;</tt></p>

<hr>
<h3>Status of this document</h3>

<p>This document has been reviewed by W3C members and other interested
parties and has been endorsed by the Director as a W3C Recommendation.
It is a stable document and may be used as reference material or cited
as a normative reference from another document. W3C's role in making
the Recommendation is to draw attention to the specification and to
promote its widespread deployment.  This enhances the functionality
and interoperability of the Web.

<p>A list of current W3C Recommendations and other technical documents
can be found at
<a href="http://www.w3.org/pub/WWW/TR/">http://www.w3.org/pub/WWW/TR/</A>.
<hr>

<h2>Abstract</h2>

<p>The HyperText Markup Language (HTML) is a simple markup language used
to create hypertext documents that are portable from one platform to
another. HTML documents are SGML documents with generic semantics that
are appropriate for representing information from a wide range of
applications. This specification defines HTML version 3.2. HTML 3.2 aims
to capture recommended practice as of early '96 and as such to be used
as a replacement for HTML 2.0 (<a href="#refs">RFC 1866</a>).

<hr>

<h2>Contents</h2>

<ul>
<li><a href="#intro">Introduction to HTML 3.2</a>
<li><a href="#sgml">HTML as an SGML application</a>
<li><a href="#html">The Structure of HTML documents</a>
<li><a href="#head">The HEAD element and its children</a>
<li><a href="#body">The BODY element and its children</a>
<li><a href="#catalog">Sample SGML Open Catalog for HTML 3.2</a>
<li><a href="#sgmldecl">SGML Declaration for HTML 3.2</a>
<li><a href="#dtd">HTML 3.2 Document Type Definition</a>
<li><a href="#latin1">Character Entities for ISO Latin-1</a>
<li><a href="#charset">Table of printable Latin-1 Character codes</a>
<li><a href="#acks">Acknowledgements</a>
<li><a href="#refs">Further Reading ...</a>
</ul>

<hr>

<h2><a name=intro>Introduction to HTML 3.2</a></h2>

<p>HTML 3.2 is W3C's specification for HTML, developed in early `96
together with vendors including IBM, Microsoft, Netscape Communications
Corporation, Novell, SoftQuad, Spyglass, and Sun Microsystems. HTML 3.2
adds widely deployed features such as tables, applets and text flow
around images, while providing full backwards compatibility with the
existing standard HTML 2.0.

<p>W3C is continuing to work with vendors on extensions for
accessibility features, multimedia objects, scripting, style sheets,
layout, forms, math and internationalization. W3C plans on incorporating
this work in further versions of HTML.

<h3><a name=sgml>HTML as an SGML Application</a></h3>

<p>HTML 3.2 is an SGML application conforming to International Standard
ISO 8879 -- Standard Generalized Markup Language. As an SGML
application, the syntax of conforming HTML 3.2 documents is defined by
the combination of the <a href="#sgmldecl">SGML declaration</a> and the
<a href="#dtd">document type definition</a> (DTD). This specification
defines the intended interpretation of HTML 3.2 elements, and places
further constraints on the permitted syntax which are otherwise
inexpressible in the DTD.

<p>The SGML rules for record boundaries are tricky. In particular, a
record end immediately following a start tag should be discarded. For
example:

<pre>&lt;P&gt;
Text</pre>

<p>
is equivalent to:</p>

<pre>&lt;P&gt;Text</pre>

<p>Similarly, a record end immediately preceding an end tag should be
discarded. For example:

<pre>Text
&lt;/P&gt;</pre>

<p>is equivalent to:
</p>

<pre>Text&lt;/P&gt;</pre>

<p>Except within literal text (e.g. the <samp>PRE</samp> element), HTML
treats contiguous sequences of white space characters as being
equivalent to a single space character (ASCII decimal 32). These rules
allow authors considerable flexibility when editing the marked-up text
directly. Note that future revisions to HTML may allow for the
interpretation of the horizontal tab character (ASCII decimal 9) with
respect to a tab rule defined by an associated style sheet.

<p>SGML entities in PCDATA content or in CDATA attributes are expanded
by the parser, e.g. <samp>&amp;#233;</samp> is expanded to the ISO
Latin-1 character decimal 233 (a lower case letter e with an acute
accent). This could also have been written as a named character entity,
e.g. <samp>&amp;eacute;</samp>. The &amp; character can be included
in its own right using the named character entity <samp>&amp;amp;</samp>.

<p>HTML allows CDATA attributes to be unquoted provided the attribute
value contains only letters (a to z and A to Z), digits (0 to 9),
hyphens (ASCII
decimal 45) or, periods (ASCII decimal 46). Attribute values can
be quoted using double or single quote marks (ASCII decimal 34 and
39 respectively). Single quote marks can be included within the
attribute value when the value is delimited by double quote marks,
and vice versa.

<p>Note that some user agents require attribute minimisation for the
following attributes: <samp>COMPACT</samp>, <samp>ISMAP</samp>,
<samp>CHECKED</samp>, <samp>NOWRAP</samp>, <samp>NOSHADE</samp> and
<samp>NOHREF</samp>. These user agents don't accept syntax such as
<samp>COMPACT=COMPACT</samp> or <samp>ISMAP=ISMAP</samp> although this
is legitimate according to the HTML 3.2 DTD.

<p>The SGML declaration and the DTD for use with HTML 3.2 are given in
appendices. Further guidelines for parsing HTML are given in
<a href="#refs">WD-html-lex</a>.

<hr>
<h3><a name=html>The Structure of HTML documents</a></h3>


<p>HTML 3.2 Documents start with a &lt;!DOCTYPE&gt; declaration
followed by an HTML element containing a <a href="#head"><samp>HEAD</samp></a>
and then a <a href="#body"><samp>BODY</samp></a> element:

<pre>  &lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"&gt;
  &lt;HTML&gt;
  &lt;HEAD&gt;
  &lt;TITLE&gt;A study of population dynamics&lt;/TITLE&gt;
  <i>... other head elements</i>
  &lt;/HEAD&gt;
  &lt;BODY&gt;
  <i>... document body</i>
  &lt;/BODY&gt;
  &lt;/HTML&gt;</pre>

<P>In practice, the <samp>HTML</samp>, <a href="#head"><samp>HEAD</samp></a>
and <a href="#body"><samp>BODY</samp></a> start and end tags can be omitted
from the markup as these can be inferred in all cases by parsers conforming
to the <a href="#dtd">HTML 3.2 DTD</a>.

<p>Every conforming HTML 3.2 document <b>must</b> start with the
<samp>&lt;!DOCTYPE&gt;</samp> declaration that is needed to distinguish
HTML 3.2 documents from other versions of HTML. The HTML specification
is not concerned with storage entities. As a result, it is not required
that the document type declaration reside in the same storage entity
(i.e. file). A Web site may choose to dynamically prepend HTML files
with the document type declaration if it is known that all such HTML
files conform to the HTML 3.2 specification.

<p>Every HTML 3.2 document must also include the descriptive title
element. A minimal HTML 3.2 document thus looks like:

<pre>  &lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"&gt;
  &lt;TITLE&gt;A study of population dynamics&lt;/TITLE&gt;</pre>


<p><i>Note: the word "Final" replaces "Draft" now that the HTML 3.2
specification has been ratified by the W3C member organizations.</i>

<hr>
<h2><a name=head>The HEAD element</a></h2>

<p>This contains the document head, but you can always omit both
the start and end tags for <samp>HEAD</samp>. The contents of the
document head is an unordered collection of the following elements:

<ul>
<li><a href="#title">The TITLE element</a>
<li><a href="#script">The STYLE element</a>
<li><a href="#script">The SCRIPT element</a>
<li><a href="#isindex">The ISINDEX element</a>
<li><a href="#base">The BASE element</a>
<li><a href="#meta">The META element</a>
<li><a href="#link">The LINK element</a>
</ul>

<pre>&lt;!ENTITY % head.content "TITLE &amp; ISINDEX? &amp; BASE?"&gt;
&lt;!ENTITY % head.misc "SCRIPT|STYLE|META|LINK"&gt;

&lt;!ELEMENT HEAD O O  (%head.content) +(%head.misc)&gt;</pre>

<p>The %head.misc entity is used to allow the associated elements
to occur multiple times at arbitrary positions within the HEAD.
The following elements can be part of the document head:

<dl>
<dt><b><a href="#title">TITLE</a></b> defines the document title,
    and is always needed.
<dt><b><a href="#isindex">ISINDEX</a></b> for simple keyword searches,
    see <samp>PROMPT</samp> attribute.
<dt><b><a href="#base">BASE</a></b> defines base URL for resolving
    relative URLs.
<dt><b><a href="#script">SCRIPT</a></b> reserved for future use
    with scripting languages.
<dt><b><a href="#style">STYLE</a></b> reserved for future use
    with style sheets.
<dt><b><a href="#meta">META</a></b> used to supply meta info as
    name/value pairs.
<dt><b><a href="#link">LINK</a></b> used to define relationships
    with other documents.
</dl>

<p><samp>TITLE</samp>, <samp>SCRIPT</samp> and <samp>STYLE</samp> are
containers and require both start and end tags. The other elements are
not containers so that end tags are forbidden. Note that conforming
browsers won't render the contents of <samp>SCRIPT</samp> and
<samp>STYLE</samp> elements.

<h3><a name=title>TITLE</a></h3>

<pre>&lt;!ELEMENT TITLE - -  (#PCDATA)* -(%head.misc)&gt;</pre>

<p>Every HTML 3.2 document <b>must</b> have exactly one
<samp>TITLE</samp> element in the document's <samp>HEAD</samp>. It
provides an advisory title which can be displayed in a user agent's
window caption etc. The content model is PCDATA. As a result, character
entities can be used for accented characters and to escape special
characters such as &amp; and &lt;. Markup is not permitted in the
content of a <samp>TITLE</samp> element.


<p>Example TITLE element:

<pre>    &lt;TITLE&gt;A study of population dynamics&lt;/TITLE&gt;</pre>

<h3><a name=style>STYLE</a> and <a name=script>SCRIPT</a></h3>

<pre>
&lt;!ELEMENT STYLE  - - CDATA -- placeholder for style info --&gt;
&lt;!ELEMENT SCRIPT - - CDATA -- placeholder for script statements --&gt;
</pre>

<p>These are place holders for the introduction of style sheets and
client-side scripts in future versions of HTML. User agents should hide
the contents of these elements.

<p>These elements are defined with CDATA as the content type. As a
result they may contain only SGML characters. All markup characters or
delimiters are ignored and passed as data to the application, except for
ETAGO ("&lt;/") delimiters followed immediately by a name character
[a-zA-Z]. This means that the element's end-tag (or that of an element
in which it is nested) is recognized, while an error occurs if the ETAGO
is invalid.

<h3><a name=isindex>ISINDEX</a></h3>

<pre>    &lt;!ELEMENT ISINDEX - O EMPTY&gt;
    &lt;!ATTLIST ISINDEX
        prompt CDATA #IMPLIED -- prompt message --&gt;</pre>

<p>The <samp>ISINDEX</samp> element indicates that the user agent should
provide a single line text input field for entering a query string.
There are no restrictions on the number of characters that can be
entered. The <samp>PROMPT</samp> attribute can be used to specify a
prompt string for the input field, e.g.

<pre>    &lt;ISINDEX PROMPT="Search Phrase"&gt;</pre>

<p>The semantics for <samp>ISINDEX</samp> are currently well defined
only when the base URL for the enclosing document is an HTTP URL.
Typically, when the user presses the enter (return) key, the query
string is sent to the server identified by the base URL for this
document. For example, if the query string entered is "ten green apples"
and the base URL is:

<pre>    http://www.acme.com/</pre>

<p>then the query generated is:

<pre>    http://www.acme.com/?ten+green+apples"</pre>

<p>Note that space characters are mapped to "+" characters and that
normal URL character escaping mechanisms apply. For further details see
the <a href="#refs">HTTP</a> specification.

<p><i><b>Note</b> in practice, the query string is resticted to Latin-1
as there is no current mechanism for the URL to specify a character
set for the query.</i>

<h3><a name=base>BASE</a></h3>

<pre>    &lt;!ELEMENT BASE - O EMPTY&gt;
    &lt;!ATTLIST BASE
        href %URL  #REQUIRED
        &gt;</pre>

<p>The <samp>BASE</samp> element gives the base URL for dereferencing
relative URLs, using the rules given by the URL specification, e.g.

<pre>    &lt;BASE href="http://www.acme.com/intro.html"&gt;
     ...
    &lt;IMG SRC="icons/logo.gif"&gt;</pre>

<p>The image is deferenced to

<pre>    http://www.acme.com/icons/logo.gif</pre>

<p>In the absence of a <samp>BASE</samp> element the document URL should
be used. Note that this is not necessarily the same as the URL used to
request the document, as the base URL may be overridden by an HTTP
header accompanying the document.

<h3><a name=meta>META</a></h3>

<pre>
&lt;!ELEMENT META - O EMPTY    -- Generic Metainformation --&gt;
&lt;!ATTLIST META
        http-equiv  NAME    #IMPLIED  -- HTTP response header name  --
        name        NAME    #IMPLIED  -- metainformation name       --
        content     CDATA   #REQUIRED -- associated information     --
        &gt;
</pre>

<p>The <samp>META</samp> element can be used to include name/value pairs
describing properties of the document, such as author, expiry date,
a list of key words etc. The <samp>NAME</samp> attribute specifies the
property name while the <samp>CONTENT</samp> attribute specifies the
property value, e.g.

<pre>    &lt;META NAME="Author" CONTENT="Dave Raggett"&gt;</pre>

<p>The <samp>HTTP-EQUIV</samp> attribute can be used in place of the
<samp>NAME</samp> attribute and has a special significance when
documents are retrieved via the Hypertext Transfer Protocol (HTTP). HTTP
servers may use the property name specified by the HTTP-EQUIV attribute
to create an RFC 822 style header in the HTTP response. This can't be
used to set certain HTTP headers though, see the HTTP specification for
details.

<pre>    &lt;META HTTP-EQUIV="Expires" CONTENT="Tue, 20 Aug 1996 14:25:27 GMT"&gt;</pre>

<p>will result in the HTTP header:

<pre>    Expires: Tue, 20 Aug 1996 14:25:27 GMT</pre>

<p>This can be used by caches to determine when to fetch a fresh copy
of the associated document.

<h3><a name=link>LINK</a></h3>

<p><samp>LINK</samp> provides a media independent method for defining
relationships with other documents and resources. <samp>LINK</samp> has
been part of HTML since the very early days, although few browsers as
yet take advantage of it (most still ignore <samp>LINK</samp> elements).

<p>LINK elements can be used <em>in principle</em>:

<ol type="a">
<li>for document specific navigation toolbars or menus
<li>to control how collections of
    HTML files are rendered into printed documents
<li>for linking associated resources such as
    style sheets and scripts
<li>to provide alternative forms of the current document
</ol>

<pre>
    &lt;!ELEMENT LINK - O EMPTY&gt;
    &lt;!ATTLIST LINK
        href    %URL    #IMPLIED    -- URL for linked resource --
        rel     CDATA   #IMPLIED    -- forward link types --
        rev     CDATA   #IMPLIED    -- reverse link types --
        title   CDATA   #IMPLIED    -- advisory title string --
        &gt;
</pre>

<dl>
<dt><b>href</b>
<dd>Specifies a URL designating the linked resource.

<dt><b>rel</b>
<dd>The forward relationship also known as the "link type". It specifies
a named relationship from the enclosing document to the resource
specified by the <samp>HREF</samp> attribute. HTML link relationships
are as yet unstandardized, although some conventions have been
established.

<dt><b>rev</b>
<dd>This defines a reverse relationship. A link from document A to
document B with <samp>REV=<em>relation</em></samp> expresses the same
relationship as a link from B to A with <samp>REL=<em>relation</em></samp>.
<samp>REV=made</samp> is sometimes used to identify the document author,
either the author's email address with a mailto URL, or a link to the
author's home page.

<dt><b>title</b>
<dd>An advisory title for the linked resource.
</dl>

<p>Here are some proposed relationship values:

<dl>
<dt><samp>rel=top</samp>
<dd>The link references the top of a hierarchy, e.g.
the first or cover page in a collection.


<dt><samp>rel=contents</samp>
<dd>The link references a document serving as a table of contents.

<dt><samp>rel=index</samp>
<dd>The link references a document providing an index
for the current document.

<dt><samp>rel=glossary</samp>
<dd>The link references a document providing a glossary
of terms that are relevant to the current document.

<dt><samp>rel=copyright</samp>
<dd>The link references a copyright statement for
the current document.

<dt><samp>rel=next</samp>
<dd>The link references the next document to visit in a guided tour.
It can be used, for example, to preload the next page.

<dt><samp>rel=previous</samp>
<dd>The link references the previous document in a guided tour.

<dt><samp>rel=help</samp>
<dd>The link references a document offering help, e.g. describing
the wider context and offering further links to relevant documents.
This is aimed at reorienting users who have lost their way.

<dt><samp>rel=search</samp>
<dd>The link references a page for searching material related
to a collection of pages

</dl>

<p>Example <samp>LINK</samp> elements:

<pre>    &lt;LINK REL=Contents HREF=toc.html&gt;
    &lt;LINK REL=Previous HREF=doc31.html&gt;
    &lt;LINK REL=Next HREF=doc33.html&gt;

    &lt;LINK REL=Chapter REV=Contents HREF=chapter2.html&gt;</pre>


<hr>
<h2><a name=body>The BODY element</a></h2>

<p>This contains the document body. Both start and end tags for
<samp>BODY</samp> may be omitted. The body can contain a wide range
of elements:

<ul>
<li><a href="#headings">Headings (H1 - H6)</a>
<li><a href="#address">The ADDRESS element</a>
<li><a href="#block">Block level Elements</a>
<li><a href="#textlevel">Text level elements</a>
</ul>

<p>The key attributes are: <samp>BACKGROUND</samp>,
<samp>BGCOLOR</samp>, <samp>TEXT</samp>, <samp>LINK</samp>,
<samp>VLINK</samp> and <samp>ALINK</samp>. These can be used to set a
repeating background image, plus background and foreground colors for
normal text and hypertext links.

<pre>&lt;!ENTITY % body.content "(%heading | %text | %block | ADDRESS)*"&gt;

&lt;!ENTITY % color "CDATA" -- a color specification: #HHHHHH @@ details? --&gt;

&lt;!ENTITY % body-color-attrs "
        bgcolor %color #IMPLIED
        text %color #IMPLIED
        link %color #IMPLIED
        vlink %color #IMPLIED
        alink %color #IMPLIED
        "&gt;

&lt;!ELEMENT BODY O O  %body.content&gt;
&lt;!ATTLIST BODY
        background %URL #IMPLIED  -- texture tile for document background --
        %body-color-attrs;  -- bgcolor, text, link, vlink, alink --
        &gt;</pre>

<p>Example:

<pre> &lt;body bgcolor=white text=black link=red vlink=maroon alink=fuchsia&gt;</pre>


<dl>
<dt><b>bgcolor</b>
<dd>Specifies the background color for the document body.
See below for the syntax of color values.

<dt><b>text</b>
<dd>Specifies the color used to stroke the document's text.
This is generally used when you have changed the background
color with the <samp>BGCOLOR</samp> or <samp>BACKGROUND</samp> attributes.

<dt><b>link</b>
<dd>Specifies the color used to stroke the text for unvisited hypertext
links.

<dt><b>vlink</b>
<dd>Specifies the color used to stroke the text for visited hypertext
links.

<dt><b>alink</b>
<dd>Specifies the highlight color used to stroke the text for hypertext
links at the moment the user clicks on the link.

<dt><b>background</b>
<dd>Specifies a URL for an image that will be used to tile the document
background.
</dl>

<p><a name=colors>Colors</a> are given in the <a href="#refs">sRGB</a>
color space as hexadecimal numbers (e.g. <samp>COLOR="#C0FFC0"</samp>),
or as one of 16 widely understood color names. These colors were
originally picked as being the standard 16 colors supported with the
Windows VGA palette.</p>

<table align=center width="80%" border=0 cellspacing=10 cellpadding=0>
<caption><b>Color names and sRGB values</b><br></caption>
<tr><td width=16><img src="images/black.gif"><td>Black  = "#000000"
<td width=16><img src="images/green.gif"><td>Green  = "#008000"<br></tr>
<tr><td width=16><img src="images/silver.gif"><td>Silver = "#C0C0C0"
<td width=16><img src="images/lime.gif"><td>Lime   = "#00FF00"<br></tr>
<tr><td width=16><img src="images/gray.gif"><td>Gray   = "#808080"
<td width=16><img src="images/olive.gif"><td>Olive  = "#808000"<br></tr>
<tr><td width=16><img src="images/white.gif"><td>White  = "#FFFFFF"
<td width=16><img src="images/yellow.gif"><td>Yellow = "#FFFF00"<br></tr>
<tr><td width=16><img src="images/maroon.gif"><td>Maroon = "#800000"
<td width=16><img src="images/navy.gif"><td>Navy   = "#000080"<br></tr>
<tr><td width=16><img src="images/red.gif"><td>Red    = "#FF0000"
<td width=16><img src="images/blue.gif"><td>Blue   = "#0000FF"<br></tr>
<tr><td width=16><img src="images/purple.gif"><td>Purple = "#800080"
<td width=16><img src="images/teal.gif"><td>Teal   = "#008080"<br></tr>
<tr><td width=16><img src="images/fuchsia.gif"><td>Fuchsia  = "#FF00FF"
<td width=16><img src="images/aqua.gif"><td>Aqua   = "#00FFFF"<br></tr>
</table>

<h3><a name=level>Block and Text level elements</a></h3>

<p>Most elements that can appear in the document body fall into one of
two groups: block level elements which cause paragraph breaks, and text
level elements which don't. Common block level elements include
<samp>H1</samp> to <samp>H6</samp> (headers), <samp>P</samp>
(paragraphs) <samp>LI</samp> (list items), and <samp>HR</samp>
(horizontal rules). Common text level elements include <samp>EM</samp>,
<samp>I</samp>, <samp>B</samp> and <samp>FONT</samp> (character
emphasis), <samp>A</samp> (hypertext links), <samp>IMG</samp> and
<samp>APPLET</samp> (embedded objects) and <samp>BR</samp> (line
breaks). Note that block elements generally act as containers for text
level and other block level elements (excluding headings and address
elements), while text level elements can only contain other text level
elements. The exact model depends on the element.

<h3><a name=headings>Headings</a></h3>

<pre>
&lt;!--
  There are six levels of headers from H1 (the most important)
  to H6 (the least important).
--&gt;

&lt;!ELEMENT ( %heading )  - -  (%text;)*&gt;
&lt;!ATTLIST ( %heading )
        align  (left|center|right) #IMPLIED
        &gt;
</pre>

<p><samp>H1</samp>, <samp>H2</samp>, <samp>H3</samp>, <samp>H4</samp>,
<samp>H5</samp> and <samp>H6</samp> are used for document headings. You
always need the start and end tags. <samp>H1</samp> elements are more
important than <samp>H2</samp> elements and so on, so that
<samp>H6</samp> elements define the least important level of headings.
More important headings are generally rendered in a larger font than
less important ones. Use the optional <samp>ALIGN</samp> attribute to
set the text alignment within a heading, e.g.

<pre>  &lt;H1 ALIGN=CENTER&gt; <i>... centered heading ...</i> &lt;/H1&gt;</pre>

<p>The default is left alignment, but this can be overridden by an
enclosing <a href="#div"><samp>DIV</samp></a> or <a
href="#center"><samp>CENTER</samp></a> element.

<h3><a name=address>ADDRESS</a></h3>

<pre>    &lt;!ENTITY % address.content "((%text;) | P)*"&gt;

    &lt;!ELEMENT ADDRESS - - %address.content&gt;</pre>

<p>The <samp>ADDRESS</samp> element requires start and end tags, and
specifies information such as authorship and contact details for the
current document. User agents should render the content with
paragraph-breaks before and after. Note that the content is restricted
to paragraphs, plain text and text-like elements as defined by the %text
entity.

<P>Example:

<PRE>&lt;ADDRESS&gt;
Newsletter editor&lt;BR&gt;
J.R. Brown&lt;BR&gt;
8723 Buena Vista, Smallville, CT 01234&lt;BR&gt;
Tel: +1 (123) 456 7890
&lt;/ADDRESS&gt;</PRE>

<h3><a name=block>Block elements</a></h3>

<dl>
<dt><b><a href="#para">P</a></b> <i>paragraphs</i>
<dd>The paragraph element requires a start tag, but the end tag can
always be omitted. Use the <samp>ALIGN</samp> attribute to set the text
alignment within a paragraph, e.g. <samp>&lt;P ALIGN=RIGHT&gt;</samp>

<dt><b><a href="#ul">UL</a></b> <i>unordered lists</i>
<dd>These require start and end tags, and contain one or more
<samp>LI</samp> elements representing individual list items.

<dt><b><a href="#ol">OL</a></b> <i>ordered (i.e. numbered) lists</i>
<dd>These require start and end tags, and contain one or more
<samp>LI</samp> elements representing individual list items.

<dt><b><a href="#dl">DL</a></b> <i>definition lists</i>
<dd>These require start and end tags and contain <samp>DT</samp>
elements that give the terms, and <samp>DD</samp> elements that give
corresponding definitions.

<dt><b><a href="#pre">PRE</a></b> <i>preformatted text</i>
<dd>Requires start and end tags. These elements are rendered with a
monospaced font and preserve layout defined by whitespace and line
break characters.

<dt><b><a href="#div">DIV</a></b> <i>document divisions</i>
<dd>Requires start and end tags. It is used with the <samp>ALIGN</samp>
attribute to set the text alignment of the block elements it contains.
<samp>ALIGN</samp> can be one of <samp>LEFT</samp>, <samp>CENTER</samp>
or <samp>RIGHT</samp>.

<dt><b><a href="#center">CENTER</a></B> <i>text alignment</i>
<dd>Requires start and end tags. It is used to center text lines
enclosed by the <samp>CENTER</samp> element. See <samp>DIV</samp>
for a more general solution.

<dt><b><a href="#bq">BLOCKQUOTE</a></b> <i>quoted passage</i>
<dd>Requires start and end tags. It is used to enclose extended
quotations and is typically rendered with indented margins.

<dt><b><a href="#form">FORM</a></b> <i>fill-out forms</i>
<dd>Requires start and end tags. This element is used to define
a fill-out form for processing by HTTP servers. The attributes
are <samp>ACTION</samp>, <samp>METHOD</samp> and <samp>ENCTYPE</samp>.
Form elements can't be nested.

<dt><b><a href="#isindex">ISINDEX</a></b> <i>primitive HTML forms</i>
<dd>Not a container, so the end tag is forbidden. This predates
<samp>FORM</samp> and is used for simple kinds of forms which have a
single text input field, implied by this element. A single
<samp>ISINDEX</samp> can appear in the document head or body.

<dt><b><a href="#hr">HR</a></b> <i>horizontal rules</i>
<dd>Not a container, so the end tag is forbidden. attributes are
<samp>ALIGN</samp>, <samp>NOSHADE</samp>, <samp>SIZE</samp> and
<samp>WIDTH</samp>.

<dt><b><a href="#table">TABLE</a></b> <i>can be nested</i>
<dd>Requires start and end tags. Each table starts with an optional
<samp>CAPTION</samp> followed by one or more <samp>TR</samp> elements
defining table rows. Each row has one or more cells defined by
<samp>TH</samp> or <samp>TD</samp> elements. attributes for
<samp>TABLE</samp> elements are <samp>WIDTH</samp>, <samp>BORDER</samp>,
<samp>CELLSPACING</samp> and <samp>CELLPADDING</samp>.
</dl>

<hr>
<h3><a name=para>Paragraphs</a></h3>

<pre>    &lt;!ELEMENT P     - O (%text)*&gt;
    &lt;!ATTLIST P
        align  (left|center|right) #IMPLIED
        &gt;</pre>

<p>The <samp>P</samp> element is used to markup paragraphs. It is a
container and requires a start tag. The end tag is optional as it can
always be inferred by the parser. User agents should place paragraph
breaks before and after <samp>P</samp> elements. The rendering is user
agent dependent, but text is generally wrapped to fit the space
available.

<p>Example:

<pre>    &lt;P&gt;This is the first paragraph.
    &lt;P&gt;This is the second paragraph.</pre>

<p>Paragraphs are usually rendered flush left with a ragged right
margin. The <samp>ALIGN</samp> attribute can be used to explicitly
specify the horizontal alignment:

<dl>
<dt><samp>align=left</samp><dd>The paragraph is rendered flush left.
<dt><samp>align=center</samp><dd>The paragraph is centered.
<dt><samp>align=right</samp><dd>The paragraph is rendered flush right.
</dl>

<p>For example:

<PRE>&lt;p align=center&gt;This is a centered paragraph.
&lt;p align=right&gt;and this is a flush right paragraph.</PRE>

<p>The default is left alignment, but this can be overridden by an
enclosing <a href="#div"><samp>DIV</samp></a> or
<a href="#center"><samp>CENTER</samp></a> element.

<h3><a name=lists>Lists</a></h3>

<p>List items can contain block and text level items, including
nested lists, although headings and address elements are excluded.
This limitation is defined via the %flow entity.

<h4><a name=ul>Unordered Lists</a></h4>

<pre>
    &lt;!ELEMENT UL - -  (LI)+&gt;
    &lt;!ENTITY % ULStyle "disc|square|circle"&gt;

    &lt;!ATTLIST UL -- unordered lists --
        type    (%ULStyle)   #IMPLIED   -- bullet style --
        compact (compact)    #IMPLIED   -- reduced interitem spacing --
        &gt;

    &lt;!ELEMENT LI - O %flow -- list item --&gt;
    &lt;!ATTLIST LI
        type   (%LIStyle)    #IMPLIED   -- list item style --
        &gt;
</pre>

<p>Unordered lists take the form:

<pre>    &lt;UL&gt;
      &lt;LI&gt; <i>... first list item</i>
      &lt;LI&gt; <i>... second list item</i>
      ...
    &lt;/UL&gt;</pre>

<P>The <samp>UL</samp> element is used for unordered lists. Both start
and end tags are always needed. The <samp>LI</samp> element is used for
individual list items. The end tag for <samp>LI</samp> elements can
always be omitted. Note that <samp>LI</samp> elements can contain nested
lists. The <samp>COMPACT</samp> attribute can be used as a hint to the
user agent to render lists in a more compact style.

<p>The <samp>TYPE</samp> attribute can be used to set the bullet style
on <samp>UL</samp> and <samp>LI</samp> elements. The permitted values
are "disc", "square" or "circle". The default generally depends on the
level of nesting for lists.

<ul>
<li type=disc>with <samp>&lt;li type=disc&gt;</samp>
<li type=square>with <samp>&lt;li type=square&gt;</samp>
<li type=circle>with <samp>&lt;li type=circle&gt;</samp>
</ul>

<p><i>This list was chosen to cater for the original bullet shapes used by
Mosaic in 1993.</i>

<h4><a name=ol>Ordered (i.e. numbered) Lists</a></h4>

<pre>
    &lt;!ELEMENT OL - -  (LI)+&gt;
    &lt;!ATTLIST OL -- ordered lists --
        type      CDATA      #IMPLIED   -- numbering style --
        start     NUMBER     #IMPLIED   -- starting sequence number --
        compact  (compact)   #IMPLIED   -- reduced interitem spacing --
        &gt;

    &lt;!ELEMENT LI - O %flow -- list item --&gt;
    &lt;!ATTLIST LI
        type      CDATA      #IMPLIED   -- list item style --
        value     NUMBER     #IMPLIED   -- set sequence number --
        &gt;
</pre>

<p>Ordered (i.e. numbered) lists take the form:</p>

<pre>    &lt;OL&gt;
      &lt;LI&gt; <i>... first list item</i>
      &lt;LI&gt; <i>... second list item</i>
      ...
    &lt;/OL&gt;</pre>

<p>The <samp>OL</samp> <samp>START</samp> attribute can be used to
initialize the sequence number (by default it is initialized to 1).
You can set it later on with the <samp>VALUE</samp> attribute on
<samp>LI</samp> elements. Both of these attributes expect integer
values. You can't indicate that numbering should be continued from a
previous list, or to skip missing values without giving an explicit
number.

<p>The <samp>COMPACT</samp> attribute can be used as a hint to the user
agent to render lists in a more compact style. The <samp>OL</samp>
<samp>TYPE</samp> attribute allows you to set the numbering style for
list items:</p>

<table border=1 width="80%" align=center>
<tr><th>Type <th colspan=2>Numbering style<br></tr>
<tr><td align=center>1 <td align=center>Arabic numbers<td align=center>1, 2, 3, ...<br></tr>
<tr><td align=center>a <td align=center>lower alpha<td align=center>a, b, c, ...<br></tr>
<tr><td align=center>A <td align=center>upper alpha<td align=center>A, B, C, ...<br></tr>
<tr><td align=center>i <td align=center>lower roman<td align=center>i, ii, iii, ...<br></tr>
<tr><td align=center>I <td align=center>upper roman<td align=center>I, II, III, ...<br></tr>
</table>

<h4><a name=dl>Definition Lists</a></h4>

<pre>
&lt;!-- definition lists - DT for term, DD for its definition --&gt;

&lt;!ELEMENT DL    - -  (DT|DD)+&gt;
&lt;!ATTLIST DL
        compact (compact) #IMPLIED -- more compact style --
        &gt;

&lt;!ELEMENT DT - O  (%text)*&gt;
&lt;!ELEMENT DD - O  %flow;&gt;
</pre>

<p>Definition lists take the form:

<pre>  &lt;DL&gt;
    &lt;DT&gt; <i>term name</i>
    &lt;DD&gt; <i>term definition</i>
    ...
  &lt;/DL&gt;</pre>

<p><samp>DT</samp> elements can only act as containers for text level
elements, while <samp>DD</samp> elements can hold block level elements
as well, excluding headings and address elements.

<p>For example:

<PRE>&lt;DL&gt;
&lt;DT&gt;Term 1&lt;dd&gt;This is the definition of the first term.
&lt;DT&gt;Term 2&lt;dd&gt;This is the definition of the second term.
&lt;/DL&gt;</PRE>

<P>which could be rendered as:

<dl>
<dt>Term 1<dd>This is the definition of the first term.
<dt>Term 2<dd>This is the definition of the second term.
</dl>

<p>The <samp>COMPACT</samp> attribute can be used with the
<samp>DL</samp> element as a hint to the user agent to render
lists in a more compact style.

<h4><a name=dir>DIR</a> and <a name=menu>MENU</a></h4>

<pre>&lt;!ELEMENT (DIR|MENU) - -  (LI)+ -(%block)&gt;
&lt;!ATTLIST (DIR|MENU)
        compact (compact) #IMPLIED
        &gt;</pre>

<p>These elements have been part of HTML from the early days. They are
intended for unordered lists similar to <samp>UL</samp> elements. User
agents are recommended to render <samp>DIR</samp> elements as
multicolumn directory lists, and <samp>MENU</samp> elements as single
column menu lists. In practice, Mosaic and most other user agents
have ignored this advice and instead render <samp>DIR</samp> and
<samp>MENU</samp> in an identical way to <samp>UL</samp> elements.

<h3><a name=pre>Preformatted Text</a></h3>

<pre>&lt;!ELEMENT PRE - - (%text)* -(%pre.exclusion)&gt;
&lt;!ATTLIST PRE
        width NUMBER #implied
        &gt;</pre>

<p>The <samp>PRE</samp> element can be used to include preformatted
text. User agents render this in a fixed pitch font, preserving spacing
associated with white space characters such as space and newline
characters. Automatic word-wrap should be disabled within
<samp>PRE</samp> elements.

<p>Note that the SGML standard requires that the parser
remove a newline immediately following the start tag
or immediately preceding the end tag.

<p><samp>PRE</samp> has the same content model as paragraphs,
excluding images and elements that produce changes in font size,
e.g. <samp>IMG</samp>, <samp>BIG</samp>, <samp>SMALL</samp>,
<samp>SUB</samp>, <samp>SUP</samp> and <samp>FONT</samp>.

<p>A few user agents support the <samp>WIDTH</samp> attribute. It
provides a hint to the user agent of the required width in characters.
The user agent can use this to select an appropriate font size or to
indent the content appropriately.

<p>Here is an example of a <samp>PRE</samp> element; a verse from
Shelley (To a Skylark):

<pre>&lt;PRE&gt;
       Higher still and higher
         From the earth thou springest
       Like a cloud of fire;
         The blue deep thou wingest,
And singing still dost soar, and soaring ever singest.
&lt;/PRE&gt;</PRE>

which is rendered as:

<pre>       Higher still and higher
         From the earth thou springest
       Like a cloud of fire;
         The blue deep thou wingest,
And singing still dost soar, and soaring ever singest.</PRE>

<p>The horizontal tab character (encoded in Unicode, US ASCII and
ISO 8859-1 as decimal 9) should be interpreted as the smallest
non-zero number of spaces which will leave the number of characters
so far on the line as a multiple of 8. Its use is strongly discouraged
since it is common practice when editing to set the tab-spacing to other
values, leading to misaligned documents.

<h4><a name=xmp>XMP</a>, <a name=listing>LISTING</a> and
<a name=plaintext>PLAINTEXT</a></h4>

<pre>&lt;![ %HTML.Deprecated [

&lt;!ENTITY % literal "CDATA"
        -- historical, non-conforming parsing mode where
           the only markup signal is the end tag
           in full
        --&gt;

&lt;!ELEMENT (XMP|LISTING) - -  %literal&gt;
&lt;!ELEMENT PLAINTEXT - O %literal&gt;

]]&gt;</pre>

<p>These are obsolete tags for preformatted text that predate the
introduction of <a href="#pre">PRE</a>. User agents may support these
for backwards compatibility. Authors should avoid using them in new
documents!

<h3><a name=div>DIV</a> and <a name=center>CENTER</a></h3>

<pre>&lt;!ELEMENT DIV - - %body.content&gt;
&lt;!ATTLIST DIV
        align   (left|center|right) #IMPLIED -- alignment of following text --
        &gt;

&lt;!-- CENTER is a shorthand for DIV with ALIGN=CENTER --&gt;
&lt;!ELEMENT center - - %body.content&gt;</pre>

<p><samp>DIV</samp> elements can be used to structure HTML documents as
a hierarchy of divisions. The <samp>ALIGN</samp> attribute can be used
to set the default horizontal alignment for elements within the content
of the <samp>DIV</samp> element. Its value is restricted to
<samp>LEFT</samp>, <samp>CENTER</samp> or <samp>RIGHT</samp>, and is
defined in the same way as for the paragraph element
<samp>&lt;P&gt;</samp>.

<p>Note that because <samp>DIV</samp> is a block-like element it will
terminate an open <samp>P</samp> element. Other than this, user agents
are <b>not</b> expected to render paragraph breaks before and after
<samp>DIV</samp> elements. <samp>CENTER</samp> is directly equivalent
to <samp>DIV</samp> with <samp>ALIGN=CENTER</samp>. Both
<samp>DIV</samp> and <samp>CENTER</samp> require start and end tags.

<p><i><samp>CENTER</samp> was introduced by Netscape before they added
support for the HTML 3.0 <samp>DIV</samp> element. It is retained in
HTML 3.2 on account of its widespread deployment.</i>

<h3><b><a name=bq>BLOCKQUOTE</a></b></h3>

<pre>&lt;!ELEMENT BLOCKQUOTE - - %body.content&gt;</pre>

<p>This is used to enclose block quotations from other works.
Both the start and end tags are required. It is often rendered
indented, e.g.

<blockquote>
They went in single file, running like hounds on a strong scent,
and an eager light was in their eyes. Nearly due west the broad
swath of the marching Orcs tramped its ugly slot; the sweet grass
of Rohan had been bruised and blackened as they passed.
</blockquote>

<p align=right><em>from "The Two Towers" by J.R.R. Tolkien.</em>

<h3><b><a name=form>FORM</a></b></h3>

<pre>
&lt;!ENTITY % HTTP-Method "GET | POST"
        -- as per HTTP specification
        --&gt;

&lt;!ELEMENT FORM - - %body.content -(FORM)&gt;
&lt;!ATTLIST FORM
        action %URL #IMPLIED  -- server-side form handler --
        method (%HTTP-Method) GET -- see HTTP specification --
        enctype %Content-Type; "application/x-www-form-urlencoded"
        &gt;</pre>

<p>This is used to define an HTML form, and you can have more than one form
in the same document. Both the start and end tags are required. For very
simple forms, you can also use the <a href="#isindex"><samp>ISINDEX</samp></a>
element. Forms can contain a wide range of HTML markup including several
kinds of <a href="#fields">form fields</a> such as single and multi-line
text fields, radio button groups, checkboxes, and menus.

<dl>
<dt><b>action</b>
<dd>This specifies a URL which is either used to post forms via email,
e.g. <samp>action="mailto:foo@bar.com"</samp>, or used to invoke a
server-side forms handler via HTTP, e.g.
<samp>action="http://www.acme.com/cgi-bin/register.pl"</samp>

<dt><b>method</b>
<dd>When the action attribute specifies an HTTP server, the method
attribute determines which HTTP method will be used to send the form's
contents to the server. It can be either <samp>GET</samp> or
<samp>POST</samp>, and defaults to <samp>GET</samp>.

<dt><b>enctype</b>
<dd>This determines the mechanism used to encode the form's contents.
It defaults to <em>application/x-www-form-urlencoded</em>.
</dl>

<p>Further details on handling forms are given in RFC 1867.

<h3><b><a name=hr>HR</a></b> <i>- horizontal rules</i></h3>

<p>Horizontal rules may be used to indicate a change in topic.
In a speech based user agent, the rule could be rendered as a pause.

<pre>&lt;!ELEMENT HR    - O EMPTY&gt;
&lt;!ATTLIST HR
        align (left|right|center) #IMPLIED
        noshade (noshade) #IMPLIED
        size  %Pixels #IMPLIED
        width %Length #IMPLIED
        &gt;</pre>

<p><samp>HR</samp> elements are not containers so the end tag is forbidden.
The attributes are: <samp>ALIGN</samp>, <samp>NOSHADE</samp>,
<samp>SIZE</samp> and <samp>WIDTH</samp>.

<dl>
<dt><b>align</b>
<dd>This determines whether the rule is placed at the left, center
or right of the space between the current left and right margins
for <samp>align=left</samp>, <samp>align=center</samp> or
<samp>align=right</samp> respectively. By default, the rule is centered.

<dt><b>noshade</b>
<dd>This attribute requests the user agent to render the rule in a
solid color rather than as the traditional two colour "groove".

<dt><b>size</b>
<dd>This can be used to set the height of the rule in pixels.

<dt><b>width</b>
<dd>This can be used to set the width of the rule in
pixels (e.g. <samp>width=100</samp>) or as the percentage between the
current left and right margins (e.g. <samp>width="50%"</samp>). The
default is 100%. </dl>

<h3><a name=table>Tables</a></h3>

<p>HTML 3.2 includes a widely deployed subset of the specification
given in <a href="#refs">RFC 1942</a> and can be used to
markup tabular material or for layout purposes. Note that the latter
role typically causes problems when rending to speech or to text
only user agents.

<pre>
&lt;!-- horizontal placement of table relative to window --&gt;
&lt;!ENTITY % Where "(left|center|right)"&gt;

&lt;!-- horizontal alignment attributes for cell contents --&gt;
&lt;!ENTITY % cell.halign
        "align  (left|center|right) #IMPLIED"
        &gt;

&lt;!-- vertical alignment attributes for cell contents --&gt;
&lt;!ENTITY % cell.valign
        "valign  (top|middle|bottom)  #IMPLIED"
        &gt;

&lt;!ELEMENT table - - (caption?, tr+)&gt;
&lt;!ELEMENT tr - O (th|td)*&gt;
&lt;!ELEMENT (th|td) - O %body.content&gt;

&lt;!ATTLIST table                       -- table element --
        align     %Where;   #IMPLIED  -- table position relative to window --
        width     %Length   #IMPLIED  -- table width relative to window --
        border    %Pixels   #IMPLIED  -- controls frame width around table --
        cellspacing %Pixels #IMPLIED  -- spacing between cells --
        cellpadding %Pixels #IMPLIED  -- spacing within cells --
        &gt;

&lt;!ELEMENT CAPTION - - (%text;)* -- table or figure caption --&gt;
&lt;!ATTLIST CAPTION
        align (top|bottom) #IMPLIED
        &gt;

&lt;!ATTLIST tr                       -- table row --
        %cell.halign;              -- horizontal alignment in cells --
        %cell.valign;              -- vertical alignment in cells --
        &gt;

&lt;!ATTLIST (th|td)                  -- header or data cell --
        nowrap (nowrap)  #IMPLIED  -- suppress word wrap --
        rowspan NUMBER   1         -- number of rows spanned by cell --
        colspan NUMBER   1         -- number of cols spanned by cell --
        %cell.halign;              -- horizontal alignment in cells --
        %cell.valign;              -- vertical alignment in cells --
        width   %Pixels  #IMPLIED  -- suggested width for cell --
        height  %Pixels  #IMPLIED  -- suggested height for cell --
        &gt;
</pre>

<p>Tables take the general form:

<pre>  &lt;TABLE BORDER=3 CELLSPACING=2 CELLPADDING=2 WIDTH="80%"&gt;
  &lt;CAPTION&gt;<i> ... table caption ...</i> &lt;/CAPTION&gt;
  &lt;TR&gt;&lt;TD&gt; <i>first cell</i> &lt;TD&gt; <i>second cell</i>
  &lt;TR&gt; ...
  ...
  &lt;/TABLE&gt;</pre>

<p>The attributes on <samp>TABLE</samp> are all optional. By default,
the table is rendered without a surrounding border. The table is
generally sized automatically to fit the contents, but you can also set
the table width using the <samp>WIDTH</samp> attribute.
<samp>BORDER</samp>, <samp>CELLSPACING</samp> and
<samp>CELLPADDING</samp> provide further control over the table's
appearence. Captions are rendered at the top or bottom of the table
depending on the <samp>ALIGN</samp> attribute.

<p>Each table row is contained in a <samp>TR</samp> element, although
the end tag can always be omitted. Table cells are defined by
<samp>TD</samp> elements for data and <samp>TH</samp> elements for
headers. Like <samp>TR</samp>, these are containers and can be given
without trailing end tags. <samp>TH</samp> and <samp>TD</samp> support
several attributes: <samp>ALIGN</samp> and <samp>VALIGN</samp> for
aligning cell content, <samp>ROWSPAN</samp> and <samp>COLSPAN</samp> for
cells which span more than one row or column. A cell can contain a wide
variety of other block and text level elements including form fields and
other tables.

<p>The <samp>TABLE</samp> element always requires both start and end tags.
It supports the following attributes:

<dl>
<dt><b>align</b>
<dd>This takes one of the case insensitive values: <samp>LEFT</samp>,
<samp>CENTER</samp> or <samp>RIGHT</samp>. It specifies the horizontal
placement of the table relative to the current left and right margins.
It defaults to left alignment, but this can be overridden by an
enclosing <a href="#div"><samp>DIV</samp></a> or
<a href="#center"><samp>CENTER</samp></a> element.

<dt><b>width</b>
<dd>In the absence of this attribute the table width is automatically
determined from the table contents. You can use the <samp>WIDTH</samp>
attribute to set the table width to a fixed value in pixels (e.g.
<samp>WIDTH=212</samp>) or as a percentage of the space between the
current left and right margins (e.g. <samp>WIDTH="80%"</samp>).

<dt><b>border</b>
<dd>This attribute can be used to specify the width of the outer border
around the table to a given number of pixels (e.g.
<samp>BORDER=4</samp>). The value can be set to zero to suppress the
border altogether. In the absence of this attribute the border should be
suppressed. Note that some browsers also accept <samp>&lt;TABLE
BORDER&gt;</samp> with the same semantics as <samp>BORDER=1</samp>.

<dt><b>cellspacing</b>
<dd>In traditional desktop publishing software, adjacent table cells
share a common border. This is not the case in HTML. Each cell is given
its own border which is separated from the borders around neighboring
cells. This separation can be set in pixels using the
<samp>CELLSPACING</samp> attribute, (e.g. <samp>CELLSPACING=10</samp>).
The same value also determines the separation between the table border
and the borders of the outermost cells.

<dt><b>cellpadding</b>
<dd>This sets the padding in pixels between the border around each cell
and the cell's contents.
</dl>

<p>The <samp>CAPTION</samp> element has one attribute <samp>ALIGN</samp>
which can be either <samp>ALIGN=TOP</samp> or <samp>ALIGN=BOTTOM</samp>.
This can be used to force the caption to be placed above the top or
below the bottom of the table respectively. Most user agents default to
placing the caption above the table. <samp>CAPTION</samp> always
requires both start and end tags. Captions are limited to plain text and
text-level elements as defined by the %text entity. Block level elements
are not permitted.

<p>The <samp>TR</samp> or table row element requires a start tag, but
the end tag can always be left out. <samp>TR</samp> acts as a container
for table cells. It has two attributes:

<dl>
<dt><b>align</b>
<dd>Sets the default horizontal alignment of cell contents. It takes
one of the case insensitive values: <samp>LEFT</samp>, <samp>CENTER</samp>
or <samp>RIGHT</samp> and plays the same role as the <samp>ALIGN</samp>
attribute on paragraph elements.

<dt><b>valign</b>
<dd>This can be used to set the default vertical alignment of cell
contents within each cell. It takes one of the case insensitive values:
<samp>TOP</samp>, <samp>MIDDLE</samp> or <samp>BOTTOM</samp> to position
the cell contents at the top, middle or bottom of the cell respectively.
</dl>

<p>There are two elements for defining table cells. <samp>TH</samp> is
used for header cells and <samp>TD</samp> for data cells. This
distinction allows user agents to render header and data cells in
different fonts, and enables speech based browsers to do a better job.
The start tags for <samp>TH</samp> and <samp>TD</samp> are always needed
but the end tags can be left out. Table cells can have the following
attributes:

<dl>
<dt><b>nowrap</b>
<dd>The presence of this attribute disables automatic word wrap
within the contents of this cell (e.g. <samp>&lt;TD NOWRAP&gt;</samp>).
This is equivalent to using the <samp>&amp;nbsp;</samp> entity for
non-breaking spaces within the content of the cell.

<dt><b>rowspan</b>
<dd>This takes a positive integer value specifying the number of
rows spanned by this cell. It defaults to one.

<dt><b>colspan</b>
<dd>This takes a positive integer value specifying the number of
columns spanned by this cell. It defaults to one.

<dt><b>align</b> <dd>Specifies the default horizontal alignment of cell
contents, and overrides the <samp>ALIGN</samp> attribute on the table
row. It takes the same values: <samp>LEFT</samp>, <samp>CENTER</samp>
and <samp>RIGHT</samp>. If you don't specify an <samp>ALIGN</samp>
attribute value on the cell, the default is left alignment for
<samp>&lt;td&gt;</samp> and center alignment for <samp>&lt;th&gt;</samp>
although you can override this with an <samp>ALIGN</samp> attribute on
the <samp>TR</samp> element.

<dt><b>valign</b> <dd>Specifies the default vertical alignment of cell
contents, overriding the <samp>VALIGN</samp> attribute on the table row.
It takes the same values: <samp>TOP</samp>, <samp>MIDDLE</samp> and
<samp>BOTTOM</samp>. If you don't specify a VALIGN attribute value on
the cell, the default is middle although you can override this with a
<samp>VALIGN</samp> attribute on the <samp>TR</samp> element.

<dt><b>width</b>
<dd>Specifies the suggested width for a cell content in pixels
excluding the cell padding. This value will normally be
used except when it conflicts with the width requirements
for other cells in the same column.

<dt><b>height</b>
<dd>Specifies the suggested height for a cell content in pixels
excluding the cell padding. This value will normally be
used except when it conflicts with the height requirements
for other cells in the same row.
</dl>

<p>Tables are commonly rendered in bas-relief, raised up with the outer
border as a bevel, and individual cells inset into this raised surface.
Borders around individual cells are only drawn if the cell has explicit
content. White space doesn't count for this purpose with the exception
of &amp;nbsp;.

<p>The algorithms used to automatically size tables should take
into account the minimum and maximum width requirements for each
cell. This is used to determine the minimum and maximum width
requirements for each column and hence for the table itself.

<p>Cells spanning more than one column contribute to the
widths of each of the columns spanned. One approach is to evenly
apportion the cell's minimum and maximum width between these
columns, another is to weight the apportioning according to the
contributions from cells that don't span multiple columns.

<p>For some user agents it may be necessary or desirable to break
text lines within words. In such cases a visual indication that this
has occurred is advised.

<p>The minimum and maximum width of nested tables contribute to the
minimum and maximum width of the cell in which they occur. Once the
width requirements are known for the top level table, the column widths
for that table can be assigned. This allows the widths of nested tables
to be assigned and hence in turn the column widths of such tables.
If practical, all columns should be assigned at least their minimum
widths. It is suggested that any surplus space is then shared out
proportional to the difference between the minimum and maximum width
requirements of each column.

<p>Note that pixel values for width and height refer to screen pixels, and
should be multiplied by an appropriate factor when rendering to very high
resolution devices such as laser printers. For instance if a user agent has
a display with 75 pixels per inch and is rendering to a laser printer with
600 dots per inch, then the pixel values given in HTML attributes should be
multiplied by a factor of 8.

<hr>
<h2><a name=textlevel>Text level elements</a></h2>

<p>These don't cause paragraph breaks. Text level elements
that define character styles can generally be nested. They can
contain other text level elements but not block level elements.

<ul>
<li><a href="#font-style">Font style elements</a>
<li><a href="#phrase">Phrase elements</a>
<li><a href="#fields">Form Fields</a>
<li><a href="#anchor">The A (anchor) element</a>
<li><a href="#img">IMG - inline images</a>
<li><a href="#applet">APPLET <em>(Java Applets)</em></a>
<li><a href="#font">FONT elements</a>
<li><a href="#basefont">BASEFONT elements</a>
<li><a href="#br">BR - line breaks</a>
<li><a href="#map">MAP - client-side image maps</a>
</ul>

<h3><a name=font-style>Font style elements</a></h3>

<p>These all require start and end tags, e.g.

<pre>  This has some &lt;B&gt;bold text&lt;/B&gt;.</pre>

<p>Text level elements must be properly nested - the following
is in error:

<pre>  This has some &lt;B&gt;bold and &lt;I&gt;&lt;/B&gt;italic text&lt;/I&gt;.</pre>

User agents should do their best to respect nested emphasis, e.g.

<pre>  This has some &lt;B&gt;bold and &lt;I&gt;italic text&lt;/I&gt;&lt;/B&gt;.</pre>

<p>Where the available fonts are restricted or for speech output, alternative
means should be used for rendering differences in emphasis.

<dl>
<dt><b>TT</b> teletype or monospaced text
<dt><b>I</b> italic text style
<dt><b>B</b> bold text style
<dt><b>U</b> underlined text style
<dt><b>STRIKE</b> strike-through text style
<dt><b>BIG</b> places text in a large font
<dt><b>SMALL</b> places text in a small font
<dt><b>SUB</b> places text in subscript style
<dt><b>SUP</b> places text in superscript style
</dl>

<P><i>Note: future revisions to HTML may be phase out STRIKE
in favor of the more concise "S" tag from HTML 3.0.</i>

<h3><a name=phrase>Phrase Elements</a></h3>

<p>These all require start and end tags, e.g.

<pre>  This has some &lt;EM&gt;emphasized text&lt;/EM&gt;.</pre>

<dl>
<dt><b>EM</b> basic emphasis typically rendered in an italic font
<dt><b>STRONG</b> strong emphasis typically rendered in a bold font
<dt><b>DFN</b> defining instance of the enclosed term
<dt><b>CODE</b> used for extracts from program code
<dt><b>SAMP</b> used for sample output from programs, and scripts etc.
<dt><b>KBD</b> used for text to be typed by the user
<dt><b>VAR</b> used for variables or arguments to commands
<dt><b>CITE</b> used for citations or references to other sources
</dl>

<h3><a name=fields>Form fields</a></h3>

<p><a href="#input"><samp>INPUT</samp></a>,
<a href="#select"><samp>SELECT</samp></a> and
<a href="#textarea"><samp>TEXTAREA</samp></a> are only allowed within
<samp>FORM</samp> elements. <a href="#input"><samp>INPUT</samp></a> can
be used for a variety of form fields including single line text fields,
password fields, checkboxes, radio buttons, submit and reset buttons,
hidden fields, file upload, and image buttons.
<a href="#select"><samp>SELECT</samp></a> elements are used for single or
multiple choice menus. <a href="#textarea"><samp>TEXTAREA</samp></a>
elements are used to define multi-line text fields. The content of the
element is used to initialize the field.

<h3><a name=input>INPUT <em>text fields, radio buttons, check boxes, ...</em></a></h3>

<p><samp>INPUT</samp> elements are not containers and so the end tag is
forbidden.

<pre>&lt;!ENTITY % IAlign "(top|middle|bottom|left|right)"&gt;

&lt;!ENTITY % InputType
        "(TEXT | PASSWORD | CHECKBOX | RADIO | SUBMIT
            | RESET | FILE | HIDDEN | IMAGE)"&gt;

&lt;!ELEMENT INPUT - O EMPTY&gt;
&lt;!ATTLIST INPUT
        type %InputType TEXT     -- what kind of widget is needed --
        name  CDATA #IMPLIED     -- required for all but submit and reset --
        value CDATA #IMPLIED     -- required for radio and checkboxes --
        checked (checked) #IMPLIED -- for radio buttons and check boxes --
        size CDATA  #IMPLIED     -- specific to each type of field --
        maxlength NUMBER #IMPLIED
        src   %URL  #IMPLIED     -- for fields with background images --
        align %IAlign #IMPLIED   -- vertical or horizontal alignment --
        &gt;</pre>

<dl>
<dt><b>type</b>
<dd>Used to set the type of input field:<p></p>

<dl>
<dt><samp>type=text</samp> <em>(the default)</em>
<dd>A single line text field whose visible size can be set using the <a
href="#isize"><samp>size</samp></a> attribute, e.g. <samp>size=40</samp>
for a 40 character wide field. Users should be able to type more than
this limit though with the text scrolling through the field to keep the
input cursor in view. You can enforce an upper limit on the number of
characters that can be entered with the <a
href="#maxlen"><samp>maxlength</samp></a> attribute. The <a
href="#name"><samp>name</samp></a> attribute is used to name the field,
while the <a href="#value"><samp>value</samp></a> attribute can be used
to initialize the text string shown in the field when the document is
first loaded.


<pre>    &lt;input type=text size=40 name=user value="your name"&gt;</pre>

<dt><samp>type=password</samp>
<dd>This is like type=text, but echoes characters using a character
like * to hide the text from prying eyes when entering passwords.
You can use <a href="#isize"><samp>size</samp></a> and
<a href="#maxlen"><samp>maxlength</samp></a> attributes to control
the visible and maximum length exactly as per
regular text fields.

<pre>    &lt;input type=password size=12 name=pw&gt;</pre>


<dt><samp>type=checkbox</samp>
<dd>Used for simple Boolean attributes, or for attributes that can take
multiple values at the same time. The latter is represented by several
checkbox fields with the same <a href="#name"><samp>name</samp></a> and
a different <a href="#value"><samp>value</samp></a> attribute. Each checked
checkbox generates a separate name/value pair in the submitted data, even
if this results in duplicate names. Use the
<a href="#checked"><samp>checked</samp></a> attribute to initialize
the checkbox to its checked state.

<pre>    &lt;input type=checkbox checked name=uscitizen value=yes&gt;</pre>

<dt><samp>type=radio</samp>
<dd>Used for attributes which can take a single value from a set of
alternatives. Each radio button field in the group should be given the
same <a href="#name"><samp>name</samp></a>. Radio buttons require an explicit
<a href="#value"><samp>value</samp></a> attribute. Only the checked radio
button in the group generates a name/value pair in the submitted data. One
radio button in each group should be initially checked using the
<a href="#checked"><samp>checked</samp></a> attribute.

<pre>
    &lt;input type=radio name=age value="0-12"&gt;
    &lt;input type=radio name=age value="13-17"&gt;
    &lt;input type=radio name=age value="18-25"&gt;
    &lt;input type=radio name=age value="26-35" checked&gt;
    &lt;input type=radio name=age value="36-"&gt;
</pre>

<dt><samp>type=submit</samp>
<dd>This defines a button that users can click to submit the form's
contents to the server. The button's label is set from the
<a href="#value"><samp>value</samp></a> attribute. If the
<a href="#name"><samp>name</samp></a>
attribute is given then the submit button's name/value pair will be
included in the submitted data. You can include several submit buttons
in the form. See <samp>type=image</samp> for graphical submit buttons.

<pre>    &lt;input type=submit value="Party on ..."&gt;</pre>

<dt><samp>type=image</samp>
<dd>This is used for graphical submit buttons rendered by an image
rather than a text string. The URL for the image is specified with the
<a href="#isrc"><samp>src</samp></a> attribute. The image alignment can
be specified with the <a href="#ialign"><samp>align</samp></a>
attribute. In this respect, graphical submit buttons are treated
identically to <a href="#img"><samp>IMG</samp></a> elements, so you can
set align to left, right, top, middle or bottom. The x and y values of
the location clicked are passed to the server: In the submitted data,
image fields are included as two name/value pairs. The names are derived
by taking the name of the field and appending ".x" for the x value, and
".y" for the y value.

<pre>&lt;p&gt;Now choose a point on the map:

    &lt;input type=image name=point src="map.gif"&gt;</pre>

<p><em><b>Note</b>: image fields typically cause problems for text-only and
speech-based user agents!</em></p>

<dt><samp>type=reset</samp>
<dd>This defines a button that users can click to reset form fields
to their initial state when the document was first loaded. You can
set the label by providing a <a href="#value"><samp>value</samp></a>
attribute. Reset buttons are never sent as part of the form's contents.

<pre>    &lt;input type=reset value="Start over ..."&gt;</pre>

<dt><samp>type=file</samp>
<dd>This provides a means for users to attach a file to the form's
contents. It is generally rendered by text field and an associated
button which when clicked invokes a file browser to select a file
name. The file name can also be entered directly in the text field.
Just like type=text you can use the <a href="#isize"><samp>size</samp></a>
attribute to set the visible width of this field in average character
widths. You can set an upper limit to the length of file names using the
<a href="#maxlen"><samp>maxlength</samp></a> attribute. Some user agents
support the ability to restrict the kinds of files to those
matching a comma separated list of MIME content types given with
the <samp>ACCEPT</samp> attribute e.g. <samp>accept="image/*"</samp>
restricts files to images. Further information can be found in
<a href="#rfc1867">RFC 1867</a>.

<pre>    &lt;input type=file name=photo size=20 accept="image/*"&gt;</pre>

<dt><samp>type=hidden</samp>
<dd>These fields should not be rendered and provide a means for servers
to store state information with a form. This will be passed back to the
server when the form is submitted, using the name/value pair defined by
the corresponding attributes. This is a work around for the statelessness
of HTTP. Another approach is to use HTTP "<a href="#refs">Cookies</a>".

<pre>    &lt;input type=hidden name=customerid value="c2415-345-8563"&gt;</pre>
</dl>

<dt><a name=name><b>name</b></a>
<dd>Used to define the property name that will be used to identify this
field's content when it is submitted to the server.

<dt><a name=value><b>value</b></a>
<dd>Used to initialize the field, or to provide a textual label for
submit and reset buttons.

<dt><a name=checked><b>checked</b></a>
<dd>The presence of this attribute is used to initialize checkboxes and
radio buttons to their checked state.

<dt><a name=isize><b>size</b></a>
<dd>Used to set the visible size of text fields to a given number of
average character widths, e.g. <samp>size=20</samp>

<dt><a name=maxlen><b>maxlength</b></a>
<dd>Sets the maximum number of characters permitted in a text field.

<dt><a name=isrc><b>src</b></a>
<dd>Specifies a URL for the image to use with a graphical submit button.

<dt><a name=ialign><b>align</b></a>
<dd>Used to specify image alignment for graphical submit buttons.
It is defined just like the <a href="#img"><samp>IMG</samp></a> align
attribute and takes one of the values: <samp>top</samp>, <samp>middle</samp>,
<samp>bottom</samp>, <samp>left</samp> or <samp>right</samp>, defaulting
to <samp>bottom</samp>.
</dl>

<h3><a name=select>SELECT <em>menus</em></a></h3>

<pre>
&lt;!ELEMENT SELECT - - (OPTION+)&gt;
&lt;!ATTLIST SELECT
        name CDATA #REQUIRED
        size NUMBER #IMPLIED
        multiple (multiple) #IMPLIED
        &gt;

&lt;!ELEMENT OPTION - O (#PCDATA)*&gt;
&lt;!ATTLIST OPTION
        selected (selected) #IMPLIED
        value  CDATA  #IMPLIED -- defaults to element content --
        &gt;
</pre>

<p><samp>SELECT</samp> is used to define select one from many or many
from many menus. <samp>SELECT</samp> elements require start and end tags
and contain one or more <samp>OPTION</samp> elements that define menu
items. One from many menus are generally rendered as drop-down menus
while many from many menus are generally shown as list boxes.

<p>Example:

<PRE>    &lt;SELECT NAME="flavor"&gt;
    &lt;OPTION VALUE=a&gt;Vanilla
    &lt;OPTION VALUE=b&gt;Strawberry
    &lt;OPTION VALUE=c&gt;Rum and Raisin
    &lt;OPTION VALUE=d&gt;Peach and Orange
    &lt;/SELECT&gt;
</PRE>

<p><samp>SELECT</samp> attributes:

<dl>
<dt><b>name</b>
<dd>This specifies a property name that is used to identify the menu
choice when the form is submitted to the server. Each selected option
results in a property name/value pair being included as part of the
form's contents.

<dt><b>size</b>
<dd>This sets the number of visible choices for many from many menus.

<dt><b>multiple</b>
<dd>The presence of this attribute signifies that the users can make
multiple selections. By default only one selection is allowed.
</dl>

<p><samp>OPTION</samp> attributes:

<dl>
<dt><b>selected</b>
<dd>When this attribute is present, the option is selected when the
document is initially loaded. It is an error for more than one option
to be so selected for one from many menus.

<dt><b>value</b>
<dd>Specifies the property value to be used when submitting the form's
content. This is combined with the property name as given by the name
attribute of the parent <samp>SELECT</samp> element.
</dl>


<h3><a name=textarea>TEXTAREA <em>multi-line text fields</em></a></h3>

<pre>
&lt;!-- Multi-line text input field. --&gt;

&lt;!ELEMENT TEXTAREA - - (#PCDATA)*&gt;
&lt;!ATTLIST TEXTAREA
        name CDATA #REQUIRED
        rows NUMBER #REQUIRED
        cols NUMBER #REQUIRED
        &gt;
</pre>

<p><samp>TEXTAREA</samp> elements require start and end tags. The
content of the element is restricted to text and character entities. It
is used to initialize the text that is shown when the document is first
loaded.

<p>Example:

<pre>
    &lt;TEXTAREA NAME=address ROWS=4 COLS=40&gt
    Your address here ...
    &lt;/TEXTAREA&gt;
</pre>

<P>It is recommended that user agents canonicalize line endings to
CR, LF (ASCII decimal 13, 10) when submitting the field's contents.
The character set for submitted data should be ISO Latin-1, unless
the server has previously indicated that it can support alternative
character sets.

<dl>
<dt><b>name</b>
<dd>This specifies a property name that is used to identify the textarea
field when the form is submitted to the server.

<dt><b>rows</b>
<dd>Specifies the number of visible text lines. Users should be able
to enter more lines that this, so user agents should provide some
means to scroll through the contents of the textarea field when the
contents extend beyond the visible area.

<dt><b>cols</b>
<dd>Specifies the visible width in average character widths. Users should
be able to enter longer lines that this, so user agents should provide
some means to scroll through the contents of the textarea field when the
contents extend beyond the visible area. User agents may wrap visible text
lines to keep long lines visible without the need for scrolling.
</dl>


<h3><a name=specials>Special Text level Elements</a></h3>

<p><a href="#anchor">A</a> (Anchor), <a href="#img">IMG</a>,
<a href="#applet">APPLET</a>, <a href="#font">FONT</a>,
<a href="#basefont">BASEFONT</a>, <a href="#br">BR</a>
and <a href="#map">MAP</a>.

<h4><a name=anchor>The A (anchor) element</a></h4>

<pre>
&lt;!ELEMENT A - - (%text)* -(A)&gt;
&lt;!ATTLIST A
        name    CDATA   #IMPLIED    -- named link end --
        href    %URL    #IMPLIED    -- URL for linked resource --
        rel     CDATA   #IMPLIED    -- forward link types --
        rev     CDATA   #IMPLIED    -- reverse link types --
        title   CDATA   #IMPLIED    -- advisory title string --
        &gt;
</pre>

<p>Anchors can't be nested and always require start and end tags.
They are used to define hypertext links and also to define
named locations for use as targets for hypertext links, e.g.

<pre>   The way to &lt;a href="hands-on.html"&gt;happiness&lt;/a&gt;.</pre>

<p>and also to define named locations for use as targets for hypertext
links, e.g.

<pre>   &lt;h2&gt;&lt;a name=mit&gt;545 Tech Square - Hacker's Paradise&lt;/a&gt;&lt;/h2&gt;</pre>

<dl>
<dt><b>name</b>
<dd>This should be a string defining unique name for the scope of the
current HTML document. <samp>NAME</samp> is used to associate a name
with this part of a document for use with URLs that target a named
section of a document.

<dt><b>href</b>
<dd>Specifies a URL acting as a network address for the linked resource.
This could be another HTML document, a PDF file or an image etc.

<dt><b>rel</b>
<dd>The forward relationship also known as the "link type". It can be
used to determine to how to deal with the linked resource when printing
out a collection of linked resources.

<dt><b>rev</b>
<dd>This defines a reverse relationship. A link from document A to
document B with <samp>REV=relation</samp> expresses the same
relationship as a link from B to A with <samp>REL=relation</samp>.
<samp>REV=made</samp> is sometimes used to identify the document author,
either the author's email address with a mailto URL, or a link to the
author's home page.

<dt><b>title</b>
<dd>An advisory title for the linked resource.
</dl>

<h4><a name=img><B>IMG</B> <i> - inline images</i></a></h4>


<pre>&lt;!ENTITY % IAlign "(top|middle|bottom|left|right)"&gt;

&lt;!ELEMENT IMG    - O EMPTY --  Embedded image --&gt;
&lt;!ATTLIST IMG
        src     %URL     #REQUIRED  -- URL of image to embed --
        alt     CDATA    #IMPLIED   -- for display in place of image --
        align   %IAlign  #IMPLIED   -- vertical or horizontal alignment --
        height  %Pixels  #IMPLIED   -- suggested height in pixels --
        width   %Pixels  #IMPLIED   -- suggested width in pixels --
        border  %Pixels  #IMPLIED   -- suggested link border width --
        hspace  %Pixels  #IMPLIED   -- suggested horizontal gutter --
        vspace  %Pixels  #IMPLIED   -- suggested vertical gutter --
        usemap  %URL     #IMPLIED   -- use client-side image map --
        ismap   (ismap)  #IMPLIED   -- use server image map --
        &gt;</pre>

<p>Used to insert images. <samp>IMG</samp> is an empty element and so
the end tag is forbidden. Images can be positioned vertically relative
to the current textline or floated to the left or right. See
<samp>BR</samp> with the <samp>CLEAR</samp> attribute for control
over textflow.

<pre><i>e.g.</i>  &lt;IMG SRC="canyon.gif" ALT="Grand Canyon"&gt;</pre>

<p><samp>IMG</samp> elements support the following attributes:

<dl>
<dt><b>src</b>
<dd>This attribute is required for every <samp>IMG</samp> element. It
specifies a URL for the image resource, for instance a GIF, JPEG or PNG
image file.

<dt><b>alt</b>
<dd>This is used to provide a text description of the image and
is vital for interoperability with speech-based and text only
user agents.

<dt><b>align</b>
<dd>This specifies how the image is positioned relative to the current
textline in which it occurs:
<p><!-- fix for Netscape spacing bug with DD --></p>

<dl>
<dt><samp>align=top</samp>
<dd>positions the top of the image
with the top of the current text line. User agents vary in how they
interpret this. Some only take into account what has occurred on the
text line prior to the IMG element and ignore what happens after it.

<dt><samp>align=middle</samp>
<dd>aligns the middle of the image with the baseline for the
current textline.

<dt><samp>align=bottom</samp>
<dd>is the default and aligns the bottom of the image with the baseline.

<dt><samp>align=left</samp>
<dd>floats the image to the current left margin, temporarily changing
this margin, so that subsequent text is flowed along the image's
righthand side. The rendering depends on whether there is any left
aligned text or images that appear earlier than the current image in the
markup. Such text (but not images) generally forces left aligned images
to wrap to a new line, with the subsequent text continuing on the former
line.

<dt><samp>align=right</samp>
<dd>floats the image to the current right margin, temporarily changing
this margin, so that subsequent text is flowed along the image's
lefthand side. The rendering depends on whether there is any right
aligned text or images that appear earlier than the current image in the
markup. Such text (but not images) generally forces right aligned images
to wrap to a new line, with the subsequent text continuing on the former
line.
</dl>

<p>Note that some browsers introduce spurious spacing with multiple left
or right aligned images. As a result authors can't depend on this being
the same for browsers from different vendors. See
<a href="#br"><samp>BR</samp></a> for ways to control text flow.

<dt><b>width</b>
<dd>Specifies the intended width of the image in pixels. When given
together with the height, this allows user agents to reserve screen
space for the image before the image data has arrived over the network.

<dt><b>height</b>
<dd>Specifies the intended height of the image in pixels. When given
together with the width, this allows user agents to reserve screen space
for the image before the image data has arrived over the network.

<dt><b>border</b>
<dd>When the <samp>IMG</samp> element appears as part of a hypertext
link, the user agent will generally indicate this by drawing a colored
border (typically blue) around the image. This attribute can be used to
set the width of this border in pixels. Use <samp>border=0</samp> to
suppress the border altogether. User agents are recommended to provide
additional cues that the image is clickable, e.g. by changing the mouse
pointer.

<dt><b>hspace</b>
<dd>This can be used to provide white space to the immediate left and
right of the image. The <samp>HSPACE</samp> attribute sets the width of
this white space in pixels. By default <samp>HSPACE</samp> is a small
non-zero number.

<dt><b>vspace</b>
<dd>This can be used to provide white space above and below the image
The <samp>VSPACE</samp> attribute sets the height of this white space
in pixels. By default <samp>VSPACE</samp> is a small non-zero number.

<dt><b>usemap</b>
<dd>This can be used to give a URL fragment identifier for a client-side
image map defined with the <a href="#map">MAP</a> element.

<dt><b>ismap</b>
<dd>When the <samp>IMG</samp> element is part of a hypertext link, and
the user clicks on the image, the <samp>ISMAP</samp> attribute causes
the location to be passed to the server. This mechanism causes problems
for text-only and speech-based user agents. Whenever its possible to
do so use the <samp>MAP</samp> element instead.
</dl>

<p>Here is an example of how you use <samp>ISMAP</samp>:

<pre>&lt;a href="/cgibin/navbar.map"&gt;&lt;img src=navbar.gif ismap border=0&gt;&lt;/a&gt;</pre>

<p>The location clicked is passed to the server as follows. The user
agent derives a new URL from the URL specified by the <samp>HREF</samp>
attribute by appending `?' the x coordinate `,' and the y coordinate of
the location in pixels. The link is then followed using the new URL. For
instance, if the user clicked at at the location x=10, y=27 then the
derived URL will be: <i>"<samp>/cgibin/navbar.map?10,27</samp>"</i>. It
is generally a good idea to suppress the border and use graphical idioms
to indicate that the image is clickable.

<p>Note that pixel values refer to screen pixels, and should be
multiplied by an appropriate factor when rendering to very high
resolution devices such as laser printers. For instance if a
user agent has a display with 75 pixels per inch and is rendering
to a laser printer with 600 dots per inch, then the pixel values
given in HTML attributes should be multiplied by a factor of 8.

<h4><a name=applet>APPLET <em>(Java Applets)</em></a></h4>

<pre>
&lt;!ELEMENT APPLET - - (PARAM | %text)*&gt;
&lt;!ATTLIST APPLET
        codebase %URL     #IMPLIED   -- code base --
        code     CDATA    #REQUIRED  -- class file --
        alt      CDATA    #IMPLIED   -- for display in place of applet --
        name     CDATA    #IMPLIED   -- applet name --
        width    %Pixels  #REQUIRED  -- suggested width in pixels --
        height   %Pixels  #REQUIRED  -- suggested height in pixels --
        align    %IAlign  #IMPLIED   -- vertical or horizontal alignment --
        hspace   %Pixels  #IMPLIED   -- suggested horizontal gutter --
        vspace   %Pixels  #IMPLIED   -- suggested vertical gutter --
        &gt;

&lt;!ELEMENT PARAM - O EMPTY&gt;
&lt;!ATTLIST PARAM
    name    NMTOKEN   #REQUIRED  -- The name of the parameter --
    value   CDATA     #IMPLIED   -- The value of the parameter --
    &gt;
</pre>

<p>Requires start and end tags. This element is supported by all Java
enabled browsers. It allows you to embed a Java applet into HTML
documents. <samp>APPLET</samp> uses associated <a
href="#param"><samp>PARAM</samp></a> elements to pass parameters to the
applet. Following the <samp>PARAM</samp> elements, the content of
<samp>APPLET</samp> elements should be used to provide an alternative to
the applet for user agents that don't support Java. It is restricted to
text-level markup as defined by the <i><samp>%text</samp></i> entity in
the DTD. Java-compatible browsers ignore this extra HTML code. You can
use it to show a snapshot of the applet running, with text explaining
what the applet does. Other possibilities for this area are a link to a
page that is more useful for the Java-ignorant browser, or text that
taunts the user for not having a Java-compatible browser.

<p>Here is a simple example of a Java applet:

<pre>
    &lt;applet code="Bubbles.class" width=500 height=500&gt;
    Java applet that draws animated bubbles.
    &lt;/applet&gt;
</pre>

<p>Here is another one using a <samp>PARAM</samp> element:

<pre>
    &lt;applet code="AudioItem" width=15 height=15&gt;
    &lt;param name=snd value="Hello.au|Welcome.au"&gt;
    Java applet that plays a welcoming sound.
    &lt;/applet&gt;
</pre>

<dl>
<dt><b>codebase =</b> <em>codebaseURL</em>
<dd>This optional attribute specifies the base URL of the applet --
    the directory or folder that contains the applet's code.
    If this attribute is not specified,
    then the document's URL is used.
<p>
<dt><b>code =</b> <em>appletFile</em>
<dd>This required attribute gives the name of the file
    that contains the applet's compiled Applet subclass.
    This file is relative to the base URL of the applet.
    It cannot be absolute.
<p>
<dt><b>alt =</b> <em>alternateText</em>
<dd>This optional attribute specifies any text
    that should be displayed
    if the browser understands the APPLET tag
    but can't run Java applets.
<p>
<dt><b>name =</b> <em>appletInstanceName</em>
<dd>This optional attribute specifies a name for the applet instance,
    which makes it possible for applets on the same page
    to find (and communicate with) each other.
<p>
<dt><b>width =</b> <em>pixels</em>
<br>
    <b>height =</b> <em>pixels</em>
<dd>These required attributes give the initial width and height
    (in pixels) of the applet display area,
    not counting any windows or dialogs that the applet brings up.
<p>
<dt><b>align =</b> <em>alignment</em>
<dd>This attribute specifies the alignment of the applet.
    This attribute is defined in exactly the same way
    as the <a href="#img"><samp>IMG</samp></a> element.
    The permitted values are: <samp>top</samp>, <samp>middle</samp>,
    <samp>bottom</samp>, <samp>left</samp> and <samp>right</samp>.
    The default is <samp>bottom</samp>.
<p>
<dt><b>vspace =</b> <em>pixels</em>
<br>
    <b>hspace =</b> <em>pixels</em>
<dd>These optional attributes specify the number of pixels above and
    below the applet (<samp>VSPACE</samp>) and on each side of the
    applet (<samp>HSPACE</samp>). They're treated the same way as the
    <samp>IMG</samp> element's <samp>VSPACE</samp> and <samp>HSPACE</samp>
    attributes.
</dl>

<p><a name=param>The <samp>PARAM</samp> element is used to pass named
parameters to applet:</a>


<pre>   <b>&lt;PARAM NAME =</b> <em>appletParameter</em> <b>VALUE =</b> <em>value</em><b>&gt;</b></pre>

<P><samp>PARAM</samp> elements are the only way to specify applet-specific
parameters. Applets read user-specified values for parameters with the
<code>getParameter()</code> method.

<dl>
<dt><b>name =</b> <em>applet parameter name</em>
<dt><b>value =</b> <em>parameter value</em>
</dl>

<p>SGML character entities such as <em><samp>&amp;eacute;</samp></em>
and <em><samp>&amp;#185;</samp></em>
are expanded before the parameter value is passed to the applet.
To include an &amp; character use <samp>&amp;amp;</samp>.

<p><em>Note: PARAM elements should be placed at the start of the
content for the APPLET element. This is not specified as part of the
DTD due to technicalities with SGML mixed content models.</em>

<h4><a name=font>FONT</a></h4>

<pre>
&lt;!ELEMENT FONT - - (%text)*     -- local change to font --&gt;
&lt;!ATTLIST FONT
    size    CDATA   #IMPLIED    -- [+]nn e.g. size="+1", size=4 --
    color   CDATA   #IMPLIED    -- #RRGGBB in hex, e.g. red: color="#FF0000" --
    &gt;</pre>


<p>Requires start and end tags. This allows you to change the font size
and/or color for the enclosed text. The attributes are: <samp>SIZE</samp>
and <samp>COLOR</samp>. Font sizes are given in terms of a scalar range
defined by the user agent with no direct mapping to point sizes etc.
The <samp>FONT</samp> element may be phased out in future revisions
to HTML.

<dl>
<dt><b>size</b>
<dd>This sets the font size for the contents of the font element. You
can set size to an integer ranging from 1 to 7 for an absolute font
size, or specify a relative font size with a signed integer value, e.g.
<samp>size="+1"</samp> or <samp>size="-2"</samp>. This is mapped to an
absolute font size by adding the current base font size as set by the
<samp>BASEFONT</samp> element (see below).

<dt><b>color</b>
<dd>Used to set the color to stroke the text. Colors are given as RGB
in hexadecimal notation or as one of 16 widely understood
<a href="#colors">color names</a> defined as per the BGCOLOR attribute
on the <a href="#body"><samp>BODY</samp></a> element.
</dl>

<p><em>Some user agents also support a <samp>FACE</samp> attribute which
accepts a comma separated list of font names in order of preference.
This is used to search for an installed font with the corresponding
name. <samp>FACE</samp> is not part of HTML 3.2.</em>

<p>The following shows the effects of setting font to absolute sizes:

<p><font size=1>size=1</font>
<font size=2>size=2</font>
<font size=3>size=3</font>
<font size=4>size=4</font>
<font size=5>size=5</font>
<font size=6>size=6</font>
<font size=7>size=7</font>

<p>The following shows the effect of relative font sizes using
a base font size of 3:

<p><basefont size=3>
<font size="-4">size=-4</font>
<font size="-3">size=-3</font>
<font size="-2">size=-2</font>
<font size="-1">size=-1</font>
<font size="+1">size=+1</font>
<font size="+2">size=+2</font>
<font size="+3">size=+3</font>
<font size="+4">size=+4</font>

<p>The same thing with a base font size of 6:

<p><basefont size=6>
<font size="-4">size=-4</font>
<font size="-3">size=-3</font>
<font size="-2">size=-2</font>
<font size="-1">size=-1</font>
<font size="+1">size=+1</font>
<font size="+2">size=+2</font>
<font size="+3">size=+3</font>
<font size="+4">size=+4</font>
<basefont size=3>

<h4><a name=basefont>BASEFONT</a></h4>

<pre>
&lt;!ELEMENT BASEFONT - O EMPTY    -- base font size (1 to 7) --&gt;
&lt;!ATTLIST BASEFONT
    size    CDATA   #IMPLIED    -- e.g. size=4, defaults to 3 --
    &gt;</pre>

<p>Used to set the base font size. <samp>BASEFONT</samp> is an empty
element so the end tag is forbidden. The <samp>SIZE</samp> attribute is
an integer value ranging from 1 to 7. The base font size applies to the
normal and preformatted text but not to headings, except where these are
modified using the <samp>FONT</samp> element with a relative font size.

<h4><a name=br>BR</a></h4>

<p>Used to force a line break. This is an empty element so the end tag
is forbidden. The <samp>CLEAR</samp> attribute can be used to move down
past floating images on either margin. <samp>&lt;BR
CLEAR=LEFT&gt;</samp> moves down past floating images on the left
margin, <samp>&lt;BR CLEAR=RIGHT&gt;</samp> does the same for floating
images on the right margin, while <samp>&lt;BR CLEAR=ALL&gt;</samp> does
the same for such images on both left and right margins.

<h4><a name=map>MAP</a></h4>

<p>The <samp>MAP</samp> element provides a mechanism for client-side
image maps. These can be placed in the same document or grouped in a
separate document although this isn't yet widely supported. The
<samp>MAP</samp> element requires start and end tags. It contains one or
more <samp>AREA</samp> elements that specify hotzones on the associated
image and bind these hotzones to URLs.

<pre>&lt;!ENTITY % SHAPE "(rect|circle|poly)"&gt;
&lt;!ENTITY % COORDS "CDATA" -- comma separated list of numbers --&gt;

&lt;!ELEMENT MAP - - (AREA)+&gt;
&lt;!ATTLIST MAP
    name    CDATA   #REQUIRED
    &gt;

&lt;!ELEMENT AREA - O EMPTY&gt;
&lt;!ATTLIST AREA
    shape   %SHAPE  rect
    coords  %COORDS #IMPLIED  -- defines coordinates for shape --
    href    %URL    #IMPLIED  -- this region acts as hypertext link --
    nohref (nohref) #IMPLIED  -- this region has no action --
    alt     CDATA   #REQUIRED -- needed for non-graphical user agents --
    &gt;</pre>

<p>Here is a simple example for a graphical navigational toolbar:

<pre>&lt;img src="navbar.gif" border=0 usemap="#map1"&gt;

&lt;map name="map1"&gt;
 &lt;area href=guide.html alt="Access Guide" shape=rect coords="0,0,118,28"&gt;
 &lt;area href=search.html alt="Search" shape=rect coords="184,0,276,28"&gt;
 &lt;area href=shortcut.html alt="Go" shape=rect coords="118,0,184,28"&gt;
 &lt;area href=top10.html alt="Top Ten" shape=rect coords="276,0,373,28"&gt;
&lt;/map&gt;</pre>

<P>The <samp>MAP</samp> element has one attribute <samp>NAME</samp>
which is used to associate a name with a map. This is then used by the
<samp>USEMAP</samp> attribute on the <samp>IMG</samp> element to
reference the map via a URL fragment identifier. Note that the value of
the <samp>NAME</samp> attribute is case sensitive.

<p>The <samp>AREA</samp> element is an empty element and so the end tag
is forbidden. It takes the following attributes: <samp>SHAPE</samp>,
<samp>COORDS</samp>, <samp>HREF</samp>, <samp>NOHREF</samp> and
<samp>ALT</samp>. The <samp>SHAPE</samp> and <samp>COORDS</samp>
attributes define a region on the image. If the <samp>SHAPE</samp>
attribute is omitted, <samp>SHAPE="RECT"</samp> is assumed.

<dl>
<dd><b>shape=rect coords="</b><i>left-x<b>,</b> top-y<b>,</b>
right-x<b>,</b> bottom-y</i><b>"</b><p>

<dd><b>shape=circle coords="</b><i>center-x<b>,</b>
center-y<b>,</b> radius</i><b>"</b> <p>

<dd><b>shape=poly
coords="</b><i>x<sub>1</sub><b>,</b>y<sub>1</sub><b>,</b>
x<sub>2</sub><b>,</b>y<sub>2</sub><b>,</b>
x<sub>3</sub><b>,</b>y<sub>3</sub><b>,</b> ...</i><b>"</b>
</dl>

<p>Where <b>x</b> and <b>y</b> are measured in pixels from the left/top
of the associated image. If <b>x</b> and <b>y</b> values are given with a
percent sign as a suffix, the values should be interpreted as percentages
of the image's width and height, respectively. For example:

<pre>   SHAPE=RECT COORDS="0, 0, 50%, 100%"</pre>

<p>The <samp>HREF</samp> attribute gives a URL for the target of the
hypertext link. The <samp>NOHREF</samp> attribute is used when you want
to define a region that doesn't act as a hotzone. This is useful when
you want to cut a hole in an underlying region acting as a hotzone.

<p>If two or more regions overlap, the region defined first in the map
definition takes precedence over subsequent regions. This means that
<samp>AREA</samp> elements with <samp>NOHREF</samp> should generally be
placed before ones with the <samp>HREF</samp> attribute.

<p>The <samp>ALT</samp> attribute is used to provide text labels which
can be displayed in the status line as the mouse or other pointing
device is moved over hotzones, or for constructing a textual menu for
non-graphical user agents. Authors are <b>strongly recommended</b> to
provide meaningful <samp>ALT</samp> attributes to support
interoperability with speech-based or text-only user agents.


<hr>
<h2><a name=catalog>Sample SGML Open Catalog for HTML 3.2</a></h2>

<p>This can be used with an SGML parser like nsgmls to verify that
files conform to the HTML 3.2 DTD. It assumes that the DTD has been
saved as the file "HTML32.dtd" and that the Latin-1 entities are
in the file "ISOlat1.ent".

<pre>
-- html32.soc: catalog for parsing HTML 3.2 documents --
SGMLDECL "HTML32.dcl"
PUBLIC "-//W3C//DTD HTML 3.2 Final//EN" HTML32.dtd
PUBLIC "-//W3C//DTD HTML 3.2 Draft//EN" HTML32.dtd
PUBLIC "-//W3C//DTD HTML 3.2//EN" HTML32.dtd
PUBLIC "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML" ISOlat1.ent
</pre>

<hr>
<h2><a name=sgmldecl>SGML Declaration for HTML 3.2</a></h2>

<p>This uses the 8 bit ISO Latin-1 character set. The size limits on
properties like literals and tag names have been considerably increased
from their HTML 2.0 values, but it is recommended that user agents avoid
imposing arbitrary length limits.

<pre>
&lt;!SGML  "ISO 8879:1986"
   --
        SGML Declaration for HyperText Markup Language version 3.2

        With support for ISO Latin-1 and increased limits
        for tag and literal lengths etc.
   --

   CHARSET
         BASESET  "ISO 646:1983//CHARSET
                   International Reference Version
                   (IRV)//ESC 2/5 4/0"
         DESCSET  0   9   UNUSED
                  9   2   9
                  11  2   UNUSED
                  13  1   13
                  14  18  UNUSED
                  32  95  32
                  127 1   UNUSED
         BASESET  "ISO Registration Number 100//CHARSET
                   ECMA-94 Right Part of
                   Latin Alphabet Nr. 1//ESC 2/13 4/1"
         DESCSET  128  32   UNUSED
                  160  96    32

   CAPACITY   SGMLREF
              TOTALCAP        200000
              GRPCAP          150000
              ENTCAP          150000

   SCOPE    DOCUMENT
   SYNTAX
      SHUNCHAR CONTROLS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
              17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 127
      BASESET  "ISO 646:1983//CHARSET
                International Reference Version
                (IRV)//ESC 2/5 4/0"
      DESCSET  0 128 0

      FUNCTION
              RE            13
              RS            10
              SPACE         32
              TAB SEPCHAR    9

      NAMING   LCNMSTRT ""
               UCNMSTRT ""
               LCNMCHAR ".-"
               UCNMCHAR ".-"
               NAMECASE GENERAL YES
                        ENTITY  NO
      DELIM    GENERAL  SGMLREF
               SHORTREF SGMLREF
      NAMES    SGMLREF
      QUANTITY SGMLREF
               ATTSPLEN 65536
               LITLEN   65536
               NAMELEN  65536
               PILEN    65536
               TAGLVL   100
               TAGLEN   65536
               GRPGTCNT 150
               GRPCNT   64

   FEATURES
     MINIMIZE
       DATATAG  NO
       OMITTAG  YES
       RANK     NO
       SHORTTAG YES
     LINK
       SIMPLE   NO
       IMPLICIT NO
       EXPLICIT NO
     OTHER
       CONCUR   NO
       SUBDOC   NO
       FORMAL   YES
   APPINFO      NONE
&gt;
</pre>

<hr>
<h2><a name=dtd>HTML 3.2 Document Type Definition</a></h2>
<pre>
&lt;!--
        W3C Document Type Definition for the HyperText Markup Language
        version 3.2 as ratified by a vote of W3C member companies.
        For more information on W3C look at  URL http://www.w3.org/

        Date: Tuesday January 14th 1997

        Author: Dave Raggett &lt;dsr@w3.org&gt;

        HTML 3.2 aims to capture recommended practice as of early '96
        and as such to be used as a replacement for HTML 2.0 (RFC 1866).
        Widely deployed rendering attributes are included where they
        have been shown to be interoperable. SCRIPT and STYLE are
        included to smooth the introduction of client-side scripts
        and style sheets. Browsers must avoid showing the contents
        of these element Otherwise support for them is not required.
        ID, CLASS and STYLE attributes are not included in this version
        of HTML.
--&gt;

&lt;!ENTITY % HTML.Version
        "-//W3C//DTD HTML 3.2 Final//EN"

        -- Typical usage:

            &lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"&gt;
            &lt;html&gt;
            ...
            &lt;/html&gt;
        --
        &gt;

&lt;!--================== Deprecated Features Switch =========================--&gt;

&lt;!ENTITY % HTML.Deprecated "INCLUDE"&gt;

&lt;!--================== Imported Names =====================================--&gt;

&lt;!ENTITY % Content-Type "CDATA"
        -- meaning a MIME content type, as per RFC1521
        --&gt;

&lt;!ENTITY % HTTP-Method "GET | POST"
        -- as per HTTP specification
        --&gt;

&lt;!ENTITY % URL "CDATA"
        -- The term URL means a CDATA attribute
           whose value is a Uniform Resource Locator,
           See RFC1808 (June 95) and RFC1738 (Dec 94).
        --&gt;

&lt;!-- Parameter Entities --&gt;

&lt;!ENTITY % head.misc "SCRIPT|STYLE|META|LINK" -- repeatable head elements --&gt;

&lt;!ENTITY % heading "H1|H2|H3|H4|H5|H6"&gt;

&lt;!ENTITY % list "UL | OL |  DIR | MENU"&gt;

&lt;![ %HTML.Deprecated [
    &lt;!ENTITY % preformatted "PRE | XMP | LISTING"&gt;
]]&gt;

&lt;!ENTITY % preformatted "PRE"&gt;

&lt;!--================ Character mnemonic entities ==========================--&gt;

&lt;!ENTITY % ISOlat1 PUBLIC
       "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML"&gt;
%ISOlat1;

&lt;!--================ Entities for special symbols =========================--&gt;
&lt;!-- &amp;trade and &amp;cbsp are not widely deployed and so not included here --&gt;

&lt;!ENTITY amp    CDATA "&amp;#38;"   -- ampersand          --&gt;
&lt;!ENTITY gt     CDATA "&amp;#62;"   -- greater than       --&gt;
&lt;!ENTITY lt     CDATA "&amp;#60;"   -- less than          --&gt;

&lt;!--=================== Text Markup =======================================--&gt;

&lt;!ENTITY % font "TT | I | B  | U | STRIKE | BIG | SMALL | SUB | SUP"&gt;

&lt;!ENTITY % phrase "EM | STRONG | DFN | CODE | SAMP | KBD | VAR | CITE"&gt;

&lt;!ENTITY % special "A | IMG | APPLET | FONT | BASEFONT | BR | SCRIPT | MAP"&gt;

&lt;!ENTITY % form "INPUT | SELECT | TEXTAREA"&gt;

&lt;!ENTITY % text "#PCDATA | %font | %phrase | %special | %form"&gt;

&lt;!ELEMENT (%font|%phrase) - - (%text)*&gt;

&lt;!-- there are also 16 widely known color names although
  the resulting colors are implementation dependent:

   aqua, black, blue, fuchsia, gray, green, lime, maroon,
   navy, olive, purple, red, silver, teal, white, and yellow

 These colors were originally picked as being the standard
 16 colors supported with the Windows VGA palette.
 --&gt;

&lt;!ELEMENT FONT - - (%text)*     -- local change to font --&gt;
&lt;!ATTLIST FONT
    size    CDATA   #IMPLIED    -- [+]nn e.g. size="+1", size=4 --
    color   CDATA   #IMPLIED    -- #RRGGBB in hex, e.g. red: color="#FF0000" --
    &gt;

&lt;!ELEMENT BASEFONT - O EMPTY    -- base font size (1 to 7)--&gt;
&lt;!ATTLIST BASEFONT
    size    CDATA   #IMPLIED    -- e.g. size=3 --
    &gt;

&lt;!ELEMENT BR    - O EMPTY    -- forced line break --&gt;
&lt;!ATTLIST BR
        clear (left|all|right|none) none -- control of text flow --
        &gt;

&lt;!--================== HTML content models ================================--&gt;
&lt;!--
    HTML has three basic content models:

        %text       character level elements and text strings
        %flow       block-like elements e.g. paragraphs and lists
        %bodytext   as %flow plus headers H1-H6 and ADDRESS
--&gt;

&lt;!ENTITY % block
     "P | %list | %preformatted | DL | DIV | CENTER |
      BLOCKQUOTE | FORM | ISINDEX | HR | TABLE"&gt;

&lt;!-- %flow is used for DD and LI --&gt;

&lt;!ENTITY % flow "(%text | %block)*"&gt;

&lt;!--=================== Document Body =====================================--&gt;

&lt;!ENTITY % body.content "(%heading | %text | %block | ADDRESS)*"&gt;

&lt;!ENTITY % color "CDATA" -- a color specification: #HHHHHH @@ details? --&gt;

&lt;!ENTITY % body-color-attrs "
        bgcolor %color #IMPLIED
        text %color #IMPLIED
        link %color #IMPLIED
        vlink %color #IMPLIED
        alink %color #IMPLIED
        "&gt;

&lt;!ELEMENT BODY O O  %body.content&gt;
&lt;!ATTLIST BODY
        background %URL #IMPLIED  -- texture tile for document background --
        %body-color-attrs;  -- bgcolor, text, link, vlink, alink --
        &gt;

&lt;!ENTITY % address.content "((%text;) | P)*"&gt;

&lt;!ELEMENT ADDRESS - - %address.content&gt;

&lt;!ELEMENT DIV - - %body.content&gt;
&lt;!ATTLIST DIV
        align   (left|center|right) #IMPLIED -- alignment of following text --
        &gt;

&lt;!-- CENTER is a shorthand for DIV with ALIGN=CENTER --&gt;
&lt;!ELEMENT center - - %body.content&gt;

&lt;!--================== The Anchor Element =================================--&gt;

&lt;!ELEMENT A - - (%text)* -(A)&gt;
&lt;!ATTLIST A
        name    CDATA   #IMPLIED    -- named link end --
        href    %URL    #IMPLIED    -- URL for linked resource --
        rel     CDATA   #IMPLIED    -- forward link types --
        rev     CDATA   #IMPLIED    -- reverse link types --
        title   CDATA   #IMPLIED    -- advisory title string --
        &gt;

&lt;!--================== Client-side image maps ============================--&gt;

&lt;!-- These can be placed in the same document or grouped in a
     separate document although this isn't yet widely supported --&gt;

&lt;!ENTITY % SHAPE "(rect|circle|poly)"&gt;
&lt;!ENTITY % COORDS "CDATA" -- comma separated list of numbers --&gt;

&lt;!ELEMENT MAP - - (AREA)*&gt;
&lt;!ATTLIST MAP
    name    CDATA   #IMPLIED
    &gt;

&lt;!ELEMENT AREA - O EMPTY&gt;
&lt;!ATTLIST AREA
    shape   %SHAPE  rect
    coords  %COORDS #IMPLIED  -- defines coordinates for shape --
    href    %URL    #IMPLIED  -- this region acts as hypertext link --
    nohref (nohref) #IMPLIED  -- this region has no action --
    alt     CDATA   #REQUIRED -- needed for non-graphical user agents --
    &gt;

&lt;!--================== The LINK Element ==================================--&gt;

&lt;!ENTITY % Types "CDATA"
        -- See Internet Draft: draft-ietf-html-relrev-00.txt
           LINK has been part of HTML since the early days
           although few browsers as yet take advantage of it.

           Relationship values can be used in principle:

                a) for document specific toolbars/menus when used
                   with the LINK element in the document head:
                b) to link to a separate style sheet
                c) to make a link to a script
                d) by stylesheets to control how collections of
                   html nodes are rendered into printed documents
                e) to make a link to a printable version of this document
                   e.g. a postscript or pdf version
--&gt;

&lt;!ELEMENT LINK - O EMPTY&gt;
&lt;!ATTLIST LINK
        href    %URL    #IMPLIED    -- URL for linked resource --
        rel     %Types  #IMPLIED    -- forward link types --
        rev     %Types  #IMPLIED    -- reverse link types --
        title   CDATA   #IMPLIED    -- advisory title string --
        &gt;

&lt;!--=================== Images ============================================--&gt;

&lt;!ENTITY % Length "CDATA"   -- nn for pixels or nn% for percentage length --&gt;
&lt;!ENTITY % Pixels "NUMBER"  -- integer representing length in pixels --&gt;

&lt;!-- Suggested widths are used for negotiating image size
     with the module responsible for painting the image.
     align=left or right cause image to float to margin
     and for subsequent text to wrap around image --&gt;

&lt;!ENTITY % IAlign "(top|middle|bottom|left|right)"&gt;

&lt;!ELEMENT IMG    - O EMPTY --  Embedded image --&gt;
&lt;!ATTLIST IMG
        src     %URL     #REQUIRED  -- URL of image to embed --
        alt     CDATA    #IMPLIED   -- for display in place of image --
        align   %IAlign  #IMPLIED   -- vertical or horizontal alignment --
        height  %Pixels  #IMPLIED   -- suggested height in pixels --
        width   %Pixels  #IMPLIED   -- suggested width in pixels --
        border  %Pixels  #IMPLIED   -- suggested link border width --
        hspace  %Pixels  #IMPLIED   -- suggested horizontal gutter --
        vspace  %Pixels  #IMPLIED   -- suggested vertical gutter --
        usemap  %URL     #IMPLIED   -- use client-side image map --
        ismap   (ismap)  #IMPLIED   -- use server image map --
        &gt;

&lt;!-- USEMAP points to a MAP element which may be in this document
  or an external document, although the latter is not widely supported --&gt;

&lt;!--=================== Java APPLET tag ===================================--&gt;
&lt;!--
  This tag is supported by all Java enabled browsers. Applet resources
  (including their classes) are normally loaded relative to the document
  URL (or &lt;BASE&gt; element if it is defined). The CODEBASE attribute is used
  to change this default behavior. If the CODEBASE attribute is defined then
  it specifies a different location to find applet resources. The value
  can be an absolute URL or a relative URL. The absolute URL is used as is
  without modification and is not effected by the documents &lt;BASE&gt; element.
  When the codebase attribute is relative, then it is relative to the
  document URL (or &lt;BASE&gt; tag if defined).
--&gt;
&lt;!ELEMENT APPLET - - (PARAM | %text)*&gt;
&lt;!ATTLIST APPLET
        codebase %URL     #IMPLIED   -- code base --
        code     CDATA    #REQUIRED  -- class file --
        alt      CDATA    #IMPLIED   -- for display in place of applet --
        name     CDATA    #IMPLIED   -- applet name --
        width    %Pixels  #REQUIRED  -- suggested width in pixels --
        height   %Pixels  #REQUIRED  -- suggested height in pixels --
        align    %IAlign  #IMPLIED   -- vertical or horizontal alignment --
        hspace   %Pixels  #IMPLIED   -- suggested horizontal gutter --
        vspace   %Pixels  #IMPLIED   -- suggested vertical gutter --
        &gt;

&lt;!ELEMENT PARAM - O EMPTY&gt;
&lt;!ATTLIST PARAM
        name    NMTOKEN   #REQUIRED  -- The name of the parameter --
        value   CDATA     #IMPLIED   -- The value of the parameter --
        &gt;

&lt;!--
Here is an example:

    &lt;applet codebase="applets/NervousText"
        code=NervousText.class
        width=300
        height=50&gt;
    &lt;param name=text value="Java is Cool!"&gt;
    &lt;img src=sorry.gif alt="This looks better with Java support"&gt;
    &lt;/applet&gt;
--&gt;

&lt;!--=================== Horizontal Rule ===================================--&gt;

&lt;!ELEMENT HR    - O EMPTY&gt;
&lt;!ATTLIST HR
        align (left|right|center) #IMPLIED
        noshade (noshade) #IMPLIED
        size  %Pixels #IMPLIED
        width %Length #IMPLIED
        &gt;
&lt;!--=================== Paragraphs=========================================--&gt;

&lt;!ELEMENT P     - O (%text)*&gt;
&lt;!ATTLIST P
        align  (left|center|right) #IMPLIED
        &gt;

&lt;!--=================== Headings ==========================================--&gt;

&lt;!--
  There are six levels of headers from H1 (the most important)
  to H6 (the least important).
--&gt;

&lt;!ELEMENT ( %heading )  - -  (%text;)*&gt;
&lt;!ATTLIST ( %heading )
        align  (left|center|right) #IMPLIED
        &gt;

&lt;!--=================== Preformatted Text =================================--&gt;

&lt;!-- excludes images and changes in font size --&gt;

&lt;!ENTITY % pre.exclusion "IMG|BIG|SMALL|SUB|SUP|FONT"&gt;

&lt;!ELEMENT PRE - - (%text)* -(%pre.exclusion)&gt;
&lt;!ATTLIST PRE
        width NUMBER #implied -- is this widely supported? --
        &gt;

&lt;![ %HTML.Deprecated [

&lt;!ENTITY % literal "CDATA"
        -- historical, non-conforming parsing mode where
           the only markup signal is the end tag
           in full
        --&gt;

&lt;!ELEMENT (XMP|LISTING) - -  %literal&gt;
&lt;!ELEMENT PLAINTEXT - O %literal&gt;

]]&gt;

&lt;!--=================== Block-like Quotes =================================--&gt;

&lt;!ELEMENT BLOCKQUOTE - - %body.content&gt;

&lt;!--=================== Lists =============================================--&gt;

&lt;!--
    HTML 3.2 allows you to control the sequence number for ordered lists.
    You can set the sequence number with the START and VALUE attributes.
    The TYPE attribute may be used to specify the rendering of ordered
    and unordered lists.
--&gt;

&lt;!-- definition lists - DT for term, DD for its definition --&gt;

&lt;!ELEMENT DL    - -  (DT|DD)+&gt;
&lt;!ATTLIST DL
        compact (compact) #IMPLIED -- more compact style --
        &gt;

&lt;!ELEMENT DT - O  (%text)*&gt;
&lt;!ELEMENT DD - O  %flow;&gt;

&lt;!-- Ordered lists OL, and unordered lists UL --&gt;
&lt;!ELEMENT (OL|UL) - -  (LI)+&gt;

&lt;!--
       Numbering style
    1   Arabic numbers      1, 2, 3, ...
    a   lower alpha         a, b, c, ...
    A   upper alpha         A, B, C, ...
    i   lower Roman         i, ii, iii, ...
    I   upper Roman         I, II, III, ...

    The style is applied to the sequence number which by default
    is reset to 1 for the first list item in an ordered list.

    This can't be expressed directly in SGML due to case folding.
--&gt;

&lt;!ENTITY % OLStyle "CDATA" -- constrained to: [1|a|A|i|I] --&gt;

&lt;!ATTLIST OL -- ordered lists --
        type      %OLStyle   #IMPLIED   -- numbering style --
        start     NUMBER     #IMPLIED   -- starting sequence number --
        compact  (compact)   #IMPLIED   -- reduced interitem spacing --
        &gt;

&lt;!-- bullet styles --&gt;

&lt;!ENTITY % ULStyle "disc|square|circle"&gt;

&lt;!ATTLIST UL -- unordered lists --
        type    (%ULStyle)   #IMPLIED   -- bullet style --
        compact (compact)    #IMPLIED   -- reduced interitem spacing --
        &gt;

&lt;!ELEMENT (DIR|MENU) - -  (LI)+ -(%block)&gt;
&lt;!ATTLIST DIR
        compact (compact) #IMPLIED
        &gt;
&lt;!ATTLIST MENU
        compact (compact) #IMPLIED
        &gt;

&lt;!-- &lt;DIR&gt;              Directory list                  --&gt;
&lt;!-- &lt;DIR COMPACT&gt;      Compact list style              --&gt;
&lt;!-- &lt;MENU&gt;             Menu list                       --&gt;
&lt;!-- &lt;MENU COMPACT&gt;     Compact list style              --&gt;

&lt;!-- The type attribute can be used to change the bullet style
     in unordered lists and the numbering style in ordered lists --&gt;

&lt;!ENTITY % LIStyle "CDATA" -- constrained to: "(%ULStyle|%OLStyle)" --&gt;

&lt;!ELEMENT LI - O %flow -- list item --&gt;
&lt;!ATTLIST LI
        type    %LIStyle     #IMPLIED   -- list item style --
        value    NUMBER      #IMPLIED   -- reset sequence number --
        &gt;

&lt;!--================ Forms ===============================================--&gt;

&lt;!ELEMENT FORM - - %body.content -(FORM)&gt;
&lt;!ATTLIST FORM
        action %URL #IMPLIED  -- server-side form handler --
        method (%HTTP-Method) GET -- see HTTP specification --
        enctype %Content-Type; "application/x-www-form-urlencoded"
        &gt;

&lt;!ENTITY % InputType
        "(TEXT | PASSWORD | CHECKBOX | RADIO | SUBMIT
            | RESET | FILE | HIDDEN | IMAGE)"&gt;

&lt;!ELEMENT INPUT - O EMPTY&gt;
&lt;!ATTLIST INPUT
        type %InputType TEXT     -- what kind of widget is needed --
        name  CDATA   #IMPLIED   -- required for all but submit and reset --
        value CDATA   #IMPLIED   -- required for radio and checkboxes --
        checked (checked) #IMPLIED -- for radio buttons and check boxes --
        size CDATA    #IMPLIED   -- specific to each type of field --
        maxlength NUMBER #IMPLIED -- max chars allowed in text fields --
        src   %URL    #IMPLIED   -- for fields with background images --
        align %IAlign #IMPLIED   -- vertical or horizontal alignment --
        &gt;

&lt;!ELEMENT SELECT - - (OPTION+)&gt;
&lt;!ATTLIST SELECT
        name CDATA #REQUIRED
        size NUMBER #IMPLIED
        multiple (multiple) #IMPLIED
        &gt;

&lt;!ELEMENT OPTION - O (#PCDATA)*&gt;
&lt;!ATTLIST OPTION
        selected (selected) #IMPLIED
        value  CDATA  #IMPLIED -- defaults to element content --
        &gt;

&lt;!-- Multi-line text input field. --&gt;

&lt;!ELEMENT TEXTAREA - - (#PCDATA)*&gt;
&lt;!ATTLIST TEXTAREA
        name CDATA #REQUIRED
        rows NUMBER #REQUIRED
        cols NUMBER #REQUIRED
        &gt;

&lt;!--======================= Tables ========================================--&gt;

&lt;!-- Widely deployed subset of the full table standard, see RFC 1942
     e.g. at http://www.ics.uci.edu/pub/ietf/html/rfc1942.txt --&gt;

&lt;!-- horizontal placement of table relative to window --&gt;
&lt;!ENTITY % Where "(left|center|right)"&gt;

&lt;!-- horizontal alignment attributes for cell contents --&gt;
&lt;!ENTITY % cell.halign
        "align  (left|center|right) #IMPLIED"
        &gt;

&lt;!-- vertical alignment attributes for cell contents --&gt;
&lt;!ENTITY % cell.valign
        "valign  (top|middle|bottom)  #IMPLIED"
        &gt;

&lt;!ELEMENT table - - (caption?, tr+)&gt;
&lt;!ELEMENT tr - O (th|td)*&gt;
&lt;!ELEMENT (th|td) - O %body.content&gt;

&lt;!ATTLIST table                       -- table element --
        align     %Where;   #IMPLIED  -- table position relative to window --
        width     %Length   #IMPLIED  -- table width relative to window --
        border    %Pixels   #IMPLIED  -- controls frame width around table --
        cellspacing %Pixels #IMPLIED  -- spacing between cells --
        cellpadding %Pixels #IMPLIED  -- spacing within cells --
        &gt;

&lt;!ELEMENT CAPTION - - (%text;)* -- table or figure caption --&gt;
&lt;!ATTLIST CAPTION
        align (top|bottom) #IMPLIED
        &gt;

&lt;!ATTLIST tr                       -- table row --
        %cell.halign;              -- horizontal alignment in cells --
        %cell.valign;              -- vertical alignment in cells --
        &gt;

&lt;!ATTLIST (th|td)                  -- header or data cell --
        nowrap (nowrap)  #IMPLIED  -- suppress word wrap --
        rowspan NUMBER   1         -- number of rows spanned by cell --
        colspan NUMBER   1         -- number of cols spanned by cell --
        %cell.halign;              -- horizontal alignment in cell --
        %cell.valign;              -- vertical alignment in cell --
        width   %Pixels  #IMPLIED  -- suggested width for cell --
        height  %Pixels  #IMPLIED  -- suggested height for cell --
        &gt;

&lt;!--================ Document Head ========================================--&gt;

&lt;!-- %head.misc defined earlier on as "SCRIPT|STYLE|META|LINK" --&gt;

&lt;!ENTITY % head.content "TITLE &amp; ISINDEX? &amp; BASE?"&gt;

&lt;!ELEMENT HEAD O O  (%head.content) +(%head.misc)&gt;

&lt;!ELEMENT TITLE - -  (#PCDATA)* -(%head.misc)
          -- The TITLE element is not considered part of the flow of text.
             It should be displayed, for example as the page header or
             window title.
          --&gt;

&lt;!ELEMENT ISINDEX - O EMPTY&gt;
&lt;!ATTLIST ISINDEX
        prompt CDATA #IMPLIED -- prompt message --&gt;

&lt;!--
    The BASE element gives an absolute URL for dereferencing relative
    URLs, e.g.

         &lt;BASE href="http://foo.com/index.html"&gt;
         ...
         &lt;IMG SRC="images/bar.gif"&gt;

    The image is deferenced to

         http://foo.com/images/bar.gif

   In the absence of a BASE element the document URL should be used.
   Note that this is not necessarily the same as the URL used to
   request the document, as the base URL may be overridden by an HTTP
   header accompanying the document.
--&gt;

&lt;!ELEMENT BASE - O EMPTY&gt;
&lt;!ATTLIST BASE
        href %URL  #REQUIRED
        &gt;

&lt;!ELEMENT META - O EMPTY -- Generic Metainformation --&gt;
&lt;!ATTLIST META
        http-equiv  NAME    #IMPLIED  -- HTTP response header name  --
        name        NAME    #IMPLIED  -- metainformation name       --
        content     CDATA   #REQUIRED -- associated information     --
        &gt;

&lt;!-- SCRIPT/STYLE are place holders for transition to next version of HTML --&gt;

&lt;!ELEMENT STYLE  - - CDATA -- placeholder for style info --&gt;
&lt;!ELEMENT SCRIPT - - CDATA -- placeholder for script statements --&gt;

&lt;!--================ Document Structure ===================================--&gt;

&lt;!ENTITY % version.attr "VERSION CDATA #FIXED '%HTML.Version;'"&gt;

&lt;![ %HTML.Deprecated [
    &lt;!ENTITY % html.content "HEAD, BODY, PLAINTEXT?"&gt;
]]&gt;

&lt;!ENTITY % html.content "HEAD, BODY"&gt;

&lt;!ELEMENT HTML O O  (%html.content)&gt;
&lt;!ATTLIST HTML
        %version.attr;
        &gt;
</pre>

<hr>
<h2><a name=latin1>Character Entities for ISO Latin-1</a></h2>
<pre>

&lt;!-- (C) International Organization for Standardization 1986
     Permission to copy in any form is granted for use with
     conforming SGML systems and applications as defined in
     ISO 8879, provided this notice is included in all copies.
     This has been extended for use with HTML to cover the full
     set of codes in the range 160-255 decimal.
--&gt;
&lt;!-- Character entity set. Typical invocation:
     &lt;!ENTITY % ISOlat1 PUBLIC
       "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML"&gt;
     %ISOlat1;
--&gt;
    &lt;!ENTITY nbsp   CDATA "&amp;#160;" -- no-break space --&gt;
    &lt;!ENTITY iexcl  CDATA "&amp;#161;" -- inverted exclamation mark --&gt;
    &lt;!ENTITY cent   CDATA "&amp;#162;" -- cent sign --&gt;
    &lt;!ENTITY pound  CDATA "&amp;#163;" -- pound sterling sign --&gt;
    &lt;!ENTITY curren CDATA "&amp;#164;" -- general currency sign --&gt;
    &lt;!ENTITY yen    CDATA "&amp;#165;" -- yen sign --&gt;
    &lt;!ENTITY brvbar CDATA "&amp;#166;" -- broken (vertical) bar --&gt;
    &lt;!ENTITY sect   CDATA "&amp;#167;" -- section sign --&gt;
    &lt;!ENTITY uml    CDATA "&amp;#168;" -- umlaut (dieresis) --&gt;
    &lt;!ENTITY copy   CDATA "&amp;#169;" -- copyright sign --&gt;
    &lt;!ENTITY ordf   CDATA "&amp;#170;" -- ordinal indicator, feminine --&gt;
    &lt;!ENTITY laquo  CDATA "&amp;#171;" -- angle quotation mark, left --&gt;
    &lt;!ENTITY not    CDATA "&amp;#172;" -- not sign --&gt;
    &lt;!ENTITY shy    CDATA "&amp;#173;" -- soft hyphen --&gt;
    &lt;!ENTITY reg    CDATA "&amp;#174;" -- registered sign --&gt;
    &lt;!ENTITY macr   CDATA "&amp;#175;" -- macron --&gt;
    &lt;!ENTITY deg    CDATA "&amp;#176;" -- degree sign --&gt;
    &lt;!ENTITY plusmn CDATA "&amp;#177;" -- plus-or-minus sign --&gt;
    &lt;!ENTITY sup2   CDATA "&amp;#178;" -- superscript two --&gt;
    &lt;!ENTITY sup3   CDATA "&amp;#179;" -- superscript three --&gt;
    &lt;!ENTITY acute  CDATA "&amp;#180;" -- acute accent --&gt;
    &lt;!ENTITY micro  CDATA "&amp;#181;" -- micro sign --&gt;
    &lt;!ENTITY para   CDATA "&amp;#182;" -- pilcrow (paragraph sign) --&gt;
    &lt;!ENTITY middot CDATA "&amp;#183;" -- middle dot --&gt;
    &lt;!ENTITY cedil  CDATA "&amp;#184;" -- cedilla --&gt;
    &lt;!ENTITY sup1   CDATA "&amp;#185;" -- superscript one --&gt;
    &lt;!ENTITY ordm   CDATA "&amp;#186;" -- ordinal indicator, masculine --&gt;
    &lt;!ENTITY raquo  CDATA "&amp;#187;" -- angle quotation mark, right --&gt;
    &lt;!ENTITY frac14 CDATA "&amp;#188;" -- fraction one-quarter --&gt;
    &lt;!ENTITY frac12 CDATA "&amp;#189;" -- fraction one-half --&gt;
    &lt;!ENTITY frac34 CDATA "&amp;#190;" -- fraction three-quarters --&gt;
    &lt;!ENTITY iquest CDATA "&amp;#191;" -- inverted question mark --&gt;
    &lt;!ENTITY Agrave CDATA "&amp;#192;" -- capital A, grave accent --&gt;
    &lt;!ENTITY Aacute CDATA "&amp;#193;" -- capital A, acute accent --&gt;
    &lt;!ENTITY Acirc  CDATA "&amp;#194;" -- capital A, circumflex accent --&gt;
    &lt;!ENTITY Atilde CDATA "&amp;#195;" -- capital A, tilde --&gt;
    &lt;!ENTITY Auml   CDATA "&amp;#196;" -- capital A, dieresis or umlaut mark --&gt;
    &lt;!ENTITY Aring  CDATA "&amp;#197;" -- capital A, ring --&gt;
    &lt;!ENTITY AElig  CDATA "&amp;#198;" -- capital AE diphthong (ligature) --&gt;
    &lt;!ENTITY Ccedil CDATA "&amp;#199;" -- capital C, cedilla --&gt;
    &lt;!ENTITY Egrave CDATA "&amp;#200;" -- capital E, grave accent --&gt;
    &lt;!ENTITY Eacute CDATA "&amp;#201;" -- capital E, acute accent --&gt;
    &lt;!ENTITY Ecirc  CDATA "&amp;#202;" -- capital E, circumflex accent --&gt;
    &lt;!ENTITY Euml   CDATA "&amp;#203;" -- capital E, dieresis or umlaut mark --&gt;
    &lt;!ENTITY Igrave CDATA "&amp;#204;" -- capital I, grave accent --&gt;
    &lt;!ENTITY Iacute CDATA "&amp;#205;" -- capital I, acute accent --&gt;
    &lt;!ENTITY Icirc  CDATA "&amp;#206;" -- capital I, circumflex accent --&gt;
    &lt;!ENTITY Iuml   CDATA "&amp;#207;" -- capital I, dieresis or umlaut mark --&gt;
    &lt;!ENTITY ETH    CDATA "&amp;#208;" -- capital Eth, Icelandic --&gt;
    &lt;!ENTITY Ntilde CDATA "&amp;#209;" -- capital N, tilde --&gt;
    &lt;!ENTITY Ograve CDATA "&amp;#210;" -- capital O, grave accent --&gt;
    &lt;!ENTITY Oacute CDATA "&amp;#211;" -- capital O, acute accent --&gt;
    &lt;!ENTITY Ocirc  CDATA "&amp;#212;" -- capital O, circumflex accent --&gt;
    &lt;!ENTITY Otilde CDATA "&amp;#213;" -- capital O, tilde --&gt;
    &lt;!ENTITY Ouml   CDATA "&amp;#214;" -- capital O, dieresis or umlaut mark --&gt;
    &lt;!ENTITY times  CDATA "&amp;#215;" -- multiply sign --&gt;
    &lt;!ENTITY Oslash CDATA "&amp;#216;" -- capital O, slash --&gt;
    &lt;!ENTITY Ugrave CDATA "&amp;#217;" -- capital U, grave accent --&gt;
    &lt;!ENTITY Uacute CDATA "&amp;#218;" -- capital U, acute accent --&gt;
    &lt;!ENTITY Ucirc  CDATA "&amp;#219;" -- capital U, circumflex accent --&gt;
    &lt;!ENTITY Uuml   CDATA "&amp;#220;" -- capital U, dieresis or umlaut mark --&gt;
    &lt;!ENTITY Yacute CDATA "&amp;#221;" -- capital Y, acute accent --&gt;
    &lt;!ENTITY THORN  CDATA "&amp;#222;" -- capital THORN, Icelandic --&gt;
    &lt;!ENTITY szlig  CDATA "&amp;#223;" -- small sharp s, German (sz ligature) --&gt;
    &lt;!ENTITY agrave CDATA "&amp;#224;" -- small a, grave accent --&gt;
    &lt;!ENTITY aacute CDATA "&amp;#225;" -- small a, acute accent --&gt;
    &lt;!ENTITY acirc  CDATA "&amp;#226;" -- small a, circumflex accent --&gt;
    &lt;!ENTITY atilde CDATA "&amp;#227;" -- small a, tilde --&gt;
    &lt;!ENTITY auml   CDATA "&amp;#228;" -- small a, dieresis or umlaut mark --&gt;
    &lt;!ENTITY aring  CDATA "&amp;#229;" -- small a, ring --&gt;
    &lt;!ENTITY aelig  CDATA "&amp;#230;" -- small ae diphthong (ligature) --&gt;
    &lt;!ENTITY ccedil CDATA "&amp;#231;" -- small c, cedilla --&gt;
    &lt;!ENTITY egrave CDATA "&amp;#232;" -- small e, grave accent --&gt;
    &lt;!ENTITY eacute CDATA "&amp;#233;" -- small e, acute accent --&gt;
    &lt;!ENTITY ecirc  CDATA "&amp;#234;" -- small e, circumflex accent --&gt;
    &lt;!ENTITY euml   CDATA "&amp;#235;" -- small e, dieresis or umlaut mark --&gt;
    &lt;!ENTITY igrave CDATA "&amp;#236;" -- small i, grave accent --&gt;
    &lt;!ENTITY iacute CDATA "&amp;#237;" -- small i, acute accent --&gt;
    &lt;!ENTITY icirc  CDATA "&amp;#238;" -- small i, circumflex accent --&gt;
    &lt;!ENTITY iuml   CDATA "&amp;#239;" -- small i, dieresis or umlaut mark --&gt;
    &lt;!ENTITY eth    CDATA "&amp;#240;" -- small eth, Icelandic --&gt;
    &lt;!ENTITY ntilde CDATA "&amp;#241;" -- small n, tilde --&gt;
    &lt;!ENTITY ograve CDATA "&amp;#242;" -- small o, grave accent --&gt;
    &lt;!ENTITY oacute CDATA "&amp;#243;" -- small o, acute accent --&gt;
    &lt;!ENTITY ocirc  CDATA "&amp;#244;" -- small o, circumflex accent --&gt;
    &lt;!ENTITY otilde CDATA "&amp;#245;" -- small o, tilde --&gt;
    &lt;!ENTITY ouml   CDATA "&amp;#246;" -- small o, dieresis or umlaut mark --&gt;
    &lt;!ENTITY divide CDATA "&amp;#247;" -- divide sign --&gt;
    &lt;!ENTITY oslash CDATA "&amp;#248;" -- small o, slash --&gt;
    &lt;!ENTITY ugrave CDATA "&amp;#249;" -- small u, grave accent --&gt;
    &lt;!ENTITY uacute CDATA "&amp;#250;" -- small u, acute accent --&gt;
    &lt;!ENTITY ucirc  CDATA "&amp;#251;" -- small u, circumflex accent --&gt;
    &lt;!ENTITY uuml   CDATA "&amp;#252;" -- small u, dieresis or umlaut mark --&gt;
    &lt;!ENTITY yacute CDATA "&amp;#253;" -- small y, acute accent --&gt;
    &lt;!ENTITY thorn  CDATA "&amp;#254;" -- small thorn, Icelandic --&gt;
    &lt;!ENTITY yuml   CDATA "&amp;#255;" -- small y, dieresis or umlaut mark --&gt;
</pre>
<hr>
<h2><a name=charset>Table of printable Latin-1 Character codes</a></h2>

<p><img src="images/latin1.gif">

<hr>
<h2><a name=acks>Acknowledgements</a></h2>

<p>The author would like to thank the members of the W3C HTML Editorial
Review Board, members of the W3C staff, and the many other people who
have contributed to this specification.

<hr>
<h2><a name=refs>Further Reading</a></h2>

<dl>
<dt><b>The World Wide Web Consortium</b>
<dd>Further information on W3C activities and pointers to the
status of work on HTML and HTTP etc. can be found at
<a href="http://www.w3.org/">http://www.w3.org/</a>.
Further information on HTML in particular can be found at
<a href="http://www.w3.org/pub/WWW/MarkUp/">http://www.w3.org/pub/WWW/MarkUp/</a>.

<dt><b>HTML 2.0 (RFC1866)</b><dd>
By Tim Berners-Lee and Dan Connolly, November 1995.
Defines the Hypertext Markup Language Specification Version 2.0.
Available from <a href="ftp://ds.internic.net/rfc/rfc1866.txt">ftp://ds.internic.net/rfc/rfc1866.txt</a>.

<dt><b>Form-based File Upload in HTML (RFC1867)</b><dd>
By E. Nebel and L. Masinter, November 1995. Describes extensions to
HTML 2.0 (RFC1866) to support file upload from HTML forms.
Available from <a href="ftp://ds.internic.net/rfc/rfc1867.txt">ftp://ds.internic.net/rfc/rfc1867.txt</a>.

<dt><b>HTML Tables (RFC1942)</b><dd>
By Dave Raggett, May 1996. This defines the HTML table model. It is a superset
of the table model defined by HTML 3.2.
Available from <a href="ftp://ds.internic.net/rfc/rfc1942.txt">ftp://ds.internic.net/rfc/rfc1942.txt</a>,
or as a W3C working draft at <a href="http://www.w3.org/pub/WWW/TR/WD-tables">http://www.w3.org/pub/WWW/TR/WD-tables</a>.

<dt><b>A Lexical Analyzer for HTML and Basic SGML</b><dd>
By Dan Connolly, June 1996. Describes lexical considerations for parsing
HTML documents. Available from <A HREF="http://www.w3.org/pub/WWW/TR/WD-html-lex">http://www.w3.org/pub/WWW/TR/WD-html-lex</A>

<dt><b>The Hypertext Transfer Protocol (HTTP)</b>
<dd>Further information of HTTP can be found at:
<a href="http://www.w3.org/pub/WWW/Protocols">http://www.w3.org/pub/WWW/Protocols</a>.

<dt><b>A Standard Default Color Space for the Internet - sRGB</b><dd>
By Michael Stokes, Mathew Anderson, Srinivasan Chandrasekar and  Ricardo
Motta, November 1996. Available from:
<a href="http://www.w3.org/pub/WWW/Graphics/Color/sRGB.html">http://www.w3.org/pub/WWW/Graphics/Color/sRGB.html</a>
This provides a precise definition for RGB that allows sRGB images
to be reproduced accurately on different platforms and media under varying
ambient lighting conditions.

</dl>

<P>
<A href="http://www.w3.org/Consortium/Legal/ipr-notice.html#Copyright">
Copyright</A> &nbsp;&copy;&nbsp; 1997 <A href="http://www.w3.org">W3C</A>
(<A href="http://www.lcs.mit.edu">MIT</A>,
<A href="http://www.inria.fr/">INRIA</A>,
<A href="http://www.keio.ac.jp/">Keio</A> ), All Rights Reserved. W3C
<A href="http://www.w3.org/Consortium/Legal/ipr-notice.html#Legal Disclaimer">liability,</A>
<A href="http://www.w3.org/Consortium/Legal/ipr-notice.html#W3C Trademarks">trademark</A>,
<A href="http://www.w3.org/Consortium/Legal/copyright-documents.html">document
use </A>and
<A href="http://www.w3.org/Consortium/Legal/copyright-software.html">software
licensing </A>rules apply.
</P>