[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Running header
From: |
Benoit Bidoggia |
Subject: |
Re: Running header |
Date: |
Sat, 11 Jun 2005 12:26:46 +0200 |
> There was a problem behind the scenes getting the running header
> right above pages with floating figures. I haven't looked at
> it for a while, but from memory, if you have a sequence of n
> consectutive pages containing floating figures, then you need
> about n runs to get all the running headers right in that
> sequence.
I saw that and I did it, but I encountered the "too deeply nested"
error; I created a Makefile that delete .ld and .li files before compiling.
>The best thing to do is to reduce n by making sure
> that ordinary pages are interspersed among the figure pages.
I can't do it; I need them.
> I would also suggest doing some experiments with smaller
> documents, to get a feel for what is happening.
I did that: the problem is the same, but if the document is not so big
the n-times-compilation doesn't complain of errors.
>Things may
> work better if the figures are inside chapters rather than
> at the end of chapters.
Yes... but I make it work using PageFoot rather then TryAfterLine for
the images at the end of chapters. Running headers show the same
problem.
> If you can't work out what is
> happening, let me know and I will do some experiments myself
> and refresh my memory on this issue.
I will thank you very much; it would be very important for me :-)
> The error message you are getting points to line 26766 of
> a cross-reference database file. This seems to be a very
> large line number.
I noticed that the file grows more and more every time I compile
my book; this is why in my Makefile I distinguished between
make all (in which I remove ld and li files and then compile
many times) and make quick (in which I just compile once).
> I suggest you begin your investigation
> of this by first moving any database files you may have
> in the document directory to some other directory, then
> removing file lout.li and all cross-reference database
> files, which in Unix you do by the command
>
> rm lout.li *.ld
I didn't use database files yet; I'll do the references chapter later.
> Then run lout a few times, and check the size of all your
> cross-reference files after each run (Unix "wc *.ld").
> These might grow a bit but should quickly settle into
> a more or less steady state. I am not sure what might
> cause them to grow without bound, as yours seems to
> be doing, but perhaps one figure nested within another,
> or some unusual thing like that, might be the cause.
I will try to some statistics of ld files.
> Another way to approach this problem might be to
> try running just one chapter at a time, to see
> whether the problem is caused by any particular
> chapter; then running one of its sections at a
> time, to narrow it down by section, and so on.
When I encoutered the problem for the first time
I had wrote just one chapter; images are spread
all over the chapter, so I presume it would be the
same for a section or another.
> If you follow all these suggestions but are still
> stuck, the next step would be to tar up your whole
> document and put it on a web site where I can grab
> it. I will look through it for you and see what I
> can find. But please, only as a last resort; and
> make sure you are running a current version of Lout,
> since I can't conveniently test against an old one.
>
I would be very very grateful to you; but - if you are
busy on other tasks - I'll just turn RunningHeaders
into a constant text.
I'm using lout 3.29; do you think I should try with 3.30?
> Jeff Kingston
Thank you very much, anyway.
Benoit Bidoggia