/* 
purpose:  Overrides for a given language
			Only include in the files referenced here styles that we want to be specific for this 
			language. 

			The UI folder off the root contains the actual stylesheets..
			Try to mach the layout/nameing and format of the originals when overriding. 

description:  
	Links/@imports files used in ProLogis site for visual/screen content.
	CSS selectors are "grouped" into arbitrary files as described in comments below:
		global.css	: global element selectors; selectors used throughout site (ie front, internal, property-search, and region)
		framing.css	: selectors related to positioning and padding
		navigation.css	: selectors related to navigation elements used throughout site
		headers.css	: selectors used by headers
		forms.css	: selectors used in forms
		forminputs.css	: ID selectors for customizing specific form elements
		lists.css	: selectors used in UL, OL, DL lists
		tables.css	: selectors for customizing table layouts
		images.css	: selectors for images, i.e. class/ID selectors for IMG tags

note:  The grouping of selectors into these files is admittedly arbitrary.  There are three common problems encountered with this strategy:
1)  Is there an existing selector for a visual element I want to mock-up?
	answer:  You will likely have to search all files for any possible candidates.
2)  I need to create a new selector but I'm confused - which file it should live?
	answer:  Typically you won't need to create a new file for your selector, but you could - just make sure to @import it from here...
				Sometimes it will seem hard to choose, "should I place this selector in framing or in global?", 
				in which case our philosophy is to try to be more granular, and thus the correct choice would likely be "framing" (in such an example).
				Basically - the point is - global.css will get filled up with junk without too much effort, so the more effort that can be put into grouping selectors the better
3)  How do I find a selector in this heap of files
	answer:  You likely have to search through all files for the candidate.
------------
In all cases usage of the CSS files will lead to better solutions to #1-#3 above.

author:  f beachler
*/
/* @import url(screen/global.css); 
@import url(screen/headers.css);
@import url(screen/pageheaders.css);
@import url(screen/forms.css);
@import url(screen/forminputs.css);
@import url(screen/lists.css);
@import url(screen/tables.css);
@import url(screen/images.css);
*/
@import url(framing.css);
@import url(navigation.css);
@import url(maps.css);