From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: xml and lpath
Date: Tue, 25 Oct 2011 14:20:59 +0200 [thread overview]
Message-ID: <4EA6A9AB.60105@wxs.nl> (raw)
In-Reply-To: <4EA69503.9020705@bbaw.de>
On 25-10-2011 12:52, Martin Fechner wrote:
> Hi all,
>
> I'm testing the possibilities of xml and ConTeXt. I was wondering if it
> is possible to make an extra setup for every text-element. So it would
> be possible to have an setup in a very flexible way. It should be
> something like this:
>
> \startbuffer[text]
> <a>
> <b>
> First text.
> <hiding type="begin"/>
> Second text.
> </b>
> Third text.
> <hiding type="end"/>
> Fourth text.
> </a>
> \stopbuffer
>
> \startxmlsetups xml:textsetups
> \xmlsetsetup{#1}{a|b}{xml:*}
> \xmlsetsetup{#1}{hiding[type='begin']}{xml:hiding:begin}
> \xmlsetsetup{#1}{hiding[type='end'}{xml:hiding:end}
> \xmlsetsetup{#1}{text()}{xml:text} % Something like this is needed
> \stopxmlsetups
>
> \startxmlsetups xml:a
> \xmlflush{#1}
> \stopxmlsetups
>
> \startxmlsetups xml:b
> \xmlflush{#1}
> \stopxmlsetups
>
> \startxmlsetups xml:hiding:begin
> \enablemode[hiding]
> \stopxmlsetups
>
> \startxmlsetups xml:hiding:end
> \disablemode[hiding]
> \stopxmlsetups
>
> \startxmlsetups xml:text
> \startnotmode[hiding]
> \xmlflush{#1}
> \crlf
> \stopnotmode
> \stopxmlsetups
>
> So that the result will be:
>
> First text.
> Fourth text.
>
> Is something like this possible or is there still another way?
it really depends on how the nesting works out as explicit grouping can
interfere
\startbuffer[text]
<a>
<b>
First text.
<hiding type="begin"/>
Second text.
</b>
Third text.
<hiding type="end"/>
Fourth text.
</a>
\stopbuffer
\startxmlsetups xml:textsetups
\xmlsetsetup{#1}{a|b|hiding}{xml:*}
\stopxmlsetups
\xmlregistersetup{xml:textsetups}
\startxmlsetups xml:a
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:b
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:hiding
\doifelse {\xmlatt{#1}{type}} {begin} {
\startnointerference
} {
\stopnointerference
}
\stopxmlsetups
\starttext
\xmlprocessbuffer{main}{text}{}
\stoptext
maybe it makes sense to have a 'hide' flag built in the serializer (or
maybe some explicit stream related hooks)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-10-25 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 10:52 Martin Fechner
2011-10-25 12:20 ` Hans Hagen [this message]
2011-10-25 13:20 ` Martin Fechner
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=4EA6A9AB.60105@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).