Re: [NTG-context] wildcard selection in xmlfilter

2018-09-12 Thread Hans van der Meer
No, never thought of ** instead of *. Also not in my printout of the manual, 
but that might be fairly outdated.
Thanks.

By the way, did you see my post on \xmllastatt from yesterday?

> On 12 Sep 2018, at 13:23, Hans Hagen  wrote:
> 
> On 9/12/2018 1:03 PM, Hans van der Meer wrote:
>> There is a difference of behaviour in \xmlfilter between
>> (1) \xmlfilter{#1}{node/command(xmlsetup)} and
>> (2) \xmlfilter{#1}{*/command(xmlsetup)}
>> (3) \xmlfilter{#1}{*/*/command(xmlsetup)}
>> In case (1) the lpath ‘node’ results in processing of the  nodes 
>> in all child nodes.
>> In case (2) and (3) no more than the corresponding level is searched.
>> Thus there is a difference in behaviour between node and * as an lpath.
>> Very unfortunate for me, because I need to process all nodes regardless of 
>> theeir node name, but selected on the basis of an attribute: 
>> \xmlfilter{#1}{*[@attribute==“yes”].
>> The difference in behaviour makes this impossible, because a general 
>> proceudre is impossible and doing a search with * and */* and */*/* etc. 
>> always will be one level too short, I expect.
>> Is this intended behaviour, and if so, is there a general solution?
> 
> did you try **
> 
> -
>  Hans Hagen | PRAGMA ADE
>  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -

dr. Hans van der Meer


___
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
___

Re: [NTG-context] wildcard selection in xmlfilter

2018-09-12 Thread Hans Hagen

On 9/12/2018 1:03 PM, Hans van der Meer wrote:

There is a difference of behaviour in \xmlfilter between
(1) \xmlfilter{#1}{node/command(xmlsetup)} and
(2) \xmlfilter{#1}{*/command(xmlsetup)}
(3) \xmlfilter{#1}{*/*/command(xmlsetup)}

In case (1) the lpath ‘node’ results in processing of the  
nodes in all child nodes.

In case (2) and (3) no more than the corresponding level is searched.

Thus there is a difference in behaviour between node and * as an lpath.
Very unfortunate for me, because I need to process all nodes regardless 
of theeir node name, but selected on the basis of an attribute: 
\xmlfilter{#1}{*[@attribute==“yes”].
The difference in behaviour makes this impossible, because a general 
proceudre is impossible and doing a search with * and */* and */*/* etc. 
always will be one level too short, I expect.


Is this intended behaviour, and if so, is there a general solution?


did you try **

-
  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
___