W3C home > Mailing lists > Public > www-style@w3.org > June 2010

Re: CSS2.1 Test Suite Beta 1

From: John Daggett <jdaggett@mozilla.com>
Date: Tue, 15 Jun 2010 17:44:58 -0700 (PDT)
To: fantasai <fantasai.lists@inkedblade.net>
Cc: www-style@w3.org
Message-ID: <2016956372.460264.1276649098785.JavaMail.root@cm-mail03.mozilla.org>
> > The linked page includes this text:
> >
> >> Note that many of the tests require the Ahem font to be installed.
> >> Without the Ahem font installed, these tests are of no value.
> >
> > As I noted back in January, this is inaccurate, the font chapter tests
> > require a whole set of fonts:
> >
> >    http://lists.w3.org/Archives/Public/public-css-testsuite/2010Jan/0057.html
> 
> I uploaded your fonts onto the W3C website:
>    http://www.w3.org/Style/CSS/Test/Fonts/
> If you can write a more comprehensive test file for the installation,
> that checks for all the installed fonts, that would be helpful. I
> think I'll write a test file for Ahem as well, since I think this was
> a good idea. ;)
> 
> I do need to update the index file to mention these other fonts, though.
> I'll go do that.

The MS tests use a whole set of Ahem_xxx.TTF fonts for the fonts
chapter, that's what my original note was about.  Those are missing
from the Test/Fonts page.

For the CSSTest set there is a test page:

  contributors/mozilla/submitted/fontreftests/test-prerequisites.xht

It doesn't test for all the fonts in the set, that's tricky to do since some
of the fonts are intentionally constructed to reveal name matching bugs.

I think it would be nice if instead of directories of fonts, the build process
zipped up Ahem and variations and the CSSTest fonts into two separate zipfiles (the
licenses are different so I think it's better to keep them separate), that 
would simplify the steps needed to install.

John Daggett
Received on Wednesday, 16 June 2010 00:46:04 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:28 GMT