Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!hp-pcd!hp-vcd!robertt
From: robertt@hp-vcd.HP.COM (Bob Taylor)
Newsgroups: comp.windows.ms.programmer
Subject: Re: ATM interferes with DEVICE_FONT bit?
Message-ID: <13790001@hp-vcd.HP.COM>
Date: 15 Feb 91 23:39:41 GMT
References: <1178@dcl-vitus.comp.lancs.ac.uk>
Organization: Hewlett Packard, Vancouver, WA
Lines: 14

> (we'll leave aside the question of why HP chose not to support device fonts in> the DJ500 driver - but that shows 'courier' as a device font even though it
> isn't; .....

The DJ500 driver doesn't support device fonts because it provides scalable fontsthat approximate all of the internal "device" fonts (and provide all of the
benefits of scalable fonts).  The DJ500, with this driver and a decently
configured host, can print text as graphics just as fast as it can print
"device" fonts.  The driver marks all of its scalable fonts as device fonts
so it can tell whether a font request given to the driver is for one of the
driver's fonts or a screen font - therefore, the driver's Courier scalable
font is marked as a device font.  For all intents and purposes, applications
should consider it as if it was really in the printer.

bob taylor
HP Vancouver