W3C home > Mailing lists > Public > public-webfonts-wg@w3.org > December 2010

RE: Test Suite in CVS

From: Levantovsky, Vladimir <Vladimir.Levantovsky@MonotypeImaging.com>
Date: Wed, 8 Dec 2010 14:55:14 -0500
To: Chris Lilley <chris@w3.org>, Tal Leming <tal@typesupply.com>
CC: WOFF Working Group FONT <public-webfonts-wg@w3.org>
Message-ID: <7534F85A589E654EB1E44E5CFDC19E3D053BE3A6B6@wob-email-01.agfamonotype.org>
It seems that this is a result of two consecutive failures - it fails to load WOFF file and fails to load the fallback font. Do we know if Prince supports CFF fonts?

Vlad


> -----Original Message-----
> From: public-webfonts-wg-request@w3.org [mailto:public-webfonts-wg-
> request@w3.org] On Behalf Of Chris Lilley
> Sent: Wednesday, December 08, 2010 2:39 PM
> To: Tal Leming
> Cc: WOFF Working Group FONT
> Subject: Re: Test Suite in CVS
> 
> On Wednesday, December 8, 2010, 8:17:09 PM, Tal wrote:
> 
> TL> On Dec 8, 2010, at 2:07 PM, Chris Lilley wrote:
> 
> >> TL> Please let me know if you have comments, concerns, etc.
> 
> >> It may be wise to mention in the tests that the font is being loaded
> over a network.
> 
> TL> That's a good point. I made the change. Does the phrasing sound
> okay?
> 
> Yes, it looks great.
> 
> I ran through the tests in Firefox, passes many and fails some due to
> not throwing out bad WOFF as per spec. Easy though for the
> implementation to do these checks and pass more, i suspect.
> 
> I also ran them through PrinceXML 7.1 and found an odd effect. Its
> doesn't display FAIL and it doesn't display PASS. It displays P
> 
> PDF sample (PrinceXML is an xhtml+css to PDF converter) and warning log
> attached.
> 
> 
> 
> --
>  Chris Lilley   Technical Director, Interaction Domain
>  W3C Graphics Activity Lead, Fonts Activity Lead  Co-Chair, W3C
> Hypertext CG  Member, CSS, WebFonts, SVG Working Groups
Received on Wednesday, 8 December 2010 19:55:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 8 December 2010 19:55:47 GMT