- From: Levantovsky, Vladimir <Vladimir.Levantovsky@MonotypeImaging.com>
- Date: Thu, 25 Jun 2009 13:28:37 -0400
- To: "Brad Kemper" <brad.kemper@gmail.com>
- Cc: "Aryeh Gregor" <Simetrical+w3c@gmail.com>, <robert@ocallahan.org>, "Jonathan Kew" <jonathan@jfkew.plus.com>, <www-style@w3.org>
> -----Original Message----- > From: Brad Kemper [mailto:brad.kemper@gmail.com] > Sent: Thursday, June 25, 2009 1:08 PM > To: Levantovsky, Vladimir > Cc: Aryeh Gregor; robert@ocallahan.org; Jonathan Kew; www-style@w3.org > Subject: Re: New work on fonts at W3C > > > On Jun 25, 2009, at 10:02 AM, Levantovsky, Vladimir wrote: > > >> Referer-based methods are unreliable, and can block users of your > own > >> site as well as letting through users of other sites. Some software > >> will strip referer headers, or even change them. (For instance, > >> IIRC, > >> no browser sends Referer headers from an HTTPS site to an HTTP > site.) > >> Depending on referer checking isn't a good idea. > > > > Thank you. I am not a web developer so I would trust the experts on > > this. > > My point was that font vendors have so far proven to be reasonable > > people willing to cooperate, which is contrary to Rob's presumption > > that we would insist on a particular way of doing things (i.e. root > > strings). > > So you would allow your fonts to be served in their raw format if > referrer based blocking was used? It could provide a large amount of > license violation, even if it wasn't perfect. This particular discussion had nothing to do with raw font format, it was relevant to discussing possible ways to subset EOT. And you lost me completely when you mention "a large amount of license violation", Can you please elaborate further? Thank you, Vladimir
Received on Thursday, 25 June 2009 17:29:11 UTC