From: cjs@weisshuhn.de (Carsten Schölzki)
Subject: [sup-talk] ISO 8859-15 at the header
Date: Thu, 27 Mar 2008 05:49:02 +0100 [thread overview]
Message-ID: <20080327044901.GA12106@weisshuhn.de> (raw)
Hi,
I started trying sup today and it seems to be wonderful for me. Till
now I'm a mutt user for over 10 years - but know I found a reason to
change...
But there is a little problem with the header-encoding. Seems, that
sup doesn't de- or encode ISO 8859-15 correct.
There are no problems with the body or with ISO 8859-1 in the
header.
Did I messed up some settings or is this bug?
I'm using sup v0.4 on MacOS X 10.5.2. - encoding in mutt works fine.
Thanks, Carsten
next reply other threads:[~2008-03-27 4:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 4:49 Carsten Schölzki [this message]
2008-04-03 1:12 ` William Morgan
2008-04-03 14:07 ` Carsten Schölzki
2008-04-05 23:35 ` William Morgan
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=20080327044901.GA12106@weisshuhn.de \
--to=cjs@weisshuhn.de \
/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