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: Thu, 14 Oct 2010 03:22:32 -0400
To: Håkon Wium Lie <howcome@opera.com>, Sylvain Galineau <sylvaing@microsoft.com>
CC: "www-font@w3.org" <www-font@w3.org>
Message-ID: <7534F85A589E654EB1E44E5CFDC19E3D049DDC228E@wob-email-01.agfamonotype.org>
On Wednesday, October 13, 2010 2:00 PM Håkon Wium Lie wrote:
> Sylvain Galineau wrote:
>  >
>  > ...the test rule would be:
>  >
>  > 	@font-face { font-family: "AcidAhemTest"; src: url(font.woff),
> url(font.ttf); }
> I don't support this change. I think there's a value to keeping things
> stable. Errors should be corrected, but -- in general, unless there
> are obvious reasons -- I don't think features should be added or
> removed.

I don't see how implementing what Sylvain has proposed would affect the features of the test. If the goal of ACID3 is to test @font-face functionality, then using TTF data format (that is optional to be supported by the browsers) cannot be considered a valid test - browsers may fail just because they do not support this *optional* format even though they are fully compliant with the CSS spec.

Given that at the time when the ACID tests were written there have been no interoperable font format mandated by any W3C spec, the test itself is faulty - failure to support an optional font format doesn't mean failed support for @font-face. 

What Sylvain is proposing is in fact correcting an error in the test itself - by adding reference to a font resource in a format that is soon to become the official interoperability standard the test would be able to fulfill its purpose for all compliant browsers.

> Aslo, by making the proposed change, it becomes possible to pass Acid3
> without supporting ttf.

And why this is an issue? TTF is an optional format that has never been mandated to be supported by browsers.

> We could end up in a situation where browser x
> support ttf only and browser y support woff only, but both of them
> pass Acid3. As a result, interoperability would suffer.

Good point! The only way to solve this issue is to remove the optional TTF resource and use interoperable and standardized WOFF format. This will insure that all browsers that pass the test are compliant with officially standardized solution, any support for optional features would be an icing on the cake.


> I'm happy to add WOFF to a future Acid test, though.
> Cheers,
> -h&kon
>               Håkon Wium Lie                          CTO °þe®ª
> howcome@opera.com                  http://people.opera.com/howcome
Received on Thursday, 14 October 2010 07:26:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:35 UTC