Re: WebFonts ready for use

Patrick Garies wrote:
> This could be dealt with by adding a shareability flag and/or domain 
> white‚Äźlisting mechanism to CSS3 Web Fonts that could prevent a Web font 
> from being shared indirectly.

That's what EOT fonts already do, and it is that model that people are 
rejecting in this thread.  Actually, the sharability information (people 
have referred to this as machine readable licences) doesn't even need 
EOT.  EOT basically is a domain whitelisting wrapper.

Basically, you are proposing to keep the status quo ante.

David Woolley
Emails are not formal business letters, whatever businesses may want.
RFC1855 says there should be an address here, but, in a world of spam,
that is no longer good advice, as archive address hiding may not work.

Received on Wednesday, 30 April 2008 23:26:42 UTC