From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.103.218.7 with SMTP id v7cs99996muq; Tue, 30 Mar 2010 07:31:52 -0700 (PDT) Received: by 10.224.34.225 with SMTP id m33mr2507453qad.61.1269959511538; Tue, 30 Mar 2010 07:31:51 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 6si5995491qwk.21.2010.03.30.07.31.50; Tue, 30 Mar 2010 07:31:51 -0700 (PDT) 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 6E7971858304; Tue, 30 Mar 2010 10:31:50 -0400 (EDT) Received: from mail-bw0-f212.google.com (mail-bw0-f212.google.com [209.85.218.212]) by rubyforge.org (Postfix) with ESMTP id 9E4E81D799AA for ; Tue, 30 Mar 2010 10:24:58 -0400 (EDT) Received: by bwz4 with SMTP id 4so11165616bwz.19 for ; Tue, 30 Mar 2010 07:24:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:content-type:from:to :subject:date:message-id:user-agent:content-transfer-encoding; bh=GKtv0a2Atq+XOslhMNYJG2WxH/SivRvODp7KVEc6ZL4=; b=HMQDoiVqACAS377SLLIPB0J+VGXU7QqGEUFm4zrbcz5NbG+66FVkFCyJtGUyq54kDN XHdygqw3kwNHCZu+Yo0jJKfYCK3dIzAyLbr3dWHYnw6DYJ5V1Iij+nGmsqmwxvwT0r3X 1h+p7neYGz9IL6dqFzVQnAPreqHfMndGxFJLw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:from:to:subject:date:message-id:user-agent :content-transfer-encoding; b=pMIm6CArXStQSIziG6STzrymnqjPK27tvMl+kSqUa84Yg6PGPdmoZE4E+C/03HxKKY DLcTZJjtuATk8Q/FatFYFwA82zVW2crVeIWFw5GoxYSGmRpg9AMN8jVtE3AE6ry8/ECc 2zeAXykvWhujslfUSXkOGkvJtLMiw0Nb277sY= Received: by 10.204.4.89 with SMTP id 25mr4570985bkq.19.1269959086238; Tue, 30 Mar 2010 07:24:46 -0700 (PDT) Received: from elly (80.174.17.224.dyn.user.ono.com [80.174.17.224]) by mx.google.com with ESMTPS id d5sm48378017bkd.19.2010.03.30.07.24.45 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 30 Mar 2010 07:24:45 -0700 (PDT) From: Israel Herraiz To: sup-talk Date: Tue, 30 Mar 2010 16:19:35 +0200 Message-Id: <1269957778-sup-2533@duck> User-Agent: Sup/git Subject: [sup-talk] Problems with encodings and Ruby 1.9 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Hi all, I am trying out Sup with Ruby 1.9 in ArchLinux, and I am facing some crashes with some messages written in different encodings. Those messages were correctly shown with Ruby 1.8. The problem is that when there are messages with some different encoding. In particular, whenever I get a message with ASCII_8BIT, Sup crashes with the following message: incompatible character encodings: UTF-8 and ASCII-8BIT This both happens in Sup next and in Sup 0.11; I have tried to fix it, touching the check method in utils.rb, without success. Well, actually with partial success, because if at line 719 I change the else condition forcing the charset to be utf-8, the message will be shown, although with wide characters not properly displayed. In a message in sup-devel, Rich pointed out that an ASCII_8BIT string means that there is a bug in Sup [1]. I am willing to debug this, but I have not found yet where the problem is. I can provide a copy of the messages causing this if someone else wants to reproduce this behavior. Any hint about how to fix this? Cheers, Israel _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk