Hi,
Debugging shows that this bug is in amslatex, and more specifically,
in the files amsmath.sty and amsgen.sty, where they mess around redefining
the \@ifnextchar command (i don't know why they want to do that).
if you insert this into the document (e.g. just after the \begin{document}):
\makeatletter
\let\new@ifnextchar\@ifnextchar
\let\new@ifnch\@ifnch
\makeatother
then error will disappear...
Please report this to LaTeX bug tracking system (as an AMSLaTeX bug),
so they can fix the bug.
Best,
v.
On Mon, 04 Nov 2002 10:59:35 +0100
Harald Hanche-Olsen <[EMAIL PROTECTED]> wrote:
> + Erik Frisk <[EMAIL PROTECTED]>:
>
> | below is a document that fails with teTeX-beta 20020530 (unfortunately I
> | have no possibility to try the latest beta). There seem to be some
> | problems with \mathfrak and AMSfonts since the text
> | [2002/01/19v2.2gAMSfontdefinitions] appears in the middle of the matrix.
>
> That seems to be a genuine AMSfonts bug, and as such has nothing to do
> with teTeX. FWIW, I see the same problem with teTeX beta-20021029.
>
> The first occurence of \mathfrak triggers the loading of a font
> description file. This happens within a matrix environment, and
> that environment (like so many AMSmath environments) is quite
> complex. I guess it reads its contents and tries to expand macros
> along the way, and that plays havoc with the file inclusion.
>
> A workaround is to use \mathfrak before you get to the matrix
> environment. For example, use it in a throwaway box:
>
> \setbox0\hbox{$\mathfrak{a}$}
>
> (before \begin{document} is fine). Then the problem goes away.
>
> But you might wish to report this to the AMSfonts maintainers as well.
>
> - Harald
