- From: Levantovsky, Vladimir <Vladimir.Levantovsky@MonotypeImaging.com>
- Date: Wed, 19 May 2010 11:43:32 -0400
- To: Dave Crossland <dave@lab6.com>, "www-font@w3.org" <www-font@w3.org>
On Tuesday, May 18, 2010 10:22 PM Dave Crossland wrote: > > On 19 May 2010 03:37, John Hudson <tiro@tiro.com> wrote: > > None of the existing embedding bits constitute or > > imply permission to create or serve a WOFF file. > > Web authors should confirm that a font is licensed > > for such use. > > Create and serve, but what about render? Rendering has nothing to do with embedding permissions. > I mean, how does this apply > to something like Prince? When Prince "serves" a WOFF, is it > considered to be "embedding" the WOFF in a document? Or is it > considered to be downloading a WOFF, unwrapping the WOFF to get a OTF, > and "embedding" the OTF in a document? My understanding is that Prince (and/or any other UA) doesn't serve a WOFF, it consumes it. Once downloaded, the WOFF is unpacked and from this moment on UA deals with unwrapped original font. Regards, Vlad
Received on Wednesday, 19 May 2010 15:45:25 UTC