From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: xml: spurious empty spaces
Date: Wed, 19 Oct 2016 13:47:14 +0200 [thread overview]
Message-ID: <2cb4dfaf-014b-15a1-6641-e7e9016ae1ca@wxs.nl> (raw)
In-Reply-To: <E10A977A-DB11-40D5-B8E8-1C25F482E5D5@uni-bonn.de>
On 10/19/2016 12:07 PM, Thomas A. Schmitz wrote:
> Hi all,
>
> below is a slightly silly example that demonstrates a problem I’m having: I want to process (in Lua) the xml element “b” only when it has an attribute “display” set. This works, but elements without the attribute leave spurious spaces in the pdf output. The workaround I’m currently using is
>
> if xml.attribute(e, "./", "display", "") ~= "yes" then
> context.unskip()
> else
> …
>
> but that seems like a kludge. Is this expected behavior, or should this be fixed?
\startxmlsetups xml:a
\ignorespaces
\xmlflush{#1}
\removeunwantedspaces
\stopxmlsetups
\startxmlsetups xml:b
\ignorespaces
\xmlfunction{#1}{b}
\removeunwantedspaces
\stopxmlsetups
> Thanks
>
> Thomas
>
> \startbuffer[test]
> <a>
> <b display="yes">test</b>
> <b>test</b>
> <b>test</b>
> <b>test</b>
> <b display="yes">test</b>
> <b display="yes">test</b>
> <b>test</b>
> </a>
> \stopbuffer
>
> \startxmlsetups xml:testsetups
> \xmlsetsetup{\xmldocument}{a|b}{xml:*}
> \stopxmlsetups
>
> \xmlregistersetup{xml:testsetups}
>
> \startluacode
> function xml.functions.b(e)
> xml.strip(e, "/", nolines, anywhere)
> if xml.attribute(e, "./", "display", "") == "yes" then
> context.space()
> context("/")
> context.space()
> lxml.flush(e)
> end
> end
> \stopluacode
>
> \startxmlsetups xml:a
> \xmlflush{#1}
> \stopxmlsetups
>
> \startxmlsetups xml:b
> \xmlfunction{#1}{b}
> \stopxmlsetups
>
> \starttext
> \xmlprocessbuffer{main}{test}{}
>
> \stoptext
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
--
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-10-19 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 10:07 Thomas A. Schmitz
2016-10-19 11:47 ` Hans Hagen [this message]
2016-10-19 16:02 ` 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=2cb4dfaf-014b-15a1-6641-e7e9016ae1ca@wxs.nl \
--to=pragma@wxs.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).