From: Andrei Thorp <garoth@gmail.com>
To: sup-talk@rubyforge.org
Subject: [sup-talk] Ruby 1.9: encodings
Date: Fri, 6 Nov 2009 22:22:28 -0500 [thread overview]
Message-ID: <80055d7c0911061922w64ef7cb0qf0c7bed008cc728c@mail.gmail.com> (raw)
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@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2009-11-07 3:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-07 3:22 Andrei Thorp [this message]
2009-12-18 15:37 ` Gaute Hope
2009-12-19 18:34 ` William Morgan
2009-12-24 16:43 ` Andrei Thorp
2009-12-24 16:47 ` Andrei Thorp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80055d7c0911061922w64ef7cb0qf0c7bed008cc728c@mail.gmail.com \
--to=garoth@gmail.com \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox