deprecation warning on ruby 1.9.3 about mms2r

[monde]

I've been wondering what to do about it myself. Thanks for putting this in an issue for others to see. We've a bunch of headaches trying to deal with UTF in a manner which is suitable to all.

[noctivityinc]

Did you ever come up with a solution for this? Im using 1.9.3 and Rails 3.2 and definitely have an issue with this requirements. The warning says to use use String#encode instead.

[noctivityinc]

And here is an interesting article that might help:
http://stackoverflow.com/questions/9126782/how-to-change-deprecated-iconv-to-stringencode-for-invalid-utf8-correction

[monde]

thanks for the link, I'll look into this again tonight

[monde]

I started hacking on this last night, I've almost completed the refactor that is suitable for Ruby 1.8 and 1.9. I'm hoping I can release it tonight.

[noctivityinc]

Awesome! Let me know when you want me to test.

Best,

Josh

Joshua Lippiner
Noctivity Inc.
.: [email protected]
.: 704-323-5661 tele
.: 310-919-3035 fax

On Oct 18, 2012, at 12:22 PM, Mike Mondragon [email protected] wrote:

I started hacking on this last night, I've almost completed the refactor that is suitable for Ruby 1.8 and 1.9. I'm hoping I can release it tonight.

—
Reply to this email directly or view it on GitHub.

[monde]

pushed MMS2R 3.9.0 tonight, let me know how it goes. I'm running it out in a production app that uses ruby 1.9.3 myself.

[noctivityinc]

Seems to work great. Thanks.

Sent from my  iPhone

On Oct 19, 2012, at 2:49 AM, Mike Mondragon [email protected] wrote:

pushed MMS2R 3.9.0 tonight, let me know how it goes. I'm running it out in a production app that uses ruby 1.9.3 myself.

—
Reply to this email directly or view it on GitHub.