Non leading whitespace in merge proposal comments is not rendered

When commenting in merge proposals I often include snippets from the diff. Whitespace after the leading +-= from the diff is rendered as a single space, making the comments difficult to read. This issue is seriously compromising the experience of using merge proposals.

I have a function in Emacs to sprinkle hard spaces into my comments, which causes the comments to render correctly, but I often forget to use it. I shouldn't have to really; the whitespace ought to be rendered correctly.

Perhaps comments could be passed through a similar function before handing them off to the rendering machinery in Launchpad? My function replaces sequences of 2 spaces with a space followed by a hard space.