From: "Willi Egger" <w.egger@xs4all.nl>
Subject: Cross file refs...
Date: Tue, 10 Oct 2000 22:16:05 +0200 [thread overview]
Message-ID: <002f01c032f7$5cab1240$0100a8c0@xs4all.nl> (raw)
Hi Hans,
Your latest mail concerning cross-file referencing is just what I was
looking for. - I tried it out but I do not get the results required:
What I did is preparing a file, which contains all te file-names involved in
the project. Each of them contains a series of referencies.
I run then texexec with the following text with a complete reference:
\section[gekart2:hoekjes]{Hoekjes snijden, opplakken en inslaan}
Een en ander staat ook beschreven in \in{hoofdstuk}[hoeken::hoeken:titel],
\about[hoeken::hoeken:titel] op en verder.
\blank
Eenvoudige hoeken \index{hoeken} kunnen uit een vierkant gesneden worden.
%\at{pagina}[hoeken::hoeken:titel]
The result of this text is in the pdf-file is:
HBB-Brevier 1
1 Hoekjes snijden, opplakken en inslaan
Een en ander staat ook beschreven in / . , " " op en verder.
Eenvoudige hoeken kunnen uit een vierkant gesneden worden.
Remarks:
In the pdf file the forward-slash after in is a 'diamond' like shape.
When I uncomment the last row with the \at comand, I geet an error message,
saying that there is a superfluous curly-brace.
Do you have an idea what is wrong?
Furthermore I tried out also the use of \useexternaldocument[somfile]. The
reference is only given as a 'diamond' like shape, no label is typeset, but
the diamond is an active hyperlink. Again the \at command is not accepted
with the same error message.
I am really interested in this feature, because once I will typeset only
parts of the work (still the same piece :-] ), I would like to have the
references correct, though the textparts where the references point to are
not included.
Thanks also for your answer concerning the \completecontent- question. - It
is indeed the point to add the criterium and it works!
Willi
next reply other threads:[~2000-10-10 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-10 20:16 Willi Egger [this message]
2000-10-11 8:35 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002f01c032f7$5cab1240$0100a8c0@xs4all.nl' \
--to=w.egger@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).