🚀 go-pugleaf

Hello,
      Earlier I asked why Windows 3.1 blocks out some of the characters in 
the 128-255 range of a 8 bit coded font when I port it from Mac to Windows.
I got an excellent explanation from Berthold Horn (Thank you Berthold!) and 
some tips on how I can edit PFB files from Henry Churchyard (Thank you Henry!).
Here I list exactly the characters in  Mac's Font that are blocked out by 
Windows (I have all the slots from 128-255 populated, except for the code 202, 
which corresponds to nonblank space char on Mac). 

Code Char Name    Code   Char Name       Code  Char Name       Code Char Name
128  Adieresis    154    odieresis       185   pi              222  fi
129  Aring        157    ugrave          188   ordamasculine   240  apple
138  adieresis    158    ucircumflex     189   Omega           253  hungarumlaut
141  ccedilla     160    dagger          190   ae              254  ogonek
142  eacute       166    paragraph       208   endash          
143  egrave       178    lessequal       215   lozenge
144  ecircumflex  179    greaterequal    221   guilsingright

	The above chars are all blocked out by Windows 3.1. Windows 3.0 blocks
out the followinfg 4 additional chars:

Code Char Name    Code   Char Name       Code  Char Name       Code Char Name
136  agrave       152    ograve          173   notequal        175  Oslash


	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. 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. 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.

Regards,
K.Desikachary,
AECL Research.