/* intermedia.css
  Style sheet for use in skeleton pages
  (including pages for language families, info about ILV,
  teaching linguistics, etc.)

Maintained-by: Website
# Revised: 20 March 2003
by Albert Bickford and Scott Starker

History:
26 Apr 2006  SAS (added picturetext and greeting)
14 Jan 2003  SAS and JAB added definition for author style and adjusted definitions for cita
                (motivated by changes to the Tetelcingo and Orizaba pages)
22 Nov 2000  JAB streamlined interaction with footer.css and with the body tags of individual pages.
17 Nov 2000  JAB moved a number of styles here from the Nahuatl style sheet
30 Oct 2000  JAB revision to fix Netscape bugs
22 May 1999	 JAB revision to incorporate familia.htm
before 5/1999	Preliminary version, used only by index.htm and lenguas.htm

This maybe should be modified so that special characters
don't ever occur in italics, because of the IE printing bug
with some printers.

WARNING: don't use the "font" property; Netscape can't use it
and it invalidates the whole block that it is a part of. Use "font-size",
"font-weight", "line-height", etc.

*/

/*
**********************************************************
BODY
*/

/* styles for headings, anchors and links have been moved
   to footer.css, since we want them the same sitewide,
   not just in the skeleton pages
   */

body {
    /*
    We want a consistent background image in all the skeleton pages.
    However, doing it with a global stylesheet won't work,
    Nav4 mistakenly interprets the
    URL relative to the page being viewed, rather than
    relative to the location of the stylesheet.
    To make matters worse, the spec in the stylesheet
    overrides the background attribute of the body tag,
    resulting in a blank background (because Nav4 can't find the file
    from the stylesheet) even if the background is specified in HTML.
    Then, of course, earlier browsers wouldn't use the stylesheet anyway.
    So, this seems sufficient reason to specify the background image
    entirely with HTML code.
	  background-image: url(img/back.gif);
    */
}

p {
	text-align: justify;
	/* line-height: 1.2em; if <sup> is not used (IE). We need to get the Unicode characters for these characters. */
}

/* Scott added this line for something in the Nahuatl pages. */
p.center {
	text-align: center;
}

.photo {
	text-align: center;
}

/* used for author's signature at the bottom of an interface page */
.signature {
	text-align: right;
}

.nav {
	text-align: center;
	font-size: 80%;
}

/* Preguntas Comunes (FAQs) are laid out with different margins. */
body.faq {
    margin-left: 2em;
    margin-right: 2em;
}
p.faq {
    margin-left: 1em;
    margin-right: 1em;
}

/* permiso: paragraphs acknowledging where graphics or other copyrighted material comes from. */
p.permiso {
    margin-left: 1em;
    margin-right: 1em;
    font-size: 80%;
    /* line-height : 1.2em%; if <sup> is not used (IE). We need to get the Unicode characters for these characters. */
}

/*
**********************************************************
STYLES USED FOR HEADINGS

Levels of structure in the HTML hierarchy (<h1>, <h2>, etc.)
are used to define the structure of the HTML and so that
some reasonable formatting occurs if the stylesheet is
not available.  <h1> is always the top-level heading
on a page (or within a column on a bilingual page);
<h2> is used for the next lower level of subheadings, etc.

For headings that don't have special class names, the definitions
in footer.css apply.

Class labels are used to indicate the type of information
that is included in a particular heading level,
so that language and family names retain a consistent appearance
across multiple pages regardless of what heading level
they are in for a particular page.
This often overrides the default appearances in footer.css.
*/

/*
Title and subtitle of a page, if distinct from language family.
.tituloConSub and .titleWithSub are the variant of .titulo and .title
that are used when a subtitle immediately follows.
*/
.titulo, .tituloC, .title, .titleC, .titleL, .titleWithSub, .tituloConSub, .titleCWithSub, .tituloCConSub { color: blue; font-size: large; }
.subtitulo, .subtitle, .subtitleC, .subtituloC	{ color: navy; font-size: large; }
/*
Put titles and subtitles to the outside margin on bilingual pages
(cf. family and language headings on language family pages below).
.titleC (for centered Spanish or English) and .titleL (for left-aligned English) are provided to over-ride this normal behavior, when we have titles on a monolingual page.
*/
.titulo, .tituloConSub, .subtitulo, .titleL { text-align: left; }
.title, .titleWithSub, .subtitle { text-align: right; }
.tituloC, .tituloCConSub, .subtituloC, 
.titleC, .titleCWithSub, .subtitleC { text-align: center; }

/* Very little extra space between titles and subtitles */
.tituloConSub, .titleWithSub, .titleCWithSub, .tituloCConSub { margin-bottom: .2em; }
.subtitulo, .subtitle, .subtitleC, .subtituloC { margin-top: 0; font-size: 90%; }

/* semiTitle used with SPAN on a logical subtitle
   when we don't want to put it in a new block */
.semiTitulo, .semiTitle {
    font-style: italic;
    font-size: 70%;
}

/* author's signature at the end of a file, as in Nahuatl pages */
.author, .autor  {
	font-size: 90%;
	line-height: 120%;
	font-weight: bold;
	font-style: italic;
	text-align: center;
}

/* Language family and subfamily,
   within a page that talks about more than one family.
   These classes may also be used on <HR>.
   */
.familia, .family, .subfamilia, .subfamily, .familiaC, .familyC, .subfamiliaC, .subfamilyC {
	margin: 0 0 0 0;
	color: green;
	font-size : large;
	line-height : 120%;
	font-weight : bold;
}
/* See also TH.familia below in section for indexes */
/* Subfamily is used primarily by familia-maya.htm,
   because there are so many common names in that family.
   Subfamily headings should look like family headings,
   except as follows.
   */
.subfamilia, .subfamily, .subfamilia, .subfamily {
	font-style: italic;
}

/* Links within headings should be the same color as the headings.
   We have to mention the pseudo-classes too, so that the colors here take precedence
   over the colors specified for links elsewhere.
   (".familia A" apparently ranks lower than "A:visited")
   */
.familia A:link, .family A:link, .subfamilia A:link, .subfamily A:link,
.familia A:visited, .family A:visited, .subfamilia A:visited, .subfamily A:visited
	{ color: green; }
/* But, still use a distinct hover color */
.familia A:hover, .family A:hover, .subfamilia A:hover, .subfamily A:hover
	{ color: red; }

/* List of common names for languages in a family or subfamily.
   These lists immediately follow a family or subfamily heading
   in a family page,
   hence the negative top margin to remove some excess white space.
   */
.lengua, .language, .lenguaC, .languageC {
	margin: -.5em 0 0 0;
	font-style: italic;
	font-weight: bold;
	font-size: medium;
	line-height : 120%;
	color: red;
}

/* On language family pages, put the language, family, and subfamily names
   to the outside margin,
   so that they appear better centered around the initial graphic.
   However, we don't want to do this if these class names are used
   on other sorts of pages, so we have to specify that it's
   only when .familia or .family are the top-level heading
   that this is done.
   */
h1.familia, h2.subfamilia, h2.lengua, h3.lengua {
	text-align: left;
}
h1.familiaC, h2.subfamiliaC, h2.lenguaC, h3.lenguaC {
	text-align: center;
}
h1.family, h2.subfamily, h2.language, h3.language {
	text-align: right;
}
h1.familyC, h2.subfamilyC, h2.languageC, h3.languageC {
	text-align: center;
}

/* Other section heads, such as a publications list in a family page */
.seccion, .section, .sectionR {
	margin: 1em 0 .5em 0;
	font-size : medium;
	font-style : normal;
	font-weight : bold;
	line-height : 120%;
	color: blue;
}
.sectionR {
	text-align: right;
}

.subseccion, .subsection {
	margin: .5em 0 .5em 0;
	font-size : medium;
	font-style : italic;
	font-weight : normal;
	line-height : 120%;
	color: navy;
}

div.picturetext {
    font-weight: bold;
}

div.greeting {
    text-align: center;
    font-size: small;
}

/*
**********************************************************
STYLES USED FOR HIGHLIGHTING WORDS IN TEXT
*/

/* See also .cita in footer.css */
/* The Unicode fonts are specified for BODY in footer.css, but we need them here in case we have to override
   the spec for BODY on certain pages.  In that case, we'd probably still want a Unicode font for these.
*/

/* .ortografia, .orthography, .fonema, .phoneme tend to be single characters */
span.ortografia, span.orthography {
	/* line-height: 1.2em; if <sup> is not used (IE). We need to get the Unicode characters for these characters. */
	color: blue;
	font-weight: bold;
	font-family : "Charis SIL", "Doulos SIL", "TITUS Cyberbit Basic", Gentium, "Lucida Sans Unicode", serif;
}
span.fonema, span.phoneme {
	/* line-height: 1.2em; if <sup> is not used (IE). We need to get the Unicode characters for these characters. */
	color: red;
	font-weight: bold;
	font-family : "Charis SIL", "Doulos SIL", "TITUS Cyberbit Basic", Gentium, "Lucida Sans Unicode", serif;
}

span.english {
}

span.espanol {
}

/*
**********************************************************
STYLES USED ONLY IN INDEXES
*/
th.familia {
	background-color : LightGrey;
	text-align: center;
	font-weight: bold;
	font-size: medium;
	line-height: 120%;
}

ul.index {
	margin-bottom: 0;
}

/*
**********************************************************
MISC. OTHER STYLES used in interface pages */

/* Special boxes of information
   highlighted for PR purposes */
p.PR-es, p.PR-en { background-color: aqua; }

.mycenter { align: center; } /* Vic Brown used this one; I doubt if any pages use it any more. */

/* no extra space between headings and lists */
/* CSS 2 provides a mechanism of doing this, but we'll have
   to rely on a class name for now.
   */
.nospace {
	margin-top: 0;
	margin-bottom: 0;
}

/* All of the main tables (those which enclose the main body of material on a page) 
should use this, so that we can easily control the page width of all pages on the site. */
table.std { width: 75%; }







