home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.programmer
- Path: sparky!uunet!paladin.american.edu!darwin.sura.net!sgiblab!ampex!decwrl!adobe!usenet
- From: byer@adobe.com (Scott Byer)
- Subject: Re: Font bug?
- Message-ID: <1992Dec22.004215.24848@adobe.com>
- Sender: usenet@adobe.com (USENET NEWS)
- Reply-To: byer@adobe.com (Scott Byer)
- Organization: Adobe Systems Incorporated
- References: <1992Dec21.183057.7007@u.washington.edu>
- Date: Tue, 22 Dec 1992 00:42:15 GMT
- Lines: 28
-
- 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.
- ---------------------------------------------------------------------
-