If you use separate css' for each webpage, you'll need a <link> statement for each.
(See book page 50.) There is nothing wrong at all with the book in this regard.

But, be aware, if you accidentally insert a comma in a link statement, it's presence will
*not* be brought to your attention. I spent half a day comparing absolutely identical webpages, code, design, css, everything, until I spotted the comma.

In my case, the effect of the comma was to ignore everything in the link statment that followed it. This meant a simple 1 pixel border was not drawn at run time. Just to make it particularly nasty, the border WAS drawn at design time, just wasn't there at run time. Arggggggh!!!!!

VV

Yep, been bitten by that a few times myself. A developer is only as good as his debugging tools!

You can use Mozilla Firefox to check your CSS, go to Tools -> JavaScript Console, it will report CSS errors there in addition to JavaScript errors (Firefox 1.5 or >).

There are also W3C validation tools that will report errors in markup, http://validator.w3.org/

There are also development tools that exist for various browsers that will submit your markup and/or CSS for validation for you.

For IE, there is the Internet Explorer Developer Toolbar
http://www.microsoft.com/downloads/d...displaylang=en

For Firefox there is the Web Developer extension
https://addons.mozilla.org/extension...info.php?id=60

HTH!

Regards,
Rich

--
Author,
Beginning CSS: Cascading Style Sheets For Web Design
CSS Instant Results

http://www.catb.org/~esr/faqs/smart-questions.html