The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

I totally understand where you're coming from.
The funny thing is, I did test using 4.7, but the only style that worked was the hover.

However, this was done rather unconventionally, where I had a server-side include, which contained its own embedded style tag, which worked. But the style settings from the main page (the body: font-family) did not!

Do you have the URI of that page where you are getting the errors, I typically test in the old Netscape 4.7x, Netscape 6.22/Mozilla and Micro$oft IE 5.0 - 6.0 so if one saw the HTML page I should be able to see what is going wrong with the page in question myself.

Reason behind multiple fonts

The reason for multiple font values with the font-family attribute is to accomodate useability on systems that do not have the intended font-family available.

Hence, the browser will start from the left and work its way in. It will render the first font it comes across that it actually has access to on its system.

It is a nice added feature that is good to get in the habit of coding. The last font listed is often either, serif or sans-serif. Basically this is telling the browser to use the default system font of the type specified (serif OR sans-serif).

Ha I am hoping he is using at least Front Page 2000 because Front Page 2002 (comes with Office XP) is just plain horrid and butchers your pages. Especially when it tries to bind CSS styles and adds M$ propietary garbage. Ya I tried out both and Front Page 2000 is the better of the two. That is if you still use that piece of garbage.

If you do have a page that has been built using FrontPage, you could try running it through a cleaner before you deploy the file live. For example DreamWeaver has a clean-up HTML option (but then if you had DW, you'd use that, wouldn't you?). Also you could try downloading HTMLtidy from W3C and the Tidy Gui as a front-end.