From: bachjh@googlemail.com (Jörg-Hendrik Bach)
Subject: [sup-talk] sup and ncursesw
Date: Wed, 10 Jun 2009 19:50:49 +0200 [thread overview]
Message-ID: <91de50e10906101050p2d23a74cy1bbfe2e80e69cca2@mail.gmail.com> (raw)
Hi all,
I recently installed sup 0.8 and find I am having problems with umlauts and
accented characters. There is a patch for the ncurses-0.9.1 gem on the sup
wiki ("utf8-issues") which allows the characters to be displayed correctly,
but after applying the patch I can't enter proper text. Hitting 'c' for
compose works, but entering '123' for subject ends in a subject line such
as:
Subject: P<85>??P<85>???C" ?C"
(it's a different set of confused characters each time)
Similar when searching for messages using '\' or 'L'.
I am on ubuntu 9.04 with libncursesw5{,-dev} version 5.7+20090207, sup 0.8.
Any hints?
cheers,
- J?rg-Hendrik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090610/aa0a2b51/attachment.html>
next reply other threads:[~2009-06-10 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 17:50 Jörg-Hendrik Bach [this message]
2009-06-12 20:03 ` William Morgan
2009-06-13 14:17 ` Jörg-Hendrik Bach
2009-06-15 14:04 ` William Morgan
2009-06-17 16:14 ` William Morgan
2009-06-18 9:26 ` Jörg-Hendrik Bach
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=91de50e10906101050p2d23a74cy1bbfe2e80e69cca2@mail.gmail.com \
--to=bachjh@googlemail.com \
/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