body, { font-family: Arial, Helvetica, sans-serif; font-size: 75%; margin-left:
                           40px; margin-right: 40px }
                           /*funny thing, though the colophon referenced at the end of this stylesheet says that Netscape 4.x doesn't support body definitions well, it seems to work for me in this stylesheet, although, I am aware that the pages have to be closely coded, because even the slightest 
HTML syntax error will break the page - including starting a row inside a table with a br instead of a p.. go figure... */

p: { font-family: Arial, Helvetica, sans-serif; font-size: 75%;  }
/* another funny thing, the open colon prevents a major design inconsistency, keeps the font sizes from inheriting from the td declaration below. Don't know why it works, but it does ...*/

td { font-family: Arial, Helvetica, sans-serif; font-size: 75%;   }
/* I guess I could list numerous class attributes on a single line, but I don't want to risk collapsing or cascading the results, since both classses are expressed as percentages ...*/


b { font-weight: bold; }

a:link { color: #333399; }

a:visited { color: #663366; }

a:hover, active  { color: #3366CC; }


.small {  font-size: 60%; }
/* expressed as 95% because I expect, at least in Explorer, the font to inherit from either the p or the td tag, however for consistency's sake, I'm going to create a footer class expressed in px. */

.smallbold {  font-size: 65%; font-weight: bold;}

.smaller { font-size: 60%;}

.small9 { font-size: 55%;}

.small9bold { font-size: 55%; font-weight: bold; }

.bold  {  font-weight: bold; }
/* This is Jonathan's idea, and past discussion, since there are many pages on the site which reflect this convention*/

.normal { font-size: 75%; font-family: Arial, Helvetica, sans-serif}
/* same as above*/

h2 {  font-size: 110%; font-weight: bold; color: #333366; text-align: center;}

h3 {  font-size: 100%; font-weight: bold; }

.here { font-weight: bold; font-size: 70%; color: #663366}

.hereLarge { font-weight: bold; font-size: 15px; color: #660099}
/*It's a dicey thing mixing px's and percentages, but I thought I'd take a chance with immediate size gratification on the headers */

.red { font-weight: 500; color: #CC0000; font-family: Arial, Helvetica, sans-serif}

.redsmaller { font-size: 9px; font-weight: bold; color: #CC0000 ;}

.blue { font-weight: bold; font-size: 12px; color: #3333CC }

.blueLarge { font-weight: bold; font-size: 16px; color: #3333CC}

.blueLarger { font-weight: bold; font-size: 18px; color: #3333CC }

.blackLargeCopy { font-weight: bold; font-size: 16px; color: #000000;}

.boldItalic { font-weight: bold; ; font-style: italic}

.italic { font-weight: normal; ; font-style: italic }

.scheduleYellow { font-size: 80%; font-weight: bold; color: #FFFF00}
.scheduleMagenta { font-size: 80%; font-weight: bold; color: #0080C0 }

.justify {  text-align: justify;}
.wrapper {  width: 67%}

/*Colophon


http://www.utoronto.ca/ian/books/xhtml2/exerpt/css-4a.html#three

Navigator 4.x

Navigator 4 supports CSS Level 1, but in a manner best described as
"shabbily." In particular, some features are not supported at all, while
others are supported in buggy and inconsistent ways. The guidelines in this
section will help you avoid the most glaring CSS problems, while at the same
time let you write CSS formatting properties that will work properly on most
other browsers, such as Internet Explorer 4 and greater, or Opera 3.6 and
greater. Mind you, please beware that complex CSS designs will force you to
do lots of extra design testing, since CSS can act very differently on
different browsers--it is easy for a seemingly innocuous CSS change to cause
odd and undesirable rendering on one of the browsers you must support!

The following, in point form, are some useful rules for using CSS with
Navigator 4. 

*    Do not count on setting CSS properties for the body element, as they
are not properly inherited by the content of the body. For example, if you
want to set the default font family for the entire document, then you should
use a rule such as 


//body,div,p,blockquote,ol,ul,dl,li,dt,dd,td,th
    {font-family: arial,helvetica,sans-serif}

*    Do not use margin-, padding-, or border- properties on inline elements,
such as em, strong, or big (this causes significant rendering errors)
*    Note that some block elements, such as p, h1 -- h6 and blockquote have
default top and bottom margins that are not set to zero size using
margin-bottom: 0, etc. Using negative margins may be possible, but this of
course won't work on other browsers. If you want to be able to control top
and bottom margins for block elements, you need to use div elements, since
they have default top and bottom margins of zero width.
*    Do not use @import rules to import one style sheet into another (it
doesn't work, and crashes some early versions of Navigator 4). Instead, use
link element to import style sheets into X/HTML documents.
*    Place external style sheet documents in the same directory as the
documents they are used by, and place all images referenced by a style sheet
in the same directory as the style sheet. Otherwise, Navigator improperly
evaluates the locations of style sheets and image files.
*    Do not use !important declarations to raise the priority of a
declaration (this declaration is not supported by Navigator 4)
*    Apply rules explicitly to elements (e.g., using class or id attributes)
and do not assume that properties are inherited from parent elements or are
cascaded down from other CSS rules: neither mechanism works reliably under
Navigator 4. For example, Navigator 4 does not always pass properties down
to other elements (e.g., setting a font family for a div element may not set
this font for paragraphs inside the div). For example, to set formatting for
a div element inside a table, write the element as

//<div class="inside-table"> .. </div>
and create a CSS rule of the form

//div.inside-table { ... css declarations ... }

*    Do not attach CSS rules to table or tr elements--Formatting for these
elements must be set using markup attributes. Similarly, if you want to set
CSS properties for the content of table cells, you must explicitly set these
properties for td or th elements.
*    Do not use margin-, padding-, or border- properties on table, tr, td,
or th elements--these properties do not work properly here. If you need to
set special margins, borders, or padding inside a table cell, then use the
markup: 


//<td><div class="table-cell"> ... content ...
//</div></td>

and apply the CSS rules to the div inside the cell.

*    Do not use margin-, padding-, or border- properties on list content
elements (li, dt, or dd), as these properties do not work properly here.
There may also be problems with such properties applied to entire lists
(i.e., applied to ol, ul, or dl elements). The safest way control margins,
padding space, or borders around an entire list is to wrap the list element
in a div element, and then apply margins, padding and borders to the div.
*    Be very careful about using margin-, padding-, or border- properties
with floated elements--this can often introduce odd formatting bugs. In
particular, you often cannot reliably set the position of a floated element
using margin properties.
*    Note that margin-top and margin-bottom (and also padding-top and
padding-bottom) only work properly for div elements--other elements, such as
headings, paragraphs, or blockquotes, retain large top and bottom margins
even when the CSS properties try and set them to zero. This is not a problem
for div elements since the top and bottom margins are, by default, of zero
width. 
*    The background-color property, applied to a block such as a paragraph,
colors only the region behind the words, and not the entire "box." A
workaround is to add a thin border to the block, but with the same color as
the background (so that the border disappears). For example, to get a solid
background color behind a paragraph, you could write:

//p {background-color: green; border: 1px solid white }

*    When setting different borders on the four sides of an element, first
use the border property to set identical borders on all sides, and then use
side-specific properties to reset individual border widths.
*    The following CSS Level 1 properties or selectors do not work on
Navigator 4, and should be avoided: background-attachment,
background-position, border-top, border-left, border-bottom, border-right
(use other border-* properties instead), display (except display:none),
font-variant, letter-spacing, list-style-image, list-style-position,
vertical-align, word-spacing, white-space:nowrap, the !important
declaration, the @import statement, :first-line and :first-letter
pseudo-elements. 
*    The following CSS Level 1 properties work, but are buggy or
inconsistent. Please see Eric Meyer's compatibility charts for details:
background-color, clear, float, line-height, all margin- properties, all
padding- properties, all border- properties.
*    Note that, for left and right margins and paddings, and also for width,
Navigator 4 always calculates percentage values relative to the width of the
browser window, and not relative to the width of the element they are
inside. At present, only Mozilla/Navigator 6 and Opera 3.6 get this right.*/