/*  ********************************************  *
 *  This style sheet is for every document page.  * 
 *  Include after MASTER.CSS                      *
 *  ********************************************  */

body {
  background-color:#FFFFFF;
  /* background-image:url('../_images/paper.jpg'); */
  margin:1em;
  padding:0px;
}

h1, h2, h3, h4, h5 {
  color:#993333;
  font-weight:normal;
  page-break-after:avoid;
  white-space:nowrap;
}

p {
  line-height:1.33;
}

img {
  border-width:0px;
}

table {
  border-collapse:collapse;
}

table, td, th {
  border-color:#CCCCFF;
  border-style:solid;
}

table {
  border-width:2px;
}

td, th {
  border-width:1px;
  padding:1em;
}

th {
  border-bottom-width:2px;
  text-align:left;
  white-space:nowrap;
}

/*  **************  */
/*  General Styles  */

/*  For warning about various forms of incompleteness, e.g., that the text 
    is still in preparation or that something is missed if browsing without 
    scripts  */

.alert {
  color:#FF0000;
}

/*  For the things that are still in preparation and not yet advanced enough 
    to be seen by ordinary readers but which we don't mind being seen as 
    long as the early state is understood  */

.draft {
  color:#887799;
  display:none;
}

/*  To suggest console input or output, and to show such things as function 
    prototypes, structure definitions and code fragments - typically applied 
    to PRE blocks  */

.input, .output, .source {
  font-family:"Courier New", Courier, monospace;
  font-size:10pt;
  margin-bottom:0pt;
  margin-top:0pt; 
  white-space:pre;
} 

/*  ****************  */
/*  Character Styles  */

/*  Styles for inline text, called "character styles" in word processing, 
    are quite a problem when using Expression Web, since they are presented 
    in the user interface only if the text that is to receive the style is 
    already in a SPAN. This is ridiculously silly since a SPAN will be 
    generated even if applying a global class. In the hope that the 
    Expression Web programmers realise this, I stick with SPAN selectors and 
    meanwhile work around the problem by making some empty definitions.  */

.citation, .definition, .emphasis, .foreign {
}

/*  Most character styles are defined in each subweb. Each subweb may 
    have a script to translate the style's name for a tooltip. All character 
    styles defined in this sheet must have names that are suitable for use 
    as tooltips without translation.  */

span.citation, span.definition, span.emphasis, span.foreign {
  font-style:italic;
}

/*  ******  */
/*  Banner  */

/*  A banner is simulated when scripts don't run. It is modelled on the 
    actual banner (presently from BANNER.HTM) that ordinarily shows in the 
    banner frame, but the fake banner is picked up by an include (presently 
    NOSCRIPT.HTM) in document and TOC pages.  */

#Banner.NoScript {
  border:1px #CCCCFF solid;
  background-color:#EEEEDD;
  min-width:640px;
  width:100%;
}

@media print {
#Banner.NoScript {
  display:none;
}
}

#Banner.NoScript #Links {
  float:right;
}

#Banner.NoScript #Logo {
  clear:right;
}

#Banner.NoScript #Logo p {
  color:#224488;
  font-family:"Times New Roman", Times, serif;
  font-size:24px;
  font-weight:bold;
  font-style:italic;
  margin:12px;
  white-space:nowrap;
}

/*  The following styles for UL and LI are needed because the FrontPage 
    Server Extensions (FPSE) at the remote site mishandle inclusions, such 
    that elements other than DIV, P and SPAN lose their class names. Later 
    editions of the FPSE, such as on the production site, have this fixed. 
    For now, treat all UL and LI tags in the Links DIV as having the 
    LinkList and LinkListItem classes respectively.  */

#Banner.NoScript #Links li,
#Banner.NoScript #Links ul {
  border:none;
  float:left;
  list-style:none;
  margin:0px;
  padding:0px;
  white-space:nowrap;
}

#Banner.NoScript #Links a {
  background-color:#DDDDCC;
  color:#3333CC;
}

#Banner.NoScript #Links a:hover {
  background-color:#FFFFEE;
  color:#6666FF;
}

#Banner.NoScript #Links span {
  padding:1ex 1ex;
}

/*  *******************  */
/*  Headers and Footers  */

div.Header {
  margin:0px;
  padding:0px;
  width:100%;
}

/*  Though headers are always (in practice) followed by a level-1 heading, 
    footers can follow just about anything, and benefit from visual 
    separation.  */

div.Footer {
  border-top:1px #88AACC solid;
  clear:both;
  margin-top:1em;
  padding-top:1em;
  width:100%;
}

div.Footer .Copyright,
div.Footer .Dates {
  font-size:smaller;
  font-weight:bold;
}

div.Footer .PlaceholderLinks {
  color:#AA88CC;
  display:none;
}

/*  *********  */
/*  Footnotes  */

/*  Though footnotes aren't common in web pages, some pages at this site were 
    written originally as Word documents and have footnotes. The editing is 
    easier if the footnotes are kept.  */

a.FootnoteReference {
  font-size:smaller;
  vertical-align:super;
}

div.Footnotes {
  clear:both;
  width:100%;
}

div.Footnotes hr {
  height:1px;
  margin:0px;
  padding:0px;
  text-align:left;
  width:25%;
}