Bug 225692 - Sent inline images are converted to PNG
Summary: Sent inline images are converted to PNG
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 4.7
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-06 09:08 UTC by Aurelien Bompard
Modified: 2017-01-07 22:45 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Aurelien Bompard 2010-02-06 09:08:39 UTC 
Version:           1.12.4 (using KDE 4.3.5)
Compiler:          gcc 4.4.2 
OS:                Linux
Installed from:    Fedora RPMs

I tried to use the HTML editor toolbar to insert an animated GIF image in my message. It attached fine (it was not animated but in the compose window that's not a problem).
When I sent it to the recipient, the image had been converted to PNG, and thus, was not animated (it was only showing the first frame).

You can try with any animated GIF, for example one of those : http://www.easyfreesmileys.com/Free-Party-Smileys/
Comment 1 Marek 2011-02-11 12:41:32 UTC 
Still same in KUBUNTU Lucid KDE 4.4.5.
It would be fantastic to send animated gif smileys
Comment 2 Laurent Montel 2011-09-14 16:31:40 UTC 
I can confirm it in kmail-4.7
Will look at it
Comment 3 Laurent Montel 2011-09-14 16:46:08 UTC 
Ok qt can't save as GIF (and it's optional) so we can't do it.
too bad.
Comment 4 Christophe Marin 2012-01-08 01:27:30 UTC 
reassign
Comment 5 Denis Kurz 2016-09-24 17:55:36 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 6 Denis Kurz 2017-01-07 22:45:54 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.