From: Johannes Graumann <johannes_graumann@web.de>
Subject: definedescription and XML
Date: Thu, 4 Jan 2007 14:52:18 +0000 (UTC) [thread overview]
Message-ID: <loom.20070104T154657-915@post.gmane.org> (raw)
Hello all,
After a good break I'm back at my XML obsession and am running into the
following issue: my environment-file contains these definitions
\defineXMLnested
[reagentlist]
[sample=]
{\definedescription[definition][width=broad,distance=1em,sample={\XMLop{sample}}]}
{}
\defineXMLnested
[reagent]
[label=]
{\startdefinition{\XMLop{label}}}
{\stopdefinition}
but in use, the definition-label-width is optimized for every single case,
rather than for the 'sample', meaning I get
One xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Twentyone xxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxx
rather than
One xxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxx
Twentyone xxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxx
Can anyone please enlighten me as to what I'm missing here?
Thanks, Joh
next reply other threads:[~2007-01-04 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 14:52 Johannes Graumann [this message]
2007-01-04 15:55 ` Hans Hagen
2007-01-04 16:23 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=loom.20070104T154657-915@post.gmane.org \
--to=johannes_graumann@web.de \
--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).