commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell (JIRA)" <>
Subject [jira] Closed: (CODEC-57) Metaphone.metaphone(String) returns an empty string when passed the word "why".
Date Sun, 27 Apr 2008 00:26:56 GMT


Henri Yandell closed CODEC-57.

    Resolution: Won't Fix

I'm marking this as WONTFIX.  I don't think we should change our Metaphone from adhering to
the original algorithm to adhere to PHP's modified algorithm, which looks like it is based
on the Perl Text-Metaphone-1.96 algorithm.

That version states that it changes the algorithm; so either this change is from the Perl
original, or added later to the PHP clone. Looking at the PHP source, it looks like there
are other differences. At least the 'CC'->'GG' one i mentioned above, but looks like others

To fix this, we would need to add a TextMetaphone class that ports the changes made in the
Perl original; but I think licensing will hurt us there. I don't think we can take PHP or
Perl code and put it in Apache licensed code. Implementing by reverse engineering seems like
a very tiring task, I know I don't have the energy for it :)

> Metaphone.metaphone(String) returns an empty string when passed the word "why".
> -------------------------------------------------------------------------------
>                 Key: CODEC-57
>                 URL:
>             Project: Commons Codec
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Commons-codec built from source using jdk 1.4.2.
> OS: Windows XP
> Java Build: 1.4.2
>            Reporter: Adam Wilmore
>             Fix For: 1.4
> An empty string is returned from the Metaphone.metaphone(String) method when passed the
value "why". Variations on the value, such as "wwwhy" and "wwhhhy" also return empty strings.
> This appears to be an issue since other implementations of the metaphone algorithm, namely
the PHP version, returns "H" when passed the value "why".

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message