Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of lukas.vlcek@gmail.com
 designates 209.85.213.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=UiFypNKCqftNJrfK+IUy573yO6ojPGgQkIzcNISpIpQJBE8YT9/pJDgqdAJ8G0zaT1
         4VjwrjBR8UKY1TePjc1F/indJfrw0Ha3PSgCEsAOIyHKWtc+bdEFlohs2vjsVIKtrzTH
         nYMXa//uLebL0AcLPF1PTdnZ3AWFfqqDzt2A8=
MIME-Version: 1.0
In-Reply-To: <BANLkTimTwgEqq3P63_StXPv+jdNb0BRPSQ@mail.gmail.com>
References: <BANLkTimTwgEqq3P63_StXPv+jdNb0BRPSQ@mail.gmail.com>
From: =?UTF-8?B?THVrw6HFoSBWbMSNZWs=?= <lukas.vlcek@gmail.com>
Date: Mon, 20 Jun 2011 13:19:02 +0200
Message-ID: <BANLkTi=DZY+Q8NGKyj9JCvyVMNnY4GgKRQ@mail.gmail.com>
Subject: Re: KStem custom lexicons configuration possible?
To: dev@lucene.apache.org
Content-Type: multipart/alternative; boundary=20cf302d49c63a960104a622e810

--20cf302d49c63a960104a622e810
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

May be I should show some examples where I think custom configuration can b=
e
useful. Let me give you two examples:

1) As of now, KStem does conflation of both words "connector" and
"connected" to the same term "connect".
2) Contrary it does not do conflation of "transaction" and "transactions" t=
o
the same term.

Having an option to modify internal lexicons I would be able to adapt the
KStem to work better for specific text corpora.

What do you think?

Regards,
Lukas

On Mon, Jun 20, 2011 at 12:55 PM, Luk=C3=A1=C5=A1 Vl=C4=8Dek <lukas.vlcek@g=
mail.com> wrote:

> Hi,
>
> Is there any API in KStem filter for lexicons configuration?
>
> As far as I understand the original code works in such a way that lexicon=
s
> are loaded from files at startup (see
> http://lexicalresearch.com/kstem-doc.txt). The author (Robert Krovetz)
> names possibility to modify lexicons among advantages of KStem compared t=
o
> other stemmers.
>
> Do people not need it? Would it be a useful addition for KStem filter to
> allow custom lexicon configurations in its API?
>
> Regards,
> Lukas
>
> Note: Big kudos to all who participated in bringing KStem into Lucene!
>

--20cf302d49c63a960104a622e810
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

May be I should show some examples where I think custom configuration can b=
e useful. Let me give you two examples:<div><br></div><div>1) As of now, KS=
tem does conflation of both words &quot;connector&quot; and &quot;connected=
&quot; to the same term &quot;connect&quot;.</div>

<div>2) Contrary it does not do conflation of &quot;transaction&quot; and &=
quot;transactions&quot; to the same term.</div><div><br></div><div>Having a=
n option to modify internal lexicons I would be able to adapt the KStem to =
work better for specific text corpora.</div>

<div><br></div><div>What do you think?</div><div><br></div><div>Regards,</d=
iv><div>Lukas<br><div><br><div class=3D"gmail_quote">On Mon, Jun 20, 2011 a=
t 12:55 PM, Luk=C3=A1=C5=A1 Vl=C4=8Dek <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:lukas.vlcek@gmail.com">lukas.vlcek@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Hi,<div><br></div><div>Is there any API in =
KStem filter for lexicons configuration?</div><div><br></div><div>As far as=
 I understand the original code works in such a way that lexicons are loade=
d from files at startup (see=C2=A0<a href=3D"http://lexicalresearch.com/kst=
em-doc.txt" target=3D"_blank">http://lexicalresearch.com/kstem-doc.txt</a>)=
. The author (Robert Krovetz) names possibility to modify lexicons among ad=
vantages of KStem compared to other stemmers.</div>


<div><br></div><div>Do people not need it? Would it be a useful addition fo=
r KStem filter to allow custom lexicon configurations in its API?</div><div=
><br></div><div>Regards,</div><div>Lukas</div><div><br></div><div>Note: Big=
 kudos to all who participated in bringing KStem into Lucene!</div>


</blockquote></div><br></div></div>

--20cf302d49c63a960104a622e810--