🚀 go-pugleaf

In article <21AUG92.10494495@wl.aecl.ca> desikacharyk@wl.aecl.ca writes:

   ....
   Since the same chars are blocked whether I port Type 1 PS or 
   TrueType fonts, I am assuming that Windows is using the same Font 
   Encoding Vector in both cases. 

Right, the default is to use Windows ANSI encoding, both for T1 and TT fonts.

   So, in order to see all the chars in my font, I should
   be able to tell MS Windows to use Font's internal encoding vector instead
   of the Windows ANSI encoding vector. 

Yes, there is a two-way choice controlled by the `Family' and `CharSet'
fields in the PFM (Printer Font Metric) file.  You can either have Windows
use the fonts `native' or `raw' encoding, or have it reencoded to Windows ANSI.
Note, however, the the rule for making this decision is totally different
for ATM than it is for PostScript printer driver, so you can easily end up
in a inconsistent state, where you get one encoding on screen and a
different encoding when printing to a PS printer.

   I am not clear if editing PFB files as 
   suggested by Henry Churchyard will achieve this, because I cannot control 
   which encoding vector is used by Windows. Any thoughts if this is
   achievable are gretefully acknowledged.

Right, all editing of the encoding vector in the PFB file is ignored if the
font is in fact reencoded to Windows ANSI.  You must also modify the PFM file.
Also, you can't edit a PFB file directly without disturbing the embedded
binary section length codes.  You have to convert it to PFA form first, edit
it, then convert back to PFB form.

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 

Naturally, an operating system and applications should support on-the-fly
reencoding.  Certainly Windows and ATM don't do this.  But at least there is
A WAY based on modification of the PFM file and reencoding of the PFB file.

Now, for the $64k question:  How on earth do you do this for TT fonts?  
Is it true that there NO WAY to reencode a TT font?  And hence one is always
stuck with Windows ANSI, and hence, for example, there is no way to get at
the ligatures `fi' and `fl', even if the font contains such glyphs?


Berthold K.P. Horn
Cambridge, Massachusetts, USA