RE: EOT-Lite File Format

Thursday, July 30, 2009 Tab Atkins, Jr. <jackalmage@gmail.com>:

>Well, I think it's pretty likely that IE9 will still support EOT -
>pages that are using EOT fonts now will 'break' without it.

>Now, hopefully it will become *practically* dead at that point, as
>everyone starts using the interoperable format.

I was assuming really dead. As in CSS Expressions dead.
Sylvain... No?

Don't know if it's a bone of contention or not, really.

Regards,

rich

-----Original Message-----
From: www-font-request@w3.org [mailto:www-font-request@w3.org] On Behalf Of Tab Atkins Jr.
Sent: Thursday, July 30, 2009 8:07 PM
To: rfink@readableweb.com
Cc: Thomas Lord; Sylvain Galineau; robert@ocallahan.org; John Daggett; www-font
Subject: Re: EOT-Lite File Format

On Thu, Jul 30, 2009 at 7:00 PM, Richard Fink<rfink@readableweb.com> wrote:
> Thursday, July 30, 2009 Thomas Lord <lord@emf.net>:
>
> Thomas Lord wrote:
>
>>That suggests a SHOULD requirement.  UAs SHOULD ignore
>>non-nil root-strings but are not obligated to do so.
>>Authors can't count on them being ignored on the one
>>hand but UA makers are encouraged to ignore them
>>entirely.
>
> Tab Atkins replied:
>
>>Nope, it has to be a MUST requirement - UAs MUST ignore non-nil
> rootstrings.  IE <= 8 browsers will just be >nonconforming (which is fine,
> since they were produced before this standard was produced), and authors can
> take >advantage of that to hack something resembling same-origin into it if
> they wish.
>
> I see it the way Tab does. UAs MUST ignore non-nil rootstrings. EOT classic
> will be dead as of >IE8. The new spec being Ex Post Facto. This seems in
> line with what's been discussed all along.

Well, I think it's pretty likely that IE9 will still support EOT -
pages that are using EOT fonts now will 'break' without it.

Now, hopefully it will become *practically* dead at that point, as
everyone starts using the interoperable format.

~TJ

Received on Friday, 31 July 2009 01:13:55 UTC