This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 720 - Ugly fonts issues
Summary: Ugly fonts issues
Status: RESOLVED FIXED
Alias: None
Product: Validator
Classification: Unclassified
Component: Website (show other bugs)
Version: 0.6.5
Hardware: Other other
: P2 enhancement
Target Milestone: 0.6.6
Assignee: Terje Bless
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-15 06:23 UTC by Ville Skyttä
Modified: 2004-05-17 21:14 UTC (History)
0 users

See Also:

Attachments

Description Ville Skyttä 2004-05-15 06:23:29 UTC 
Many reports about this in www-validator@.

As discussed in the last qa-dev meeting, should we
- Use only generic font families?
- Use no font families at all?
Comment 1 Terje Bless 2004-05-15 12:07:23 UTC 
I nuked all the specific fonts except the Bitstream Vera variants. I've also
extracted the common items between headers into one selector so it's now only
one place to modify the font settings for all headings if we want to further
tweak it.

I've also set the variant to small-caps for headings -- despite Bitstream Vera
lacking such a variant -- just to see how it looks. If it looks awkward we can
nuke it before release.
Comment 2 Ville Skyttä 2004-05-16 07:17:11 UTC 
FWIW, I don't personally like small-caps, +1 for nuking it from base.css and
navbar.css.
Comment 3 Terje Bless 2004-05-17 17:14:41 UTC 
An informal poll on IRC was vaguely in fabour of the small-caps, with a caveat
that some fonts are not kind to small-caps variants. Considering the removal of
the specific (ugly) font families a fix for the bug, and the small-caps issue
one of individual taste for now. Closing FIXED and we'll do the small-caps thing
as needed later (probably by fiddling with the fonts).