Displaying 20 results from an estimated 4000 matches similar to: "xapian-0.9.4 queryparser build errors after applying utf-8 patch"
2006 Apr 05
1
build error : xapian-core-0.9.4_svn6707 with UTF-8 patch
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
2006 Jun 12
1
Ruuid had non-zero exit status (PR#8965)
> source("http://www.bioconductor.org/biocLite.R")
> biocLite(c("Ruuid"))
Running getBioC version 0.1.6 with R version 2.3.1
Running biocinstall version 1.8.4 with R version 2.3.1
Your version of R requires version 1.8 of Bioconductor.
trying URL
'http://bioconductor.org/packages/1.8/bioc/src/contrib/Ruuid_1.10.0.tar.gz'
Content type 'application/x-gzip'
2008 Sep 16
0
[PATCH] Add set_max_wildcard_expansion method to the queryparser.
---
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
2010 Oct 28
1
hypens in words + NEAR + 3 terms + AND_MAYBE => crash
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
2009 Jan 15
2
Xapian core build failure under gcc 2.95
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
2006 Dec 06
1
Bug and patch for +terms with wildcards
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
2012 Jan 05
1
Enhance synonyms feature of the query parser (patch included)
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");
2009 Jun 01
2
Xapian .lemony files
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.
2006 Mar 07
2
FLAG_BOOLEAN_ANY_CASE does not work
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
2006 Oct 30
1
QueryParser and prefixes
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
2010 Feb 01
0
Solaris core dump
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
2007 Apr 12
0
Re: [Xapian-commits] 8186: trunk/xapian-core/ trunk/xapian-core/queryparser/ trunk/xapian-core/tests/
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
2010 Feb 01
2
Xapian core dumping on Solaris
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
2005 Dec 09
1
QueryParser and utf-8 strings
Hi all,
I am rather new to xapian, I just recently tried to include it in
my application, so bear with me if this has already been discussed.
I was playing with QueryParser and noticed that it expects
input to be in ISO8859_1 encoding - characters above 0x80 are
transliterated, and are not considered letters. For example,
using single word (in utf-8 encoding) "bo?e" as input for
2024 Jan 04
1
Possible bug using FLAG_WORD_BREAKS with fullwidth Unicode codepoints
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,
2007 Oct 19
1
Re: [Xapian-commits] 9476: trunk/xapian-core/ trunk/xapian-core/include/xapian/ trunk/xapian-core/queryparser/ trunk/xapian-core/tests/
olly wrote:
> SVN root: svn://svn.xapian.org/xapian
> Changes by: olly
> Revision: 9476
> Date: 2007-10-19 03:47:11 +0100 (Fri, 19 Oct 2007)
>
> Log message (14 lines):
> include/xapian/queryparser.h,queryparser/queryparser.cc,
> queryparser/queryparser.lemony,queryparser/queryparser_internal.h,
> tests/queryparsertest.cc: Since calling
2018 Apr 11
0
how to build 64bit xapian using MSVC2017?
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
2006 May 17
3
QueryParser lowercase / uppercase and stemming
Hello.
There are several problems I couldn't find a solution.
1. QueryParser does not perform stemming
I am working with PHP5 and use the xapian wrapper written by Daniel M?nard
I build a query using parseQuery. Output of the parsed query shows that
terms are not stemmed, although a stemmer is set ( see code snippet)
# create a XapianDatabase object to search in
$db = new
2011 Dec 14
1
How to enable stemming with default_op set to OP_NEAR
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
2007 Jul 31
0
10 commits - doc/swfdec-docs.sgml doc/swfdec-sections.txt libswfdec-gtk/swfdec_gtk_loader.c libswfdec/Makefile.am libswfdec/swfdec_as_context.c libswfdec/swfdec_as_frame.c libswfdec/swfdec_buffer.c libswfdec/swfdec_debugger.c libswfdec/swfdec.h
doc/swfdec-docs.sgml | 1
doc/swfdec-sections.txt | 19 ++
libswfdec-gtk/swfdec_gtk_loader.c | 43 +----
libswfdec/Makefile.am | 4
libswfdec/swfdec.h | 3
libswfdec/swfdec_as_context.c | 2
libswfdec/swfdec_as_frame.c | 3
libswfdec/swfdec_buffer.c | 12 -
libswfdec/swfdec_debugger.c |