ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Meer, H. van der" <H.vanderMeer@uva.nl>
To: ConTeXt NTG <ntg-context@ntg.nl>
Subject: parameter setting
Date: Sat, 16 Jun 2012 12:11:46 +0000	[thread overview]
Message-ID: <4E63CEE0-BC3A-4C66-91FB-DEF9FF197BE4@uva.nl> (raw)

In order to be able to use attributes on xml-nodes freely, the following situations can arise:

The foregroundcolor parameter gets a value:
<node color="red"> correctly sets ..[foregroundcolor=\xmlatt{#1}{color}] color to red.

However, in the next case the current foregroundcolor should be left as is, but reverts to black:
<node> ..[foregroundcolor=] and is apparently reset to the general default.

trying the following seemed the solution, but it does not work:
..[\doifnot{\xmlatt{#1}{color}}{\empty}{foregroundcolor=\xmlatt{#1}{color}}]
giving in the log:
{foregroundcolor=orange}' in line 16 (249>:)
check  > missing or ungrouped '=' after '\doifnot {}{}

Putting the above \doif inside an \expanded{} does not alter the behaviour.

How to accomplish leaving the parameter as is for an absent attribute?

Hans van der Meer



___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


             reply	other threads:[~2012-06-16 12:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-16 12:11 Meer, H. van der [this message]
2012-06-16 13:18 ` Wolfgang Schuster
2012-06-16 14:04   ` Meer, H. van der
2012-06-16 14:09     ` Wolfgang Schuster

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=4E63CEE0-BC3A-4C66-91FB-DEF9FF197BE4@uva.nl \
    --to=h.vandermeer@uva.nl \
    --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).