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 751143 - Geary doesn't decode content transfer encoding for preview
Geary doesn't decode content transfer encoding for preview
Status: RESOLVED DUPLICATE of bug 714317
Product: geary
Classification: Other
Component: client
0.10.x
Other Linux
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-06-18 09:12 UTC by Lorenz
Modified: 2016-12-20 13:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Lorenz 2015-06-18 09:12:36 UTC 
Dear developers,

emails encoded with a Base64 encoding are not decoded prior to showing the first couple of words in the message column. It would be nice if the content transfer encoding was decoded prior to showing the beginning of the message there.

The same happens for quoted-printable content transfer encoding (and all other encodings, I suppose), although there the effect is much less annoying (still, it shows =FC instead of ü, etc).

Sometimes it also cuts the preview text off after a couple of characters, but I suppose that's a different bug.

I am using Geary 0.10.0 from the Debian unstable repository.

Thanks for the great email client!
Lorenz
Comment 1 Robert Schroll 2015-06-19 03:01:20 UTC 
See also bug 714317 and bug 713571.

The problem is that these previews are generated before we have the full text of the email.  Thus, we can't parse them into MIME parts and properly get the text to be displayed.  I think the proper solution is to recalculate the preview text once we have the full email downloaded.
Comment 2 Michael Gratton 2016-12-20 13:36:16 UTC 
I think this was actually fixed a while ago, but has definitely been made obsolete by the ongoing work on Bug 714317, so I'm going to mark this as a duplicate.

*** This bug has been marked as a duplicate of bug 714317 ***