home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!usc!sol.ctr.columbia.edu!destroyer!cs.ubc.ca!uw-beaver!news.u.washington.edu!ns1.nodak.edu!usenet
- From: enders@bolshoi.cc.misu.NoDak.edu (Todd Enders)
- Newsgroups: comp.sys.next.misc
- Subject: Re: Converting Mac PS fonts to NeXT?
- Message-ID: <BzKr9L.DzI@ns1.nodak.edu>
- Date: 20 Dec 92 20:22:33 GMT
- References: <1992Dec19.192946.3346@metrosoft.com>
- Sender: usenet@ns1.nodak.edu (News login)
- Reply-To: enders@bolshoi.uucp
- Organization: North Dakota Higher Education Computing Network
- Lines: 24
- Nntp-Posting-Host: bolshoi.cc.misu.nodak.edu
-
- Gordon Van Huizen writes
- > Meta Pro provides conversion to and from many font file
- > formats and will generate AFM files. It doesn't create
- > ..FONT wrappers and since it runs on a Mac, it can't really
- > help with the installation - plus you need a Mac. I haven't
- > tried it under Executor. If you use Meta Pro for any volume
- > of fonts, be prepared to do a lot of work by hand to get them
- > installed on the NeXT.
- >
- Meta Pro seems to have a bug building AFM files when converting
- from Mac True Type to NeXT Type 1 fonts. The fault seems to be in the
- space character which *always* gets a width of 122 in the AFM file (and
- seemingly in the PS font file as well). Now, this is *way* too narrow
- for a space, and makes using a font difficult, as everything is run
- together. I've tried to tweak the AFM files by hand, but it doesn't
- seem to effect the character, but it *does* effect the cursor position
- on the screen.
-
- The bug is indeed unfortunate, since there are several True Type Mac
- fonts in PD that beg conversion
-
- Todd enders@bolshoi.uucp
- uunet!bolshoi!enders
- enders@bolshoi.cc.misu.nodak.edu
-