I'm working on a document using algorithm2e. I'm moving it to
Elsevier's format, the elsart document class.
However, I get errors when loading algorithm2e:
********************************************************
Package `algorithm2e' Release 3.9 -- october 04 2005 --
- algorithm2...@lirmm.fr mailing list for announcement about
releases
- algorithm2e...@lirmm.fr mailing list for discussion about
package
subscribe by emailing sy...@lirmm.fr with 'subscribe <list>
<firstname name>'
- Author: Christophe Fiorio (fio...@lirmm.fr)
********************************************************
! Too many }'s.
l.1616 }
?
Is there a fix for this? A Google Groups search shows me that others
have experienced the error too, but no fix.
Thanks in advance,
wwwald
the algorithm2e package assumes it's running in one of the standard
classes, so you need to define things that are missing in elsart.
also, since elsart defines an algorithm environment already, you need
to undefine it before loading algorithm2e.
\makeatletter
\newif\if@restonecol
\makeatother
\let\algorithm\relax
\let\endalgorithm\relax
seems to do it for me, but then i don't have a document to play with.
--
Robin Fairbairns, Cambridge
> \makeatletter
> \newif\if@restonecol
> \makeatother
> \let\algorithm\relax
> \let\endalgorithm\relax
That did the trick perfectly. I'll inform the algorithm2e author
with this information, I think an [elsart] option would be a
suitable option.
I initially got things running by commenting out portions of
algorithm2e.sty and elsart.cls, but your solution is much more
elegant.
Thanks a lot,
wwwald
Andre Costa, Melbourne.
> rf...@cl.cam.ac.uk (Robin Fairbairns) wrote:
>
>> \makeatletter
>> \newif\if@restonecol
>> \makeatother
>> \let\algorithm\relax
>> \let\endalgorithm\relax
>
> That did the trick perfectly. I'll inform the algorithm2e author
> with this information, I think an [elsart] option would be a
> suitable option.
Just to let you guys know... I got a reply from the developer of
algorithm2e, mentioning that the problem is known and that his next
release will contain a fix for it.
Greets,
wwwald