Displaying 4 results from an estimated 4 matches for "indextext".
Did you mean:
index_text
2007 Mar 28
2
Moving indextext.cc into core.
One of the items on the ToDo list for version 1.0 at
http://wiki.xapian.org/TodoFor1_2e0#preview is:
"Rework Omega's indextext.cc as a xapian-core "TextSplitter" class."
I've been wondering about this for a while now. Currently, we have the
Query Parser in Xapian core, but no text processing. Clearly, it makes
sense to have a "text splitter" class in whichever library the query
parser is...
2004 Jun 28
2
[Fwd: Irix install of omega fails.]
OK, I'll try again.
Thanks,
Jim.
-------------- next part --------------
An embedded message was scrubbed...
From: Jim Lynch <jwl@sgi.com>
Subject: Irix install of omega fails.
Date: Mon, 28 Jun 2004 14:16:46 -0400
Size: 2057
Url: http://lists.tartarus.org/pipermail/xapian-discuss/attachments/20040628/212669c1/Irixinstallofomegafails.eml
2005 Dec 30
1
Query Parser, filenames and compound words
When I submit a filename to the query parser it breaks it up
Example:
/home/user/file_name.ext
becomes
Xapian::Query((home:(pos=1) PHRASE 5 user:(pos=2) PHRASE 5 file:(pos=3) PHRASE
5 name:(pos=4) PHRASE 5 ext:(pos=5)))
which does not find the document.
If I do an single term query not using the query parser then I find the
document.
The Query Parser also breaks up hyphenated terms
2006 May 26
1
Unicode troubles
Hi,
I've tried to follow all helpful tips I've found in the mailing-list
and I've applied these two utf-8 patches;
http://article.gmane.org/gmane.comp.search.xapian.general/2324
http://article.gmane.org/gmane.comp.search.xapian.general/1927
Now the QueryParser works as I wants it to do, and creates the terms
correctly. But sadly I can't find any documents. If I do this;
$ quest