From: Johannes Graumann <graumann@caltech.edu>
Subject: Re: Re: Re: ConTeXt, XML, multiple attributes evaluation
Date: Wed, 30 Nov 2005 12:07:33 -0800 [thread overview]
Message-ID: <dml0rb$9ab$1@sea.gmane.org> (raw)
In-Reply-To: <438D6489.4020900@wxs.nl>
Thanks,
Does what I want and opens the door for further exploration ...
Joh
Hans Hagen wrote:
> Johannes Graumann wrote:
>
>>Hans,
>>
>>I'm just not getting it ... can't find the appropriate documentation
>>maybe? http://www.pragma-ade.nl/general/manuals/example.pdf is all I got
>>and e.g. "XMLop" does not show up at all in there ...
>>
>>
> XMLop{xx} is a shortcut for \XMLpar{list}{xx}{some default}
>
> and as long as the current element is list that will work, so
>
> \defineXMLenvironment[list]
> {here \XMLop{xx} works fine}
> {but here the last element encountered may be another than list}
>
>>I tryed to get this working (just trial and error), but I just don't
>>understand ... can you kick me some more into the right direction?
>>
>>\mapXMLvalue {list:packed} {yes} {packed}
>>\mapXMLvalue {list:packed} {no} {unpacked}
>>\mapXMLvalue {list:setup} {\XMLpar{list}{setup}{}} {setup}
>>\defineXMLenvironment
>> [list]
>> [packed=no,setup=1]
>> {%
>> \startitemize[%
>> \XMLval{list:setup}{\XMLop{setup}}{},
>> \XMLval{list:packed}{\XMLop{packed}}{}
>> ]%
>> }%
>> {\stopitemize}
>>
>>Likly many a thing doesn't make sense at all - I just don't get it.
>>
>>Any hint is highly appreciated,
>>
>>
> This works ok here:
>
> \mapXMLvalue {list:packed} {yes} {packed}
> \mapXMLvalue {list:packed} {no} {unpacked}
>
> \defineXMLenvironment
> [list]
> [packed=no,setup=1]
> {\startitemize[\XMLop{setup},\XMLval{list:packed}{\XMLop{packed}}{}]}
> {\stopitemize}
>
> \defineXMLenvironment
> [item]
> {\item}
> {\endgraf}
>
> \starttext
>
> \startXMLdata
> <list packed='yes'>
> <item>item one</item>
> <item>item two</item>
> </list>
> \stopXMLdata
>
> \startXMLdata
> <list>
> <item>item one</item>
> <item>item two</item>
> </list>
> \stopXMLdata
>
> \startXMLdata
> <list packed='yes' setup='a'>
> <item>item one</item>
> <item>item two</item>
> </list>
> \stopXMLdata
>
> \startXMLdata
> <list setup='a'>
> <item>item one</item>
> <item>item two</item>
> </list>
> \stopXMLdata
>
> \stoptext
>
> (it may help to look at the x-* files in the context/base path)
>
> Hans
--
+----------------------------------------------------------------------+
| Johannes Graumann, Dipl. Biol. |
| |
| Graduate Student Tel.: ++1 (626) 395 6602 |
| Deshaies Lab Fax.: ++1 (626) 395 5739 |
| Department of Biology |
| CALTECH, M/C 156-29 |
| 1200 E. California Blvd. |
| Pasadena, CA 91125 |
| USA |
+----------------------------------------------------------------------+
prev parent reply other threads:[~2005-11-30 20:07 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
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 [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='dml0rb$9ab$1@sea.gmane.org' \
--to=graumann@caltech.edu \
--cc=graumann@its.caltech.edu \
--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).