#SL PFB files, Post
2 messages in this thread
When I run post (v. 1.86; post.library 1.7), I set up the init.ps file to look
through my font directories for PostScript Type 1 fonts. I include SoftLogik's
PFB files that came with ArtExpression, because these (in theory) should give
me the 35 fonts in Post that are assumed to be built into a PostScript printer.
However, when running a file that calls (for instance) Times-Roman, Post gives
this error message:
post: error: typecheck, command –begin–
If I preload the SoftLogik PFB file into Post, it will run and render
Times-Roman. If Post searches and loads the font because it was called in the
PostScript file, it creates that error.
This is not a problem with the file names. I have renamed all my PFB files to
FontName.PFB and init.ps knows about the .PFB extension. SnoopDOS reveals that
the files are being found and loaded. Fonts work correctly in all other cases.
There is something funny about the SoftLogik PFB files.
Well, according to our programmers (who used Post to experiment with PFBs), the
fonts will work fine as long as you pre-load tehm with Post's Load font menu.
There are indeed problems in "batch mode" when post looks in the font
directories specified in the init.ps file.
There are two quick fixes: 1. Pre-load all of the fonts used in the document,
or 2. Replace the first character of the following three lines in the PFB file
with a percent character (using a binary proof text editor like CED or
TTX):
example: FontDirectory/DemoFont known {/DemoFont findfont…
/UniqueID get… {save true}…
change to: %ontdirectory/Demofont known {/DemoFont findfont… %UniqueID
get… %save true}…
Make sure the the number of bytes of the PFB file doesn't change.
Mark @ Soft-Logik Publishing