Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Tero Tilus <tero@tilus.net>
To: Sup developers <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Bug: UTF-8 error when sending messages
Date: Sat, 29 Jan 2011 20:17:36 +0200	[thread overview]
Message-ID: <1296324611-sup-2693@tilus.net> (raw)
In-Reply-To: <1296270677-sup-4339@poincare>

Adeel Ahmad Khan, 2011-01-29 05:11:
>     invalid byte sequence in UTF-8
...
> I am using a nearly fresh installation of Sup 0.12.1 with Ruby
> 1.9.2p136.  I have LOCALE="en_US.UTF-8".

Both the errors were from regex matches against message body.  Somehow
your editor doesn't know your locale or is not obeying it.  As a
result non-utf8 stuff gets saved to disk and sup gets confused.

-- 
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  reply	other threads:[~2011-01-29 18:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-29  3:11 Adeel Ahmad Khan
2011-01-29 18:17 ` Tero Tilus [this message]
2011-01-30 15:58 ` Gaute Hope
     [not found] <mailman.75.1296431981.25874.sup-devel@rubyforge.org>
2011-01-31 18:24 ` Adeel Ahmad Khan
2011-02-01 13:34   ` Gaute Hope

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=1296324611-sup-2693@tilus.net \
    --to=tero@tilus.net \
    --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