Crossreferencing with beta-version

Crossreferencing with beta-version

[Willi Egger]

Hi Hans,

First of all: IT WORKS! Its great to see the new functionality. Thanks for
your reply.

When I mailed you the last time you asked me, whether I was using the
'project'-mechanism. - No. I do however think, whether it would be better to
start packing this project into this mechanism.

Is there a simple way to generate the *.tuo files of each referenced file? -
Of course my project isn't comparable to what you referred to, but I got
still to run texexec for about 30 files and will have to rename each file of
the generated output...

Best regards Willi

Re: Crossreferencing with beta-version

[Hans Hagen]

At 10:14 PM 10/13/00 +0200, Willi Egger wrote:
>Hi Hans,
>
>First of all: IT WORKS! Its great to see the new functionality. Thanks for
>your reply.
>
>When I mailed you the last time you asked me, whether I was using the
>'project'-mechanism. - No. I do however think, whether it would be better to
>start packing this project into this mechanism.
>
>Is there a simple way to generate the *.tuo files of each referenced file? -
>Of course my project isn't comparable to what you referred to, but I got
>still to run texexec for about 30 files and will have to rename each file of
>the generated output...

Eh ... I don't understand this. 

you can feed texexec with somefile*.tex or you may want to make a batch
file with some 30 lines: 

texexec somefile --result=somefile-01 

or so. The advantage of the project mechanism is that you can run
components more conveniently.  

Hans

-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------