From: Simon Pepping <spepping@scaprea.hobby.nl>
Subject: Re: XML attributes
Date: Mon, 15 Oct 2001 20:50:18 +0200 [thread overview]
Message-ID: <20011015205018.B11400@scaprea> (raw)
In-Reply-To: <5.1.0.14.1.20011015094816.03377ac8@server-1>; from pragma@wxs.nl on Mon, Oct 15, 2001 at 09:56:32AM +0200
On Mon, Oct 15, 2001 at 09:56:32AM +0200, Hans Hagen wrote:
> At 11:08 PM 10/13/2001 +0200, Simon Pepping wrote:
> >I have been experimenting a bit with attributes, e.g. in this phrase:
> ><item>And even worse<ref/>, <ref name="att"/> attributes <ref/> will not
> >be the
> >same as in &context;.</item>
> >
> >1. In the third ref element, the value \XMLpar{ref}{name}{\relax} is
> > not relax. Because the element has no (rather an implicit)
> > attribute name, the context value is left as it was set by the
> > preceding ref element. I think it would be better if attribute
> > values are local to the element, and there exists a command that
> > lets the user store the value in a control sequence, much like
> > \defXMLstring\command.
>
> locality is a bit of a problem since you don't want tex's grouping to
> interfere;
>
> this is why the following method is to be used (eg):
>
> \defineXMLenvironment[whatever][bla=,junk=]
>
> now, each time the element is encountered, 'bla' and 'junk' are set to
> nothing, so you start afresh.
That is not yet described in example.pdf. I saw it in an example you
gave me, but it has no effect. Perhaps in an updated version (mine is
cont-tmf from 9 August)?
Simon
--
Simon Pepping
email: spepping@scaprea.hobby.nl
next prev parent reply other threads:[~2001-10-15 18:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 21:08 Simon Pepping
2001-10-15 7:56 ` Hans Hagen
2001-10-15 18:50 ` Simon Pepping [this message]
2002-07-09 9:47 scarsoluigi
2002-07-09 19:05 ` Simon Pepping
2002-07-10 6:51 scarsoluigi
2002-07-10 20:05 ` Simon Pepping
2002-07-12 16:31 ` Hans Hagen
2003-06-05 22:06 Jedrzej Nasiadek
2003-06-06 19:37 ` Simon Pepping
2003-06-06 20:55 ` Jedrzej Nasiadek
2003-06-13 16:18 ` Hans Hagen
2003-06-07 0:03 ` Jedrzej Nasiadek
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=20011015205018.B11400@scaprea \
--to=spepping@scaprea.hobby.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).