Eh, bad news.
So I've been testing Sup in an 1.9 environment further, and I have
found that there are a great deal of problems with regards to
encodings. "invalid byte sequence in US-ASCII" is something you'll see
frequently. This seems to be when parsing messages that have non-ascii
chararacters.
Ouch :(
Has this already been taken care of in the git somewhere?
-AT
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk