Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.postscript > #295
| From | helbig@astro.multiCLOTHESvax.de (Phillip Helbig---undress to reply) |
|---|---|
| Newsgroups | comp.lang.postscript |
| Subject | Re: PostScript, Fortran, GhostScript: need help pinpointing a problem |
| Date | 2011-08-14 15:02 +0000 |
| Organization | Multivax C&R |
| Message-ID | <j28o33$1cj$1@online.de> (permalink) |
| References | <j286e5$j1r$1@online.de> <4097c3f8-0d56-4a4d-82cc-d08ebc469840@a31g2000vbt.googlegroups.com> |
In article
<4097c3f8-0d56-4a4d-82cc-d08ebc469840@a31g2000vbt.googlegroups.com>,
SaGS <sags5495@gmail.com> writes:
> In short, it's an assumption made by the "reencode" procedure defined
> by the PostScript code that may have been true for languagelevel 1
> PostScript, but not necessarily for languagelevel 2 or 3.
OK. In general, does this mean that there is no guaranteed backward
compatibility?
> More precisely, the code assumes that if a font name is not already
> registered in FontDirectory, then that font does not really exist.
> Then it uses non-existent font names to force reencoding of PostScript
> fonts; these names are formed from the "base" PostScript font names
> with an extra character ("R") at the end, like "Helvetica-
> BoldObliqueR".
>
> Ghostscript starts with an empty FontDirectory, and uses the resource
> machinery (introduced in languagelevel 2) to find and load fonts. The
> "reencode" procedure does not find the name "Symbol" in FontDirectory,
> and assumes it has to be the name of a reencoded version of
> "Symbo" (the name it received less last character). So, the error you
> see.
OK, now I understand where it's coming from. Since it's a GhostScript
thing, then it is clear why the file prints OK.
> Workaround: pass "-c /Symbol findfont pop -f" on Ghostscript's command
> line, before the file you want to process. This forces loading the
> Symbol font, so it will be present in the FontDirectory.
I can't get this to work. (I mainly used GV but am now testing a new
version of GhostScript.)
What, exactly, should I type at the command line (that of the OS or of
GS), when should I hit <RETURN>, should I quote the command etc. I've
tried all permutations.
Is there an easy way to edit the file (preferably inserting something
only at the beginning of the file) to avoid this error?
Another question: Why is the Symbol font not found in the first place?
I thought it was rather standard.
Back to comp.lang.postscript | Previous | Next — Previous in thread | Next in thread | Find similar
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