🚀 go-pugleaf

harris@garfield.catt.ncsu.edu (Michael Harris) writes:

>jpenne@ee.ualberta.ca (Jerry Penner) writes:

>>It does seem kind of silly though to
>>make you stuff fonts into DLLs since it's hard to get them back out
>>again if you want to modify them.

>Actually, it does make a little sense if you think about it.  As soon as you
>put it in a DLL, you have all of the magical capabilities of a DLL.  Such as
>only one copy of the font in memory at once, etc.
					      ^^^

Yes, that part is nice.  Still, since the font managing code in the
operating system should be able to regulate this aspect of things.
OS/2 v2.0 still has the MSDOS problem of font file inconsistency all
over the place.  The OS/2 terminal program uses some bizarre font
which you can't change (you get two sizes).  The windowed DOS or OS/2
sessions use a limited set of fonts which aren't usable by any other
applications.  I realize that they require fixed-width fonts.  What I
don't understand is why they can't use a default font if the user-
specified one is proportional (or just make it fixed width by using
the em-width).  I like the way most of the other fonts in the system
are consistent and customizable by using the font palette utility in
the System Settings directory.

What's the 'etc'?  Other than only having one copy of a font in memory,
what are the other advantages?  Purgeability?  Ok.  I still don't see
it being very easy to copy and then modify fonts shipped with the
system.  And of course they're a pain to create.  And you did say it
made "a little sense", [not a lot]. :)
-- 
Jerry Penner   jpenne@ee.ualberta.ca   Try a 1-line .sig today.