Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| Lars> actally, I planned to ditch support for algorithm.sty, and use
| Lars> the float.sty directly instead. and the current float support is
| Lars> supposed to do this.
|
| Then this has to be done before 1.2.0.
I thought it already done.
| And are you sure we will never need floats which are not definable by
| float.sty?
If the floats are not supported by float.sty you have to ERT. I think
that is fair.
| Lars> | Also, the insettoc should enable algorithm when there is a
| Lars> list of | algorithms. This is easy.
|
| Lars> No, it is not... not with inseettoc. Algorithm is part of the
| Lars> dynamically created floats, thus the only special case floats we
| Lars> have is figure and table. (algorithm is special only in the
| Lars> sense that we have it added/enabled by default.)
|
| Currently, insettoc has explicit knowledge of possible lists,
| including algorithms. Of course, if you remove that, it will become
| trickier.
Actually it has not. Floats are now in general user definable, and
insettoc will not pick up the new float types.
So the current state is that insettoc just happens to work.
--
Lgb
