Donna M Smillie wrote
> So, it looks like you've stumbled across another of those
> peculiar quirks of browser implementation of CSS, and rather a
> good one at that!  :-)  It *looks* like one should always name at
> least one font in font-family definitions to ensure that text is
> displayed correctly.  Maybe it's something like - with just
> "sans-serif" the browser uses some sort of system font, but if a
> named font is specified as well, even if that font isn't
> installed it forces the browser to check installed fonts and it
> uses one of those instead.  Or something like that.
>
> Weird!  :-)

I thought a bit about it, and though I can't replicate it on my PC (it looks
fine as it is), perhaps it would be best to specify the character encoding
in the HTML file so the user's OS doesn't use its default, which may vary
from system to system. -David

<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">

• Web Designer Courses
• Off the Shelf Training Courses

HWG hwg-style mailing list archives, maintained by Webmasters @ IWA