https://bugs.kde.org/show_bug.cgi?id=501276
--- Comment #7 from Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> --- (In reply to Roke Julian Lockhart Beedell from comment #6) > Do you have a writing standard for Bugzilla reports? It'd be difficult with > absolutely no markup syntax (unlike GitLab, etc). Apologies. Looking at others reports, it looks like removing header markers (letting them just be standard paragraph text) and code indicators would work, because I see a lot of usage of URI bibliographies to ensure that they don't render the content actually unreadable. (In reply to Nate Graham from comment #5) > s practically unreadable due to the unnecessary formatting that isn't > rendered by Bugzilla Could it be you're seeing what I do at GitHub on my smartphone – backticks rendering *over* text? [^1] If so, that makes a lot more sense. I've been using a monospaced font for so long that I forgot about it. [^1] https://github.com/orgs/community/discussions/144767#discussion-7493333 -- You are receiving this mail because: You are watching all bug changes.
