From: David Arnold <dwarnold45@cox.net>
Subject: Re: Duplicate names in figure libraries
Date: Wed, 3 May 2006 23:19:40 -0700 [thread overview]
Message-ID: <2DDB450D-EF5B-4E40-8D3A-85593AAD430F@cox.net> (raw)
In-Reply-To: <4459122D.1080800@wxs.nl>
Hans et al,
I'm afraid I don't know enough xml to understand this.
How would something lik this change with your suggested strategy?
<figure>
<file>sec4twoa.png</file>
<label>sec4twoa</label>
<copyright>College of the Redwoods Mathematics Department</copyright>
<comment></comment>
</figure>
Here's why I asked. You have a team working on Chapter 5, which has
sections 1-7. Let's say each person volunteers to write a section.
Unless they agree on a naming strategy beforehand, there could be
duplicate names in the figure library files.
And then you could have several chapters with more sections.
On May 3, 2006, at 1:27 PM, Hans Hagen wrote:
> Willi Egger wrote:
>> Hi David,
>>
>> unless Hans releases some magic, there is no way than to have
>> different
>> labels in both files.
>>
>>
> we can consider adding a <rl:collection>somename</rl:collection>
> element so that one has to use somename:somelabel to locate a graphic
>
> Hans
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
> | www.pragma-pod.nl
> -----------------------------------------------------------------
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
prev parent reply other threads:[~2006-05-04 6:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 4:28 David Arnold
2006-05-03 16:16 ` Willi Egger
2006-05-03 20:27 ` Hans Hagen
2006-05-04 6:19 ` David Arnold [this message]
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=2DDB450D-EF5B-4E40-8D3A-85593AAD430F@cox.net \
--to=dwarnold45@cox.net \
--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).