TYPE DESIGN INFORMATION PAGE last updated on Fri Dec 13 00:51:35 EST 2024
FONT RECOGNITION VIA FONT MOOSE
|
|
|
|
Dave Brezina on Web Fonts
The entire text below is due to David Brezina, 2010. I think we (type designers) maintain an old illusion about how our market works. People do not buy fonts because they could not get them for free anywhere else. They buy them out of sympathy, understanding the value of our work and/or legal reasons. They could get them for free, easier, and faster (!). It is not that we would be shooting in our typefaces. It is more like we have been shot already. We already accepted the piracy as a burden of our business. If I am right in this view, we do not need any kind of DRM. The expected "new" web piracy won't change a thing. I would very much like to see some study or educated estimate re this view. Or at least an authoritative opinion. It is crucial information for designers in order to evaluate the formats properly. Otherwise, they are just left aiming for the most security. What we, however, want is a tool to limit webfont licences exclusively for web. We want to make a profit out of this #webrisk and keep distinction between web and print fonts. Why? If I am not sure whether opening my fonts for web use is going to make me money I would rather keep the new market separated from the old working one. That is the motivation behind the web-specific format. Acceptance of non-security, but limited to web. Personally, I think that opening to web market is surely going to make a profit. An objectively, we are not going to have strictly (that is: not-convertible) webspecific format ever. Not with current technologies where the fonts are described with curves. The only option I see is bitmap fonts &c. .webfonts is just bundled metadata with print font (we can have them in OT table as Berlow suggest, why another format simple-to-hack when most are not going to care?), EOT Lite is a very thin wrapper as far as I understood, but at least not so trivial. It will become easy convertible (assumption), but at least something. Typekit and similar tools offer only limited security by obfuscation. So far too easy to circumvent. These techniques are not imo worth complicating life of paying customers. Even though the interface is sexy, it is still another interface. Therefore: prepare the fonts for web (have them subsetted, add web exclusive license, permission tables, and go naked! Or if you are shy, have EOT Lite. Sidenote about obfuscation methods. Some of them impair the fonts' kerning and OT features. Not a good idea. My concern is purely of egoistic designer. With my limited abilities I tried to produce as good font as possible and I don't want crippled copies of my font ripped off from various webservices floating around. I want constant quality of my work world-wide, nothing smaller, if possible. The very first person who paid a compliment to my typeface on web was the one who posted it on a Russian download server (being it ripped from my MATD PDF specimen). Just thought it illustrates the situation pretty well. :-) |
EXTERNAL LINKS |
| | |
| | |
|
Luc Devroye ⦿ School of Computer Science ⦿ McGill University Montreal, Canada H3A 2K6 ⦿ lucdevroye@gmail.com ⦿ https://luc.devroye.org ⦿ https://luc.devroye.org/fonts.html |