Hi Giacomo & Jeff,

This should be caused by Solaris iconv libraries.

Evolution always tries to use the smallest charset to describe mail
text. For example, when you specify ISO-8859-15, evolution firstly check
whether ASCII is enough. If enough, charset is set as ASCII. Checking is
done by iconv, but unfortunately there's some problem with converting
UTF-8 to ASCII on Solaris. Some non-ASCII characters are wrongly
recognized as valid ASCII characters.

Compared to Evolution, Thunderbird doesn't contain this IA. So its
charset is always identical to your specified one.

Thanks,
-Simon

On Mon, 2006-02-27 at 09:51 -0500, Jeffrey Stedfast wrote:
> Sounds to me like the mails are getting mangled by some third-party mail
> software somewhere because Evolution ALWAYS tags the charset on outgoing
> mail.
> 
> Also, I noticed that the Content-Transfer-Encoding was "8BIT", Evolution
> would say "8bit" not "8BIT" so this definitely suggests mangling by some
> other software - perhaps you should check your mail server software?
> 
> Jeff
> 
> On Mon, 2006-02-27 at 15:29 +0100, Giacomo Tufano wrote:
> > I just discovered (by some angry reply to my messages) that evolution
> > (currently using 2.5.4 on OpenSolaris build 32, but the problem, AFAIK,
> > was existing also in 1.4.x version) do not correctly handle accented
> > characters.
> > 
> > Apparently in the message evo sends the character code header is missing
> > and the text is encoded UTF-8, whatever the coding I choose in the
> > program.
> > 
> > This email as a sample, I'm logged with an it_IT.ISO8859-15 locale in
> > Nevada_32, Edit->Character encoding is 'Western European, New
> > (iso8859-15)'.
> > 
> > The euro gliph don't appear when I press AltGr-E (it works in, say,
> > thunderbird), but appears as '¤'. Every accented char appears as garbage
> > on the receiving side: some sample being 'à' (this is a accented grave)
> > or 'ì' (i accented grave) or '§' (this is the paragraph gliph).
> > 
> > You can see it (from a non evo client in a different locale) if you
> > force (UTF-8) as the encoding (just make a check).
> > 
> > HTML composing apparently works... in the "text only" part of the
> > message (yes, it sends always multipart messages with a text and html
> > part) says:
> > 
> > -
> > Content-type: text/plain
> > Content-transfer-encoding: 8BIT
> > 
> > the text encoded UTF-8
> > -
> > In the html:
> > Content-type: text/html; charset=utf-8
> > Content-transfer-encoding: 7BIT
> > [...]
> > qualit&#224;, &#224; &#232; &#233; &#236; &#242; &#249; &#176;&#167;<BR>
> > -
> > 
> > The html part is readable, of course, from any email client.
> > 
> > Just wandering if nobody noticed this one before and, from another point
> > of view, if there is some Evo user that do not use US keyboard and ASCII
> > text (and, therefore, is not impacted by this problem). Or, may be, it
> > is a Solaris problem...
> > 
> > Any hint/info/workaround/open bug/whatever? I like Evo (I know, probably
> > I'm masochist-kind) but this is (obviously) a blocker for email use, if
> > not using html (that, correctly, it is not always welcome on the
> > receiving side).
> > 
> > Regards,
> > gt
> > 
> > _______________________________________________
> > Evolution-list mailing list
> > Evolution-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/evolution-list
> > 

_______________________________________________
Evolution-list mailing list
Evolution-list@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-list

Reply via email to