From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.79.9 with SMTP id c9cs636agb; Fri, 6 Nov 2009 19:28:36 -0800 (PST) Received: by 10.224.104.130 with SMTP id p2mr2836709qao.164.1257564515363; Fri, 06 Nov 2009 19:28:35 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 1si720414qyk.70.2009.11.06.19.28.33; Fri, 06 Nov 2009 19:28:35 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id BF2841D78866; Fri, 6 Nov 2009 22:28:33 -0500 (EST) X-Greylist: delayed 359 seconds by postgrey-1.31 at rubycentral.org; Fri, 06 Nov 2009 22:28:26 EST Received: from mail-fx0-f226.google.com (mail-fx0-f226.google.com [209.85.220.226]) by rubyforge.org (Postfix) with ESMTP id F0DE21D78863 for ; Fri, 6 Nov 2009 22:28:27 -0500 (EST) Received: by fxm26 with SMTP id 26so509544fxm.19 for ; Fri, 06 Nov 2009 19:28:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=jUJ/+dVGmg6hUvutevr6roxnAk3tfUmGZ0I+NXpW8eg=; b=qmRlruUArgsIgE43avUFI3DLDR0zbWwhZEUUsnfWtdLNhWn1LaoVqPQVHLXpqDfZve B3Gw2Q0QLYm5W4yRlVJvOGKnbgEX5rynSKraNrvT6B5hi3MUaajxCY+0w7szetgBC4gQ VQivgWwbVpkSbdnpvw3JCP/Hy5vQ40zH+3o0Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=A3ufEyEuYEttamhEUpItH5VeiHrr1kbS5sNpkJV12NdxutIJW4O9FZN2m5fancFbVD HHD1Szslo+8okz/iFa2fB0PMFnkq/tdjc4wo2qN5kUM1qCHqsxacnfjradPubzf1hVdu pQoPBYYCmTduWLmLuI4ik+39Bz/TqSazfUwXg= MIME-Version: 1.0 Received: by 10.204.26.134 with SMTP id e6mr5390716bkc.87.1257564148472; Fri, 06 Nov 2009 19:22:28 -0800 (PST) Date: Fri, 6 Nov 2009 22:22:28 -0500 Message-ID: <80055d7c0911061922w64ef7cb0qf0c7bed008cc728c@mail.gmail.com> From: Andrei Thorp To: sup-talk@rubyforge.org Subject: [sup-talk] Ruby 1.9: encodings X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org 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