lout-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Problem with lout on Solaris -- Report + Sections + Postscrip t == e


From: Gallagher, Greg
Subject: RE: Problem with lout on Solaris -- Report + Sections + Postscrip t == error
Date: Thu, 16 Sep 1999 21:00:29 +0400 (MSD)

Yup, that's the key!  Thanks!!

Greg Gallagher

ps sorry for e-mail HTML if I did... forced to used Exchange here.  Bah...

-----Original Message-----
From: Valeriy E. Ushakov [mailto:address@hidden]
Sent: Thursday, September 16, 1999 11:22 AM
To: Lout Mailing List
Cc: Gallagher, Greg
Subject: Re: Problem with lout on Solaris -- Report + Sections +
Postscript == error


On Thu, Sep 16, 1999 at 07:00:42PM +0400, Gallagher, Greg wrote:

> mcbain:/home/ggallag/cvs-work/risk-analysis$ lout -S risk.lout > output.ps
> lout file "risk-production" (from "risk.lout" line 28):
>      1,1: unresolved cross reference @SectionList&&566.risk-production.1
>      1,1: unresolved cross reference @SectionList&&566.risk-production.1

> And it looks like this when you view the postscript:
>
> ??. Risk to Production Systems

Simply rerun lout.  On the very first run through the document lout
doesn't know section numbers yet.  But they are written into the
database and on the next run they are resolved.  I guess you have
generated PDF output (that was ok) as your next command, but by that
time section numbers were already known and that's why the PDF was ok.
If you had produced PS output, the PS output would be ok too.

This will also happens when you add a new structure element (new
section or subsection).  You will need at least two runs to resolve
xrefs.

Hope that helps.

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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]