Structural Example
A paragraph...
Structural Example
A paragraph...
\end{verbatim} \subsubsection{Names}The element name immediately follows the tag open delimiter. Names consist of a letter followed by up to 33 letters, digits, periods, or hyphens. Names are not case sensitive. For example: \begin{verbatim} A H1 h1 another.name name-with-hyphens \end{verbatim} \subsubsection{Attributes}In a start tag, whitespace and attributes are allowed between the element name and the closing delimiter. An attribute consists of a name, an equal sign, and a value. Whitespace is allowed around the equal sign.\par The value is either: \begin{itemize} \item A string literal, delimited by single quotes or double quotes, or \item A name token; that is, a sequence of letters, digits, periods, or hyphens. \end{itemize}For example: \begin{verbatim}
\end{verbatim}
The length of an attribute value
(after replacing entity and numeric
character referencees) is limited
to 1024 characters.
\begin{DL}{allow this much space}
\item[NOTE 1:
] Some implementations allowed
any character except space or '$>$'
in a name token, for example $<$A HREF=foo/bar.html$>$
. As a result, there are many documents
that contain attribute values that
should be quoted but are not. While
parser implementators are encouraged
to support this idiom, its use in
future documents is stictly prohibited.
\item[NOTE 2:
] Some implementations also
consider any occurence of the $>$ character
to signal the end of a tag. For compatibility
with such implementations, it may
be necessary to represent $>$ with
an entity or numeric character reference;
for example: $<$IMG SRC="eq1.ps" ALT="a
$>$ b"$>$
\end{DL}
Attributes with a delcared value
of NAME (e.g. ISMAP , COMPACT ) may
be written using a minimized syntax.
The markup:
\begin{verbatim}
-
\end{verbatim}
can be written as
\begin{verbatim}
-
\end{verbatim}
\subsection{Undefined tag and attribute names}It is a principle to be conservative
in that which one produces, and liberal
in that which one accepts. HTML
parsers should be liberal except
when verifying code. HTML generators
should generate strictly conforming
HTML.\par
The behaviour of WWW applications
reading HTML documents and discovering
tag or attribute names which they
do not understand should be to behave
as though, in the case of a tag,
the whole tag had not been there
but its content had, or in the case
of an attribute, that the attribute
had not been present.
\subsection{Character Data }The charcters between the tags represent
text in the ISO-Latin-1 character
set, which is a superset of ASCII.
Because certain characters will be
interpreted as markup, they should
be "escaped"; that is, represented
by markup $--$ entity or numeric character
references. For example:
\begin{verbatim}
When a<b, we can show that...
Brought to you by AT&T
\end{verbatim}
The HTML DTD includes entities for
each of the non-ASCII characters
so that one may reference them by
name if it is inconvenient to enter
them directly:
\begin{verbatim} Kurt Gödel was a famous logician and mathematician.
\end{verbatim}
\begin{DL}{allow this much space}
\item[NOTE 1:
] To ensure that a string of
characters has no markup, it is sufficient
to represent all occurrences of $<$
, $>$ , and \& by character or entity
references.
\item[NOTE 2:
] There are SGML features (
CDATA , RCDATA ) to allow most $<$
, $>$ , and \& characters to be entered
without the use of entity or character
references. Because these features
tend to be used and implemented inconsistently,
and because they require 8-bit characters
to represent non-ASCII characters,
they are not employed in this version
of the HTML DTD. An earlier HTML
specification included an XMP element
whose syntax is not expressible in
SGML. Inside the XMP , no markup
was recognized except the $<$/XMP$>$
end tag. While implementations are
encouraged to support this idiom,
its use is obsolete.
\end{DL}
\subsubsection{Comments}To include comments in an HTML document
that will be ignored by the parser,
surround them with $<$!$--$ and $--$$>$.
After the comment delimiter, all
text up to the next occurrence of
$--$ is ignored. Hence comments cannot
be nested. Whitespace is allowed
between the closing $--$ and $>$. (But
not between the opening $<$! and $--$.)\par
For example:
\begin{verbatim}
J.R. Brown
JimquickPost News, Jumquick, CT 01234
Tel (123) 456 7890
\end{verbatim} $<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$ \section{BASE} \par This element allows the URL of the document itself to be recorded in situations in which the document may be read out of context. URLs within the document may be in a "partial" form relative to this base address. \par Where the base address is not specified, the reader will use the URL it used to access the document to resolve any relative URLs. \par The one attribute is: \begin{DL}{allow this much space} \item[HREF ]the URL \end{DL} $<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$ \section{Line Break} \par The line break element marks that a new line must be started at the given point. \subsection{Typical rendering} \par A new line with indent the same as that of line-wrapped text. \subsection{Examples} \begin{verbatim} Tim Berners-LeeWorld Wide Web project
CERN
1211 Geneva 23
Switzerland I think that I shall never see
A hoarding lovely as a tree
In fact, unless the hoardings fall
I'll never see a tree at all.
\end{verbatim} \subsection{See also:} Paragraph marks $<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$ \section{BLOCKQUOTE} \par The BLOCKQUOTE element allows text quoted from another source to be rendered specially. \subsection{Typical rendering} \par A typical rendering might be a slight extra left and right indent, and/or italic font. BLOCKQUOTE causes a paragraph break, and typically a line or so of white space will be allowed between it and any text before or after it. \par Single-font rendition may for example put a vertical line of "$>$" characters down the left margin to indicate quotation in the Internet mail style. \subsection{Example} \begin{verbatim}I think it ends
Soft you now, the fair Ophelia. Nymph, in thy orisons, be all my sins remembered.but I am not sure. \end{verbatim} \section{Fill-out Forms and Input fields}Forms are composed by placing input fields within paragraphs, preformatted/literal text, lists and tables. This gives considerable scope in designing the layout of forms. The form features use the following elements which are all known as HTML level 2 elements. \begin{DL}{allow this much space} \item[FORM ]a form within a document. \item[INPUT ]one input field \item[TEXTAREA ]a multline input field \item[SELECT ]A selection from a finite set of options \item[OPTION ]one option within a SELECT \end{DL} Each field is defined by an INPUT element and must have an NAME attribute which uniquely names the field in the document. Additional optional attributes can be used to specify the type of the field (defaults to free text), its size/precision, its initial value and whether the field is currently disabled or in error: \begin{verbatim} \end{verbatim} This fictitious example is a questionnaire that will be emailed to www\_admin@info.cern.ch . The FORM element is used to delimit the form. There can be several forms in a single document, but the FORM element can't be nested. The ACTION attribute specifies a URL that designates an HTTP server or an email address. If missing, the URL for the document itself will be assumed. The effect of the action can be modified by including a method prefix, e.g. ACTION="POST http://...." . This prefix is used to select the HTTP method when sending the form's contents to an HTTP server. Would it be cleaner to use a separate attribute, e.g. METHOD ?\par Servers can disable forms by sending an appropriate header or by an attribute on the optional HTMLPLUS element at the very start of the document, e.g. $<$htmlplus forms=off$>$ .\par Here, the $<$P$>$ and $<$UL$>$ elements have been used to lay out the text (and input fields. The browser has changed the background color within the FORM element to distinguish the form from other parts of the document. The browser is responsible for handling the input focus, i.e. which field will currently get keyboard input.\par For many platforms there will be existing conventions for forms, e.g. and shift- keys to move the keyboard focus forwards and backwards between fields, while an key submits the form. In the example, the and buttons are specified explicitly with special purpose fields. The button is used to email the form or send its contents to the server as specified by the ACTION attribute, while the button resets the fields to their initial values. When the form consists of a single text field, it may be appropriate to leave such buttons out and rely on the key.\par The INPUT element is used for a large variety of typed of input fields.\par When you need to let users enter more than one line of text, you should use the TEXTAREA element.\par The RADIO and CHECKBOX types of INPUT field can be used to specify multiple choice forms in which every alternative is visible as part of the form. An alternative is to use the SELECT element which is generally rendered in a more compact fashion as a pull down combo list. \subsection{FORM}The FORM element is used to delimit the form. There can be several forms in a single document, but the FORM element can't be nested. \par The ACTION attribute specifies a URL that designates an HTTP server or an email address. If missing, the URL for the document itself will be assumed. The effect of the action can be modified by including a method prefix, e.g. ACTION="POST http://...." . This prefix is used to select the HTTP method when sending the form's contents to an HTTP server. Would it be cleaner to use a separate attribute, e.g. METHOD ? \subsection{INPUT}The INPUT element represents a field whose contents may be edited by the user. It has the following attributes. \begin{DL}{allow this much space} \item[NAME ] Symbolic name used when transferring the form's contents. This attribute is always needed and should uniquely identify this field. \item[TYPE ] Defines the type of data the field accepts. Defaults to free text. \item[SIZE ] Specifies the size or precision of the field according to its type. \item[MAXLENGTH ] The maximum number of characters that will be accepted as input. This can be greater that specified by SIZE , in which case the field will scroll appropriately. The default is unlimited. \item[VALUE ] The initial value for the field, or the value when checked for checkboxes and radio buttons. This attribute is required for radio buttons. \item[SRC ] A URL or URN specifying an image - for use only with TYPE=IMAGEMAP. \item[ALIGN ] Vertical alignment of the image - for use only with TYPE=IMAGEMAP. \end{DL} \paragraph{Propsed } \begin{DL}{allow this much space} \item[CHECKED ] When present indicates that a checkbox or radio button is selected. \item[DISABLED ] When present indicates that this field is temporarily disabled. Browsers should show this by "greying it" out in some manner. \item[ERROR ] When present indicates that the field's initial value is in error in some way, e.g. because it is inconsistent with the values of other fields. Servers should include an explanatory error message with the form's text. \end{DL} \subsubsection{Types}The following types of fields can be defined with the TYPE attribute : \begin{DL}{allow this much space} \item[TEXT ] Single line text entry fields. Use the SIZE attribute to specify the visible width in characters, e.g. SIZE="24" for a 24 character field. The MAX attribute can be used to specify an upper limit to the number of characters that can be entered into a text field, e.g. MAX=72 . Use the TEXTAREA element for text fields which can accept multiple lines (see below). \item[HIDDEN ]No field is presented to the user, but the content of the field is sent with the submitted form. This value may be used to transmit state information about client/server interaction. \item[CHECKBOX ] Used for simple Boolean attributes, or for attributes which can take multiple values at the same time. The latter is represented by a number of checkbox fields each of which has the same NAME . \item[RADIO ] 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 NAME . \item[SUBMIT ] This is a button that when pressed submits the form. It offers authors control over the location of this button. You can use an image as a submit button by specifying a URL with the SRC attribute. \item[RESET ] This is a button that when pressed resets the form's fields to their initial values as specified by the VALUE attribute. You can use an image as a reeset button by specifying a URL with the SRC attribute. \end{DL} \paragraph{Proposed types} \begin{DL}{allow this much space} \item[RANGE ] This allows you to specify an integer range with the MIN and MAX attributes, e.g. MIN=1 MAX=100 . Users can select any value in this range. \item[INT ] For entering integer numbers, the maximum number of digits can be specified with the SIZE attribute (excluding the sign character), e.g. size=3 for a three digit number. \item[FLOAT ] For fields which can accept floating point numbers. \item[SCRIBBLE ] A field upon which you can write with a pen or mouse. The size of the field in millimeters is given as SIZE= width , height. The units are absolute as they relate to the dimensions of the human hand, rather than pixels of varying resolution. The scribble may involve time and pressure data in addition to the basic ink data. You can use scribble for signatures or sketches. The field can be initialised by setting the SRC attribute to a URL which contains the ink *2 . The VALUE attribute is ignored. \item[AUDIO ] This provides a way of entering spoken messages into a form. Browsers might show an icon which when clicked pops-up a set of tape controls that you can use to record and replay messages. The initial message can be set by specifying a URL with the SRC attribute. The VALUE attribute is ignored. \end{DL} \paragraph{Obsolete types}DATE Fields which can accept a recognized date format.\par URL For fields which expect document references as URLs or URNs. \begin{DL}{allow this much space} \item[IMAGE ] This allows you to specify an image field upon which you can click with a pointing device. The SRC and ALIGN attributes are exactly the same as for the IMG and IMAGE elements. The symbolic names for the x and y coordinates of the click event are specified with .x and .y for the given with the NAME attribute. The VALUE attribute is ignored. \end{DL} When you need to let users enter more than one line of text, you should use the TEXTAREA element. \subsection{OPTION}The OPTION element can take the following attributes: \begin{DL}{allow this much space} \item[SELECTED ] Indicates that this option is initially selected. \item[VALUE ]When present indicates the value to be returned if this option is chosen. The returned value defaults to the contents of the option element. \end{DL} \paragraph{Proposed attributes} \begin{DL}{allow this much space} \item[DISABLED ] When present indicates that this option is temporarily disabled. Browsers should show this by "greying it" \end{DL} The contents of the OPTION element is presented to the user to represent the option. It is used as a returned value if the VALUE attribute is not present. \subsection{SELECT}The SELECT element allows the user to chose one of a set of alternatives described by textual labels, Every alternative is represented by the OPTION element. \subsubsection{Attributes} \begin{DL}{allow this much space} \item[MULTIPLE ]The MULTIPLE attribute is needed when users are allowed to make several selections, e.g. $<$SELECT MULTIPLE$>$ . \end{DL} \paragraph{Proposed attributes} \begin{DL}{allow this much space} \item[ERROR ]The ERROR attribute can be used to indicate that the initial selection is in error in some way, e.g. because it is inconsistent with the values of other fields. \end{DL} \subsubsection{Typical rendering}SELECT is typically as a pull down or pop-up list. \subsubsection{Example}e.g. \begin{verbatim} \end{verbatim} \begin{DL}{allow this much space} \item[out in some manner. \end{DL} \subsection{TEXTAREA}When you need to let users enter more than one line of text, you should use the TEXTAREA element, e.g. \begin{verbatim} \end{verbatim} The text up to the end tag is used to initialize the field's value. This end tag is always required even if the field is initially blank. The ROWS and COLS attributes determine the visible dimension of the field in characters. Browsers are recommended to allow text to grow beyond these limits by scrolling as needed. In the initial design for forms, multi-line text fields were supported by the INPUT element with TYPE=TEXT . Unfortunately, this causes problems for fields with long text values as SGML limits the length of attribute literals. The HTML+ DTD allows for up to 1024 characters (the SGML default is only 240 characters!). $<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$ \section{Headings} \par Six levels of heading are supported. (Note that a hypertext node within a hypertext work tends to need fewer levels of heading than a work whose only structure is given by the nesting of headings.) \par A heading element implies all the font changes, paragraph breaks before and after, and white space (for example) necessary to render the heading. Further character emphasis or paragraph marks are not required in HTML. \par H1 is the highest level of heading, and is recommended for the start of a hypertext node. It is suggested that the the text of the first heading be suitable for a reader who is already browsing in related information, in contrast to the title tag which should identify the node in a wider context. \par The heading elements are \begin{verbatim}
, , , , ,
\end{verbatim}
\par It is not normal practice to jump from one header to a header
level more than one below, for example for follow an H1 with
an H3. Although this is legal, it is discouraged,
as it may produce strange results for example when generating
other representations from the HTML.
\subsection{Example:}
\begin{verbatim} This is a heading
Here is some text
Second level heading
Here is some more text.
\end{verbatim}
\subsection{Parser Note:}
\par Parsers should not require any specific order to heading elements,
even if the heading level increases by more than one between
successive headings.
\subsection{Typical Rendering}
\begin{DL}{allow this much space}
\item[H1
]Bold very large font, centered. One or two lines clear space
between this and anything following. If printed on paper,
start new page.
\item[H2
]Bold, large font,, flush left against left margin,
no indent. One or two clear lines above and below.
\item[H3
]Italic, large font, slightly indented from the left margin.
One or two clear lines above and below.
\item[H4
]Bold, normal font, indented more than H3.
One clear line above and below.
\item[H5
]Italic, normal font, indented as H4.
One clear line above.
\item[H6
]Bold, indented same as normal text, more than H5.
One clear line above.
\end{DL}
\par These typical values are just an indication,
and it is up to the designer of the presentation software to
define the styles. The reader may have options to customize these.
When writing documents, you should assume that whatever is done
it is designed to have the same sort of effect as the styles
above.
\par The rendering software is responsible for generating suitable
vertical white space between elements, so it is NOT normal or
required to follow a heading element with a paragraph mark.
$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$
\section{Horizontal Rule}
\subsection{Typical Rendering}
\par Some sort of divider between sections of text such as a full
width horizontal rule or equivalent graphic.
\subsection{Example}
\par The horizontal rule is typically used for separating heading
information (when more than just a heading) from content,
etc.
\begin{verbatim} The Albatross
The Bumstead Monthly, 1948
The following information is culled from
this and suvccessive issues of the magazine.
Thanks are due to the editor-in-chief,
A.R. Bunstead, for her help and advice.
Copyright IQR Inc.
This recording may not be sold, resold,
hired out, used, or talked about in too great
a depth without the publisher's written or
videotaped consent.
The Albatross, most fabled and infamous of ..
\end{verbatim}
$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$
\section{IMG: Embedded Images}
\par Status: $<$A HREF="../StatusMeanings.html\#z5"
NAME="z7"$>$Extra
\par The IMG element allows another document to be inserted inline.
The document is normally an icon or small graphic,
etc. This element is NOT intended for embedding other HTML text.
\par Browsers which are not able to display inline images ignore
IMG elements. Authors should note that some browsers will be
able to display (or print) linked graphics but not inline graphics.
If the graphic is essential, it may be wiser to make a link to
it rather than to put it inline. If the graphic is essentially
decorative, then IMG is appropriate.
\par The IMG element is empty: it has no closing tag.
It has two attributes:
\begin{DL}{allow this much space}
\item[SRC
]The value of this attribute is the URL of the document to
be embedded. Its syntax is the same as that of the HREF attribute of the A tag.
SRC is mandatory.
\item[ALIGN
]Take values TOP or MIDDLE or BOTTOM,
defining whether the tops or middles of bottoms of the graphics
and text should be aligned vertically.
\item[ALT
]Optional alternative text as an alternative to the graphics
for display in text-only environments.
\end{DL}
\par Note that IMG elements are allowed within anchors.
\subsection{Example}
\begin{verbatim} Warning: < IMG SRC ="triangle.gif" ALT="Warning:"> This must be done by a
qualified technician.
< A HREF="Go.html">< IMG SRC ="Button.ps" ALT="GO">
\end{verbatim}
$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$
\section{ISINDEX}
\par This element informs the reader that the document is an index
document. As well as reading it, the reader may use a keyword
search.
\par The node may be queried with a keyword search by suffixing
the node address with a question mark, followed by a list of
keywords separated by plus signs. See the network address
format .
\par Note that this tag is normally generated automatically by
a server. If it is added by hand to an HTML document,
then the client will assume that the server can handle a search
on the document. Obviously the server must have this capability
for it to work: simply adding $<$ISINDEX$>$ in the document
is not enough to make searches happen if the server does not
have a search engine!
\par Status: standard.
\subsection{Example of use:}
\begin{verbatim} , , ,
\end{verbatim}
\par It is not normal practice to jump from one header to a header
level more than one below, for example for follow an H1 with
an H3. Although this is legal, it is discouraged,
as it may produce strange results for example when generating
other representations from the HTML.
\subsection{Example:}
\begin{verbatim} This is a heading
Here is some text
Second level heading
Here is some more text.
\end{verbatim}
\subsection{Parser Note:}
\par Parsers should not require any specific order to heading elements,
even if the heading level increases by more than one between
successive headings.
\subsection{Typical Rendering}
\begin{DL}{allow this much space}
\item[H1
]Bold very large font, centered. One or two lines clear space
between this and anything following. If printed on paper,
start new page.
\item[H2
]Bold, large font,, flush left against left margin,
no indent. One or two clear lines above and below.
\item[H3
]Italic, large font, slightly indented from the left margin.
One or two clear lines above and below.
\item[H4
]Bold, normal font, indented more than H3.
One clear line above and below.
\item[H5
]Italic, normal font, indented as H4.
One clear line above.
\item[H6
]Bold, indented same as normal text, more than H5.
One clear line above.
\end{DL}
\par These typical values are just an indication,
and it is up to the designer of the presentation software to
define the styles. The reader may have options to customize these.
When writing documents, you should assume that whatever is done
it is designed to have the same sort of effect as the styles
above.
\par The rendering software is responsible for generating suitable
vertical white space between elements, so it is NOT normal or
required to follow a heading element with a paragraph mark.
$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$
\section{Horizontal Rule}
\subsection{Typical Rendering}
\par Some sort of divider between sections of text such as a full
width horizontal rule or equivalent graphic.
\subsection{Example}
\par The horizontal rule is typically used for separating heading
information (when more than just a heading) from content,
etc.
\begin{verbatim} The Albatross
The Bumstead Monthly, 1948
The following information is culled from
this and suvccessive issues of the magazine.
Thanks are due to the editor-in-chief,
A.R. Bunstead, for her help and advice.
Copyright IQR Inc.
This recording may not be sold, resold,
hired out, used, or talked about in too great
a depth without the publisher's written or
videotaped consent.
The Albatross, most fabled and infamous of ..
\end{verbatim}
$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$
\section{IMG: Embedded Images}
\par Status: $<$A HREF="../StatusMeanings.html\#z5"
NAME="z7"$>$Extra
\par The IMG element allows another document to be inserted inline.
The document is normally an icon or small graphic,
etc. This element is NOT intended for embedding other HTML text.
\par Browsers which are not able to display inline images ignore
IMG elements. Authors should note that some browsers will be
able to display (or print) linked graphics but not inline graphics.
If the graphic is essential, it may be wiser to make a link to
it rather than to put it inline. If the graphic is essentially
decorative, then IMG is appropriate.
\par The IMG element is empty: it has no closing tag.
It has two attributes:
\begin{DL}{allow this much space}
\item[SRC
]The value of this attribute is the URL of the document to
be embedded. Its syntax is the same as that of the HREF attribute of the A tag.
SRC is mandatory.
\item[ALIGN
]Take values TOP or MIDDLE or BOTTOM,
defining whether the tops or middles of bottoms of the graphics
and text should be aligned vertically.
\item[ALT
]Optional alternative text as an alternative to the graphics
for display in text-only environments.
\end{DL}
\par Note that IMG elements are allowed within anchors.
\subsection{Example}
\begin{verbatim} Warning: < IMG SRC ="triangle.gif" ALT="Warning:"> This must be done by a
qualified technician.
< A HREF="Go.html">< IMG SRC ="Button.ps" ALT="GO">
,
\end{verbatim}
\par It is not normal practice to jump from one header to a header
level more than one below, for example for follow an H1 with
an H3. Although this is legal, it is discouraged,
as it may produce strange results for example when generating
other representations from the HTML.
\subsection{Example:}
\begin{verbatim} This is a heading
Here is some text
Second level heading
Here is some more text.
\end{verbatim}
\subsection{Parser Note:}
\par Parsers should not require any specific order to heading elements,
even if the heading level increases by more than one between
successive headings.
\subsection{Typical Rendering}
\begin{DL}{allow this much space}
\item[H1
]Bold very large font, centered. One or two lines clear space
between this and anything following. If printed on paper,
start new page.
\item[H2
]Bold, large font,, flush left against left margin,
no indent. One or two clear lines above and below.
\item[H3
]Italic, large font, slightly indented from the left margin.
One or two clear lines above and below.
\item[H4
]Bold, normal font, indented more than H3.
One clear line above and below.
\item[H5
]Italic, normal font, indented as H4.
One clear line above.
\item[H6
]Bold, indented same as normal text, more than H5.
One clear line above.
\end{DL}
\par These typical values are just an indication,
and it is up to the designer of the presentation software to
define the styles. The reader may have options to customize these.
When writing documents, you should assume that whatever is done
it is designed to have the same sort of effect as the styles
above.
\par The rendering software is responsible for generating suitable
vertical white space between elements, so it is NOT normal or
required to follow a heading element with a paragraph mark.
$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$
\section{Horizontal Rule}
\subsection{Typical Rendering}
\par Some sort of divider between sections of text such as a full
width horizontal rule or equivalent graphic.
\subsection{Example}
\par The horizontal rule is typically used for separating heading
information (when more than just a heading) from content,
etc.
\begin{verbatim} The Albatross
The Bumstead Monthly, 1948
The following information is culled from
this and suvccessive issues of the magazine.
Thanks are due to the editor-in-chief,
A.R. Bunstead, for her help and advice.
Copyright IQR Inc.
This recording may not be sold, resold,
hired out, used, or talked about in too great
a depth without the publisher's written or
videotaped consent.
The Albatross, most fabled and infamous of ..
\end{verbatim}
$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$
\section{IMG: Embedded Images}
\par Status: $<$A HREF="../StatusMeanings.html\#z5"
NAME="z7"$>$Extra
\par The IMG element allows another document to be inserted inline.
The document is normally an icon or small graphic,
etc. This element is NOT intended for embedding other HTML text.
\par Browsers which are not able to display inline images ignore
IMG elements. Authors should note that some browsers will be
able to display (or print) linked graphics but not inline graphics.
If the graphic is essential, it may be wiser to make a link to
it rather than to put it inline. If the graphic is essentially
decorative, then IMG is appropriate.
\par The IMG element is empty: it has no closing tag.
It has two attributes:
\begin{DL}{allow this much space}
\item[SRC
]The value of this attribute is the URL of the document to
be embedded. Its syntax is the same as that of the HREF attribute of the A tag.
SRC is mandatory.
\item[ALIGN
]Take values TOP or MIDDLE or BOTTOM,
defining whether the tops or middles of bottoms of the graphics
and text should be aligned vertically.
\item[ALT
]Optional alternative text as an alternative to the graphics
for display in text-only environments.
\end{DL}
\par Note that IMG elements are allowed within anchors.
\subsection{Example}
\begin{verbatim} Warning: < IMG SRC ="triangle.gif" ALT="Warning:"> This must be done by a
qualified technician.
< A HREF="Go.html">< IMG SRC ="Button.ps" ALT="GO">
This is a heading
Here is some textSecond level heading
Here is some more text. \end{verbatim} \subsection{Parser Note:} \par Parsers should not require any specific order to heading elements, even if the heading level increases by more than one between successive headings. \subsection{Typical Rendering} \begin{DL}{allow this much space} \item[H1 ]Bold very large font, centered. One or two lines clear space between this and anything following. If printed on paper, start new page. \item[H2 ]Bold, large font,, flush left against left margin, no indent. One or two clear lines above and below. \item[H3 ]Italic, large font, slightly indented from the left margin. One or two clear lines above and below. \item[H4 ]Bold, normal font, indented more than H3. One clear line above and below. \item[H5 ]Italic, normal font, indented as H4. One clear line above. \item[H6 ]Bold, indented same as normal text, more than H5. One clear line above. \end{DL} \par These typical values are just an indication, and it is up to the designer of the presentation software to define the styles. The reader may have options to customize these. When writing documents, you should assume that whatever is done it is designed to have the same sort of effect as the styles above. \par The rendering software is responsible for generating suitable vertical white space between elements, so it is NOT normal or required to follow a heading element with a paragraph mark. $<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$ \section{Horizontal Rule} \subsection{Typical Rendering} \par Some sort of divider between sections of text such as a full width horizontal rule or equivalent graphic. \subsection{Example} \par The horizontal rule is typically used for separating heading information (when more than just a heading) from content, etc. \begin{verbatim}The Albatross
The Bumstead Monthly, 1948 The following information is culled from this and suvccessive issues of the magazine. Thanks are due to the editor-in-chief, A.R. Bunstead, for her help and advice.Copyright IQR Inc.
This recording may not be sold, resold, hired out, used, or talked about in too great a depth without the publisher's written or videotaped consent.The Albatross, most fabled and infamous of .. \end{verbatim} $<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$ \section{IMG: Embedded Images} \par Status: $<$A HREF="../StatusMeanings.html\#z5" NAME="z7"$>$Extra \par The IMG element allows another document to be inserted inline. The document is normally an icon or small graphic, etc. This element is NOT intended for embedding other HTML text. \par Browsers which are not able to display inline images ignore IMG elements. Authors should note that some browsers will be able to display (or print) linked graphics but not inline graphics. If the graphic is essential, it may be wiser to make a link to it rather than to put it inline. If the graphic is essentially decorative, then IMG is appropriate. \par The IMG element is empty: it has no closing tag. It has two attributes: \begin{DL}{allow this much space} \item[SRC ]The value of this attribute is the URL of the document to be embedded. Its syntax is the same as that of the HREF attribute of the A tag. SRC is mandatory. \item[ALIGN ]Take values TOP or MIDDLE or BOTTOM, defining whether the tops or middles of bottoms of the graphics and text should be aligned vertically. \item[ALT ]Optional alternative text as an alternative to the graphics for display in text-only environments. \end{DL} \par Note that IMG elements are allowed within anchors. \subsection{Example} \begin{verbatim} Warning: < IMG SRC ="triangle.gif" ALT="Warning:"> This must be done by a qualified technician. < A HREF="Go.html">< IMG SRC ="Button.ps" ALT="GO">
- Term the first
- definition paragraph is reasonably long but is still displayed clearly
- Term2 follows
- Definition of term2
- Term
- definition paragraph
- Term2
- Definition of term2
- list element
- another list element ...
- When you get to the station, leave by the southern exit, on platform one.
- Turn left to face toward the mountain
- Walk for a mile or so until you reach the "Asquith Arms" then
- Wait and see...
What to do
This is a one paragraph.
This is a second.
This is a third. \end{verbatim} \subsection{Bad example} \begin{verbatim}
What not to do
I found that on my XYZ browser it looked prettier to me if I put some paragraph tags
- Around lists, and
- Inside headings.
None of the paragraph tags in this example should be there.
\end{verbatim} \subsection{See also} \par Line Break $<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$ \section{PRE: Preformatted text} \par Preformatted elements in HTML are displayed with text in a fixed width font, and so are suitable for text which has been formatted for a teletype by some existing formatting system. \begin{verbatim} \end{verbatim} \par The optional attribute is: \begin{DL}{allow this much space} \item[WIDTH ]This attribute gives the maximum number of characters which will occur on a line. It allows the presentation system to select a suitable font and indentation. Where the WIDTH attribute is not recognized, it is recommended that a width of 80 be assumed. Where WIDTH is supported, it is recommended that at least widths of 40, 80 and 132 characters be presented optimally, with other widths being rounded up. \end{DL} \par Within a PRE element, \begin{itemize} \item Line boundaries within the text are rendered as a move to the beginning of the next line, except for one immediately following or immediately preceding a tag. \item The $<$p$>$ tag should not be used. If found, it should be rendered as a move to the beginning of the next line. \item Anchor elements and character highlighting elements may be used. \item Elements which define paragraph formatting (Headings, Address, etc) must not be used. \item The ASCII Horizontal Tab (HT) character must be interpreted as the smallest positive nonzero number of spaces which will leave the number of characters so far on the line as a multiple of 8. Its use is not recommended however. \end{itemize} \subsubsection{Example of use} \begin{verbatim}This is an example line\end{verbatim} \subsubsection{Note: Highlighting} \par Within a preformatted element, the constraint that the rendering must be on a fixed horizontal character pitch may limit or prevent the ability of the renderer to render highlighting elements specially. \subsubsection{Note: Margins} \par The above references to the "beginning of a new line" must not be taken as implying that the renderer is forbidden from using a (constant) left indent for rendering preformatted text. The left indent may of course be constrained by the width required. $<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$ \section{TITLE} \par The title of a document is specified by the TITLE element. The TITLE element must occur in the HEAD of the document. \par There may only be one title in any document. It should identify the content of the document in a fairly wide context. \par It may not contain anchors, paragraph marks, or highlighting. The title may be used to identify the node in a history list, to label the window displaying the node, etc. It is not normally displayed in the text of a document itself. Contrast titles with headings . The title should ideally be less than 64 characters in length. That is, many applications will display document titles in window titles, menus, etc where there is only limited room. Whilst there is no limit on the length of a title (as it may be automatically generated from other data), information providers are warned that it may be truncated if long. \subsubsection{Examples of use} \par Appropriate titles might be \begin{verbatim}
EM element. A citation is
typically italic and has no formal necessary structure:
Moby Dick is a book title.
\end{verbatim}
$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$
\section{Obsolete elements}
\par The following elements of HTML
are obsolete. It is recommended that client implementors implement
the obsolete forms for compatibility with old servers.
\subsubsection{Plaintext}
\par Status: $<$A HREF="StatusMeanings.html\#z8"
NAME="z59"$>$Obsolete .
\par The empty PLAINTEXT tag terminates the HTML entity.
What follows is not SGML. In stead, there's an old HTTP convention
that what follows is an ASCII (MIME "text/plain") body.
\par An example if its use is:
\begin{verbatim}