Article View: comp.fonts
Article #735Why Windows Blocks Out Some Upper ASCII codes - Solution
From: desikacharyk
Date: Wed, 09 Sep 1992 22:35
Date: Wed, 09 Sep 1992 22:35
65 lines
3473 bytes
3473 bytes
Hello Font Enthisiasts, Earlier I asked why Windows 3.1 blocks out as many as 24 characters in the 128-255 range of a 8 bit coded font when I port it from Mac to Windows. I got excellent help from Berthold Horn, who suggested that this problem was caused by Windows because it re-encodes the font to the ANSI encoding vector. Berthold also suggested that I get the Font Utilities Package from Y&Y, and reprocess the PFB and PFM files such that the Font's "native" encoding vector is used instead of the Window's Default ANSI encoding vector. I got the above package (cost US$75) and reprocessed my files, and installed them under ATM2.0. The problem was solved as expected. For the interest of other users, I am summarizing below the steps I have gone through to solve this problem: a) Produced the PC compatible AFM and PFB files through Fontographer 3.2, using the Mac Encoding Vector. b) Ported the above files to PC, after running them through the Apple File Exchange utility on Mac. c) Ran the AFMtoPFM utility (with flags -v -d -s) on the AFM file to create the PFM (Printer Metric File). d) Ran the REENCODE utility (with flags -v -c=MAC ) on the PFB file to reprocess it to use the MAC Encoding Vector. The file MAC.VEC, used in the above process is supplied by Y&Y on its utilities diskette. This file contains the Mac Encoding Vector. e) Installed the PFM and PFB files thus processed under ATM2.0. Now I can display all the Chars in the Font on the screen and print them on a Postscript printer. SUCCESS!!!! Finally, it is a pleasant to task to thank Bethold K.P. Horn for his invaluable help and thank Y&Y for sending the Font Utilities Package promptly. For those who are interested, the Address of Y&Y is: Y&Y, 106 Indian Hill, Carlisle, MA 01741, USA (508) 371-3286 (Voice), and (508)371-2004 (Fax) Regards, K.Desikachary, AECL Research. Appendix To make this message comprehensive, below I list all the characters in Mac's Font that were 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
Technical Details
Message-ID:
<9SEP92.16350943@wl.aecl.ca>Path:
arc1-ca.pugleaf.net!sparky!uunet!usc!cs.utexas.edu!torn!cunews!nrcnet0!cu23.crl.aecl.ca!wl.aecl.ca!desikacharykShow Full Headers
Complete Article Headers
Newsgroups: comp.fonts Path: arc1-ca.pugleaf.net!sparky!uunet!usc!cs.utexas.edu!torn!cunews!nrcnet0!cu23.crl.aecl.ca!wl.aecl.ca!desikacharyk From: desikacharyk@wl.aecl.ca Subject: Why Windows Blocks Out Some Upper ASCII codes - Solution Message-ID: <9SEP92.16350943@wl.aecl.ca> Sender: news@cu23.crl.aecl.ca (USENET News System) Nntp-Posting-Host: wc4.wl.aecl.ca Organization: AECL RESEARCH Date: Wed, 9 Sep 1992 22:35:09 GMT Lines: 66