From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Figure Libraries
Date: Mon, 03 Apr 2006 10:09:44 +0200 [thread overview]
Message-ID: <4430D847.5000003@elvenkind.com> (raw)
In-Reply-To: <02528812-41D4-42FD-BC02-260ED91B1F08@cox.net>
David Arnold wrote:
> My workaround was to rename the second instance \externalfigure
> [sec4foura], but I am wondering a bit about this mechanism.
You really should use unique names for your figures, you know.
How else can you differentiate between the one in section 4
and the one in section 2?
Greetings, Taco
next prev parent reply other threads:[~2006-04-03 8:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 16:39 David Arnold
2006-04-03 8:09 ` Taco Hoekwater [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-19 17:10 Figure libraries Willi Egger
2006-03-20 8:57 ` Hans Hagen
2006-03-20 9:15 ` Taco Hoekwater
2006-03-20 9:50 ` Willi Egger
2006-03-20 9:30 ` Hans Hagen
2006-03-20 9:51 ` Willi Egger
2006-03-20 10:26 ` Willi Egger
2006-01-15 3:15 David Arnold
2006-01-15 12:46 ` Henning Hraban Ramm
2006-01-16 8:51 ` Willi Egger
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=4430D847.5000003@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.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).