From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Henri Menke <henrimenke@gmail.com>
Subject: Re: \xmlfirst broken?
Date: Mon, 17 Jul 2017 10:22:10 +0200 [thread overview]
Message-ID: <1541dbd6-2fc1-f028-0579-c8a338559e42@wxs.nl> (raw)
In-Reply-To: <1500255625.2522.4.camel@gmail.com>
On 7/17/2017 3:40 AM, Henri Menke wrote:
> Dear list,
>
> A recent question on TeX.SX is asking about XML processing.
> https://tex.stackexchange.com/questions/380935
>
> To reproduce the error from the question I copied the demo from the XML manual. First of all we
> have demo.xml:
>
>
> <?xml version='1.0' standalone='yes'?>
> <document>
> <section>
> <title>Some title</title>
> <content>
> <p>a paragraph of text</p>
> <p>another paragraph of text</p>
> </content>
> </section>
> </document>
>
>
> And then we have a ConTeXt document:
>
>
> \startxmlsetups xml:demo:base
> \xmlsetsetup{#1}{*}{-}
> \xmlsetsetup{#1}{document|section|p}{xml:demo:*}
> \stopxmlsetups
>
> \xmlregisterdocumentsetup{demo}{xml:demo:base}
>
> \startxmlsetups xml:demo:document
> \starttitle[title={Contents}]
> \placelist[chapter]
> \stoptitle
> \xmlflush{#1}
> \stopxmlsetups
>
> \startxmlsetups xml:demo:section
> \startchapter[title=\xmlfirst{#1}{/title}]
> \xmlfirst{#1}{/content}
> \stopchapter
> \stopxmlsetups
>
> \startxmlsetups xml:demo:p
> \xmlflush{#1}\endgraf
> \stopxmlsetups
>
> \starttext
> \xmlprocessfile{demo}{demo.xml}{}
> \stoptext
>
>
> This works partially. Some entities are printed fine but stuff in \xmlfirst is missing. I can
> reproduce this in TL2017 and latest beta. In the attached PDF you can see that the section has no
> title and no content (exactly the stuff \xmlfirst was supposed to get).
just comment the line:
\xmlsetsetup{#1}{*}{-}
or provide setups for content and title too
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2017-07-17 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 1:40 Henri Menke
2017-07-17 8:22 ` Hans Hagen [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=1541dbd6-2fc1-f028-0579-c8a338559e42@wxs.nl \
--to=pragma@wxs.nl \
--cc=henrimenke@gmail.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).