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 777783 - display inline text/* parts
display inline text/* parts
Status: RESOLVED OBSOLETE
Product: geary
Classification: Other
Component: client+engine
master
Other Linux
: Normal enhancement
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on: 769868
Blocks:
 
 
Reported: 2017-01-26 11:15 UTC by Federico Bruni
Modified: 2021-07-05 13:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Federico Bruni 2017-01-26 11:15:08 UTC
This was discussed last July. Eventually I followed Mike's suggestion to open an issue:
https://mail.gnome.org/archives/geary-list/2016-July/msg00048.html

Basically, a text attachment displayed inline does not appear because its type is text/x-lilypond instead of text/plain:

    --=-=-=
    Content-Type: text/x-lilypond
    Content-Disposition: inline; filename=zing.ly
    
    ...other text not visible...

As Mike wrote:

"There's perhaps an argument for simply always displaying text/* parts though, in that since the author of the email added it inline, then regardless of the format it should be displayed since that was the author's intent. That works fine just so long as there aren't any popular, yet broken email clients out there that use "Content-Disposition: inline" when they actually mean something else - I'm not sure if this is the case however."


Mike, you might want to have a look at this commit (bug #713545):

git show 67c4fa2cf74f0180a8317ebb695907ec6f385194
Comment 1 Michael Gratton 2018-04-12 07:31:45 UTC
This will in general depend on cleaning up how we work with multipart message, per Bug 769868.
Comment 2 GNOME Infrastructure Team 2021-07-05 13:24:35 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/geary/-/issues/

Thank you for your understanding and your help.