<basefont size=2>
Basefont is size 2, <b>bold</b> <i>italic</i> <tt>tt</tt><br>
<basefont size=3>
Basefont is size 3, <b>bold</b> <i>italic</i> <tt>tt</tt>
<BR>
Inserts a line break 
<BR clear="left">
this is some text, this is some text.
After a line break 
<BR clear="right">
This is is some text, this is some text,
After a line break 
<center>
</center>
<font size=1>1</font> <font size=2>2</font> <font size=3>3</font> <font size=4>4</font> <font size=5>5</font> <font size=6>6</font> <font size=7>7</font> |
1 2 3 4 5 6 7 |
Starting with the default font <font size=5>incr,</FONT> <font size=7>ease,</FONT> R <font size=6>e</FONT> <font size=5>d</FONT> <font size=4>u</FONT> <font size=3>c</FONT> <font size=2>e</FONT> |
Starting with the default font increase,Reduce
|
<font size=+2> 2 sizes larger than basefont </FONT> <font size=-2> 2 sizes smaller than basefont </FONT> |
2 sizes larger than basefont 2 sizes smaller than basefont |
<HR size=1>
<HR size=20>
<HR width=30>
<HR width=30%>
<HR width=50% align="left">
<HR width=50% align="centre">
<HR width=50% align="right">
<HR size=5 noshade>
<ISINDEX prompt="What?">Use the extensions to <OL> and <UL> in preference to the extensions to <LI>.
<ol type=1>
- <li>
- <li><ol type=a>
- <li>
- <li><ol type=i>
- <li>
- <li><ol type=A>
- <li>
- <li><ol type=I>
- <li>I could go on
</ol>
</ol>
</ol>
</ol>
</ol>
<ol start=5>
- <li>
- <li><ol start=9>
- <li>
- <li>
- <li>And so on
</ol>
</ol>
<NOBR></NOBR>
<ul type=disc>
- <li><ul type=circle>
- <li><ul type=square>
- <li>I could go on
</ul>
</ul>
</ul>
The text might contain long strings like
this-is-a-long-string-with-lots-of-hyphens-in-it which just cant be broken
very easily without screwing up the page appearance
Examples
I'm afraid the explanation is too esoteric for me to simplify (or understand)
So you're going to have to look at the original netscape documentation
for this
With the release of Java, The push pull mechanism of netscape
will have to be dismissed into the domains of the obsolete.
Captions align to the top by default.
by adding WBRs the problem is solved.
this-
character codes
In addition to the usual
& escaped entities:
® -> Registered Trademark -> ®
© -> Copyright -> ©
backgrounds
<BODY [BACKGROUND=image]
[BGCOLOR=#rrggbb]
[TEXT=#rrggbb]
[LINK=#rrggbb]
[VLINK=#rrggbb]
[ALINK=#rrggbb] >
Document here
</BODY>
dynamic documents and the art of pushing and pulling
tables
<TABLE [border=size]>...</TABLE>
<TR [rowspan] [align=alignment] [valign=alignment]>..</TR>
<TD [nowrap] [align=alignment] [valign=alignment]>..</TD>
<TH [nowrap] [align=alignment] [valign=alignment]>..</TH>
<CAPTION [align=alignment]>..</CAPTION>
<MAP NAME="map_name">...</MAP>
This defines a client side image map.
The default url is normally set to be the current document.
THe behaviour of the browser when overlapping areas are defined is not
documented.
<MAP NAME=name >
<!-- DEFAULT HREF="default_url" -->
<AREA SHAPE="RECT" HREF="url1" COORDS="x1,y1,x2,y2" TARGET="frame_name">
<AREA SHAPE="CIRCLE" HREF="url2" COORDS="origin_x,origin_y,x2,y2" TARGET="frame_name">
<AREA SHAPE="POLY" HREF="url3" COORDS="x1,y1,x2,y2,..." TARGET="frame_name">
</MAP>
<IMG SRC="url" USEMAP="#name">