RE: Including WOFF in ACID3

Sylvain Galineau <[email protected]>
Newsgroups gmane.comp.web.fonts
Message-ID <045A765940533D4CA4933A4A7E32597E28081C0A@TK5EX14MBXC111.redmond.corp.microsoft.com>
> From: [email protected] [mailto:[email protected]] On
> Behalf Of John Hudson
> Sent: Friday, October 15, 2010 10:47 AM
> To: [email protected]
> Cc: [email protected]
> Subject: Re: Including WOFF in ACID3
> 
> Håkon Wium Lie wrote:
> 
> >  > I'd like to see Acid 4 limit itself to actual W3C web
> recommendations.
> 
> > That would make the test much less valuable for interoperability
> > purposes. For example, JavaScript is essential for today's web apps
> > and it's not a W3C Rec. The same goes for TTF/OpenType, the payload
> > which WOFF carries.
> 
> That's reasonable, but I think the documentation of the test should
> clarify the status of the individual test objects, vis à vis web
> standards, and explain what is being tested and why. Testing handling
> of
> TTF/OTF as a delivered payload is different from giving the impression
> that the test requires a browser to support download of raw TTF/OTF
> files.

I strongly support that. Håkon and I chatted on the phone today and it is 
pretty clear that ACID3 is neither meant to be a conformance test nor an 
accurate reflection of real-world interop practices. Thus changes of this 
nature are neither really necessary nor desired. Unfortunate imo but that's
what we have.

I certainly support better clarity as to what these tests do and do not
measure. The ACID2 guide referenced by Håkon is a good example.

I consider the issue resolved on my end. Thanks!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.