Path: utzoo!utgpu!news-server.csri.toronto.edu!helios.physics.utoronto.ca!ria!obelix.gaul.csd.uwo.ca!hackett
From: hackett@obelix.gaul.csd.uwo.ca (MICHAEL HACKETT)
Newsgroups: comp.sys.apple2
Subject: Re: TrueType on GS and PostScript problem on AWGS
Message-ID: <3300@ria.ccs.uwo.ca>
Date: 7 Jun 91 17:51:12 GMT
References: <63B24CBB8AFF603C72@vax5.cit.cornell.edu>
Sender: news@ria.ccs.uwo.ca
Organization: University of Western Ontario, London, Ont.
Lines: 27

In article <63B24CBB8AFF603C72@vax5.cit.cornell.edu> WRDJ@VAX5.CIT.CORNELL.EDU ("In a night without day, on a road without end.") writes:

>     Second:  Lots of fun discussion about TrueType on the GS has been going on.
>Personally, I'd love to see it, but I'm also concerned about the speed.  The 
>printing speed I'm not *too* concerned about, I've pretty much resigned myself
>to slow printing.  But TrueType is also used for display (improving WYSIWYG by
>a great deal), so all that computation would have to be done while scrolling,
>redrawing, etc.  This is where I assumed there'd be a major problem.  I'd love
>to have TrueType, but I'd hate to have it completely negate the benefits of my
>Zip (whenever it arrives...)
>
>     I'd like to hear more, though...
>
>Bill D.


    My plan was to do just what the font manager does now when it tries to
load a new font.  If it can't find a bitmap of the appropriate size, it
tries to scale another bitmap to the required size.  Instead of doing this,
I'd like to have it get the outline and render the bitmap for the entire
font at this time.  Thus, apart from this initial delay, the system will run
no slower than it does now.  The main problem right now, as mentioned in
earlier posts, is that the Font Manager, at this time, will not accept
bitmaps that are larger than 32K.  This would not likely be a problem for
screen fonts, but when printing, larger font sizes are needed.