From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: more xml in mkiv
Date: Tue, 25 Mar 2008 13:42:25 +0100 [thread overview]
Message-ID: <115224fb0803250542p36f66333s13762506b27aae7e@mail.gmail.com> (raw)
In-Reply-To: <60260297-8E33-4EED-B1C8-6A14B6BD6DD2@uni-bonn.de>
On Tue, Mar 25, 2008 at 1:17 PM, Thomas A. Schmitz
<thomas.schmitz@uni-bonn.de> wrote:
>
> On Mar 24, 2008, at 11:34 PM, Hans Hagen wrote:
> > works here, just to be sure i uploaded a new current
> >
> > Hans
> >
>
> Thanks Hans! You're right; I worked on a minimal example for a long
> time and got confused. I tried again; this example demonstrates the
> behavior (I tested on two different computers to be really sure :-):
>
> test.xml:
>
> <document>
> <section>
> <label>A</label>
> <content>text
> <itemize>
> <item>
> one
> </item>
> <item>
> two
> </item>
> <item>
> three
> </item>
> </itemize>
> more text
> </content>
> </section>
> </document>
>
> test-style.tex:
>
> \startxmlsetups xml:mysetups
> \xmlsetsetup{\xmldocument}{document|section|itemize|item}{xml:*}
> \stopxmlsetups
\startxmlsetups xml:mysetups
\xmlsetsetup{\xmldocument}{document|section|content|itemize|item}{xml:*}
\stopxmlsetups
> \xmlregistersetup{xml:mysetups}
>
> \startxmlsetups xml:document
> \xmlflush{#1}
> \stopxmlsetups
>
> \startxmlsetups xml:section
> \section{\xmlfirst{#1}{label}} \xmlfirst{#1}{content}
> \stopxmlsetups
\startxmlsetups xml:section
\section{\xmlfirst{#1}{label}}
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:content
\xmlflush{#1}
\stopxmlsetups
> \startxmlsetups xml:itemize
> \startitemize
> \xmlflush{#1}
> \stopitemize
> \stopxmlsetups
>
> \startxmlsetups xml:item
> \item \xmlflush{#1} \par
> \stopxmlsetups
also possible
\startxmlsetups xml:item
\startitem
\xmlflush{#1}
\stopitem
\stopxmlsetups
> \starttext
> \xmlprocess{main}{\inputfilename}{}
> \stoptext
Not sure if this works, I can't test it at the moment.
Wolfgang
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-03-25 12:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 21:28 Thomas A. Schmitz
2008-03-24 22:34 ` Hans Hagen
2008-03-25 12:17 ` Thomas A. Schmitz
2008-03-25 12:42 ` Wolfgang Schuster [this message]
2008-03-25 13:39 ` Thomas A. Schmitz
2008-03-25 14:38 ` Peter Rolf
2008-03-25 15:14 ` Thomas A. Schmitz
2008-03-25 15:36 ` Peter Rolf
2008-03-25 17:08 ` Thomas A. Schmitz
2008-03-25 17:32 ` Peter Rolf
2008-03-25 17:51 ` Hans Hagen
2008-03-25 15:29 ` Wolfgang Schuster
2008-07-14 14:45 ` Thomas A. Schmitz
2008-07-14 15:21 ` Wolfgang Schuster
2008-07-14 16:22 ` Thomas A. Schmitz
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=115224fb0803250542p36f66333s13762506b27aae7e@mail.gmail.com \
--to=schuster.wolfgang@googlemail.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).