Problem description: Not all formatting options available when editing a question or answer are available in comments.
Steps to reproduce:
1. Open the wiki-style playground thread: http://ask.libreoffice.org/en/question/3598/is-there-a-wiki-style-playground-on-this-site/
2. Try to use any of the following formatting:
a. In-line code: `~/.bashrc`
b. Bug link: fdo#123456
c. Internet link: [wikipedia](http://www.wikipedia.org/)
d. Italic text: *italic*
e. Bold text: **bold**
Current behavior: Text is displayed as plain text in all cases.
Expected behavior: Text is displayed in the formatted form (as occurs in a question or answer).
This has only stopped functioning for the examples shown since the upgrade to Askbot v0.7.48 on 4th July 2013.
Operating System: All
Version: 188.8.131.52 release
Adding Qubit to the CC list. Will leave it to the QA team to confirm.
The corresponding settings:
Settings → Data rules & Formatting → Data entry and display rules →
Editor for the comments 
Enabled: Plain text editor
Disabled: Same editor as for questions and answers
Is it an intentional modification?
Another regression from the previous version of askbot: hard returns.
Two carriage returns (using CTRL-ENTER) in a comment used to render as a single carriage return. That formatting now renders as the empty string.
Personally, I'd like to use the same syntax in comments and in answers (see my suggestion here: http://askbot.org/en/question/10091/why-do-comments-have-a-different-syntax-than-answers/ )
Just a few minor additions. The related AskLO thread (for completeness) is:
It appears the strikethrough syntax does work in comments under v0.7.48. I just tested it here:
The matter of quoting in a comment I am less certain of as I guess I would generally just use quotation marks. Am I misunderstanding what is suggested here in comment #3? The matter of line feed / new line (CTRL+ENTER) rendering as an empty string is confirmed. I don't think I have used this, although it could be useful.
That's correct the default plain text editor in the comments does not support markdown, but it's possible to use the same editor for the comments as the one used for the questions and the answers.
I have just noticed a further issue with how userids are handled. When responding using a comment in this thread:
... I typed "@email@example.com" to direct my comment at the OP instead of the initial comment by manj_k and the resultant text that has displayed is "<@firstname.lastname@example.org">p>@email@example.com". Admittedly this would seem to me an unusual userid, but perhaps this form of userid automatically results from one of the offered signin methods? In any case it needs to be handled better than it currently is (at least for these less common forms).
> it's possible to use the same editor for the comments as the one used for the questions and the answers
Thanks Evgeny. So standard HTML markup will work. Is there a particular HTML markup code that is needed for userid references?
This is a separate issue @firstname.lastname@example.org - apparently does not work for user names that are email addresses. Simply @user works.
RE: editor - just go to the settings available to the admins and change comments editor to "the same as editor for questions".
The current editor for comments does not allow paragraphs, new lines, thus limiting the possibilities to put more clarity into a comment. A better editor would be very helpful and would also decrease the usage of Answers when a Comment could be more appropriate.
What's the status of this bug? Sounds like several bugs being named here. Policy is one bug per issue.
Is this NEW, since Qubit seems to be onfirming this?
(In reply to comment #9)
> What's the status of this bug? Sounds like several bugs being named here.
> Policy is one bug per issue.
I think all/most of these issues are caused by or related to our current comment settings in Askbot. There might be a couple of outliers that don't fit-in, but once we resolve the comment-formatting question, the chaff will fall away and the remaining issues will be easier to spot :-)
> Is this NEW, since Qubit seems to be onfirming this?
I'll mark this as NEW (as it is a real issue and we're working on how best to address it).
See our discussion here (comments on the Question itself):
I would propose to enable
"Editor for the comments: Same editor as for questions and answers"
on a trial basis.
(In reply to comment #11)
> I would propose to enable
> "Editor for the comments: Same editor as for questions and answers"
> on a trial basis.
> Any objections?
Nobody has complained or voiced dissent on the mailing list, so I think it's fine to enable this feature for now.
[I'll go do that now...]
Ok, maybe actually we should have the same editor for the comments as for Q&A to avoid all the confusions.
I am setting this bug RESOLVED as FIXED, since the question editor has now been turned on for the comments as well and appears to work as expected for the cases I originally reported. Thanks to everyone who assisted with this.