Why is the font of description input boxes not monospace?

Asked by Oxwivi

The description box I'm using right now to write this simply uses the system's default font to render the texts. However, Launchpad does not allow any sort of text formatting, and all texts are published as monospace. Furthermore, the information mostly transmitted via the input, like error messages and terminal outputs, are likely easier read in monospace.

The above being the case, why isn't the description box not coded to display the text in monospace? It should be far more useful to see the texts as it will appear when submitted and make the text more readable and editable for submitter. Should I submit a bug report requesting such a change?

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Colin Watson
Solved:
Last query:
Last reply:
Revision history for this message
Best Colin Watson (cjwatson) said :
#1

That would be the bug I just linked to this question.

Revision history for this message
Colin Watson (cjwatson) said :
#2

Though I'd add that questions (unlike bugs) are in fact not rendered in monospace.

Revision history for this message
Oxwivi (oxwivi) said :
#3

Thanks Colin Watson, that solved my question.

Revision history for this message
Oxwivi (oxwivi) said :
#4

Ah, that is true. But it'd be better served by a markup feature, as the question could include technical details better formatted as monospace.

Revision history for this message
Colin Watson (cjwatson) said :
#5

Possibly. We will hopefully get to proper Markdown support at some point in the not too distant future, but we need to have comment editing in place first as Markdown makes it much more likely that one will make a slight formatting error that one wants to correct.