similar to: Stemmer in Xapian, some questions from student.

Kevin writes: > Of course, I can fix it by myself and check every terms length, but > that will add more overhead to big data computing. How is the overhead different whether your code checks it or Xapian does? Best regards, Adam -- "Oh, we all like motorcycles, to some degree." Adam Sj?gren asjo

Hi, I've just noticed that set_max_wildcard_expansion() has been removed in favour of set_max_expansion() in Xapian. Has the new method been added to the Perl-bindings? We have some old Perl code that uses set_max_wildcard_expansion(), and I have a test of too large expansion that now returns "something terrible happened" instead of"Exception: Wildcard ... expands too much

Hi, In the documentation of FTS lucene, I need little more clarification about this section: -------------------------------------------------- --with-lucene --with-stemmer The second switch is only required if you have compiled libstemmer yourself or if it's included in the CLucene you are using. -------------------------------------------------- I am totally unsure but as I understand,

On Sun, Jan 24, 2016 at 10:28:22PM +0100, Adam Sj?gren wrote: > Olly writes: > > Fixed. Being a wiki, anyone can fix such links - please feel free to. > > I was under the impression that you had to create an account and get it > verified first or something, to prevent spam, as I saw no > "Edit"-button/link, so I didn't even try. You actually already have an

How can i get the source of xapian -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xapian.org/pipermail/xapian-devel/attachments/20081007/cbc58294/attachment-0001.html>

Hi! I am going to use non-snowball russian stemmer with Xapian. There is a good one at http://www.aot.ru. I've found that current implementation of Xapian::Stem does not allow it (there is no public interface for Xapian::Stem::Internal). Do you apply patches? Are there any recommendations for writing patches? Regards, Oleg Obolenskiy highpower at mail.ru

I'm using Xapian as a search back-end on a website. My client has certain search terms that the stemmer does not stem in a way they would like. For example "continuity" stems to "continu", which produces undesirable results in their application. Is there a way to override the stemming of certain words in a way that is compatible with the indexing stemmer and the query

Hello xapian devs, I had shown interest in writing a krovetz stemmer for xapian and spoke to James Aylett about it. Since it was hard to code the stemmer in snowball, I came up with a C++ implementation of the stemmer. But since it is a dictionary based stemmer, im having problems on deciding how to create the dictionary. I did check out some of the implementations of the Krovetz stemmer online

> On 30 Nov 2014, at 17:51, Abhishek Singh Kushwah <abhishek18kushwah at gmail.com> wrote: > > > Two of the implementation of algorithms has already been rejected > > previously due to licenses both being the implementation of porter > > but our xapian use implementation in snowball which i assume is > > under GPL. The only cases I can think you might be

Hey guys Hi :) I've implemented a PaiceHusk stemmer externally So what I am doing right now is passing a pointer to my StemPaiceHusk class(which in turn has been subclassed from Stemimplementation) to the Stem::Stem(StemImplementation *p) constructor .So basically,I have to include "paicehusk.h" in my indexer .However,I now want to make it a part of the Xapian library so that I

On Fri, Jul 08, 2016 at 06:42:23PM -0700, Kevin Duraj wrote: > The issue is that delve was renamed to xapian-delve but documentation > is still saying that delve is delve. Who has access to update the > documentation? > > http://www.linuxfromscratch.org/blfs/view/svn/general/xapian.html That website has nothing to do with Xapian, so you probably need to contact whoever runs it.

On Sun, Jan 24, 2016 at 03:05:31PM +0100, Adam Sj?gren wrote: > James writes: > > It?d be helpful if people could check if they have any problem > > accessing the sites over https. > > Works for me (Iceweasel 43.0.4, browsing from Denmark) - cool! Yes, many thanks to James for working on this. > I spotted these when clicking around a little: > > ? The link

Hello. I'm interested in creating a Hebrew stemmer to use with Xapian. Hebrew is a complicated language to stem, as it uses the semitic "root" system, rather than prefixes and suffixes, and has many irregularities in accidence (morphology). Fortunately, two bright fellows from the Technion University in Israel have already created a Hebrew morphological analyzer as part of their

Hello, As mentioned on the project ideas page, Adding more support for stemmer algorithm, i found an implementation of Krovetz Stemmer Algo in C++ but before working on it to merge it into xapian, i needed help in recognizing the license information associated with the source code. To avoid further licensing issues kindly someone check the link

Hi, is there a xapian stemmer suitable for polish or czech languages? Thanks, Torsten

Hi, I'm using Xapian bindings for Python in my project. How could I use a custom stemmer instead of the included one (Snowball)? The one I'm looking at right now is Hunspell (http://hunspell.sourceforge.net/) which has Python bindings (http://code.google.com/p/pyhunspell/). Thanks in advance, Eugene

Hi everyone, I was working on the Paice-Husk Stemmer, which is a Bite Size Project for Xapian, and I have created a C++ as well as Snowball version of it. I read the algorithm, and picked the rules from here: http://www.comp.lancs.ac.uk/computing/research/stemming/paice/descript.htm The C++ code takes rules as input from a file and generates the stem of given word, whereas the Snowball version

I've noticed some strange results from the stemmer in the Ruby port: irb(main):003:0> @stem.stem_word("anybody") => "anybodi" irb(main):004:0> @stem.stem_word("swimmingly") => "swim" irb(main):005:0> @stem.stem_word("fiercely") => "fierc" irb(main):006:0> @stem.stem_word("fraudulently") =>

Hey Hi Olly :) Thank you so much for your detailed help and feedback on the stemmer patch . Ive begun working on all the points that you mentioned.Will send a new pull request in a couple of days.:) Sorry for the shabby patch,I'm just new to this stuff,Ill do better next time. :) -Regards -Aarsh -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Fri, Jul 22, 2016 at 07:19:43PM -0700, Kevin Duraj wrote: > I would like to propose to change the following code while indexing a > term that is larger than 245 characters and then crashing and aborting > the entire index, we could rather truncate the term to 245 characters > and continue with indexing. Kevin -- I wonder what others are currently doing when this comes up (or if