W3C home > Mailing lists > Public > www-font@w3.org > July to September 1996

Re: Re[2]: pixel fonts

From: Tiro TypeWorks <tiro@portal.ca>
Date: Fri, 09 Aug 1996 11:39:11 -0700
Message-Id: <199608091832.LAA02541@kefron.portal.ca>
To: www-font@w3.org
Sorry if people have already received this. I got a rather garbled
mail-bounce message and couldn't figure out which of the original three
recipients hadn't received it.

Glen Rippel wrote:

>     There is a market for pixel based fonts within memory constrained 
>     devices, however.....  For collaborative documents the world went with 
>     scalable type already for products like Envoy and Acrobat. The web 
>     already makes use of scalable fonts by referencing the FONT-FACE= tag 
>     like in Internet Explorer and Netscape Navigator. I is almost 
>     impossible to move towards bitmaps again.  

A move towards bitmaps certainly seems unlikely (although LettError have
certainly made a good showing of the clever, creative things you can do with
pixel fonts that you can't do with scaleable outlines -- I suspect there is
a market for such fonts and associated tools, as they present web and
multimedia designers with a decidedly playful way of dealing with display
text). I, however, fully support Erik's criticism of font embedding
developments to date. As professional type designers, neither Erik nor I are
keen on seeing our fonts being shot around the world in a variety of
insecure document formats (of which Acrobat is definitely an example). The
current FONT-FACE= tag is not a problem, as it relies on the font in
question being present on the end-user's system. Systems which conspire to
put that font on the end-user's system so they can view and print a given
website or electronic document are a problem, and a represent a serious
threat to type designers' livelihoods.

My own idea for a solution is to give designers and foundries greater
control over the ways in which their fonts can be used (i.e. control within
font format technology), and modify existing payment and distribution models
to reflect that control. Designers who intend their fonts to be used
primarily for print media applications should be able to disable the font in
such a way that it cannot be used in electronic documents; they then take
their chances in the traditional graphic design and typography market.
Designers who want to make their typefaces available for web design and
other electronic applications should be subsidised by the software and
Internet developers whose products are made more valuable by the existence
of such fonts. Matthew Carter's Verdana is an excellent example of the
latter: Microsoft paid Matthew to design the typeface and Tom Rickner to
hint it, then give it away free. Obviously they see this as a good
investment, as it increases the value of, among other things, their Internet
Explorer. If software developers want to create tools which make it possible
to send embedded fonts all over the world, they should be the one's paying
for font development.

John Hudson, Type Director

Tiro TypeWorks
Vancouver, BC

Tiro TypeWorks
Vancouver, BC
Received on Friday, 9 August 1996 14:33:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:29 UTC