<div dir="ltr"><div><div>Hello, Stefan, Andrew and others!!!<br><br></div><div>You advised to use tagging style like:<br><br>n:sg:px3sp:nom<br>or<br>
n|sg|px3sp|nom<br><br></div><div>Is there any particular reason why ":" or "|" instead of "<" or ">". Is it possible to use "," (comma)? What do you usually use in your projects?<br></div><div><br></div><div>Thank you!<br></div>With best wishes,<br></div>Mansur<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On 22 February 2018 at 11:52, Stefan Evert <span dir="ltr"><<a href="mailto:stefanML@collocations.de" target="_blank">stefanML@collocations.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Mansur,<br>
<br>
most of the remaining issues are related to CQPweb, so Andrew will be in a much better position to answer them and help you with the debugging. Some of them are clearly (mis-)configuration issues, e.g. the failure to locate the CEQL backend that is part of CQPweb or the failure to run CQP.<br>
<br>
Are you working with an up-to-date version of CQPweb checked out from the SVN repository?<br>
<br>
<br>
> 3) After rebooting computer any search does not work at all:<br>
> ERROR: CQP backend startup failed; the reported CQP version [] could not be parsed.<br>
> But from the comman line I can perform search with 'cqp -e' and it seems to be working, at least I can see search results.<br>
<br>
This suggests that you have CQP installed, but in a "private" path that's only visible to your user account and not to the Web server running CQPweb. You may also need to configure CQPweb and set appropriate paths there.<br>
<br>
> 4) Is it possible to choose ranges of periods in search according to the 'date'?<br>
> <text id="" date=?????><br>
<br>
I think Andrew is working on support for date attributes in CQPweb.<br>
<br>
In plain CQP, there are two ways of doing date searches:<br>
<br>
a) The reasonable way: Store your dates in a simple standard format – I prefer ISO YYYY-MM-DD, so alphabetical and chronological sort order are the same – and then construct regular expressions for your suitable date ranges, e.g. in the global constraint of a CQP query:<br>
<br>
… :: match.text_date = "2011-03.*"; # anything in March 2011<br>
<br>
… :: match.text_date = "1990-(01-(1[2-9]|[23]\d)|02-.<wbr>*|03-([0-1]\d|2[0-4]))"; # 12 Jan 1990 .. 24 Mar 1990<br>
<br>
b) The "I'm a Unix hacker way": convert your dates to 32-bit integers and use numeric comparisons. The obvious choice would be consecutive numbers for days (or even seconds as in Unix timestamps), but conversion from/to human-readable dates will be complicated. However, you could encode the ISO-format above _without_ the hyphens to get 8-digit numbers, e.g.<br>
<br>
<text id="…" date="20180222"><br>
<br>
and then cast to integers for numerical comparisons:<br>
<br>
… :: int(match.text_date) >= 19900112 & int(match.text_date) <= 19900324;<br>
<br>
Nice trick, isn't it?<br>
<br>
> 5) When I press 'Show tags' button I get<br>
> 2012_ нче_ елда_ республикада_ 55_ мең_ 839_ бала_ дөньяга_ килгән_ ._<br>
> but no tags.<br>
<br>
That's because CQPweb failed to do proper HTML-escaping for the annotation strings (which is not only incovenient but also a security risk).<br>
<br>
@Andrew: has this bug been fixed in the lastest CQPweb code?<br>
<br>
I've been bitten by similar issues before and would recommend avoiding HTML metacharacters (and other funny things) in annotation strings. Better recode to something like<br>
<br>
n:sg:px3sp:nom<br>
<br>
or even<br>
<br>
|n|sg|px3sp|nom|<br>
<br>
so you can use the "contains" operator in searches.<br>
<br>
> I think it is maybe because I didn't replace "<" and ">" in my morphological tags to their XML entities yet. Please, correct me if I'm wrong.<br>
<br>
That won't help! With -x, cwb-encode will decode the XML entities in your input file and you'll end up with < and > in the indexed corpus. You could encode without the -x flag, but then your annotation strings will be<br>
<br>
&lt;n&gt;&lt;sg&gt;&lt;px3sp&<wbr>gt;&lt;nom&gt;<br>
<br>
which happens to display nicely only until HTML escaping in CQPweb is fixed – and you will have to search for<br>
<br>
[pos = ".*&lt;nom&gt;.*"]<br>
<br>
instead of<br>
<br>
[pos = ".*<nom>.*"]<br>
<br>
> 7) I also saw the button 'Export corpus -> Export whole corpus'. Does that mean that users can download the whole corpus? Is it possible to turn it off somehow?<br>
<br>
AFAIK, only users with the "full access privilege" are allowed to download a corpus. So if you want to disable downloads, simply keep to "normal access".<br>
<br>
<br>
Best,<br>
Stefan<br>
<br>
______________________________<wbr>_________________<br>
CWB mailing list<br>
<a href="mailto:CWB@sslmit.unibo.it">CWB@sslmit.unibo.it</a><br>
<a href="http://liste.sslmit.unibo.it/mailman/listinfo/cwb" rel="noreferrer" target="_blank">http://liste.sslmit.unibo.it/<wbr>mailman/listinfo/cwb</a><br>
</blockquote></div><br></div>