Font bug?

Thread View: comp.sys.next.programmer

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Sean Lamont Mon, 21 Dec 1992 18:30

#1920

Author: 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

Re: Font bug?

#1927

Author: Scott Byer
Date: Tue, 22 Dec 1992 00:42

28 lines
1726 bytes

Sean Lamont writes

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

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

Well...

It sounds like the AppKit is trying to determine if the font is a
pi font or a roman character font so that it can turn off the
Heavier/Lighter buttons for pi fonts (because, in general, pi fonts
don't come in families with varied weights, so those buttons don't
make sense).  There is no sure way to tell, but the way most used
is to check if the encoding is defined as StandardEncoding.

I would be inclined to say that it's a problem with the fonts, that
if they are standard roman-based fonts that they should be using
StandardEncoding as their encoding vector.

--
Scott Byer                             NeXTMail: byer@mv.us.adobe.com
Adobe Systems Incorporated               These are *my* opinions, and  
1585 Charleston Road, P.O. Box 7900        do not necessarily reflect
Mountain View, CA 94039-7900             the opinions of my employer.
---------------------------------------------------------------------

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads