Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!dcl-cs!gdt!ccsdc
From: ccsdc@gdt.bath.ac.uk (Dave Cunningham)
Newsgroups: comp.lang.postscript
Subject: Re: MAC-PC fonts
Message-ID: <1989Dec6.110609.11854@gdt.bath.ac.uk>
Date: 6 Dec 89 11:06:09 GMT
References: <6987@uqvax.decnet.uq.oz>
Reply-To: ccsdc@gdt.bath.ac.uk (Dave Cunningham)
Organization: University of Bath, England
Lines: 35

In article <6987@uqvax.decnet.uq.oz> CCMIGUEL@uqvax.decnet.uq.oz writes:
>
>Another little problem. I cannot get single opening and closing quotes from
>a NTX or a SilentWriter using MS-DOS MSWord V5.0 although I *can* get them
>on the old LaserWriter Plus. Microsoft has given up on offering a solution
>(they even sent me a new *flaky* driver that works even worse). Does anybody
>know why this may be so. What is different between NTX and Plus that caused the
>damnedly useful single quotes to be placed somewhere else (Ventura has no such
>problem and neither does MSWord on the Mac. 
>
>
You problem is almost certainly due to a change Microsoft introduced at
WORD v5.0. In the POSTSCRP.INI file for v5.0 the characters 39 (single quote)
and 96 (grave) are mapped on to the PostScript characters 'quotesingle'
and 'grave' - this was not true in v4. Proper opening and closing quotes
can be re-instated by editing one line (line 211 in my copy):

change
	0 [ 39/quotesingle 96/grave
to
	0 [

The ASCII quote and grave characters are still available in the extended
character set. There are many other changes to character mapping between
v4 and v5 so it is worth running 'character_test.mac' to get a definitive
list.

While on the subject of WORD 5 and PostScript, has anyone successfully
built a PS driver at a resolution other than 300 dpi?
We have a Compugraphic 9400PS typesetter (1200 or 2400 dpi) and the standard
driver produces poor grays because of an explicit call to 'setscreen'.
I have removed the call to 'setscreen' on my copy - this seems to make no
difference on files sent to an Apple LaserWriter but gives much improved
results on the typesetter. Does anyone know if the 'setscreen' call
does anything useful?