Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.mixmin.net!news2.arglkargh.de!news.visyn.net!visyn.net!not-for-mail
From: "Mark T. B. Carroll" <mtbc@bcs.org>
Newsgroups: comp.lang.postscript
Subject: Re: PostScript, Fortran, GhostScript: need help pinpointing a problem
Date: Sun, 14 Aug 2011 08:24:02 -0400
Organization: none
Lines: 33
Message-ID: <87k4agji59.fsf@ixod.org>
References: <j286e5$j1r$1@online.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: hoshi.visyn.net uORo3t86pskiFRHt/8DujpFu/3RUE34fk6H22zFS2vo=
X-Complaints-To: abuse@open-news-network.org
NNTP-Posting-Date: Sun, 14 Aug 2011 12:24:02 +0000 (UTC)
X-User-ID: coqAFjijLbk554svwFmZ5T6H02JxiPJdV0V2UTTjiEE=
Cancel-Lock: sha1:JgcauTk69fYa0YVogfWcAG9jD3c=
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
Xref: x330-a1.tempe.blueboxinc.net comp.lang.postscript:293

helbig@astro.multiCLOTHESvax.de (Phillip Helbig---undress to reply)
writes:

> With a new version of GhostScript, I see an error message which points 
> to the problem.  However, I am still not clear what the actual source of 
> the problem is and how to correct it.

Hmm, at a glance, I'm not sure either.

> /reencode                                                                       
> { dup FontDirectory exch known                                                  
>   { findfont }                                                                  
>   { dup nbuff cvs dup length 1 sub 0 exch getinterval                           
>     findfont begin                                                              
>     currentdict dup length dict begin                                           
>         { 1 index /FID ne {def} {pop pop} ifelse } forall                       
>         /FontName exch def                                                      
>         /Encoding lpemuEncoding def                                             
>     currentdict dup end end                                                     
>     /FontName get exch definefont                                               
>   } ifelse                                                                      
> } bdef                                                                          

This part is significant. The "l" gets chopped off "Symbol" basically
through this "length 1 sub" I think. I've no idea why. But even then
there's the question of the definition of l and W in the Symbol font.
Maybe somebody who knows more about font encodings and StandardEncoding
and whatever can tell us more.

In the worst case, it's possible that one of us can point you to a tool
that does what you need without such weirdness. (-:

Mark