Thanks, that's helpful. Is there a way to collect these pieces of information
and print them at the end together with rest of the processing information. I'm
thinking of something like:
mkiv lua stats > 2 overful boxes, 3 underful boxes
or:
warning > 2 overful boxes, 3 underful boxes
What do
Readers,
I'm working on a couple of volumes of papers set up and generated
separately (though within the same project). Some of the papers in
the second volume make cross references to papers in the first.
Now this is working well so long as the reference is to the details
associated with, say, a
On 3/4/2021 12:32 PM, denis.ma...@ub.unibe.ch wrote:
Thanks, that's helpful. Is there a way to collect these pieces of information
and print them at the end together with rest of the processing information. I'm
thinking of something like:
mkiv lua stats > 2 overful boxes, 3 underful boxes
or
Richard Mahoney schrieb am 04.03.2021 um 09:04:
Readers,
I'm working on a couple of volumes of papers set up and generated
separately (though within the same project). Some of the papers in
the second volume make cross references to papers in the first.
Now this is working well so long as the re
Thanks Wolfgang,
Hans kindly sent me a simple minimal. I've adjusted it to include a
call
to \pagereference and it works. I'm currently trying to test my
project
to see why my own calls to \pagereference do not result in any output,
despite the fact that all the calls to the reference ids in chapt
Wolfgang [and Hans &c.],
I'm attaching a minimal(ish) example of a project structure with
a call to \pagereference. One can see from the output of master000.tex
that the cross references to an external file all work, *apart* from
the call to \pagereference. (This is the same issue that I am having
