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 696031 - Save as draft, then open later, changes formatting
Save as draft, then open later, changes formatting
Status: RESOLVED DUPLICATE of bug 532492
Product: evolution
Classification: Applications
Component: Mailer
3.4.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[composer]
Depends on:
Blocks:
 
 
Reported: 2013-03-18 05:36 UTC by darren
Modified: 2013-09-02 16:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description darren 2013-03-18 05:36:05 UTC
In Evolution 3.4.4 on openSUSE 12.2

I was editing an email as a reply to another email. Inline quoting with ">" characters.

I saved it as draft, closed Evolution and rebooted. Opened Evolution, opened the draft email to continue editing.

I found the paragraph style of the whole email was now "Preformatted", whereas it should have been "Normal". The text that I was editing had gained carriage returns at the ends of the lines, thus, breaking automatic line wrapping. I manually deleted the carriage returns and replaced them with spaces, and changed the style back to "Normal". Now everything seems to be as it should have been.

I'm guessing that when I open an email from the Drafts folder, it appears as though I had highlighted an email and selected "Edit as New Message". The formatting changes are not the expected behaviour. Perhaps the carriage returns appear in the process of saving the draft, which is also not the expected behaviour.

Ideally you should also fix "Edit as New Message", which has similar formatting changes that are neither expected nor desired by the user.
Comment 1 André Klapper 2013-09-02 16:57:51 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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