Even if makebm is an internal macro, renaming the in-document
definition to, say, \differentname doesn't change a thing. I still get
the same grouping level error, with:
\differentname #1$->\bm {#1}
$
[EMAIL PROTECTED] ... {\hbox {#1$\displaystyle [EMAIL PROTECTED] #2$
}}{\hbox {#1$\textstyle \m...
[EMAIL PROTECTED]@@p ...fmmode [EMAIL PROTECTED] #1{#2}{#2}{#2}{#2}
\else \bfseries #1#2\fi
[EMAIL PROTECTED] ...ound \z@ [EMAIL PROTECTED]@@p \boldmath {{a}}
}
\differentname #1$->\bm {#1}
$
On Sat, May 31, 2008 at 11:06 AM, Frank Küster <[EMAIL PROTECTED]> wrote:
>
>
> --
> Frank Küster
> Debian Developer (teTeX/TeXLive)
>
>
> ---------- Forwarded message ----------
> From: Taco Hoekwater <[EMAIL PROTECTED]>
> To: Frank Küster <[EMAIL PROTECTED]>
> Date: Wed, 28 May 2008 23:37:49 +0200
> Subject: Re: [NTG-pdftex] Bug#458059:
> Frank Küster wrote:
>>
>> Hm, can you give me a short hint
>>
>> - what tells you that it's a macro error, and
>
> That snippet was the actual error context so you have to read it
> upside down, and there is a bit of information missing. The
> general overview is:
>
> \makebm expands into something containing
> \bm that expands into something containing
> [EMAIL PROTECTED] that expands into something containing
> [EMAIL PROTECTED]@@p that expands into something containing
> [EMAIL PROTECTED] that expands into something containing
> \makebm ... (full circle)
>
>> - where the error probably is?
>
> It seems \makebm is an internal macro of the bm package, and the
> document-level definition of \makebm to redefines that macro.
>
> Perhaps this is the result of a recent update of the bm package.
> At least that would explain why the documentation may have been
> run with errors in the past.
>
> There is a simple solution: use a different macro name for the
> in-document definition.
>
> Best wishes,
> Taco
>
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
