>>I just started using, successfully, CSS in my CHM help file.
>>
>>Cascading Style Sheets allow to apply the same style to all HTML files, and make changes globally.
>>
>>All it takes is one additional line in each HTML file, for instance (erase extra spaces in the tags):
>>
>>

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

>>
>>Sample css document (mystyles.css) (erase extra spaces in the tags):
>>
>>

>>< STYLE TYPE="text/css" >
>>H0 {}
>>H1 {color: #FF0000}
>>H2 {color: #00B000}
>>BODY {background-color: #80FFFF}
>>TD {background-color: #90EED0}
>>< /STYLE >
>>

>>
>>After that, any changes to background color, font size, etc., have to be done only once, in mystyles.css.
>>
>>Hilmar.
>
>Just to comment that CSS can be done "inline" in the header section of the HTML file (no separate .css file), in the format you've used (ie with the STYLE tags). If linked as a separate .css file as you've done it, the the STYLE tags are not necessary.

I know, but what I find most interesting is to make global changes throughout an entire web site or throughout an entire help file (or selected HTML files). This can be done only through an external CSS.

>It does make testing variations of style quick & easy.

Well, I'm just learning. I copied some commands almost verbatim from my HTML textbook (changing colors, and adding some elements, such as <TD>, and they didn't mention whether <STYLE> was needed or not. I did ask myself, why do I have to enclude this?

One more thing: the textbook states that the highest-level header is ignored by both fourth-generation browsers - that's why I included H0. Do you know the reason for this queer behavior (ignoring the highest-level header)?

Hilmar.