Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Also, seems to be throwing lots of invalid encoding errors
Date: Tue, 30 Oct 2007 13:39:43 -0700	[thread overview]
Message-ID: <1193776545-sup-5951@south> (raw)
In-Reply-To: <671354B2-98BF-4CE7-B8AC-7C55581C46BB@foundinteractive.com>

Excerpts from Timothy Johnson's message of Fri Oct 12 10:51:41 -0700 2007:
> Any fixes for this error?
>   warning: error decoding message body from "iso-8859-1": invalid  
> encoding ("utf-8", ""iso-8859-1"")
> and variations on that message.

I'm pretty sure this is just iconv being finnicky. I think it happens
when there's something about the message that it doesn't like when
converting between those two character sets.

At any rate, it's not fatal and I'm not sure that there's really a good
solution without rewriting the Ruby iconv bridge, which is basically a
one-method API.

-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2007-10-30 20:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12 17:51 Timothy Johnson
2007-10-30 20:39 ` William Morgan [this message]
2007-10-14  9:26 Nicolas Pouillard

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=1193776545-sup-5951@south \
    --to=wmorgan-sup@masanjin.net \
    /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