@charset "iso-8859-1";

/*******************************************************************************
*  base.css : 2005-06-28 : Ruthsarian Layouts
* ------------------------------------------------------------------------------
*  base set of stylesheet rules needed to form the layout, and layout only.
*  color and fonts and such are not handled here.
*  side column widths are defined in EMs. see base_pixels.css for a pixel
*  version instead.
*******************************************************************************/

#overwrite
{
color:#000000;
}

#overwrite a
{
color:#000000;
}

body
{
	background-color:#E1D7D5;
	color: #fff;
		font-family: arial, helvetica, sans-serif;
			font-size: 100.1%;	/* font sizing approach recommended by Dave 
				   Silvester on the css-discuss list. "the 
				   .1 is important." */
		margin: 0;
	padding: 1em;
}

#pageWrapper
{
	width: 700px;
	margin-left: auto;
	margin-right: auto;
	border-style: solid;	/* explicitly defined within eact selector in 
				   case you want change border styles (to mix 
				   it up) between elements */
	border-width: 0 1px;	/* puts a border on the left and right sides of
				   the page. #masthead and #footer will handle 
				   the top and bottom borders */
	background-color:#333333;
		font-size: 80%;
}

#outerColumnContainer, #innerColumnContainer
{
	border-right-width: 0;	/* to get from 3 to 2 columns, we must hide the
				   right-side border */
}

#outerColumnContainer
{
	z-index: 1;
	border-color: #fff;	/* set default color to white. set the real
				   color inside colors.css */
	border-style: solid;
	border-width: 0 11em;	/* sets the width of the borders used to create
				   the left and right columns' background 
				   color. */
	border-right-width: 0;
		border-left-color:#333333;	/* left hand column background color */
	border-right-color: #bb8;	/* right hand column background color */
}
#innerColumnContainer
{
	z-index: 2;
	width: 100%;
	margin-right:0;
	border-right-width: 0;
		border-style: solid;
	border-width: 1px 1px;	/* puts borders between center and the side 
				   columns. */
	margin: 5px -1px;		/* compensation for the borders because of
				   100% width declaration on this object */

}
* html #innerColumnContainer
{
	position: relative;	/* fix a render bug in IE under certain
				   conditions */
}
#contentColumn
{
	margin: 0 -1px;		/* without this, boxes stop floating next to 
				   each other */
	width: 100%;
}
#leftColumn, #contentColumn
{
	float: left;
	position: relative;	/* IE has a display/render bug with non-floated 
				   block elements inside floated block elements. 
				   setting position:relative on the floating
				   element seems to resolve this. */
	z-index: 10;
	overflow: visible;	/* fix for IE italics bug */

}
#rightColumn
{
	position: absolute;
	margin: 0;
	padding: 0;
	width: 0;
	height: 0;
	border: none;	
	float: right;		
}
#leftColumn
{
	background-color:transparent;
	width: 11em;
	margin: 0 1px 0 -11em;	/* like in the #contentColumn selector, without
				   the 1px margin on the opposite side of the 
				   box, boxes stop floating next to each 
				   other */
}

#buttons{
	padding-top:5px;
	padding-right:5px;
	height: 20px;
	width: 400px;
	color:#000000;
	font-family: Verdana, Arial, Helvetica, sans-serif;
	font-size: 12px;
	text-decoration:none;
}

#buttons a{
	padding-top:5px;
	padding-right:5px;
	height: 20px;
	width: 400px;
	color:#000000;
	font-family: Arial, Helvetica, sans-serif;
	font-size: 50px;
	text-decoration:none;
}

#buttons a:hover{
	padding-top:5px;
	padding-right:5px;
	height: 20px;
	width: 400px;
	color:#000000;
	font-family: Arial, Helvetica, sans-serif;
	font-size: 12px;
	text-decoration:underline;
}

#footer
{
	position: relative;
	height: 20px;
		text-align: center;

}
#masthead
{
	background-image:url(../images/banner2.jpg);
	height: 85px;
	border-style: solid;
	border-width: 1px 0;	/* handles the top of the layout's border and the
				   bottom of the masthead section */
	background-color:#6F5765;
	color:#000000;
}

#footer
{
	border-style: solid;
	border-width: 0px 0px 1px;	/* handles the top of the footer section and 
				   the bottom of the entire layout */
		background-color:#333333;
	color: #fff;
}

#masthead, #footer
{
	padding: 0em;
}

.breaker
{
	background-image:url(../images/bandA.gif);
	border-bottom: solid 1px #fff;
	text-align: center;
	height:5px;
}

.clear
{
	clear: both;
	padding-bottom: 1px;	/* for Gecko-based browsers */
	margin-bottom: -1px;	/* for Gecko-based browsers */
}

.hnav
{
	border-style: solid;
	border-width: 0 0 1px 0;
}

.hide, #oldBrowserNotice, .ieSixCharDupBug
{
	/* hide elements that CSS-targeted browsers shouldn't show */
	display: none !important;
}
#contentColumn
{
	border-width: 0;	/* reset value from that in the version 4 
				   stylesheet. this isn't in borders.css because
				   were you to create a print.css and not 
				   include borders.css, then the v4 border would
				   still remain when you print. */
}
/*
	The below block of CSS is invalid, and will invalidate this stylesheet.
	So it is up to you to decide how you want to handle this. The below CSS
	is a fix for IE/Win to help it better handle text that is wider than 
	the available area. It does not handle this as expected, and forces the
	floated elements to start stacking. This is a very undesirable thing.
	Until a CSS-compliant way is devised, this CSS block will have to do.

	So, do you live with invalid CSS? This comes down to a sort of markup
	morals issue. Some people live and die by w3 validation. If it isn't
	valid, it isn't good. Others don't validate at all, rather focusing
	on "real-world" results.

	I think the answer might be somewhere in the middle, but perhaps 
	leaning torwards w3 validation. It's good to work torwards validation.
	Indeed, I think documents should be able to validate against a w3
	or other validator. However there are times where you will find reason
	to explicitly defy the specs and include invalid markup or CSS.

	It is already done once in the markup of this layout, using the name
	attribute of an anchor tag. That attribute is deprecated in XHTML 1
	but without it, backwards compatibility at even the most base level
	is destroyed. So I purposely break the spec in order to provide that
	backwards compatibility. Remove the one line, and it validates fine.

	I am willing to break the markup when I have a good reason. And I think
	this is the same type of situation. IE breaks horribly without this 
	fix. I am willing to include this invalid line of CSS in order to 
	keep IE happy. Using the * html selector, I know that CSS-compliant
	browsers (the ones where validation matters) won't apply this CSS block.
	Pretty much ONLY IE will apply this CSS. I have a reason to break the
	CSS, I am fairly certain of its effect on other browsers (none), and
	so I include it here.

	I could have used the conditional comments that IE supports in it's
	proprietary side of HTML. However that requires _every_ document to
	contain the extra lines necessary to do this. This removes any
	central point of control over at least some of the CSS being
	applied.

	In a template(d) environment, perhaps I would take that alternate route.
	But here, where I'm not in a template(d) environment, I choose to add
	this directly into the CSS.
*/

html>body 
{
	padding-bottom: 1.01em;	/* this is to fix a bug in mozilla that results
				   in a 1px line of white below the footer when
				   the document gets very long. extremely long
				   documents may generate the bug again. if
				   you experience that, increasing this value
				   may help. i think this is related to moz's
				   off-by-one troubles as the bug does not
				   occur in any other browser */
}

#outerColumnContainer, #contentcolumn	/* selector case hack to reset version 4
					   stylesheet setting */
{
	background-color: #fff;		/* this sets the background color on the
					   center column */
	color: #000;

}

#leftColumn, #rightColumn, #contentColumn
{
	color: #000;
}

#leftColumn, #centerColumn, #rightColumn, #masthead
{
	padding-top: 0.0;
	padding-bottom: 0.0;	/* this is the vert padding talked about in the
				   previous selector. */
}

* html #pageWrapper
{
	word-wrap: break-word;
	text-align: left;	/* keep the content left-aligned */
}

* html body
{
	text-align: center;	/* hack to center this under IE5 */
}

* html #outercolumncontainer
{
	/* IE5.0/Win fix for 1px whitespace between masthead and body. */
	margin-top: -1px;
	border-top: solid 1px #000;
}

html>body #rightColumn
{
	display: none;	/* for compliant browsers, hide this column entirely */
}
* html #rightColumn *
{
	display: none;	/* ie's ghost-text bug is triggered by key elements
			   having display:none set. #rightColumn is one of those
			   key elements. so we display:none all child
			   elements (doesn't trigger the bug) and try to
			   make #rightColumn have no chance to affect
			   document flow. */
}

.vnav 
{
	margin: 0;
	padding: 0px;
	background-color:transparent;
	color:#FFFFFF;
	text-decoration:none;
	margin: 0em 0;
}

.vnav a
{
	margin: 0;
	padding: 0px;
	background-color:transparant;
	color:#FFFFFF;
	text-decoration:none;
	font-size:14px;
}

.vnav a:hover
{
	margin: 0;
	padding: 0px;
	background-color:transparant;
	color:#990000;
	text-decoration:underline;
	font-size:14px;
}

.mainnav a
{
	margin: 0;
	padding: 0px;
	background-color:transparant;
	color:#000000;
	text-decoration:none;
	font-size:14px;
}

.mainnav a:hover
{
	margin: 0;
	padding: 0px;
	background-color:transparant;
	color:#990000;
	text-decoration:underline;
	font-size:14px;
}

* html .vnav ul li a/* hide from IE5.0/Win & IE5/Mac */
{
	height: 1%;
}
* html .vnav ul
{
	position: relative;	/* IE needs this to fix a rendering problem */
}

.vnav ul li a
{
	color:#000000;
	background-color:#333333;
}
#rightColumn .vnav ul li a:hover, .vnav ul li a:hover
{
	background-color:#0000CC;
	color: #fff;
}
#rightColumn .vnav ul li a
{
	color: #336;
	background-color:#000099;
}
.hnav, .hnav ul li a
{
	background-color:#000099;
	color: #336;
}
.hnav ul li a:hover
{
	background-color: #336;
	color: #fff;
}
#innerColumnContainer, #masthead, #footer, .hnav
{
	border-color: #000;
}

/* :root is an invalid pseudo class but mozilla knows it */
:root code
{
	font-size: 120%;	/* monospace fonts are typically smaller that 
				   'normal' fonts under Mozilla. */
}

/*
	Time to try and get all the heading elements to the same size 
	regardless of browser. (IE seems to put them a big bigger
	than Mozilla, typically.)
*/

p, h1, h2, h3, h4, h5, h6
{
	margin: 1px 5px;
	}

h1
{
	font-size: 210%;
}
h2
{
	font-size: 180%;
}
h3
{
	font-size: 140%;
}
h4
{
	font-size: 126%;
}
h5
{
	font-size: 110%;
}
h6
{
	font-size: 100%;
}

/******************************************************************************/