﻿
/*  ************************************************************************  *
 *                               document.css                                 *
 *  ************************************************************************  */

/*  This style sheet is for every document page. Include after MASTER.CSS  */

/*  ************************************************************************  */

/*  The default expecation is that the document page is viewed as the whole 
    of its window. This certainly is how the page is worked on at design 
    time. Text for the document is prepared naturally, i.e., as headings, 
    paragraphs, tables, etc., directly in the BODY. 

    This also must work in the browser. If nothing else, the document may be
    viewed with scripts disabled. It must also work if scripts load the 
    document into a frame (whether a FRAME or IFRAME). 
    
    This stylesheet is definitive for the page's essential styling. Be 
    aware, however, that scripts may build a viewer above what is written as 
    the page's BODY. The viewer is a set of BODY, DIV and IFRAME elements, 
    which each have an ID for styling. What was written as the document's 
    BODY becomes a DIV in the viewer. For the viewer's styling, see 
    VIEWER.CSS.  */

body {
  background-color:#FFFFFF;
  border:0;
  margin:0;
  padding:1em;
}

h1, h2, h3, h4, h5 {
  color:#993333;
  font-weight:normal;
  page-break-after:avoid;       /*  Internet Explorer 8 and higher  */
  white-space:nowrap;
}

p {
  line-height:1.33;
}

img {
  border-width:0;
}

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 text that is still in preparation and is advanced enough that I want 
    to see it when working on the document and don't mind if others see it, 
    as long as it's plainly not fully displayed  */

.draft {
  color:#887799;
  display:none;
}

/*  A trial for getting attention  */

.highlight {
  background-color:#FFFF99;
}

/*  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, .highlight {
}

/*  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;
}

/*  ****************  */
/*  Simulated Banner  */

/*  A banner, ordinarily outside the document page, is simulated in all 
    document pages when scripts don't run.  */

#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;
}

/*  Some colouring and spacing that is particular to the fake banner  */

#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:0;
  padding:0;
  width:100%;
}

div.Abstract {
  border-bottom:1px #99CCFF solid;
  border-top:1px #99CCFF solid;
  clear:both;
  color:#333366;
  margin-bottom:1em;
  margin-top:1em;
  padding-bottom:1em;
  padding-left:2em;
  padding-right:2em;
  padding-top:1em;
  width:67%;
}

div.Abstract p {
  font-style:italic;
}

div.Notice {
  border-bottom:1px #99CCFF solid;
  border-top:1px #99CCFF solid;
  clear:both;
  color:#333399;
  margin-bottom:2em;
  margin-top:2em;
  padding-bottom:1em;
  padding-left:2em;
  padding-right:2em;
  padding-top:1em;
  width:75%;
}

div.Notice p {
  font-size:12pt;
}

/*  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. Editing of those 
    for presentation here was easier if the footnotes could be kept. 
    Footnotes have anyway turned out to be useful for some new pages.  */

a.FootnoteReference {
  bottom:1ex;
  font-size:smaller;
  position:relative;
  vertical-align:0;
}

div.Footnotes {
  clear:both;
  width:100%;
}

/*  To separate the footnotes from preceding text, but without taking the 
    whole width (as would seem to be required by a visible border), remember 
    to begin the footnotes with an HR.  */

div.Footnotes hr {
  height:1px;
  margin:0px;
  padding:0px;
  text-align:left;
  width:25%;
}

/*  ************************************************************************  *
 *        Copyright © 2007-2021. Geoff Chappell. All rights reserved.         *
 *  ************************************************************************  */
