> On 17 Sep 2018, at 21:12, Hans van der Meer <havdm...@ziggo.nl> wrote:
>
> This completely escapes me: \xmlstrippednolines behaves differently for:
> (1) no embedded nodes - just the node content
> (2) embedded nodes - outer node encloses node content
> See the minimal example.
>
> For me this works out a disaster, because in the second case the outer node
> is added, throwing my program completely off track.
>
> Questions:
> Is this the defined behaviour? Then what other means can be used to get the
> node content and nothing but the node content in both cases?
\startxmlsetups xml:text
tex: \xmlflush{#1}\crlf
xmlstrippednolines: \xmlstripnolines{#1}{.}\xmlflush{#1}\crlf
\stopxmlsetups
> Why does \xmlstrippednolines behaves in this manner?
No idea about that.
Best wishes,
Taco
Taco Hoekwater
Elvenkind BV
___________________________________________________________________________________
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
___________________________________________________________________________________
