https://bugs.kde.org/show_bug.cgi?id=456905
--- Comment #3 from James Graham <james.h.gra...@protonmail.com> --- (In reply to Jan Bidler from comment #2) > Hm, I initially encountered it, because I chat on a matrix<->discord bridge > from neochat, and whenever I used newlines, they showed up as double > newlines on discord. That led me to check Element and noticed that it > doesn't generate <br> and \n . > I would find it nice if we'd prettify the source, because the \n don't > really give any meaningful input in formatted_body, although this does seem > like an issue on the bridge software for not ignoring the \n to begin with. It would be interesting to know if that is the bridge or discord that treats the /n as newlines in the formatted body. However if it's causing an actual issue we can put in a fix I don't see that as prettification. We shouldn't break compatibility where it isn't necessary. It shouldn't be too hard to write a string replace to specifically target <br />/n and replace with <br>. We need to keep it specific though as when I used to replace all /n in the formatted body I broke quotes. -- You are receiving this mail because: You are watching all bug changes.
