- From: Richard Fink <rfink@readableweb.com>
- Date: Mon, 6 Jul 2009 19:52:52 -0400
- To: "'Thomas Phinney'" <tphinney@cal.berkeley.edu>, "'Erik van Blokland'" <erik@letterror.com>
- Cc: <www-font@w3.org>
Thomas and Erik, Along the lines of Erik's "partial font" idea, what about custom naming? I can crack open a font and name it Bluefish WebDust. Or GWDFRHYU. Then all I have to do is declare the font with that name using @font-face in the CSS. It would seem to me that a would-be "font borrower" (Hah!) might lose some trust in the integrity of that file if such were the case. Do you see any glaring problems arising from that approach to obfuscation? Anybody else see an unwanted technical problem in that? -----Original Message----- From: www-font-request@w3.org [mailto:www-font-request@w3.org] On Behalf Of Thomas Phinney Sent: Monday, July 06, 2009 6:23 PM To: Erik van Blokland Cc: www-font@w3.org Subject: Re: Partial fonts The fonts are completely useful as web fonts, but you have broken their main utility as desktop fonts. Of course, there are issues of cross-font kerning and layout tables. Also, what if the user needs to further customize the CSS? T On Mon, Jul 6, 2009 at 1:59 AM, Erik van Blokland<erik@letterror.com> wrote: > Folks, > > here's an idea for you to shoot holes in. A font is split up into parts, > existing CSS mechanisms are used to glue them together without any > javascript or extra coding by the user (beyond the css specification > anyway). > The fonts by themselves are pretty useless. They can be reassembled of > course, but this will take some effort. > > http://letterror.com/develop/webfonts/partials/ > > Cheers, > Erik > > > -- "Men occasionally stumble over the truth, but most of them pick themselves up and hurry off as if nothing ever happened." - Sir Winston Churchill
Received on Monday, 6 July 2009 23:53:39 UTC