DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25243>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25243

Soundex does not have the "difference" Algorithm

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Normal                      |Enhancement
         OS/Version|Other                       |All
           Platform|Other                       |All
            Version|1.1 Final                   |1.2 Final



------- Additional Comments From [EMAIL PROTECTED]  2003-12-10 00:21 -------
I have added an implementation of the Soundex DIFFERENCE algorithm, a feature
requested by this ticket. Note that this commit only covers adding the
difference() APIs to the Soundex class and not the whole encoder framework. More
on why below.

The DIFFERENCE algorithm seems to be defined only over the Soundex function in
the web browsing and googling I have done. For example: "Returns the difference
between the SOUNDEX values of two character expressions as an integer." from
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_de-dz_8co5.asp

I could see that the following could be added to RefinedSoundex without any issue:

    public int difference(String s1, String s2) throws EncoderException {
        return Soundex.difference(this, s1, s2);
    }

For now though, the difference API is only on Soundex for the following reasons:
The DIFFERENCE algoritm as found (Google) is only over the Soundex function and
unit tests have only been provided for the Soundex function. 

It does not appear at first glance that such a difference function would useful
for base64 and URL encoded strings for example. This is the principal reason why
I have not implemented the feature over the whole codec framework as the patches
submitted do. If we wanted such an implementation to cover the entire coded
framework we would also need unit tests for the difference API for each of the
codec sub-packages. But again, I am not convinced at the use of difference API
for the URL encoding for example. Please clarify and make me see the light
otherwise :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to