Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Rich Lane <rlane@club.cc.cmu.edu>
To: "Johann Klähn" <kljohann@gmail.com>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Accept ASCII_8BIT in String.check
Date: Wed, 24 Mar 2010 23:20:13 -0400	[thread overview]
Message-ID: <1269487066-sup-656@zyrg.net> (raw)
In-Reply-To: <b0bc07101003241921t5183709j67e7848025aac824@mail.gmail.com>

Excerpts from Johann Klähn's message of 2010-03-24 22:21:32 -0400:
> I was having problems with encoded emails. Using archlinux / ruby
> 1.9.1_p378 Iconv.iconv returns the encoding ASCII_8BIT,
> which was rejected by String.check.
> 
> Before I was getting debug messages like this when converting mails or
> building the index:
>  couldn't transcode text from ISO-8859-1 (ISO-8859-1) to utf8) (...)
> (got unexpected encoding ASCII-8BIT (String::CheckError))
> My String.check now contains:
>   if respond_to?(:encoding) && !(encoding == Encoding::UTF_8 ||
> encoding == Encoding::ASCII || encoding == Encoding::ASCII_8BIT)
> And everything is working as expected. Instead of text.ascii the real
> umlauts are displayed.
> 
> Hope that helps,
> Johann

An ASCII_8BIT string means there's a bug in sup. Please add an assertion
so that the program exits when the encoding is ASCII_8BIT and post the
backtrace. Also, what sup version is this?
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

  reply	other threads:[~2010-03-25  3:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b0bc07101003241915t22d13ea2w26468d9d72df972f@mail.gmail.com>
2010-03-25  2:21 ` Johann Klähn
2010-03-25  3:20   ` Rich Lane [this message]
2010-03-25  8:02     ` Johann Klähn

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=1269487066-sup-656@zyrg.net \
    --to=rlane@club.cc.cmu.edu \
    --cc=kljohann@gmail.com \
    --cc=sup-devel@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