From: israel.herraiz@gmail.com (Israel Herraiz)
Subject: [sup-talk] System encoding versus messages encoding
Date: Mon, 21 Apr 2008 22:37:23 +0200 [thread overview]
Message-ID: <691d00b80804211337h32fe47b0l7c5ab0b331ae71af@mail.gmail.com> (raw)
Hi there,
I have been using Sup for a couple of days, and I have found some
problems with the encoding of messages written in ISO-8859-1(5).
The encoding in my system is en_US.UTF-8, but most of the email that I
receive is in Spanish, and usually encoded with ISO-8859-1 (and
sometimes with ISO-8859-15).
When I start Sup, it detects my UTF-8 and tries to decode the messages
with that encoding, that results in hardly readable messages (most of
the sentences where wide characters appear are truncated).
If I start it with "LANG=en_US.ISO-8859-1 sup" it now detects the new
encoding, and the messages are more readable, but I can not see the
right characters because my terminal enconding is UTF-8 (but at least
the sentences are not truncated).
With Mutt (and other email clients), I still use UTF-8 as my system
encoding, and I see ISO-8859-1 messages correctly. The encoding of the
messages is of course included in the headers.
As far as I know (considering what I have read in the documentation
and in the archives of this mailing list), Sup determines the encoding
using the environment variables and tries to decode all the messages
using that encoding. For people working in different languages and
environments (like me, I write in English and Spanish, some people
send me messages in UTF-8, some other in ISO-88159-1), having an
overall encoding for all the messages is not a good solution.
Would it possible to decode each message according to its headers?
Please correct me if I am wrong in any of my assumptions on how Sup
encodes/decodes messages.
By the way, I am using the Git version of Sup (as of today :-).
Cheers,
Israel
next reply other threads:[~2008-04-21 20:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 20:37 Israel Herraiz [this message]
2008-04-22 11:39 ` Shot (Piotr Szotkowski)
2008-04-22 23:18 ` William Morgan
2008-04-23 0:09 ` Israel Herraiz
2008-04-23 2:03 ` William Morgan
2008-04-23 1:08 ` Israel Herraiz
2008-04-23 1:53 ` William Morgan
2008-04-24 19:36 ` Marc Hartstein
2008-04-24 23:10 ` [sup-talk] [PATCH] fixed dlopen of libc for os x Grant Hollingworth
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=691d00b80804211337h32fe47b0l7c5ab0b331ae71af@mail.gmail.com \
--to=israel.herraiz@gmail.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