[
https://issues.apache.org/jira/browse/CODEC-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082617#comment-13082617
]
Matthew Pocock commented on CODEC-125:
--------------------------------------
Gary and I where talking about altering the interface from String -> String to
CharSequence -> Set<CharSequence>, or something similar. However, this would
mean that BeiderMorseEncoder would no longer extends StringEncoder. Lucene and
Solr use string encoders for indexing. If BeiderMorseEncoder was no longer a
string encoder, would it be available to these down-stream projects?
> Implement a Beider-Morse phonetic matching codec
> ------------------------------------------------
>
> Key: CODEC-125
> URL: https://issues.apache.org/jira/browse/CODEC-125
> Project: Commons Codec
> Issue Type: New Feature
> Reporter: Matthew Pocock
> Priority: Minor
> Attachments: Rule$4$1-All_Objects.html, acz.patch, bm-gg.diff,
> bmpm.patch, bmpm.patch, bmpm.patch, bmpm.patch, bmpm.patch, bmpm.patch,
> bmpm.patch, bmpm.patch, comparator.patch, fightingMemoryChurn.patch,
> fightingMemoryChurn.patch, fixmeInvariant.patch, handleH.patch,
> majorFix.patch, performanceAndBugs.patch, testAllChars-mem-profile.html,
> testEncodeGna.patch
>
>
> I have implemented Beider Morse Phonetic Matching as a codec against the
> commons-codec svn trunk. I would like to contribute this to commons-codec.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
