From: Sebastian Lipp <bacuh@riseup.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] Umlauts broken
Date: Fri, 24 May 2013 13:59:14 +0200 [thread overview]
Message-ID: <20130524115914.GA3518@eee.Speedport_W_504V_Typ_A> (raw)
Hi.
I was really happy as I heard, that sup is actively developed again. Too
long time ago I had to leave sup because it got broken more and more...
Just tried to install (via gem) and run it via rbenv under ruby
1.9.3-p327 and 1.9.3-p392. With both I have the problem that characters
like Umlauts are not show correctly. For example: "ä" becomes "\xe4".
When setting $SUP_LOG_LEVEL to debug I get several of those lines:
couldn't transcode text from ASCII (ASCII) to UTF8 ("<20130523193529.GB30"...): got String::CheckError (unexpected encoding ASCII-8BIT)
I'm not sure if this is related to my encoding problems. Any of those
lines seem to be referencing to header lines.
I was long enough without sup so I can wait for the compatibility with
ruby 2.0.0 but I would really prefer to sup again sooner.
So have you any solution, work-around or patch at hand for this problem
or do you have any idea how I can help debug this problem?
LG
basti
--
react!OR :: Frühlingstr. 17 | 87439 Kempten
selbstverwaltetes JuZe :: Infoladen | Umsonstladen | Offener Raum
https://react.or.ke :: Telefon: 0831 52623689
Der react!OR lebt von Dingen, die anderswo übrig sind. Aktuell gesucht:
Mehrfachstecker, Verlängerungskabel, Nähmaschine, Diktiergerät,
Papierschneidebrett, Dosenöffner ... mehr: <https://react.or.ke/suche>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2013-05-24 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 11:59 Sebastian Lipp [this message]
2013-05-24 14:22 ` Gaute Hope
2013-05-25 14:32 ` Sebastian Lipp
2013-05-25 15:07 ` 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=20130524115914.GA3518@eee.Speedport_W_504V_Typ_A \
--to=bacuh@riseup.net \
--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