From: anonymous <sup-bugs@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [issue37] special characters still not working
Date: Tue, 29 Dec 2009 13:30:40 +0000 [thread overview]
Message-ID: <1262093440.47.0.488412386269.issue37@masanjin.net> (raw)
In-Reply-To: <1262093440.47.0.488412386269.issue37@masanjin.net>
New submission from anonymous:
I still have problems with special characters. (Namely German "Umlaute"). They
get displayed as M-CM-6 or M-CM-<.
I've tried the (old) patches from the wiki but that didnt help. (I tried the
ncurses patch - the libc one seemed already applied.
I'm running gentoo and installed sup using gem.
----------
messages: 99
nosy: anonymous
priority: bug
ruby_version: ruby 1.8.7 (2009-06-12 patchlevel 174) [x86_64-linux]
status: unread
sup_version: 0.9
title: special characters still not working
_________________________________________
Sup issue tracker <sup-bugs@masanjin.net>
<http://masanjin.net/sup-bugs/issue37>
_________________________________________
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
parent reply other threads:[~2009-12-29 13:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1262093440.47.0.488412386269.issue37@masanjin.net>]
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=1262093440.47.0.488412386269.issue37@masanjin.net \
--to=sup-bugs@masanjin.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