After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 753870 - Subject charset
Subject charset
Status: RESOLVED FIXED
Product: geary
Classification: Other
Component: composer
unspecified
Other Linux
: Normal normal
: 0.11.2
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-08-20 11:27 UTC by Nikos Roussos
Modified: 2016-07-11 12:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nikos Roussos 2015-08-20 11:27:55 UTC
Although emails are being sent as utf-8 (body) when the Subject contains non latin characters is encoded in iso-8859 charset.

Example from the source of an email I sent containing Greek characters:

=?iso8859-7?b?7OXm3fIg7OX03CDs8P3x4fI=?=
Comment 1 Michael Gratton 2016-06-29 00:32:04 UTC
Hi Nikos, thanks for taking the time to report this.

Geary uses the GMime library for encoding its headers, and this behaviour is a deliberate design decision as far as I can tell, to save having to do unnecessary encoding.

Is this behaviour causing particular issues for you? Geary could set an override to always encode non-ASCII strings as UTF-8, but I wonder if that would cause issues for other users?
Comment 2 Nikos Roussos 2016-06-29 10:51:26 UTC
I guess it depends on how other clients handle it. Most of them could probably handle both cases, but since ISO8859* encoding are vastly considered deprecated it's more likely to have a mail client out there that will have issues with the current setting than using utf8.

It's actually how I noticed the bug. One friend complained that he couldn't read my email subjects (using Rainloop).
Comment 3 Jeffrey Stedfast 2016-06-30 00:57:23 UTC
I've dropped iso-8859-7 from GMime's charset map.
Comment 4 Jeffrey Stedfast 2016-06-30 00:58:03 UTC
Oh, oops, I thought this was filed under GMime and not Geary. Apologies for closing.
Comment 5 Michael Gratton 2016-06-30 05:33:10 UTC
No probs. Since we're assuming UTF-8 support by always using it for message body parts, we may as well also always use it for non-ASCII/ISO8859-1 headers.

Fix pushed to master as f10f898. If no one complains I'll cherry pick this for 0.11 as well.
Comment 6 Michael Gratton 2016-07-11 12:43:56 UTC
And cherry picked to geary-0.11 as aef8e47. Thanks!