Article View: comp.fonts
Article #635Re: Why Windows 3.1 blocks out some of the upper ASCII codes?
From: Henry Churchyard
Date: Thu, 20 Aug 1992 02:29
Date: Thu, 20 Aug 1992 02:29
54 lines
2814 bytes
2814 bytes
In article <26724@life.ai.mit.edu>, bkph@wheat-chex.ai.mit.edu (Berthold K.P. Horn) writes:
>
> In article <18AUG92.15521044@wl.aecl.ca> desikacharyk@wl.aecl.ca writes:
>
>> I have a Font with all the upper ascii slots (codes from 128-255)
>> populated. It is a custom designed font that exists in Type 1 and Type 3
>> PS Formats.
[...]
>> When I installed
>> these fonts under Windows 3.0, I found that I cannot display/print 27 upper
>> ASCII characters.
>the default
> encoding vector differs from platform to platform. On the Mac it is
> `standard roman encoding', in MS Windows it is `Windows ANSI' [...]
> When you say you can't get a character in positions 208, 215, 221, 222, 240,
> 253, and 254, this is because Windows ANSI has Eth, multiple, Yacute, Thorn,
> eth, yacute, and thorn in those positions, and these characters do not occur
> in Mac `standard roman encoding'.
> DON'T think in terms of NUMBERS, but CHARACTERS (character names maybe).
If you're really not afraid to go to a low level, you could use the
T1UTILS1 package by I. Lee Hetherington to swap around the character
names inside type 1 font files which are in windows .PFB format or
unix .PFA format (but not Mac System extension format). Of course,
you would have to change the .AFM to match, and regenerate a new .PFM
from the .AFM (REFONT11 from ftp.cica.indiana.edu does this). Also,
when swapping around characternames inside the Type1, beware of
fouling up seac's (one of the numerical parameters to _seac_, the
command that generates composite characters, refers to the character
in the font which has the name which is associated with that number in
the StandardEncoding vector). A port of T1UTILS1.ZIP to Ms-Dos is
available on garbo.uwasa.fi, and on the garbo mirror in
wuarchive.wustl.edu. Sorry, can't help you with Truetype...
Archie search:
Host garbo.uwasa.fi
Location: /pc/fonts
FILE -rw-rw-r-- 81472 Jun 12 01:20 t1utils1.zip
Host plaza.aarnet.edu.au
Location: /micros/pc/garbo/pc/fonts
FILE -r--r--r-- 81472 Jun 12 01:20 t1utils1.zip
Host wuarchive.wustl.edu
Location: /mirrors4/garbo.uwasa.fi/fonts
FILE -rw-rw-r-- 81472 Jun 11 20:20 t1utils1.zip
--
--Henry Churchyard churchh@emx.cc.utexas.edu
Technical Details
Message-ID:
<78042@ut-emx.uucp>Path:
arc1-ca.pugleaf.net!sparky!uunet!ogicse!uwm.edu!cs.utexas.edu!ut-emx!churchhReferences:
<18AUG92.15521044@wl.aecl.ca> <26724@life.ai.mit.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!ogicse!uwm.edu!cs.utexas.edu!ut-emx!churchh From: churchh@ut-emx.uucp (Henry Churchyard) Newsgroups: comp.fonts Subject: Re: Why Windows 3.1 blocks out some of the upper ASCII codes? Summary: T1UTILS Message-ID: <78042@ut-emx.uucp> Date: 20 Aug 92 02:29:28 GMT Article-I.D.: ut-emx.78042 References: <18AUG92.15521044@wl.aecl.ca> <26724@life.ai.mit.edu> Organization: The University of Texas at Austin, Austin, Texas Lines: 54