Well obviously the meta argument, taking a step back, is if the community insists on porting to ruby, doing all the work for him, such that the happy and cooperative leader can now collect sweet support contracts from MORE corporate users and increase the resume fodder value of his original product...
What looks better on dude's resume:
Author of a Java library with 1000 users resulting in $50K/yr support contract revenue
or
Author of a multiplatform Java and Ruby library with 2000 users resulting in $100K/yr support contract revenue
or
Author of a Java library, got into a fight with the ruby community mostly because I don't know the difference between licenses, copyrights, and patents, and now I've only got 500 users and $25K/yr of revenue
[0] : https://github.com/threedaymonk/text/issues/21#issuecomment-...
https://drive.google.com/viewerng/viewer?url=patentimages.st...
Searching on the USPTO website returns no related patents:
http://patft.uspto.gov/netahtml/PTO/search-bool.html
The indication, to me, is that the patent has not made it past the application process.
Systems such as this, however, have enjoyed patent protection in the past (Soundex, notably), and his own metaphone and double metaphone systems are cited in several other patents. Google patent search is your friend here.
Snarky comment: The USPTO has a habit of not denying any applications.