[
https://issues.apache.org/jira/browse/CODEC-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037653#comment-14037653
]
michael tobias commented on CODEC-187:
--------------------------------------
ok i just tried a name i know generates loads of phonetic tokens (I use it a
lot for testing) and there are discrepancies.
For ASHKENAZI APPROX test the name JARZOMBEK
Steve Morse generates 54 tokens. The Commons Codec generates 48 tokens.
The 'missing' tokens appear to be:
iarzomvik
iorzomvik
xarzombik
xarzomvik
xorzombik
xorzomvik
having said that I am not sure we should be TOO worried as the comparison is
probably good enough in general use - but debugging this example might pinpoint
an error that is more important for other names.
M
> Beider Morse Phonetic Matching producing incorrect tokens
> ---------------------------------------------------------
>
> Key: CODEC-187
> URL: https://issues.apache.org/jira/browse/CODEC-187
> Project: Commons Codec
> Issue Type: Bug
> Affects Versions: 1.9
> Reporter: michael tobias
> Priority: Minor
> Fix For: 1.10
>
> Attachments: CODEC-187.patch, CODEC-187_ashkenazi_approx_any.patch,
> CODEC-187_ashkenazi_approx_any_v2.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
(v6.2#6252)
