Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.postscript > #298

Re: PostScript, Fortran, GhostScript: need help pinpointing a problem

From Helge Blischke <h.blischke@acm.org>
Newsgroups comp.lang.postscript
Subject Re: PostScript, Fortran, GhostScript: need help pinpointing a problem
Followup-To comp.lang.postscript
Date 2011-08-14 19:19 +0200
Message-ID <9aqed7FaurU1@mid.individual.net> (permalink)
References <j286e5$j1r$1@online.de> <4097c3f8-0d56-4a4d-82cc-d08ebc469840@a31g2000vbt.googlegroups.com> <j28o33$1cj$1@online.de> <9aqc25Fon7U1@mid.individual.net> <j28vj7$7v4$1@online.de>

Followups directed to: comp.lang.postscript

Show all headers | View raw


Phillip Helbig---undress to reply wrote:

> In article <9aqc25Fon7U1@mid.individual.net>, Helge Blischke
> <h.blischke@acm.org> writes:
> 
>> > Is there an easy way to edit the file (preferably inserting something
>> > only at the beginning of the file) to avoid this error?
>> You may insert the line
>> /Symbol findfont pop
>> just after the line
>> lpemuldict begin
>> to preload the Symbol font into the FontDirectory.
> 
> That worked; thanks!  I could modify the Fortran program to always put
> in this line (presumably it wouldn't hurt).
> 
>> > Another question: Why is the Symbol font not found in the first place?
>> > I thought it was rather standard.
>> as SaGS states above, Ghostscript starts with an empty FontDirectory
>> dictioary, whereas most PostScript printers (still) preload the fonts
>> embedded in the printer (the so called ROM fonts) during a (vendor
>> specific) startup procedure.
> 
> OK.  However, the 12 other fonts the Fortran program uses (Roman,
> Sans-Serif and Typewriter and each bold/non-bold italic/non-italic) all
> display correctly in GhostScript; why is it only the Symbol font which
> has the problem?
because of how the reencode procedure your fortran program spits out is 
defined. Roughly said, it works as follows:
1) if the font is already in FontDirectory, use it as it is.
2) otherwise, chop off the last letter from the requested font name, 
retrieve the font having the truncated name, reencode it and save it under 
the original name in FontDorectory (so it won't be reencoded a second time).
Thus, e.g. the font
/Helvetica-BoldOblique
will be saved as 
/Helvetica-BoldObliqueR
(R for "reencoded") in the interpreter's FontDirectory.

Helge

Back to comp.lang.postscript | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

PostScript, Fortran, GhostScript: need help pinpointing a problem helbig@astro.multiCLOTHESvax.de (Phillip Helbig---undress to reply) - 2011-08-14 10:01 +0000
  Re: PostScript, Fortran, GhostScript: need help pinpointing a problem "Mark T. B. Carroll" <mtbc@bcs.org> - 2011-08-14 08:24 -0400
  Re: PostScript, Fortran, GhostScript: need help pinpointing a problem SaGS <sags5495@gmail.com> - 2011-08-14 05:12 -0700
    Re: PostScript, Fortran, GhostScript: need help pinpointing a problem helbig@astro.multiCLOTHESvax.de (Phillip Helbig---undress to reply) - 2011-08-14 15:02 +0000
      Re: PostScript, Fortran, GhostScript: need help pinpointing a problem Helge Blischke <h.blischke@acm.org> - 2011-08-14 18:39 +0200
        Re: PostScript, Fortran, GhostScript: need help pinpointing a problem helbig@astro.multiCLOTHESvax.de (Phillip Helbig---undress to reply) - 2011-08-14 17:11 +0000
          Re: PostScript, Fortran, GhostScript: need help pinpointing a problem Helge Blischke <h.blischke@acm.org> - 2011-08-14 19:19 +0200
  Re: PostScript, Fortran, GhostScript: need help pinpointing a problem ken <ken@spamcop.net> - 2011-08-14 20:09 +0100

csiph-web