Re: PDF generates a TOC, PS does Not with Report

[Valeriy E. Ushakov]

On Thu, Sep 30, 1999 at 08:16:14PM +0400, Greg Gallagher wrote:

>    I've gone through the lists looking to see if this is a known bug or
> not, and didn't find anything so I have to bug you guys :)  I'm using
> lout versions 3.17 and 3.16, both yield the same problem:  I wrote a
> report and the TOC is generated in the PDF but not at ALL in the
> postscript.  I thought at first that it was just a ghostview problem,
> but sure enough the ps document is 25 pages, and the PDF is 26.  And I
> looked through the postscript itself and, sure enough, nada ... no table
> of contents.

In the makefile you've sent me, you run lout twice to obtain PS and
then you run lout the third time to obtain PDF.  But your document
requires _3_ runs to resolve properly.  That's why you see no TOC in
PS, but see it in PDF, which you generate as the third run, when
everything is in place.  Run lout 3 times and you'll see the TOC in
PS.

Three runs are needed because on the first run the @ContentsPlace is
flushed and contents entries have no place to attach to.  You will see
the message about no @ContentsPlace preceding the
@ContentsPlace&&preceding.

On the second run lout knows that there're galleys targeting the
@ContentsPlace, but, for some reason that I can explain right now, the
@ContentsPlace receives a different internal number and so contents
entry still can't find their target.

On the third run everything is settled and TOC manifests in the
output.

The unified diff between the symbol section of lout.li files from the
first and the second run follows.  Note that on the first run
@ContentsPlace was assigned internal number 21, but on the second it's
assigned 19, while contents entries in the database (written out
during the first run) are looking for the old 21.

--- symbols.1   Fri Oct  1 02:54:15 1999
+++ symbols.2   Fri Oct  1 02:54:37 1999
@@ -17,9 +17,9 @@
 00symbol 16 @BasicSetup @DocumentSetup @ReportSetup @SectionList
 00symbol 17 @BasicSetup @DocumentSetup @ReportSetup @Section
 00symbol 18 @BasicSetup @NumberMarker
-00symbol 19 @BasicSetup @DocumentSetup @ReportSetup @SubSectionList
-00symbol 20 @BasicSetup @DocumentSetup @ReportSetup @Section @SubSection
-00target 21 @BasicSetup @DocumentSetup @ContentsPlace
+00target 19 @BasicSetup @DocumentSetup @ContentsPlace
+00symbol 20 @BasicSetup @DocumentSetup @ReportSetup @SubSectionList
+00symbol 21 @BasicSetup @DocumentSetup @ReportSetup @Section @SubSection
 00symbol 22 @BasicSetup @DocumentSetup @ReportSetup @SubSubSectionList
 00symbol 23 @BasicSetup @DocumentSetup @ReportSetup @Section @SubSection 
@SubSubSection
 00symbol 24 @BasicSetup @DocumentSetup @ReportSetup @Report @IndexPart

Jeff, perhaps, can shed some light on the relevant internals of why
the renumbering happens.

Hope this helps.

SY, Uwe
-- 
address@hidden                         |       Zu Grunde kommen
http://www.ptc.spbu.ru/~uwe/            |       Ist zu Grunde gehen