HTML documents can be written using plain ASCII text and can be created using any ASCII text editor (such as emacs or vi ). In addition, SCOhelp provides full support for the ISO 8859-1 Latin Alphabet No. 1 character set. However, not all text editors and word processors produce character codes for Latin Alphabet No. 1.
In addition to the characters that you can type in to a file directly with a text editor or word-processor, you may also include the standard set of HTML special characters as well as a SCOhelp extended special character set.
You can preview any document you write using HTML by selecting Open File from the File menu.
Here is a simple HTML document:
<HTML> <HEAD> <TITLE>A simple HTML example</TITLE>In HTML, tags are used to markup the text, and the browser decides how to format the text based on the HTML tags. Tag names in HTML are not case sensitive, so any combination of upper and lowercase text will usually work (exceptions to this rule are noted below).<BODY> <H1>This is a level one heading</H1> <P> Welcome to the world of HTML. This is one paragraph. <P> And this is a second paragraph.
HTML start tags typically begin with a left angle bracket (<), followed by the tag name, and ended with a right angle bracket (>). The end tag is the same as the start tag except a slash (/) follows the left angle bracket.
Most HTML tags are paired.
The above example uses <TITLE> to begin a document title
and a corresponding end title tag (</TITLE>)
to specify end of the title of the document.
Similarly,
the <H1> and </H1> start and
end a level 1 heading.
Some HTML tags do not require an end tag.
This is a feature of the HTML language
which allows writers to reduce the amount of typing
that is required to produce valid HTML documents.
For example, the <P> tag begins a paragraph
but does not require an end tag.
While it is not necessary to use end tags on paragraphs,
it is permissible and encouraged in the HTML specification.
Other tags which do not require a paired end tag are:
<HEAD>,
<BODY>,
<LI>,
<DT>,
and
<DD>.
Every HTML document should have a title. A title is typically displayed near the top of the window, separately from the document, and is used primarily for document identification (for example, when displaying the results of a full text search). Title tags use the following syntax:
<TITLE>Text of title</TITLE>
HTML provides six levels of headings
(numbered 1 through 6), with 1 being the most prominent.
Headings are typically displayed in larger and/or bolder fonts
than the normal body text.
Although you can use them in any order you wish,
the first level heading in
each document should be tagged <H1>,
with the second level tagged <H2>, and so on.
Headings use the following syntax:
<Hx><text of heading</Hx>In this example, x signifies a heading level between 1 and 6.
In simple documents, the first heading is usually the same as the title.
You must begin each paragraph with <P>.
Without the <P> tags,
the document might become one large paragraph.
That is because HTML was designed to be used
on a wide variety of computer screens,
using browsers with scalable windows.
As a result, traditional line endings used in
word processors are not meaningful in HTML.
Lines are adjusted to fit the window,
words may be wrapped to the next line at any point,
and consecutive spaces or tabs are collapsed into a single space.
HTML enables you to to create hypertext links from parts of one file (text and/or images) into another document (or image) using ``anchors''. When text is used for an anchor it is typically distinguished by a color change, an underline, or both when displayed on the screen.
The tag for an anchor is <A>,
but its syntax is a bit different than other tags
because it uses ``attributes'' to convey additional information.
The full syntax for the <A> is quite detailed,
but the basic syntax needed to create an anchor to another document is:
<A HREF="URL"> "Another document" </A>As usual, the start tag begins with
<A,
which is followed by a space and HREF="URL">.
In this case, HREF is an attribute name and URL
(Uniform Resource Locator)
may be a pointer to a file on your local system,
a topic in the online documentation
installed on the help server in your organization,
or even a file or node somewhere on the Internet.
The anchor text which follows may be the title of another document
or a keyword or phrase that requires further explanation;
in any case, it will typically be highlighted in the browser.
Finally, the usual end tag appears at the end of the anchor.
The following is an example of an anchor which is a hypertext link to a file named Glossary.html. In the example, the anchor uses the word ``Glossary'' as the anchor text linking the current document to the file named Glossary.html.
<P> For definition of terms used here, please refer to the <A HREF="Glossary.html">Glossary</A>.
A unique feature of SCOhelp is the navigation aids on the
help toolbar.
Among these are buttons
to access the table of contents and index of the book that you
are reading,
and to move to the previous and next topics in that book.
The mechanism used to do this is the <LINK> tag.
The <LINK> tag works like the <A> tag,
with a few differences:
<LINK> start tag has no corresponding end tag.
That is not because it is optional.
It is an empty tag, containing no content, by design.
So, do not put any text after the <LINK> tag
and do not use a </LINK>.
<LINK> tag for the purposes described here,
the REL attribute must be set to one of
contents, index, previous, or next.
The REL attribute specifies the relationship
of the document being linked to the current document.
HREF attribute must specify the URL
of an HTML file which corresponds to the
keyword used on the REL attribute.
<LINK> tag should be placed
near the top of your HTML file.
Ideally, to conform to the HTML specification,
you would place any <LINK> tags
between the <HEAD> and <BODY> tags.
Although it is not strictly necessary to use
<HEAD> and <BODY> tags, it is recommended.
SCOhelp will not mind if you do not, but it does not hurt
to plan for the future.
For example, the <LINK> tags for this document are:
<LINK HREF=/XHelp/CONTENTS.html REL=contents> <LINK HREF=/XHelp/INDEX.html REL=index> <LINK HREF=/XHelp/xhelpC.glossary.html REL=next> <LINK HREF=/XHelp/helpD.authtools.html REL=previous>
SCOhelp uses URLs (Uniform Resource Locators) to specify the location of other documents, or even a specific location within a document. The Uniform Resource Locator is an addressing method used by a variety of software packages that work over networks.
The syntax for a URL depends on the type
of network access that is being specified, the ``scheme''.
A URL defines the type of access
(in most cases http or file)
and the path to the file.
Use the http (HyperText Transfer Protocol) scheme
for addressing files from an HTTP server.
Use the file scheme for addressing files
on your local machine's filesystems.
The syntax for each of these two schemes is:
http://host.domain[:port]/path/filename
file:/path/filename
The //host.domain signifies the network address of the machine (host) within a specific network topology (domain). The port signifies the network port; by default, the help server uses port 457.
The syntax of typical URLs used in online documentation or context-sensitive help looks like these:
http://localhost:457/dochome.html http:/XHelp/CONTENTS.html http:/NetAdminG/helpD.docserver.html http:INDEX.htmlfile:/etc/hosts
Which format, or how specific your URL is, depends on a number of factors. Factors you must consider when specifying a URL are:
localhost:457.
If the server is on another machine, or you expect
other client machines to access your documents,
you might have to use the //host.domain:port
that is appropriate for your configuration.
Avoid using a fully-qualified URL with the //host.domain:port if you expect to have to move it to another machine someday, and especially if you intend to distribute your files onto other servers.
To create a link to a configuration file that exists on each machine in a network, you would use the file scheme to ensure that the user would be looking at the file as it exists on their own machine.
On the other hand, if the file is only available on the server, or if your goal is to show only the file on the server, then use the http scheme.
Uniform Resource Locators (URLs) can be specified relative to the location of the document that contains the anchor, or fully qualified using either http or file schemes. Files that are local to the book can simply be named in the URL. Files in a related book might be referenced using a relative path. Files on another server must use a fully qualified URL.
Use full pathnames when linking to documents that are not directly related. For example, consider a group of documents that comprise a single user's manual. Links within this group should be relative links. Links to other documents (perhaps a reference to related software) should use full path names. If you follow this rule, you will not have to update the internal hyperlinks if you move the user's manual to another directory.
If you want to insert a link from your document to this help file, assuming the default stand-alone help server configuration, you could use the following, fully-qualified URL:
<A HREF="http://localhost:457/XHelp/helpD.html> Writing HTML documents</A>The text
Writing HTML documents would be highlighted in the
text of your document and it would provide a hypertext link
leading to the top of this document.
For example (assuming the default scohttp configuration), if you want to refer to a file named /usr/lib/scohelp/XHelp/helpD.html on your local machine and you are editing a file named /usr/lib/scohelp/Personnel/vacation.html, you could use either the partial HREF:
HREF=../XHelp/helpD.htmlor, the fully qualified HREF:
http://localhost:457/XHelp/helpD.html
URLs are also used on the World Wide Web to create hypertext links to other World Wide Web servers. If you need more information on URLs see RFC 1630. For more information on obtaining RFCs see, ``Obtaining RFCs from the Internet'' in the Networking Guide. If you are connected to the Internet, a URL for RFC 1630 is:
http://www.w3.org/hypertext/WWW/Addressing/URL/uri-spec.htmlIf you need more information, see also A Beginner's Guide to URLs in the Web Resources section of the NCSA Mosaic for the X Window System User's Guide. The URL is:
http://www.ncsa.uiuc.edu/demoweb/url-primer.html
HTML supports unnumbered, numbered, and description lists.
Unnumbered Lists are marked lists. Different HTML viewers display unnumbered lists differently. They might appear as bullets, filled circles, or dashes to indicate the items. SCOhelp displays an unnumbered list with a bullet.
To make an unnumbered list,
<UL>) tag.
<LI>)
followed by the individual item.
(No closing </LI> tag is needed.)
</UL>).
<UL> <LI> apples <LI> bananas </UL>produces a result like this:
As you can see from the example,
it is not necessary to use a <P> tag
immediately after a <LI> tag,
but it is understood to be there.
If you do add an extra <P>,
you will likely see an extra paragraph space in SCOhelp.
List items can contain more than one paragraph
if you separate them with the
paragraph tag (<P>).
Numbered or ordered lists use syntax similar to unnumbered lists. The beginning and ending tags change. To create an ordered list:
<OL>) tag.
<LI>)
followed by the individual item.
No closing </LI> tag is needed.
</OL> tag.
<OL> <LI> apples <LI> bananas </OL>produces a result like this:
As you can see from the example,
it is not necessary to use a <P> tag
immediately after a <LI> tag,
but it is understood to be there.
If you do add an extra <P>,
you will likely see an extra paragraph space in SCOhelp.
List items can contain more than one paragraph
if you separate them with the paragraph tag (<P>).
Definition lists are used to mark up
glossary-style or hanging-item lists.
Unlike other lists, the body of definition lists
consist of definition terms (<DT>)
and definition descriptions (<DD>).
These are usually used in pairs, but it is also
permissible to use multiple definition terms
and/or multiple definition descriptions.
To make a definition list:
<DL>) tag.
<DT>)
followed by the text of the definition term.
Repeat as needed. (No closing </DT> tag is needed.)
<DD>)
followed by the text of the definition description.
Repeat as needed. (No closing </DD> tag is needed.)
</DL> tag.
<DL> <DT> Cable type <DD> Select the connector type on your EISA configuration screen. Acceptable types are shielded IBM Token-Ring Network PC Adapter Cable (or equivalent) or unshielded (twisted pair). <DT> Interrupt type/number <DD> The default interrupt type and number is edge-triggered 15. <DT> Speed <DD>You must set the speed of the Compaq card to match the speed of the network (either 4 or 16 Mbps). </DL>produces output resembling the following:
As you can see from the example,
it is not necessary to use a <P> tag
immediately after a <DD> tag,
but it is understood to be there.
If you do add an extra <P>,
you will likely see an extra paragraph space in SCOhelp.
Definition descriptions, like list items,
can contain more than one paragraph
if you separate them with the paragraph tag (<P>).
All of the list types can be nested. However, if you are nesting unnumbered lists you may find that SCOhelp will not vary the indents used for the list items.
Preformatted text is text that you want to retain
the look and format of what you enter in the HTML
code. Use the <PRE>
(preformatted) tag to include fixed width font text
(for example Courier) and to
cause spaces, new lines, and tabs to be significant.
This is especially useful for programming code. For example,
the following code:
<PRE>
#!/bin/sh
#
# xd.1
#
# extract modes and driver information from grafinfo files
#
for Fname in $*
do
sed -e "s/
BEGIN {
vendor = 1
P0 = ""
P1 = ""
P2 = ""
P3 = ""
P4 = ""
M0 = ""
M1 = ""
M3 = ""
M4 = ""
}
</PRE>
would look like this when displayed:
#!/bin/sh
#
# xd.1
#
# extract modes and driver information from grafinfo files
#
for Fname in $*
do
sed -e "s/
BEGIN {
vendor = 1
P0 = ""
P1 = ""
P2 = ""
P3 = ""
P4 = ""
M0 = ""
M1 = ""
M3 = ""
M4 = ""
}
While you can insert anchors (<A>) in
<PRE> sections,
you should not use other HTML tags.
Individual words or sentences can be put in various formats. HTML divides these into two general types:
While you could get the same italic font by specifying it directly,
semantic tags have other advantages.
The format of semantic or logical tags
can be altered by each user if they desire
by specifying different fonts in a resource file.
Character tags are linked to a given look
(for example, <B> for bold text).
So, text within character tags has to
be recoded if you want to change their appearance.
The advantage of this approach
(similar in concept to a word processor style sheet)
is that it gives your reader greater control over
how some textual elements will appear on the screen.
Use semantic and character format tags in pairs, placing content between the start tag and end tag. The following example includes a variety of semantic and character format tags within a paragraph:
<P> The two types of text-level tags are <EM>semantic</EM> and <EM>character format</EM> tags. Use semantic tags to identify information types such as citations to a book, as in <CITE>The Chicago Manual of Style</CITE>. Use character format tags to specify a font, such as <I>italic</I> or <B>bold</B> or <TT>monospaced</TT> fonts.
The following are lists of the available semantic and character format tags:
<CITE><CODE><DFN><EM><KBD>passwd to change your password.''
<SAMP>A.
<STRONG><VAR><B><I><TT>SCOhelp can display X Bitmap (XBM) or GIF format images within documents. Each image takes time to process and slows down the initial display of the document. Using a particular image multiple times in a document causes very little performance degradation compared to using the image only once.
To include an inline image in your document, use
the syntax:
<IMG SRC=image_URL>
In this example, image_URL
is the URL of the image file.
The URL syntax for <IMG> tags
is identical to that used in anchors.
If the image file is a GIF file,
then the filename part of image_URL must
end with .gif.
Similarly, filenames of X Bitmap images
must end with .xbm.
For example, if you want to include the image newex.gif,
enter the following:
<IMG SRC=newex.gif>This produces the following when formatted:
There is a lot more to HTML than what is discussed here. Some other tags deserve special attention.
<ADDRESS><ADDRESS> tag to specify an address,
whether it is a full postal address or an e-mail address.
The contents are typically rendered in an italic font.
Like a <P> tag, it causes a line break and space
before and after.
Unlike a <P> tag,
you must end it with an </ADDRESS> end tag.
<BR><BR> tag simply forces a line break.
Unlike the <P> tag, it does not cause a space.
It is often used within an <ADDRESS>,
as you can see in the example below.
No end tag is required.
<HR><HR> tag
produces a horizontal line the width of the help window,
as you can see in the example below.
No end tag is required.
Thus, one use for the hard line break is something like an address. For example, the following code:
<HR> <ADDRESS> The Santa Cruz Operation, Inc<BR> 400 Encinal Street<BR> P.O. Box 1900 <BR> Santa Cruz, CA 95061<BR> </ADDRESS> <HR>produces a result resembling the following:
<, >, ", and & have special meaning in HTML. If you need to use them in a document, you must use special entity references. They are:
< for left brackets
> for right brackets
& for ampersand
&dq; for quotes in a tag attribute
< instead of <.
For mathematical and technical documentation, SCO has added an extended symbol font to HTML. To use a special character, find it in the ``Symbol'' column in the following table, and use the HTML code listed on the same line. The ISO name is the character name designated for the character in the appendix of the SGML standard (ISO 8879:1986).
The characters listed in the following table are available for use in addition to those listed in ``List of HTML numerical character references''.
------------------------------------------------------------------------
HTML ISO
Symbol code Name Description
------------------------------------------------------------------------
• <scosym>•</scosym> bull Bullet, round
◊ <scosym>◊</scosym> loz Diamond
(TM) <scosym>™</scosym> trade Trademark sign
------------------------------------------------------------------------
&Agr; <scosym>&Agr;</scosym> Agr Capital Greek Alpha
&Bgr; <scosym>&Bgr;</scosym> Bgr Capital Greek Beta
Γ <scosym>Γ</scosym> Ggr Capital Greek Gamma
Δ <scosym>Δ</scosym> Dgr Capital Greek Delta
&Egr; <scosym>&Egr;</scosym> Egr Capital Greek Epsilon
&Zgr; <scosym>&Zgr;</scosym> Zgr Capital Greek Zeta
&EEgr; <scosym>&EEgr;</scosym> EEgr Capital Greek Eta
Θ <scosym>Θ</scosym> THgr Capital Greek Theta
&Igr; <scosym>&Igr;</scosym> Igr Capital Greek Iota
&Kgr; <scosym>&Kgr;</scosym> Kgr Capital Greek Kappa
Λ <scosym>Λ</scosym> Lgr Capital Greek Lambda
&Mgr; <scosym>&Mgr;</scosym> Mgr Capital Greek Mu
&Ngr; <scosym>&Ngr;</scosym> Ngr Capital Greek Nu
Ξ <scosym>Ξ</scosym> Xgr Capital Greek Xi
&Ogr; <scosym>&Ogr;</scosym> Ogr Capital Greek Omicron
Π <scosym>Π</scosym> Pgr Capital Greek Pi
&Rgr; <scosym>&Rgr;</scosym> Rgr Capital Greek Rho
Σ <scosym>Σ</scosym> Sgr Capital Greek Sigma
&Tgr; <scosym>&Tgr;</scosym> Tgr Capital Greek Tau
ϒ <scosym>ϒ</scosym> Ugr Capital Greek Upsilon
&PHgr; <scosym>&PHgr;</scosym> PHgr Capital Greek Phi
&KHgr; <scosym>&KHgr;</scosym> KHgr Capital Greek Chi
Ψ <scosym>Ψ</scosym> PSgr Capital Greek Psi
Ω <scosym>Ω</scosym> OHgr Capital Greek Omega
α <scosym>α</scosym>] agr Small Greek alpha
β <scosym>β</scosym> bgr Small Greek beta
γ <scosym>γ</scosym> ggr Small Greek gamma
δ <scosym>δ</scosym> dgr Small Greek delta
ε <scosym>ε</scosym> egr Small Greek epsilon
ζ <scosym>ζ</scosym> zgr Small Greek zeta
η <scosym>η</scosym> eegr Small Greek eta
&thetas; <scosym>&thetas;</scosym> thgr Small Greek theta
ι <scosym>ι</scosym> igr Small Greek iota
κ <scosym>κ</scosym> kgr Small Greek kappa
λ <scosym>λ</scosym> lgr Small Greek lambda
μ <scosym>μ</scosym> mgr Small Greek mu
ν <scosym>ν</scosym> ngr Small Greek nu
ξ <scosym>ξ</scosym> xgr Small Greek xi
&ogr; <scosym>&ogr;</scosym> ogr Small Greek omicron
π <scosym>π</scosym> pgr Small Greek pi
ρ <scosym>ρ</scosym> rgr Small Greek rho
σ <scosym>σ</scosym> sgr Small Greek sigma
&sfgr; <scosym>&sfgr;</scosym> sfgr Small Greek terminal sigma
τ <scosym>τ</scosym> tgr Small Greek tau
υ <scosym>υ</scosym> ugr Small Greek upsilon
&phis; <scosym>&phis;</scosym> phgr Small Greek phi
χ <scosym>χ</scosym> khgr Small Greek chi
ψ <scosym>ψ</scosym> psgr Small Greek psi
ω <scosym>ω</scosym> ohgr Small Greek omega
------------------------------------------------------------------------
♣ <scosym>♣</scosym> clubs Clubs
♦ <scosym>♦</scosym> diams Diamonds
♥ <scosym>♥</scosym> hearts Hearts
♠ <scosym>♠</scosym> spades Spades
------------------------------------------------------------------------
<- <scosym>←</scosym> larr Left arrow
<: <scosym>⇐</scosym> Left double arrow
> <scosym>→</scosym> rarr Right arrow
> <scosym>⇒</scosym> Right double arrow
<> <scosym>↔</scosym> harr Both arrow
⇔ <scosym>⇔</scosym> Double both arrow
↓ <scosym>↓</scosym> darr Down arrow
⇓ <scosym>⇓</scosym> dArr Down double arrow
⇑ <scosym>⇑</scosym> uArr Up double arrow
↑ <scosym>↑</scosym> uarr Up arrow
------------------------------------------------------------------------
∠ <scosym>∠</scosym> Angle sign
″ <scosym>″</scosym> Prime Double prime, seconds
⊕ <scosym>⊕</scosym> Circle plus
⊗ <scosym>⊗</scosym> otimes Circle multiply
∇ <scosym>∇</scosym> nabla Gradient
∞ <scosym>∞</scosym> infin Infinity
∫ <scosym>∫</scosym> int Integral sign
< <scosym>⟨</scosym> lang Left angle bracket
∗ <scosym>∗</scosym> lowast Math asterisk
− <scosym>−</scosym> minus Minus
⊥ <scosym>⊥</scosym> perp Perpendicular
&vprime; <scosym>&vprime;</scosym> vprime Prime, minutes, foot mark
√ <scosym>√</scosym> radic Radical, root
> <scosym>⟩</scosym> rang Right angle bracket
------------------------------------------------------------------------
∧ <scosym>∧</scosym> and Logical AND
∨ <scosym>∨</scosym> lo Logical OR
------------------------------------------------------------------------
⌊ <scosym>⌊</scosym> lfloor Left bottom brace
⌈ <scosym>⌈</scosym> lceil Left ceiling
⌊ <scosym>⌊</scosym> lfloor Left floor
⌈ <scosym>⌈</scosym> lceil Left top brace
⌋ <scosym>⌋</scosym> rfloor Right bottom brace
⌉ <scosym>⌉</scosym> rceil Right ceiling
⌋ <scosym>⌋</scosym> rfloor Right floor
⌉ <scosym>⌉</scosym> rceil Right top brace
------------------------------------------------------------------------
∼ <scosym>∼</scosym> sim Approximates
≈ <scosym>≈</scosym> Approximately equal
∩ <scosym>∩</scosym> cap Cap, intersection
∪ <scosym>∪</scosym> cup Cup, union
∅ <scosym>∅</scosym> empty Empty set
∃ <scosym>∃</scosym> exist Exists
∀ <scosym>∀</scosym> forall For all
>= <scosym>≥</scosym> ge Greater than or equal to
≡ <scosym>≡</scosym> equiv Identical with
<= <scosym>≤</scosym> le Less than or equal to
≠ <scosym>≠</scosym> ne Not equal
∉ <scosym>∉</scosym> notin Not member of
⊄ <scosym>⊄</scosym> nsub Not subset of
∝ <scosym>∝</scosym> prop Proportional to
⇔ <scosym>⇔</scosym> Reversible reaction
⇔ <scosym>⇔</scosym> Reversible reaction
∈ <scosym>∈</scosym> isin Set membership
⊂ <scosym>⊂</scosym> sub Subset
⊃ <scosym>⊃</scosym> sup Superset
⊆ <scosym>⊆</scosym> sube Subset, equals
⊇ <scosym>⊇</scosym> supe Superset, equals
∋ <scosym>∋</scosym> ni Such that
∴ <scosym>∴</scosym> there4 Therefore
------------------------------------------------------------------------
ℵ <scosym>ℵ</scosym> aleph Aleph
ℑ <scosym>ℑ</scosym> Ifraktur
ℜ <scosym>ℜ</scosym> Rfraktur
In addition to the characters in ``List of SCO extended HTML special characters'', you may also use a technique known as ``numerical character references'' to include the characters listed in the following table. The ISO names are included for future reference only and may not currently be used as entity names in HTML.
--------------------------------------------------------------
HTML ISO
Symbol code Name Description
--------------------------------------------------------------
¡ ¡ iexcl Inverted exclamation
¢ ¢ cent Cent sign
£ £ pound Pound sterling
¤ ¤ curren General currency sign
¥ ¥ yen Yen sign
| ¦ vbar Broken vertical bar
§ § sect Section sign
¨ ¨ die Umlaut (dieresis)
© © copy Copyright
ª ª ordf Feminine ordinal
<< « laquo Left angle quote, guillemotleft
¬ ¬ not Not sign
- ­ shy Soft hyphen
® ® reg Registered trademark
¯ Macron accent
° ° degree Degree sign
± ± plusmn Plus or minus
2 ² Superscript two
3 ³ Superscript three
´ ´ acute Acute accent
µ Micro sign
¶ ¶ para Paragraph sign
· · middot Middle dot
¸ ¸ Cedilla
1 ¹ Superscript one
º º ordm Masculine ordinal
>> » raquo Right angle quote, guillemotright
¼ ¼ frac14 Fraction one-fourth
½ ½ frac12 Fraction one-half
¾ ¾ frac34 Fraction three-fourths
¿ ¿ iquest Inverted question mark
--------------------------------------------------------------
Á À Aacute Capital A, acute accent
À Á Agrave Capital A, grave accent
  Acirc Capital A, circumflex accent
à à Atilde Capital A, tilde
Å Ä Aring Capital A, ring
Ä Å Auml Capital A, dieresis or umlaut mark
Æ Æ AElig Capital AE dipthong (ligature)
Ç Ç Ccedil Capital C, cedilla
É È Eacute Capital E, acute accent
È É Egrave Capital E, grave accent
Ê Ê Ecirc Capital E, circumflex accent
Ë Ë Euml Capital E, dieresis or umlaut mark
Í Ì Iacute Capital I, acute accent
Ì Í Igrave Capital I, grave accent
Î Î Icirc Capital I, circumflex accent
Ï Ï Iuml Capital I, dieresis or umlaut mark
Ð Ð ETH Capital Eth, Icelandic
Ñ Ñ Ntilde Capital N, tilde
Ó Ò Oacute Capital O, acute accent
Ò Ó Ograve Capital O, grave accent
Ô Ô Ocirc Capital O, circumflex accent
Õ Õ Otilde Capital O, tilde
Ö Ö Ouml Capital O, dieresis or umlaut mark
--------------------------------------------------------------
× × times Multiply sign
--------------------------------------------------------------
Ø Ø Oslash Capital O, slash
Ú Ù Uacute Capital U, acute accent
Ù Ú Ugrave Capital U, grave accent
Û Û Ucirc Capital U, circumflex accent
Ü Ü Uuml Capital U, dieresis or umlaut mark
Ý Yacute Capital Y, acute accent
--------------------------------------------------------------
Þ Þ THORN Capital THORN, Icelandic
ß ß szlig Small sharp s, German (sz ligature)
--------------------------------------------------------------
á à aacute Small a, acute accent
à á agrave Small a, grave accent
â â acirc Small a, circumflex accent
ã ã atilde Small a, tilde
ä ä auml Small a, dieresis or umlaut mark
å å aring Small a, ring
æ æ aelig Small ae dipthong (ligature)
ç ç ccedil Small c, cedilla
é è eacute Small e, acute accent
è é egrave Small e, grave accent
ê ê ecirc Small e, circumflex accent
ë ë euml Small e, dieresis or umlaut mark
í ì iacute Small i, acute accent
ì í igrave Small i, grave accent
î î icirc Small i, circumflex accent
ï ï iuml Small i, dieresis or umlaut mark
ð eth Small eth, Icelandic
ñ ñ ntilde Small n, tilde
ó ò oacute Small o, acute accent
ò ó ograve Small o, grave accent
ô ô ocirc Small o, circumflex accent
õ õ otilde Small o, tilde
ö ö ouml Small o, dieresis or umlaut mark
--------------------------------------------------------------
÷ ÷ divide Division sign
--------------------------------------------------------------
ø ø oslash Small o, slash
ú ù uacute Small u, acute accent
ù ú ugrave Small u, grave accent
û û ucirc Small u, circumflex accent
ü ü uuml Small u, dieresis or umlaut mark
ÿ yacute Small y, acute accent
þ þ thorn Small thorn, Icelandic
ÿ ÿ yuml Small y, dieresis or umlaut mark
While tag nesting is okay, try to avoid overlapping tags. Consider the following example:
<B>This is an example of <SAMP>overlapping HTML</B> tags.</SAMP>The sample text tag (
<SAMP>) tag
should print in a fixed-width, Courier font,
and <B> signifies bold-face type.
Because this creates overlapping formatting instructions,
the results of this code are unpredictable.
Most of the time the words `overlapping HTML'' display
in a Courier font with the word ``tags'' placed
in bold.
This is because the words ``overlapping HTML''
are contained within both the <B> and <SAMP> tags.
If you want the words ``overlapping HTML tags'' to appear in Courier
and the rest to be in bold, the sample should be coded:
<B>This is an example of</B> <SAMP>overlapping HTML tags.</SAMP>Similarly, if you wanted to print the whole sentence in bold except the word ``overlapping'', you can ``nest'' the format as follows:
Here while the sample tag is embedded or nested inside the bold text, they do not overlap.
Nest (or embed) anchors and character formats, but avoid embedding anything else. It is acceptable to nest or embed anchors within other elements. For example,
<H1><A HREF="Destination.html">My heading</A></H1>Do not embed a heading or other element within an anchor. For example,
<H1> <A HREF="Destination.html"> My heading </A> </H1>
While character style tags can be used to modify the appearance of other tags, avoid embedding other types of element tags. Although it is tempting to embed a heading within a list, in order to make the font size larger, the results can be unpredictable.
Here is an example of an HTML document:
Example 3-1 A long HTML sample document
<TITLE>A Longer Example</TITLE>
<H1>A Longer Example</H1>
<P>
This is a simple document. This is the first
paragraph.
<P>
This is the second paragraph, which shows special effects. This is a
word in <I>italics</I>. This is a word in <B>bold</B>.
Here is an inlined GIF image: <IMG SRC="newex.gif">.
<P>
This is the third paragraph, which demonstrates links.
Here is a hypertext link from
the word <A HREF=/XHelp/CONTENTS.html>Contents</A>
to the table of contents of the online help book.
<P>
<H2>A second-level header</H2>
Here is a section of text that should display as a
fixed-width font:
<P>
<PRE>
Should the wide world roll away,
Leaving black terror,
Limitless night,
Nor God, nor man, nor place to stand
Would be to me essential,
If thou and thy white arms were there,
And the fall to doom a long way.
Stephen Crane 1871-1900
</PRE>
This is a unnumbered list with two items: <P>
<UL>
<LI> cranberries
<LI> blueberries
</UL>
This is the end of my example document. <P>
When formatted, the above document looks like this::
This is a simple document. This is the first paragraph.
This is the second paragraph, which shows special effects. This is a word in italics. This is a word in bold. Here is an inlined GIF image:
This is the third paragraph, which demonstrates links. Here is a hypertext link from the word Contents to the table of contents of the online help book.
Here is a section of text that should display as a fixed-width font
Should the wide world roll away,
Leaving black terror,
Limitless night,
Nor God, nor man, nor place to stand
Would be to me essential,
If thou and thy white arms were there,
And the fall to doom a long way.
Stephen Crane 1871-1900
This is a unnumbered list with two items:
See also: