https://bugs.kde.org/show_bug.cgi?id=223616
--- Comment #7 from Bernd Oliver Sünderhauf <[email protected]> --- Created attachment 75448 --> https://bugs.kde.org/attachment.cgi?id=75448&action=edit Testcase: eml file This is still a wishlist item, rather than a bug, as long as real world testcases, where this otherwise useful (and common) behaviour distorts the message content, can't be fixed appropriately. I prepared a testcase and comparing Thunderbird and Kmail rendering. Firstly, Thunderbird renders *bold*, /italics/ and _underscore_ but doesn't remove the markup. This might be preferable because it ensures no information gets lost, though it is visually less appealing. So if we stick with our way, we need to be 100% on the secure side. In more complex cases, both clients to some extent show inconsistentencies, such as: - the way precendence is handled in multi-formatting, with both browsers showing inconsistencies (why don't we actually render */text/* both italics and bold?) - Thunderbird render /var/log/ in italics, and *foo*bar* in bold while we don't - We render numeric-only expressions in bold/italics/whatever, while Thunderbird doesn't - We render *_foo* bold, but not /*foo* - while Thunderbird does it the other way around. Firstly, I'd propose to making an informed decision whether we want to keep on removing the markup. If yes, then we need to be more careful about potentially incorrect, potentially complex expressions. In any case, multi-format rendering should be at least handled in a consistent way, possibly multi-formatted with the exception of /*foo*/ (which is comment markup), or - the other way around - ignoring multiple formatting altogether. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
