Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!dcl-cs!alan
From: alan@comp.lancs.ac.uk (Alan Phillips)
Newsgroups: comp.windows.ms.programmer
Subject: ATM interferes with DEVICE_FONT bit?
Message-ID: <1178@dcl-vitus.comp.lancs.ac.uk>
Date: 11 Feb 91 13:02:48 GMT
Reply-To: alan@comp.lancs.ac.uk (Alan Phillips)
Organization: Department of Computing at Lancaster University, UK.
Lines: 16

I'm having a problem using EnumFonts. What I want to do is to present the
user with a list of _device_ fonts, so he can choose something that will send
text to the printer as text rather than graphics.

Without ATM, the font_type argument that the font enumeration proc gets
has a valid DEVICE_FONT bit, and I can distinguish GDI fonts from device fonts
(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; and the question of why the Epson 24pin driver claims to have no
device fonts even though it does).

With ATM, the DEVICE_FONT bit seems to be _set_ for _all_ fonts. So unless you
know what font names map to fonts in the printer, you're stuck. ATM does this
even if 'use resident fonts' is selected.

Anyone seen this? Better, anyone got a workround?