Postscript and umlauts

[Phil Underwood]

On Sun, 07 May 2000, Roger Schuster wrote:
>Am Sam, 06 Mai 2000 schrieb Phil Underwood:
>
>Hi,=20
>
>> Ahem. Chasm does actually allow you to select the font for
>> Postscript printing, and also different sizes for station names and ot=
her
>> text. I'd be interested to hear if this works with your problem.
>
>Unfortunately not. The actual Chasm release compiled well on my box but
>it "segfaults" immediately after starting it. :-( The older release for
>Survex 0.91 worked but here I was too stupid to apply your patch to the
>original Survex sources.=20
>
>In the meantime I took a look into the Postscript output of printps and
>in the ASCII part of the file the special characters are correct! I
>edited it manually and changed the fonts in the preamble section.
>Indeed this changed the appearance of the document on screen but the
>umlauts are still missing so I think it is a problem witch the
>character encoding. Does in Postscript something exist like
>"charset=3Diso-8859-1" in HTML?=20
>

I've just had a look through the PostScript Language Reference (3rd
Ed.)(C)(TM) and  there is a short script that will change the encoding as
required. However, it uses Level 2 features, so may not be compatible wit=
h
older kit.

--CUT EXAMPLE--
/Helvetica findfont
dup length dict begin
{ 1 index /FID ne
{def}
{pop pop}
ifelse
} forall
/Encoding ISOLatin1Encoding def
currentdict
end
/Helvetica-ISOLatin1 exch definefont pop
--CUT--
Put this after the line %%Pages:

You need to replace the "Helvetica" strings with the name of the font
you're using, and also change the font description later in the file to=20

<your_font>-ISOLatin1 (ie what is shown on the last line.

This works on my system, and brings up umlauts etc successfully on GhostV=
iew
I can't test it on a real printer, because I don't have one:(

--=20
Phil Underwood <furbrain@furbrain.screaming.net>
Homepage: http://members.xoom.com/bighairyone/
"It's not what you've got, it's how you make it explode."