MTPRO2 with Y&Y tex - my results
Posted: Sun Mar 12, 2006 10:53 pm
Following in murray's footsteps, here are my results with Y&Y.
Here is my platform:
Y&Y TeX 2.2.3 2001 May 22
DVIWindo (32) Previewer 2.2.6
DVIPSONE 2.2.6 2001 Jun 23
Platform: Win2k SP4 on P4 with 512MB
I installed the fonts manually after unzipping. The stylefile, fontdefs
and tfms went into the right places, and the mtpro2 pfb files into c:\psfonts
where other tex .pfb's reside.
I then copied
\texmf\doc\fonts\mtpro2\Test_latex.tex
to a working directory and latex'd it with:
yandytex.exe +latex -v -L test_latex
y&y yielded usual tex verbosity with no warnings.
I then tried the y&y previewer DVIWindo which yielded
garbled results, presumably because win2k does not know
about the mathtime fonts. I've seen this behaviour in the
past for fonts which lack .pfm files. There were no .pfm's
in the MTPRO2 zip.
I then generated PS using:
dvipsone -l=letter Test_latex.dvi
which gave the following warnings:
** No /.notdef line* No /.notdef line* No /.notdef line* No /.notdef line* No /.
notdef line*** No /.notdef line* No /.notdef line* No /.notdef line* No /.notdef
line* No /.notdef line* No /.notdef line** No /.notdef line...
These warnings were generated in response to the mtpro2 fonts, but
I don't have enough knowledge to diagnose further. If I switch back to default fonts, the warnings disappear. I have also seen similar warnings
caused by other fonts when using a RIP, so I am sure the warnings are
caused by the fonts.
I then distilled the PS file with acrobat 5 distiller. No problem there.
I then compared my PDF to the PDF in the MTPRO2 zip file.
The files compared well. All characters present and accounted for.
HOWEVER : I am surprised by the small variations in character positions
between the two PDF files. I would expect tex/dvips to produce identical
positioning, but there are subtle shifts in some characters but not in
others. Fortunately for me, my version looks better :-)
Conclusion:
1) good result
2) need PFM files to make the previewer work correctly.
3) something in the fonts needs to be fixed to prevent the .notdef
warnings.
George.
Here is my platform:
Y&Y TeX 2.2.3 2001 May 22
DVIWindo (32) Previewer 2.2.6
DVIPSONE 2.2.6 2001 Jun 23
Platform: Win2k SP4 on P4 with 512MB
I installed the fonts manually after unzipping. The stylefile, fontdefs
and tfms went into the right places, and the mtpro2 pfb files into c:\psfonts
where other tex .pfb's reside.
I then copied
\texmf\doc\fonts\mtpro2\Test_latex.tex
to a working directory and latex'd it with:
yandytex.exe +latex -v -L test_latex
y&y yielded usual tex verbosity with no warnings.
I then tried the y&y previewer DVIWindo which yielded
garbled results, presumably because win2k does not know
about the mathtime fonts. I've seen this behaviour in the
past for fonts which lack .pfm files. There were no .pfm's
in the MTPRO2 zip.
I then generated PS using:
dvipsone -l=letter Test_latex.dvi
which gave the following warnings:
** No /.notdef line* No /.notdef line* No /.notdef line* No /.notdef line* No /.
notdef line*** No /.notdef line* No /.notdef line* No /.notdef line* No /.notdef
line* No /.notdef line* No /.notdef line** No /.notdef line...
These warnings were generated in response to the mtpro2 fonts, but
I don't have enough knowledge to diagnose further. If I switch back to default fonts, the warnings disappear. I have also seen similar warnings
caused by other fonts when using a RIP, so I am sure the warnings are
caused by the fonts.
I then distilled the PS file with acrobat 5 distiller. No problem there.
I then compared my PDF to the PDF in the MTPRO2 zip file.
The files compared well. All characters present and accounted for.
HOWEVER : I am surprised by the small variations in character positions
between the two PDF files. I would expect tex/dvips to produce identical
positioning, but there are subtle shifts in some characters but not in
others. Fortunately for me, my version looks better :-)
Conclusion:
1) good result
2) need PFM files to make the previewer work correctly.
3) something in the fonts needs to be fixed to prevent the .notdef
warnings.
George.