YAP problems with mtpro2 (MathTime fonts)

[iwerning]

Hi,

I just bought MathTime Pro II from PC-Tex to use with my MikTex 2.5 / Winedt.

I installed the fonts as described by PCTex (http://www.pctex.com/kb/56.html)
[except I did things the way MikTex 2.5 wants them: I ran initexmf --edit-config-file updmap to add a line to the updmap)

Everything works in Yap with the dvi in pkfonts render mode or if I compile the postscript with dvips or then the pdf with ps2pdf.

But I have terrible problems with the dvips render mode in Yap. It just goes completely crazy and I get error messages that just don't stop poping (I have to shut down YAP). The errors only seem to appear with math.

1. The first kind of error I get is:
   invalid vector<T> subscript
   (but this occurs even if the document has no math subscripts (so I'm not sure what this refers to).

2. I also get "unknown exception"

3. The one that really hangs the thing is "Invalid DVI file", it seems to be appearing continuosly. If I try to close the error message hitting OK or closing the window it is still there (i.e. I think it is reappearing every instant)

Note: my YAP and MikTex were working fine before the installation, in pkfont and dvips rendering mode, and seem to be working fine without loading the mtpro2 package.

Below is a minimalist sample document that produces the errors.

Any help would be HUGELY APPRECIATED.

Thanks -Ivan

% this is the most minimalist example
\documentclass{article}
% removing any of these two packages seems to fix the problem
% but T1 is the recommended encoding by mtpro2!
\usepackage[T1]{fontenc}
\usepackage{mtpro2}

\begin{document}
% on this first page you may not get an error message...

Hello. Just some text here.
\newpage
% ... on this second one you will get an error

Now some math:
\begin{equation}
2+3
\end{equation}
\end{document}

[iwerning]

I haven't found any solution. Still the same problem. Perhaps things will work in future updates of Yap given that Ulrike documented the problem and other related ones.

For now, I resigned myself to using YAP in the PK rendering mode.

-Ivan

[iwerning]

Actually, one correction: in the minimalist file removing the T1 encoding line does not help. I thought it did, but I ran it again and it does not! Thus, ignore the line about encoding. That is, I get the same error with

% this is even more minimalist...
\documentclass{article}
\usepackage{mtpro2}
\begin{document}
% on this first page you may not get an error message...

Hello. Just some text here.
\newpage
% ... on this second one you will get an error

Now some math:
\begin{equation}
2+3
\end{equation}
\end{document}

[mauvia]

I just installed mtpro2 and I have exactly the same problem as discussed here. Is there anything new about this topic? Anyone found a solution or the real cause? Is there something I could do to investigate further?

Thanks,
Mau

[shimer]

Hi Ivan,
I can replicate this problem using your "even more minimalist" file. I am running YAP 2.5.2466. The only difference is that I can get out of the "Invalid DVI file" errors by hitting "OK" several times.
-Rob

[iwerning]

So now it is two of us with the problem.

Anyone out there know the solution?

-Ivan

[U_Fischer]

There has been a similar bug report in connection with augie font and the calligra font. The main problem is that debugview doesn't show an error and that the error isn't reproducible on each system.

I made some test with debugview and allmost all trace options turned on and had the impression that the problem is connected to the tfm. A correct document load the tfm, get some values and then continues with "getting page":

[1740] core: opening file [...]\cmr10.tfm (2 0x1 1 0)
[1740] libdvi: header size: 18
[1740] libdvi: smallest character code: 0
[1740] libdvi: largest character code: 127
[1740] libdvi: width table size: 36
[1740] libdvi: height table size: 16
[1740] libdvi: depth table size: 10
[1740] libdvi: italic correction table size: 5
[1740] libdvi: lig/kern table size: 88
[1740] libdvi: kern table size: 10
[1740] libdvi: extensible character table size: 0
[1740] libdvi: font parameter size: 7
[1740] libdvi: checkSum: 011374260171
[1740] libdvi: designSize: 10485760
[1740] libdvi: getting page #0
[1740] core: accessing file D:\UlleDoku\test\test.dvi: OK

A faulty document uninitialize the core library:

[1756] core: opening file "[...]\callig15.tfm" (2 0x1 1 0)
[1756] libdvi: header size: 18
[1756] libdvi: smallest character code: 0
[1756] libdvi: largest character code: 255
[1756] libdvi: width table size: 131
[1756] libdvi: height table size: 16
[1756] libdvi: depth table size: 16
[1756] libdvi: italic correction table size: 1
[1756] libdvi: lig/kern table size: 7
[1756] libdvi: kern table size: 0
[1756] libdvi: extensible character table size: 0
[1756] libdvi: font parameter size: 6
[1756] libdvi: checkSum: 0476512246
[1756] libdvi: designSize: 15728640
[1756] core: uninitializing core library
[1756] core: unloading fndb 011F5CF8

In pk-rendering mode, debugview doesn't show any call to the tfm, YAP seems not to use it, so this would explain why only dvips render mode is affected.

Also the error did go away if I let YAP used the tfm of another font by renaming it to callig15.tfm.

I will put this in the original bug report. Perhaps Christian can then figure out what's happening.

Ulrike Fischer

[iwerning]

Ulrike:
Interesting. But are the error messages similar to the ones I get? (I didn't run a debugger to trace errors, so I can't compare that).
-Ivan

[iwerning]

Ulrike:
Sorry it seems that you say that with this other font problem there are no error messages. In my case I get 3 error messages as described in my first post.
-Ivan

[U_Fischer]

Yes I also see errors. I get a "miktex report" with the invalid-vector message, and in the copied info there is also the unknown exception.

But the debugview log doesn't show an error message.

You could search the bug tracker for the bug report [ 1539138 ] MiKTeX 2.5: YAP problem to see more.

Ulrike Fischer