Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Israel Herraiz <isra@herraiz.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] Problems with encodings and Ruby 1.9
Date: Tue, 30 Mar 2010 16:19:35 +0200	[thread overview]
Message-ID: <1269957778-sup-2533@duck> (raw)

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


                 reply	other threads:[~2010-03-30 14:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1269957778-sup-2533@duck \
    --to=isra@herraiz.org \
    --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