Bug 352978 - If using identity based templates signature looses html format
Summary: If using identity based templates signature looses html format
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: commands and actions (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-21 12:06 UTC by Maarten
Modified: 2018-01-31 16:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maarten 2015-09-21 12:06:48 UTC
Note, the version is 4.14.9.
In Identity I defined a html signature with some monospace characters. I also defined a template for a new message like:
-------------------------------------------------------------------------
%REM="Standardvorlage für neue Nachrichten"%-
Sehr geehrte/r Frau/Herr,

%CURSOR

Mit freundliche Grüßen
M. B.

--
%SIGNATURE
-------------------------------------------------------------------------
The signature will not be formatted according to the html definitions but simply as raw text.

Reproducible: Always

Steps to Reproduce:
1. create html signature
2. create a template with variable %SIGNATURE
3. write new message

Actual Results:  
Raw text signature

Expected Results:  
HTML formatted signature
Comment 1 Denis Kurz 2017-06-23 20:21:05 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-01-31 16:54:20 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.