[Q] LaTeX2e: \include cannot be nested?
HJan Chang
While trying to convince my colleagues that LaTeX2e is 99.9% backward
compatible with LaTeX 2.09, one of our old latex file failed under my
newly installed LateX2e because of the nested \include files.
Is it true that \include *really* cannot be nested or have I missed
something during the installation of latex2e?
Any help would be greatly appreciated.
--h.j. hj...@netcom.com
David Kastrup
>While trying to convince my colleagues that LaTeX2e is 99.9% backward
>compatible with LaTeX 2.09, one of our old latex file failed under my
>newly installed LateX2e because of the nested \include files.
>Is it true that \include *really* cannot be nested or have I missed
>something during the installation of latex2e?
Nested includes really never have worked properly. Try using
\input if you want to nest files inside of \include d files.
--
David Kastrup, Goethestr. 20, D-52064 Aachen Tel: +49-241-72419
Email: d...@pool.informatik.rwth-aachen.de Fax: +49-241-79502
Robin Fairbairns
>While trying to convince my colleagues that LaTeX2e is 99.9% backward
>compatible with LaTeX 2.09, one of our old latex file failed under my
>newly installed LateX2e because of the nested \include files.
>
>Is it true that \include *really* cannot be nested or have I missed
>something during the installation of latex2e?
There's definite code that prevents it working. I presume the
intention is to avoid problems with .aux files, but there's nothing in
the (publicly accessible) bugs database about it...
Try submitting a bug report yourself -- at least that'll get the
reasoning out in the open...
On the general point, 2e is very largely backwards compatible, but
there are problems in the areas of --
+ things that always were broken in 2.09, and have been mended so
that people who relied on broken behaviour are trapped
+ things that used internal, undocumented, LaTeX 2.09 font commands
+ small implementations (since 2e is a good bit larger)
Also, of course, 2e is slower that 2.09 (mostly because of all the
extra checking it does) and it's *much* slower in compatibility mode.
--
Robin (Campaign for Real Radio 3) Fairbairns r...@cl.cam.ac.uk
U of Cambridge Computer Lab, Pembroke St, Cambridge CB2 3QG, UK
<a href="http://www.cl.cam.ac.uk/users/rf/robin.html">Private page</a>
Matthew Swift
The problem with .aux files is sufficient to prohibit nested \includes; I am at
work on code to overcome this.
The original problem which led me to it was wanting a version of \include
without a \clearpage. That's easy enough, but you run into trouble with the
.aux files and TeX's \write mechanism whose action is delayed until the page is
shipped out in order, e.g., to allow accurate cross references to page numbers.
The code limitation to overcome is that only one output stream is dedicated in
the kernel to be the \auxout. I am going to try to change it to a wheel of,
say, 4 streams. Since I have not actually done this yet, I'm not sure if other
problems might arise.
Matt