On Aug 17, 2010, at 8:59 PM, Russ Cox wrote:
>> Postscript is fine, I'll just ignore the proliferation
>> of PDF until I've got time to dig in and look more
>> deeply into eqn and the ghostscript sources.
>
> It's almost certainly that addpsfonts isn't adding
> the right ps fonts. I've never seen a problem with
> ps2pdf misbehaving when it has all the right fonts.
Thanks for the pointers Russ.
Symbols look great on Plan 9's page when you're looking at the .ps file. It's
the ps2pdf conversion that botches it as can also be seen by looking at this
small example:
.NH
Test
.PP
.EQ
p = sqrt{{P sub ac Z} over A}
.EN
All of the Lucida fonts are included in the .ps. I'm starting to think that
the mapping for S and S1 are the actual problems, but only when going through
the ps2pdf conversion. The radical and radicalex settings do get thrown off.
S is also the problem for the left [ and right ] creation:
11 /S f (\351) 2941 1172 w
(\357) 2941 1282 w
(\353) 2941 1392 w
See the following from a .ps file:
%
% A few arrays used to adjust reference points and character widths in some
% of the printer resident fonts. If square roots are too high try changing
% the lines describing /radical and /radicalex to,
%
% /radical [0 -75 550 0]
% /radicalex [-50 -75 500 0]
%
% Move braceleftbt a bit - default PostScript character is off a bit.
%
/Sdefs [
/bracketlefttp [201 500]
/bracketleftbt [201 500]
/bracketrighttp [-81 380]
/bracketrightbt [-83 380]
/braceleftbt [203 490]
/bracketrightex [220 -125 500 0]
/radical [0 0 550 0]
/radicalex [-50 0 500 0]
/parenleftex [-20 -170 0 0]
/integral [100 -50 500 0]
/infinity [10 -75 730 0]
] def
/S1defs [
/underscore [0 80 500 0]
/endash [7 90 650 0]
] def
With a little experimentation, it will be possible to add an additional
preprocessor to scrub the .ps file before converting to pdf.
-jas
