commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "michael tobias (JIRA)" <>
Subject [jira] [Commented] (CODEC-187) Beider Morse Phonetic Matching producing incorrect tokens
Date Thu, 12 Jun 2014 23:45:03 GMT


michael tobias commented on CODEC-187:

OK I have it working. There were TWO copies and I changed the wrong one.

BUT I am afraid the BUG is still not fixed.

GENERIC APPROX is now good for the (limited) testing I have done but ASHKENAZI APPROX is unchanged:

ASHKENAZI APPROX: - fails dreadfully!
Should create tokens: abram abrom avram avrom obram obrom ovram ovrom Ybram Ybrom ombram ombrom
imbram imbrom
Solr creates: abrAm AvrAm BbrAm

I can supply the relevant debug info if you need it.


> Beider Morse Phonetic Matching producing incorrect tokens
> ---------------------------------------------------------
>                 Key: CODEC-187
>                 URL:
>             Project: Commons Codec
>          Issue Type: Bug
>    Affects Versions: 1.9
>            Reporter: michael tobias
>            Priority: Minor
>             Fix For: 1.10
>         Attachments: CODEC-187.patch
> I believe the Beider Morse Phonetic Matching algorithm was added in Commons Codec 1.6
> The BMPM algorithm is an EVOLVING algorithm that is currently on version 3.02 though
it had been static since version 3.01 dated 19 Dec 2011 (it was first available as opensource
as version 1.00 on 6 May 2009).
> I can see nothing in the Commons Codec Docs to say which version of BMPM was implemented
so I am not sure if the problem with the algorithm as coded in the Codec is simply an old
version or whether there are more basic problems with the implementation.
> How do I determine the version of the algorithm that was implemented in the Commons Codec?
> How do we ensure that the algorithm is updated if/when the BMPM algorithm changes?
> How do we ensure that the algorithm as coded in the Commons Codec is accurate and working
as expected?

This message was sent by Atlassian JIRA

View raw message