GhostPCL character chart?

[Brian K. White]

Did you get either of my long and detailed posts?
I also offered to look at a sample of your actual print job for pcl 
codes that affect character set & font selection, and try your capture 
on my system to see what it produces.

There there are a lot of possible pcl6 commandline options, but all we 
have used for 15 years is a pcl2pdf / pcl2fax script that ends up doing

-dQUIET -dSAFER -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=...

And the script doesn't do anything else like set any env variables to 
control pcl6.

So the choice of glyph is down to the pcl init and other codes earlier 
in the print job, and the installed fonts.

Fonts are complicated in gs/pcl6 so I won't even try to suggest what to 
look for that might be off, because there are only about a million 
things that affect each other in bizarre ways,
https://www.ghostscript.com/doc/9.52/Use.htm#Font_lookup
https://www.ghostscript.com/doc/9.52/Use.htm#Font_related_parameters

Maybe try one or more of these options to see what it's doing and maybe 
see how/why it selected a given font to render glyphs.
https://www.ghostscript.com/doc/9.52/Use.htm#Debugging

Maybe a quick & dirty manual override test that doesn't risk messing up 
the rest of your system might be to get a tar of a fonts directory from 
me or out of an rpm, and use -I or -sFONTPATH=dir  to force pcl6 to use 
it instead of it's normal font discovery process, just to see what you get.

First I'd just try some of the bare examples from my earlier emails that 
intentionally don't have any pcl codes in them, just to get a baseline, 
to see what happens when you know you can't possibly be perturbing it 
with any PJL or PCL commands, and then go from there based on what you 
get. Like, Do you get a blank space like I did, or do you get a glyph? 
You just said to Mark that you get a glyph, but you did not say you get 
a glyph from a bare echo command, and that makes all the difference.

-- 
bkw


On 6/29/20 12:33 AM, Jay R. Ashworth via Filepro-list wrote:
> ----- Original Message -----
>> From: "Fairlight via Filepro-list" <filepro-list at lists.celestial.com>
>>> Well, see, that's what I would have expected.  But I get SINGLE_DAGGER instead,
>>> whose name I could *not* remember the other day.
>>>
>>> But wait:
>>>
>>> CHR(255)?
>>>
>>> My code has
>>>
>>> CHR("255")
>>>
>>> It's been a long time, but CHR is one of the things that still takes a numeric
>>> literal?  Could that be my problem?
>>>
>>> This came off a machine running, maybe 4.5; I think the current machine's on
>>> 5.0.
>> Yeah, it was taking the first character of field 255 on you.
> I think I was unclear: the code came to me with quotes, and I was working
> with quotes.
>
> I tried taking them *off* and got a syntax error, likely because my fields
> don't go to 255.  :-)
>
> It sounds awfully like, though, I have a switch bad on pcl2pdf -- telling it
> to expect input in a codepage where 255 is a SINGLE_DAGGER, not NBSP or
> another NO-GLYPH...
>
> This has never worked on this install, nor, I think, on this version of pcl6.
>
> I believe we bought this from Steve Asman some years back, so...
>
> Cheers,
> -- jra


-- 
bkw