W3C home > Mailing lists > Public > www-validator@w3.org > December 2002

Re: Fonts in validator page

From: (wrong string) äper <christoph.paeper@tu-clausthal.de>
Date: Thu, 12 Dec 2002 09:50:57 +0100
Message-ID: <002101c2a1bb$96eff620$3ef4ae8b@heim4.tuclausthal.de>
To: <www-validator@w3.org>
Cc: "Ruurd Pels" <ruurd@acklin.nl>

Ruurd Pels <ruurd@acklin.nl>:
>
> I'm habitually using Konqueror under Linux, and the fonts on the validator
> page are absolutely horrendous.

Which one do you mean:

|  font-family:     "Luxi Sans", Tahoma, Verdana, "Myriad Web", Syntax,
sans-serif;

IMHO "sans-serif" would suffice, but except Verdana the others aren't such
bad choices, most probably your Linux' TrueType or antialiasing support is
disabled / not configured correctly.

Btw.: I noticed some other flaws in the CSSs:

The HTML element for abbreviations is not abbrev but abbr.

| a img {color: white} /* The only way to hide the border in NS 4.x */

May be so, but without a background color things get messy in a graphical
browser with images turned off.

Most of the h1-6 stuff from CORE stylesheets should be left out (e.g.
*spacing) or at least be condensed.

Shouldn't "Tip Of The Day" & "Jump To:" read "Tip of the Day" & "Jump to:"
or better leave it to text-transform:capitalize;. Actually there should be a
text-transform value in CSS that handles capitalization rules according to
the text language. On valid results the notice is capitalized ("This Page Is
Valid XYZ!"), on invalid just partly ("This page is *not* Valid XYZ!").
Capitalization in the Revalidate box isn't done consistently, too.

h2#result strong {text-transform:uppercase;} (for "not") maybe.
"h2.invalid a" should get a different color, just like "h2.valid a" has.

Finally I think CSS updates needn't wait for a full validator update.

Christoph Päper
Received on Thursday, 12 December 2002 03:50:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:14:05 GMT