home *** CD-ROM | disk | FTP | other *** search
- This is a description of how to convert Macintosh type 1 postscript fonts
- so they can be used on the NeXT.
-
- The required programs are included.
- This may not be quite kosher, since I didn't write them, but they are PD.
- The compiled versions are included for those with no compilers. There
- were compiled under 2.1, but should work for older versions too.
- The programs need to be run from a shell, so you'll need to run
- a Terminal program or equivalent.
-
- I don't claim to be an expert, I can only provide an account of my
- experiences, and take no responsibility for problems you may encounter.
-
- Two files are necessary for the NeXT postscript font: the "printer" font,
- or just font file, and the AFM (Adobe Font Metric) file.
-
- The first task is to get the fonts from the Mac to the NeXT.
- The AFM file can be transferred in ASCII format, and comes over
- correctly. The printer font must come over in MacBinary format.
-
- First for the AFM file.
- If the transfer was in MacBinary, you need to convert to ASCII with
- the mcvert program. You type "mcvert -Uu file.AFM". This will
- give you a file called "file.AFM.text". You need to rename this file
- to "file.afm".
- If the transfer was in ASCII, you just need to rename the file from
- "file.AFM", to "file.afm".
-
- Check the file to make sure that the filename is the same as the font
- name in the AFM file! If it isn't, the Workspace won't be able to figure
- the fonts out. I spent a real frustrating hour and a half figuring this
- out the hard way.
-
- Now for the "printer" font.
- Rename the font from file to file.bin. This is an undocumented feature
- of mfrc which I don't remember how I found out. If you don't give the
- file a ".bin" suffix, the program doesn't correctly convert the last
- few lines of the file.
- Run the program: "mfrc file.bin".
- This will convert the type 1 postscript font from MacBinary to ASCII,
- the resultant file will be named "file".
-
- Again, check that the font name in the file is the same as the filename,
- and that the filenames for the font and AFM files match!
-
- Now, create a directory "{/NextLibrary,/LocalLibrary,~}/Fonts/file.font",
- depending on preference and permissions. Move or copy the font and AFM
- file into the directory.
-
- Next do a "buildafmdir directory", where "directory" is the one of
- "{/NextLibrary,/LocalLibrary,~}/Fonts", in which you created the font
- directory.
-
- You're done. The Workspace now knows about the font, and you can
- probably use it in any program.
-
- I say probably, because of my experience.
- I have purchased 2 type 1 postscript fonts for the Mac, withe the express
- intent of using them for the NeXT.
- One of them came with a mismatch between the file name and the font name
- as indicated in the file. This must work fine on Macs, but the NeXT
- doesn't respect that.
- The other font was a bar code font. This font is odd. It converted
- fine, but none of the NeXTStep programs that edit postscript can use
- the font (WriteNow, Draw, etc.). They all give the message
- <<Unusable Font>> in the Font panel. If I create a postscript file by
- hand, I can display the file with Preview. The font shows up as a bar
- code. I can also create the appropriate files for use with latex, and
- TeXView shows the bar codes correctly. Also, 2 of the 6 point sizes
- don't work. I've tried re-loading the fonts, but no good.
-
- So, good luck, I hope things go more smoothly than they have for me.
-
- Remember, I don't really know anything about how these fonts work,
- I just use the programs.
-
- Lothar Kaul
-
- kaul@bionette.cgrb.orst.edu
-