Font Styles not applying to all pages

[Guest]

I've created a styles.css page and linked it to all my FP2003 pages.
This is in the header of each page:

<link rel="stylesheet" type="text/css" href="styles.css">
</head>

For some reason, the font size style I have defined in my css page is not
applying to all my pages. This is what I have in the css page:

body
{
font-family: Arial;
font-size: 10pt
}

The Arial font works on all pages, but not all page fonts are taking on the
10pt size. Some of the pages that aren't working have graphics and custom
interactive buttons before the body text occurs. Could any of these be
causing this abnormality?
On one page in particular, I've done a code search on "style" and "font" and
there are no other occurances of these terms except for a font tag at the end
of the page which has a start and end tag.

I'm stumped. Any ideas?

 

[Ronx]

Are you using tables in any pages? Font sizes will not cascade into
table cells.
Change the style to:
body, p, td, th, li{
font-family: Arial, Helvetica, sans-serif;
font-size: 13px;
}

pt (point) is a printers measure (exactly 1/72 inches) and how 10pt is
rendered on a screen will vary from browser to browser, OS to OS. px
(pixel) is a definite measure related to the screen, and will always
be rendered the same way.

 

[Kevin Spencer]

The first "C" is CSS means "Cascading." This indicates that Style Sheets
"cascade," or are overruled by styles and style sheets that are "closer" to
the elements they affect. For example, you can redefine styles in a page
repeatedly, and of course, inline styles overrule all other styles.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Paranoia is just a state of mind.

 

[Guest]

Thanks Kevin

The first "C" is CSS means "Cascading." This indicates that Style Sheets
"cascade," or are overruled by styles and style sheets that are "closer" to
the elements they affect. For example, you can redefine styles in a page
repeatedly, and of course, inline styles overrule all other styles.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Paranoia is just a state of mind.

 

[Guest]

Yes, it's in the tables where it's not working. I didn't know this.
Tanks a bunch.

 

[Murray]

Are you using tables in any pages? Font sizes will not cascade into table

cells.

That's true only on pages without a valid and complete doctype. In quirks
mode there is a problem with this inheritance. In standards mode, there is
not.

 

[Guest]

OK Murray, tell me more.
I've heard a little about the doctype, but even FP2003 does not define
anything under the doctype heading (at least that I've seen in the code that
FP generates).

What's the doctype for and why should it be used.
Is this where the mode is defined.

 

[Kathleen Anderson [MVP - FrontPage]]

See the links at the bottom of this page:
http://www.spiderwebwoman.com/tutorials/doctypesolution.asp

 

[Murray]

I think I have this right....

The doctype is a statement that sits at the very top of your page. It was
originally created in SGML as a way of describing the KIND of markup that
followed, and was used exclusively by the validators to determine if the
declared kind of markup and the actual markup on the page were consistent.
During the NN4x/IE5+ fun years, browser manufacturers realized that quirks
mode (or bugwards mode) rendering was not adequate for meeting the emerging
standards, and so they were trapped in a dilemma - do they have to release a
NEW browser version for rendering Standards compliant pages? Instead they
hit on the notion of using a page's doctype, originally used only by the
validators, to completely switch the browser's rendering rules on the fly.
This allowed the same browser to successfully render differently coded
pages. It is clearly a good approach - so good that it's called "Doctype
Switching".

In fact, you can write your own document description - especially fun if you
are a fan of sand in the eyes, and bamboo slivers under the fingernails! 8)

W3C has loads of info about doctypes on their site....

 

[Guest]

I'm impressed.
You must of studied under Einstein.

Don
*********

 

[Guest]

Thanks Kathleen.
There's alot more to DOCTYPE than I ever imagined.

 

[Guest]

This looks pretty close to what I'm experiencing. I'm creating a very simple
site that non webmasters can maintain. My style sheet defines H3 as
{ font-family: Arial, Verdana, Helvetica, sans-serif; color: #29349A;
font-size: 14pt; font-weight=bold }, but the text displays in Verdana. I can
get the Arial only by specifying it directly at the text level.
<h3><font face="Arial" size="4">text</font></h3>
or by stripping out all the other font names from the CSS, which they want
to keep. It's got to be something simple, but I've tried all the usual
sources.

 

[Murray]

but the text displays in Verdana

Then there is some other later style that is overriding it.

It's got to be something simple

Probably is - can you post a link to the page, please?

 

[Guest]

Probably is - can you post a link to the page, please?
Murray - I would if I could, but it's confidential. I can't find any font
instruction above that would override the definition. Any other ideas?

 

[Murray]

Is it possible to sanitize it enough to post its code here? Or maybe you
could email me the link?