similar to: Multiple spelling suggestions

Greets, I'm giving a stab at patching the CPAN module to add the missing WritableDatabase::add_spelling and remove_spelling, but need a bit of guidance since I'm coming in cold, and pressed for time (aren't we all). I've modified XS/WritableDatabase.xs and added the two necessary functions, and also added the two basic tests in t/index.t. Compilation completes cleanly, but

Hello, I am looking at the Xapian database spelling support, with the idea of getting rid of the cumbersome use of aspell in my application. One advantage of aspell, though, (in my eye), is that it can supply a list of alternate spellings, not just the one it considers best. In some cases, this can be useful. 2 examples on my test index: porbability: xapian suggests portability, which is nice,

This is my test case, what am I doing wrong? It seems that the API is used incorrectly, but I cannot find the problem... --- 8< --- #!/usr/bin/perl use Search::Xapian qw(:all); use strict; my $xa = new Search::Xapian::WritableDatabase ("/tmp/xapian", DB_CREATE_OR_OVERWRITE); my $indexer = Search::Xapian::TermGenerator->new();

Hi Guys, Here's a simple test case that causes a segfault with the perl bindings patched to enable spelling correction: use strict; use warnings; use Search::Xapian; my $db = Search::Xapian::WritableDatabase->new("test.db", Search::Xapian::DB_CREATE_OR_OPEN); if (!defined($db)) { die("Failed to open xapian_database: $!"); } my $indexer =

Hi All, I'm using the TermGenerator::index_text() on version 1.0.4 with the FLAG_SPELLING turned on, because the new spelling suggestion stuff seems awesome, but I'm getting a segv. (gdb) bt #0 0xb7ae153c in Xapian::WritableDatabase::add_spelling (this=0xa553988, word=@0xbff97724, freqinc=1) at ./include/xapian/ base.h:154 #1 0xb7becf47 in

If I spell "commission" wrongly with an s instead of a t, Xapian (via the QueryParser's get_corrected_query_string function) is finding the right spelling: http://www.whatdotheyknow.com/search/commistion However, if I miss the s out completely, it doesn't find it: http://www.whatdotheyknow.com/search/commision Any idea why that is? Missing the last i out also doesn't

Hi Everyone, I?m a student in Peking University, China, my name is Xiaobing Liu, I?m interest in Spelling correction project. I think Xapian?s Spelling correction is based on edit distance with trusted dictionary. I have some questions about the spelling correction algorithm. 1. The Spelling correction algorithm depends on which dictionary, the dictionary in inverted index or other

Greets, I suppose this isn't a major issue, but are there any plans to complete the spelling suggestion facility across a search cluster? I seem to recall reading somewhere in the docs that it's TODO. Regards Henry

Hi to all, First, I would like to say a big thank you for the work which was done on my 'wish bug' to allow mapping one field to multiple prefixes (http://www.xapian.org/cgi-bin/bugzilla/show_bug.cgi?id=93). That's great! I have upgraded to 1.0.4 and I am revisiting my code, replacing the php query parser I wrote with Xapian's one. Everything works well, but I have some

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

Hello! I'm Shubham Sharma, a 3rd year Information Systems student at BITS Pilani, and I'd like to explore the possibilities of a GSOC Project that would aim at improving the tolerant retrieval capabilities via *phonetic* correction(: misspellings that arise because the user types a query that sounds like the target term. ) I did find spelling correction via edit distance in

*Hi all,* * * *The following is my general idea for the project. For a complete query parser I still need to consider more details. Please give me feedback because the description of this project is lack of detailed information, and I can submit my proposal without giant deviation.* * * design principle of query parsing: 1) better understanding user input. All search engine do is understanding

Hi guys.I've finished an example indexer which acts like a grep replacement for a file.It indexes each line containing a proper noun in a given text file.The line containing the proper noun will be displayed upon searching for that noun.I would like to add it to the community code examples.I'm planning to write more examples which demonstrate some advanced features of Xapian along similar

Hi, Is it necessary to set the down below flag to the TermGenerator, if I want the "Did you mean ..." spelling corrections? Xapian::TermGenerator::flags::FLAG_SPELLING Thank you very much Markus

Hi Olly, Please find attached my latest patch for the Perl spelling stuff. I've also added the missing sections in the man pages. I've left most of the unit tests out since I don't have enough experience with Xapian to comfortably code these. If you could pop those in when you get the time, that would be great. Cheers Henry Combrinck -------------- next part --------------

Hello, guys! How's it going? I would like to offer you myself again to implement one of the ideas during the GSoC 2012. I want to take care of the "Learning To Rank" project, but I would also be glad to pick the "QueryParser reimplementation", "Dynamic Snippets", "Gmane Search improvements" or even "Replace socket code with ZeroMQ" project (I

Greets, Please find attached a patch (against current svn) for consideration. It covers a few missing elements on the Perl side of things: add_spelling() and test/s. remove_spelling() and test/s. get_corrected_query_string() and test/s. get_spelling_suggestion() and test/s. man pages for the above and for WritableDatabase::close() are also patched. Please let me know of any errors (especially

I am working with version 1.2.7 and want to use stemming and synonyms. I use the perl-bindings and get some problems. First of all: the perl-bindings dont allow the QueryParser a third argument when calling parse_query! So i cannot set a default prefix (which perhaps is the solution to my problem, but later more) i have a simple testcase: 3 documents, every document only has one word:

Hello Sir, I am a third-year student at the Department of mathematics at IIT Kharagpur. I have good experience in Information Retrieval and Machine Learning. I have read many chapters of the book Introduction to Information Retrieval. Recently I am doing a project on tagging a question on a Q&A Forum using ranking the tags and probabilistic inference. I also have software development

I've uploaded Xapian 1.2.3 (including Search::Xapian 1.2.3.0). As usual you can download from: http://xapian.org/download You can read an overview of the release here: http://trac.xapian.org/wiki/ReleaseOverview/1.2.3 The full lists of user-visible changes are linked to from there, and from the "[news]" links on the download page. As always, if you encounter problems, please