From: marko.myllymaki@iki.fi (Marko Myllymäki)
Subject: [sup-talk] char. encoding problems - garbled output
Date: Thu, 17 Jan 2008 14:51:51 +0200 [thread overview]
Message-ID: <478F4F67.1040405@iki.fi> (raw)
Hi,
Sup seems very promising email-client for my purposes, good job!
However, I have some problems with wrong character encodings which
garble the sup output a bit unusable...
Uppercase umlaut characters seem to be the biggest problem. But I may
also have some configuration option wrong..
The following mail has weird content-type:
Content-type: multipart/mixed; boundary="===============2134700068=="
And here is the garbled output for that mail, which makes also other
lines in the message list interface garbled :(
----
Yest. 9am laskutus >Some subject text... +/INBOX K?~DYT?~D EHDOTTOMASTI
VIITETT
?~D Jan 15
----
This kind of content-type works fine with umlaut ??????:
Content-type: text/plain; charset=ISO-8859-1; format=flowed
But this doesn't:
Content-type: text/plain; Format=Flowed; Charset=iso-8859-1
I'm not actually sure what causes these problems, there may be something
else too... at the moment I'm using thunderbird email client and it
handles all the encodings well. But I want to change it to Sup :)
-Marko
next reply other threads:[~2008-01-17 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 12:51 Marko Myllymäki [this message]
2008-01-19 17:25 ` William Morgan
2008-01-25 12:09 ` Marko Myllymäki
2008-01-30 17:24 ` 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=478F4F67.1040405@iki.fi \
--to=marko.myllymaki@iki.fi \
/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