<div dir="ltr"><div dir="ltr">On Mon, Dec 2, 2019 at 9:15 AM Hardie, Andrew <<a href="mailto:a.hardie@lancaster.ac.uk">a.hardie@lancaster.ac.uk</a>> wrote:<br></div><div dir="ltr"><br></div><div>Hi Andrew,</div><div><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-GB">
<div class="gmail-m_-6123567886645970590WordSection1">
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:10pt">What you want in terms of manipulable auto-defaults is largely what CEQL is designed to provide. One of the new types of plugin under
development is the </span><i style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:10pt">CEQL Extender</i><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:10pt"> which will enable you to override CEQL grammar rules as per what you want. The example plugin of this sort is in fact one that adds a “</span><i style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:10pt">within s</i><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:10pt">” (or some other xml element) clause to everything. See </span><br></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Verdana,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><a href="https://sourceforge.net/p/cwb/code/HEAD/tree/gui/cqpweb/trunk/lib/plugins/builtin/CeqlExtender/AddWithinRangeOfXml.php" target="_blank">https://sourceforge.net/p/cwb/code/HEAD/tree/gui/cqpweb/trunk/lib/plugins/builtin/CeqlExtender/AddWithinRangeOfXml.php</a><span style="font-size:10pt;font-family:Verdana,sans-serif;color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Verdana,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Verdana,sans-serif;color:rgb(31,73,125)">Also, the new implementation of case sensitivity in 3,3 will allow the sensitivity defaults to be set per attribute.</span></p></div></div></blockquote><div><br></div><div>That looks very useful indeed!</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-GB"><div class="gmail-m_-6123567886645970590WordSection1"><p class="MsoNormal"><span style="font-size:10pt;font-family:Verdana,sans-serif;color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:10pt">It would be a bad idea, from a design perspective, to make the kinds of changes you suggest at the CQP level, where things like changing
the default case sensitivity or adding special treatment for “word” etc. etc. would be radical and very bad for backward-compatibility.</span></p></div></div></blockquote><div><br></div><div>All clear. Thanks for the answers.</div><div><br></div><div>Best wishes,</div><div>Scott </div></div></div>