Eckart Begemann <[EMAIL PROTECTED]>
wrote:
>I encountered a serious problem ... :-(
>A simple LaTeX-code not that long (some 13 pages I think)
>makes LaTeX go out of capacity, when
>musixlyr is trying to allocate a newdimen
>(\setlyrics{}{}).
>I cannot quite imagine this, I used to have much bigger source files,
>with a lot more musics. Does MusixLyr swallow a lot of memory?
>Even hugelatex (MiKTeX) crashes at the same spot.
>
>Any similar experiences?
>
Eckart:
I am not sure what your problem is. However, TeX can report "cpapcity
exceeded" when there are simple mistakes and typographical errors in some of
the code one enters. One "likely suspect" is an argument that has a missing
end brace }. (TeX tries to absorb all the intervening text to the end of
the file, and treat it as one argument of a macro, for example.)
You can easily find what is accepted as it normally should be, versus what
may appear to be wrong, by checking the log file (sometimes), or by adding a
simple line or two to your input file....
\tracingmacros=1% Add this line anywhere, and all macros after it will be
shown, including the arguments they are accepting. (The log file will be
quite large!)
\tracingall\tracingonline=0% The \tracingall turns on all the available
tracing capabilities, including, the \tracingmacros capability, and it is
recommended to follow it immediately by \tracingonline=0 so you don't have
to watch it all on the screen. However, the log file will be immense.
Again, you might get a clue as to what is going wrong.
Good luck.
Joel Hunsberger
[EMAIL PROTECTED]
