<div>No, I didn't suggest waht you say, I was just calling your attention to the difference
between your RegEx and that from the manual...</div>
<div><br /></div>
<div>Manual<br /></div>
<div>[(lemma="go") & !(word="went"%c |
word="gone"%c)];</div>
<div> </div>
<div><br /></div>
<div>Yours</div>
<div>([word="en"][word="tierra"])</div>
<div><br /></div>
<div>to match yours to the manual one, regex should be: !(word="en"
word="tierra")</div>
<div><br /></div>
<div><br /></div>
<div><br /></div>
El Mar, 28 de Julio de 2020, 23:42, Josep M. Fontana escribió:<br />> Thanks Maarten
and to everybody who responded.<br />> <br />> Yes. What you say makes total sense. I
had assumed that since in essence<br />> the complex pattern involving grouped expressions
are all within a<br />> single parenthesis '( )' and that allows one to treat it as if it
were a<br />> single word within '[]', the ! operator would work the same way it works<br
/>> when it is associated to any expression inside square brackets.<br />> <br />>
Andrés seems to suggest to enclose everything within square brackets but<br />> that
doesn't work. In principle it shouldn't word because the convention<br />> is that square
brackets enclose a word. So it makes sense that we can't<br />> do that. Once we allow to
use parenthesis to form groups of sequences of<br />> words that are treated essentially as
a single unit, however, why can't<br />> we use the same operators we use with single
expressions enclosed within<br />> '[ ]'? I don't see why it shouldn't be possible.<br
/>> <br />> If no one has asked this before it must mean that there are not that<br
/>> many people who would need to do this kind of search and of course I<br />> have no
idea of how hard this might be to implement. Having said this,<br />> however, I certainly
think that this would be very useful. I find the<br />> idea of doing a diff as Andrew
suggests a bit unpractical.<br />> <br />> JM<br />> <br />> On 28/07/2020 22:41,
Maarten Janssen wrote:<br />>> I did not look in detail at the implementation in CWB -
but if these were normal regular<br />>> expressions, your query<br />>><br
/>>> [(word="f[ei]rid.*")|(word="muert[ao].*")]
!(([(pos="S.*")<br />>> &<br />>>
(word="d.*")][word=".*el"][word="ca[buv]allo.*"])|[word="entierra"]|([word="en"][word="tierra"]))<br
/>>><br />>> should match<br />>><br />>> cayo *muerto* en tierra<br
/>>><br />>> Namely - “muerto” for the first part of the query, and
nothing for the second - there is no<br />>> indication of how long the second part
should be - add a word requirement after it and it<br />>> even becomes unwelldefined
what you would mean by it; it would be different if you were<br />>> looking for a
specific word after it that cannot be one of several, like [!(word=“en<br />>>
?tierra” | word=“ca[buv]allo")] - but your second part has a variable word
length. What you<br />>> are looking for is a negative look-ahead, which you cannot do
by negating the parts of what<br />>> you are looking for - and given how query matches
work in CWB I would be very surprised if<br />>> there is a negative look-ahead...<br
/>>> _______________________________________________<br />>> CWB mailing list<br
/>>> CWB@sslmit.unibo.it<br />>>
http://liste.sslmit.unibo.it/mailman/listinfo/cwb<br />>
_______________________________________________<br />> CWB mailing list<br />>
CWB@sslmit.unibo.it<br />> http://liste.sslmit.unibo.it/mailman/listinfo/cwb<br />> <br
/><br /><br /><br />_______________________<br />
andrés
chandía<br /><a href="http://www.chandia.net" target="_blank"><img
src="http://mail.chandia.net/images/chandia_net.png" alt="chandia.net" border="0" /></a> <a
href="https://twitter.com/chandianet" target="_blank"><img
src="http://mail.chandia.net/images/ico_tw.png" alt="" width="20" height="20" /></a><br /><a
href="http://chandia.net/content/dungupeyem" title="Analizador y generador mofológico de
mapudüngun">Düngupeyem</a> | <a href="http://chandia.net/content/iecmap" title="Interfaz
de explotación de corpus del mapudüngun">IECMap</a> | <a
href="http://chandia.net/content/isecmap" title="Interfaz sencilla de explotación de corpus
del mapudüngun">ISECMap</a> | <a href="http://chandia.net/content/nmt" title="Unificador
ortográfico de mapudüngun">NMT</a> | <a href="http://corlexim.cl" title="Corpus lexicográfico
de mapudüngun">Corlexim</a><br /><br />Desarrollador de:<br /><a
href="https://parles.upf.edu">Parles.upf</a> | <a href="https://iwch.upf.edu"
title="Interfície Web de Consulta d'Horaris UCA TCL UPF">IWCH</a> | <a
href="http://amindterapia.com">Amind terapia</a> | <a href="http://koyaktumapuche.net">ONG
Mapuche koyaktu</a> | <a href="https://parles.upf.edu/llocs/nocando">Nocando</a> | <a
href="https://iac.upf.edu">IAC</a> | <a href="https://iac.upf.edu/cddz">CddZ</a> | <a
href="https://iac.upf.edu/isac">ISAC</a> | <a href="http://catcg.upf.edu">CatCg</a><br /><span
style="font-size: 18pt; color: rgb(79, 98, 40); font-family: Webdings;">P</span> <span
style="font-size: 10pt; color: rgb(79, 98, 40);">No imprima innecesariamente. ¡Cuide el
medio ambiente!</span>