W3C home > Mailing lists > Public > www-font@w3.org > October to December 2010

RE: Including WOFF in ACID3

From: Levantovsky, Vladimir <Vladimir.Levantovsky@MonotypeImaging.com>
Date: Tue, 19 Oct 2010 13:24:06 -0400
To: Mikko Rantalainen <mikko.rantalainen@peda.net>, "www-font@w3.org" <www-font@w3.org>
Message-ID: <7534F85A589E654EB1E44E5CFDC19E3D04A276FC9B@wob-email-01.agfamonotype.org>
On Tuesday, October 19, 2010 2:47 AM Mikko Rantalainen wrote:
> 
> considering that ACID 3 was supposed to test features that were in
> CR state or better in 2004, it should be pretty clear that WOFF does
> not apply. 

<snip />

> I have to say that no CR state or better in 2004 said that
> @font-face must support TTF. Regardless of this, I think ACID 3 should
> not be changed for this.
 
Sounds like the double standard treatment here. Is it appropriate? If we want to be consistent, the test in question must either be removed or changed.

ACID 3 tests may be old, but they are also current. Since we already established that TTF has never been mandated to be supported, and it is not the goal of ACID 3 tests to enforce the TTF support either, I would consider this a bug in the existing test, and what Sylvain has proposed is a simple bug fix. 

It is perfectly normal to fix bugs as they are discovered, and for this reason ACID 3 must be changed IMO. The proposed change will not affect any existing browser - every single one that passed this particular test before will pass it again with no changes. So, what is the reason for not fixing this bug?

> I'd like to see WOFF test in ACID 4, though.

Yes, I would say this is a must. WOFF is the format that is going to be standardized by W3C.

Regards,
Vladimir
Received on Tuesday, 19 October 2010 17:29:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:01:42 UTC