search for: add_spelling

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 Xapian::TermGenerator::Internal::index_text (this=0xa553970, itor= {p = 0xab2d69f " North Face Windwall 1 Jacket boys", end = 0xab2d6c1 "", seqlen = 1}, weight=3, prefix...

...s the patch to enable spelling against Search-Xapian-1.0.4.0: http://rusty.devel.infogears.com/xap-perl-spelling.diff Here's the backtrace against 1.0.4: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208211776 (LWP 27230)] 0x001c9bbc in Xapian::WritableDatabase::add_spelling (this=0x9d77de0, word=@0xbf846fa0, freqinc=1) at ./include/xapian/base.h:154 154 return dest; Current language: auto; currently c++ (gdb) bt #0 0x001c9bbc in Xapian::WritableDatabase::add_spelling (this=0x9d77de0, word=@0xbf846fa0, freqinc=1) at ./include/xapian/ base.h:154 #1 0x003...

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 in the test suites). I've successfully patched,...

...3 then the term limit should be checked > when you call add_document() or replace_document(). I'm using trunk, r13989. Ok, I have my stupid hat on this morning, so please bear with me: ... # $raw_text could contain up to 110k of text. $analyzer->index_text ($raw_text, ...); $index->add_spelling(...foreach word in $raw_text...); ... $index->add_document($xpdoc); ... Now, when you say I need to truncate my term lengths to 240, what exactly are we talking about? Truncating $raw_text is obviously not it; are we talking about making sure that each term/word in $raw_text does not exceed 24...

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 running...

...s in the future or is it something which is not likely to happen? Being able to give the correct spelling for an author's name, for example, would be great... Also, I wonder about how to manage the spellings on the long run: - if I add a document, new spellings are added in the database via add_spelling(). - if I remove a document, the spellings for that document won't go away (I mean decrease frequency, delete if 0 or less), unless I call remove_spelling() myself. However, there's no API way to get the list of spellings for that document. - if I modify a document (correcting bad spellin...