From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: ConTeXt, XML, multiple attributes evaluation
Date: Tue, 29 Nov 2005 08:37:17 +0100 [thread overview]
Message-ID: <438C052D.3080308@elvenkind.com> (raw)
In-Reply-To: <dmglhi$nv1$1@sea.gmane.org>
Johannes Graumann wrote:
>
> but this doesn't work ...
But it worked fine for me!?
Anyway, it is probably a better idea to do it like this:
\defineXMLenvironment [list]%
{%
\let\listoptions\empty
\XMLifequalelse{list}{setup}{n}
{\appendtocommalist{n}\listoptions}
{}%
\XMLifequalelse{list}{packed}{yes}
{\appendtocommalist{packed}\listoptions}
{\appendtocommalist{unpacked}\listoptions}%
\expanded{%
\startitemize[\listoptions]%
}%
}%
{\stopitemize}
Because that way, the xml attributes can be optional.
If it still doesn't work, please explain what goes wrong.
Greetings, Taco
next prev parent reply other threads:[~2005-11-29 7:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 4:30 Johannes Graumann
2005-11-29 7:34 ` Richard Gabriel
2005-11-29 9:52 ` Hans Hagen
2005-11-29 11:02 ` Richard Gabriel
2005-11-29 7:37 ` Taco Hoekwater [this message]
2005-11-29 19:58 ` Johannes Graumann
2005-11-29 21:15 ` Hans Hagen
2005-11-30 1:36 ` Johannes Graumann
2005-11-30 8:36 ` Hans Hagen
2005-11-30 20:07 ` Johannes Graumann
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=438C052D.3080308@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).