Font bug?

Article View: comp.sys.next.programmer

Article #1920

Back to comp.sys.next.programmer Previous Next

#1920

From: Sean Lamont
Date: Mon, 21 Dec 1992 18:30

21 lines
1521 bytes

In "NeXT-ifying" some type 1 fonts I made the following discovery:  A number
of fonts did not respond to the "lighter", "heavier" buttons, although the
weights were correct in the font file.

I narrowed it down to the following fact: If the font used a standard
encoding vector (Encoding AdobeStandardEncoding) , the lighter/heavier
worked fine on the font.  However, if it used a custom encoding vector
(ie Encoding AppleStandard, with an array in the font file to define
what it was [array 256 def, etc]) it would not work.  For any files
that exhibited this problem I modified the encoding vector back to
adobe standard encoding and it worked fine.

Have other people experienced this problem?  Is it a postscript
weirdness or a bug?


-- 
Sean T. Lamont                           |   "Don't oppress me, It's
zeno@genetics.washington.edu             |    'computer of color!' "
lamont@abstractsoft.com                  |_______________________________
Abstract Software

Technical Details

Message-ID: <1992Dec21.183057.7007@u.washington.edu>

Path:

arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!usenet.coe.montana.edu!news.u.washington.edu!phylo.genetics.washington.edu!zeno

Show Full Headers

Complete Article Headers

Newsgroups: comp.sys.next.programmer
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!usenet.coe.montana.edu!news.u.washington.edu!phylo.genetics.washington.edu!zeno
From: zeno@phylo.genetics.washington.edu (Sean Lamont)
Subject: Font bug?
Message-ID: <1992Dec21.183057.7007@u.washington.edu>
Sender: news@u.washington.edu (USENET News System)
Organization: University of Washington, Seattle
Date: Mon, 21 Dec 1992 18:30:57 GMT
Lines: 21