search for: lemoni

I have encountered the following build errors after applying xapian-qp-utf8-0.9.2.patch. There is no build error before the patch. - CentOS 4.2 64 bit version (RHEL 4.0.2 compatible) - AMD Opteron dual processor Can anybody tell me what I am missing? Thanks! Sungsoo Kim -------------------------------------------------- [root at saturn queryparser]# make make all-am make[1]: Entering

Hi All, I wanted to add a small tweak to my installation of the Query Parser. Should I be editing queryparser.lemony? I tried that and the make didn't include my change. I applied the same change to queryparser_internal.cc and it worked fine. Is the .lemony file something used internally and I can ignore? Or do I need to run something prior to make to convert the files? Thanks, Mike Boone.

This is another error different from the previous posting. I want to compile xapian-core-0.9.4_svn6707 with UTF-8 patch. But I failed to compile it due to the following errors. Environment : CentOS 4.3 x86_64 Sungsoo Kim ---------------------------------- g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I../common -I../api -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include

Probably an uncaught malformed query - the following form of search queries causes a crash for me (core 1.2.3, Perl API, 64bit Debian Lenny, self-compiled): x-y NEAR test NEAR test The first term can be anything with a hyphen in it but word characters at the beginning and end ("3--3" will do). The other 2 terms can be anything. "test NEAR x-y NEAR test" will not cause a

--- search-xapian/XS/QueryParser.xs | 6 ++++++ search-xapian/Xapian/QueryParser.pm | 7 +++++++ xapian-core/include/xapian/queryparser.h | 3 +++ xapian-core/queryparser/queryparser.cc | 6 ++++++ xapian-core/queryparser/queryparser.lemony | 9 +++++++++ xapian-core/queryparser/queryparser_internal.h | 4 +++- 6 files changed, 34

Hi all, My app uses prefixes for user-defined labels and directory names. Since these are case-sensitive, I chose XLABEL and XDIR respectively. Labels and directories may start with an upper-case, so a ":" is always inserted between the prefix and the term itself. These prefixes are mapped with add_boolean_prefix to "dir" and "label". Let's imagine I index a

I have found that lower cased boolean operators such as "and" or "or" does not work. Of course I never forget setting FLAG_BOOLEAN_ANY_CASE flag. QP seems to treat them as terms. Just look at the following tests regardless of search results! $ python search.py -v woman AND man Performing query 'Xapian::Query((woman:(pos=1) AND man:(pos=2)))' 0 results

Hi, Under gcc 2.95 Xapian fails to build like so: g++ -DHAVE_CONFIG_H -I. -I./common -I./include -I/home/dsainty/not-backed-up/pkgsrc/textproc/xapian/work/.buildlink/include -Wall -W -Wredundant-decls -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wformat-security -fno-gnu-keywords -Wundef -O2 -c queryparser/queryparser_internal.cc

Very few people seem to be using synonym in Xapian, I recently found some problems in the use of synonyms. Normally, I think we should not contain any prefix info in synonym table except that 'Z'. For example, I have the following synonyms and prefix info: db.add_synonym("search", "find"); db.add_synonym("Zsearch", "Zfind");

In current Xapian SVN HEAD, there is a bug in the query parser concerned with the handling of wildcard terms with a "+" prefix. Specifically, a query such as "+foo* bar" will be parsed by the query parser into Xapian::Query("bar") if there are no terms in the database which start "foo". Instead, since the "+" term cannot be matched, I believe

hi, Olly Betts, Thank you for you answer. My xapian version is 1.2.8. Need I upgrade it to 1.4 if I want to build it with MSVC2017 x64? lishu at fiberhome.com From: Olly Betts Date: 2018-03-29 11:10 To: 李澍; xapian-discuss Subject: Re: how to build 64bit xapian using MSVC2017? On Tue, Mar 20, 2018 at 08:28:24PM +0000, Olly Betts wrote: > Related to this, the appveyor build is

hello everyone, I am Maheshwar, a prefinal year Computer Science undergraduate student at BITS-Pilani, India. When i was going through the GSOC ideas , i felt interested in Quesry parser project. Till now i have implemented a couple of LL(1) parsers as a part of my assignment in Compiler construction course, so i would love to join and contribute to this project. So can any one tell me how to go

olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 8186 > Date: 2007-04-11 23:38:53 +0100 (Wed, 11 Apr 2007) > > Log message (7 lines): > queryparser/queryparser.lemony: Fix regression introduced by > Richard's change, and restructure to make the handling for each case > more obvious. Thanks for the catch: I

Hi everyone, I'm having a problem with xapian (the matchspy branch, with Python bindings) on Solaris 10 / SPARC. Users can run queries for a few hours with no problems, then it returns "inflate failed (invalid code lengths set)" to Python and dumps core. gdb reports: #0 0xfe6dc910 in inflate_table () from /usr/lib/libz.so.1 #1 0xfe6d9d6c in inflate () from /usr/lib/libz.so.1 #2

Hi All, I know that from version 1.2.6, if default_op is OP_NEAR or OP_PHRASE then stemming of the terms is disabled, since positional information isn't indexed for stemmed terms by default. However, I would like to try using OP_NEAR as default_op with stemming because I think the near operator is somehow different from exact phrase. Then I wanna see how the search results looks with this

Hi, Olly: I post the error in the attachment, any methods to fix it? Run the command (.\lemon.exe -q -oqueryparser_internal.cc -hqueryparser_token.h queryparser.lemony) will get the error. If it is hard to fix, I will upgrade xapian to 1.4. But I worry it will cost me too much time to modify my application code. Thanks a lot. Here is the error details: lemon.c: #define LISTSIZE 30

Hi everyone, I'm having a problem with xapian (the matchspy branch, with Python bindings) on Solaris 10 / SPARC. Users can run queries for a few hours with no problems, then it returns "inflate failed (invalid code lengths set)" to Python and dumps core. gdb reports: #0 0xfe6dc910 in inflate_table () from /usr/lib/libz.so.1 #1 0xfe6d9d6c in inflate () from /usr/lib/libz.so.1 #2

I think I found a bug in Xapian 1.5 when using FLAG_WORD_BREAKS for input that contains characters in Unicode Halfwidth and Fullwidth Forms (https://unicode.org/charts/PDF/UFF00.pdf). Since I am undecided yet if and how to fix this in Xapian I haven't come up with a pull request. Because trac currently is offline, I could not file a bug. I hope it's OK to post my analysis here first,

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect