Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 157 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

It is intended that there is no syntax highlighting in expanded posts on the review page. I disagree with this intention. I think that they should have syntax highlighting. The argument is simple. The review page picks out certain posts that have a higher chance of being of bad quality so that users may review them and act appropriately.

  • With syntax highlighting it will be easier to spot posts in which the code formatting needs editing.
  • With syntax highlighting it will be easier to spot problems in code that might help in answering the question.

Against this it may be argued that the implementation too much work for too little benefit. I disagree. Many posts need improvement and making it easier to find which to improve is a good thing. An example of this is the two points above. Syntax highlighting might make the difference of whether a problem is spotted or not.

share|improve this question
+1. As you said, it is common for first posts to have no formatting. The current implementation makes no distinction between posts which have no formatting, and those that do. – Matt Dec 16 '11 at 10:28
To quote a bit more from balpha's answer that you linked: it is pretty much working as intended, since on the review page, you'd have to implement the "this answer belongs this question, which has these tags, which require this syntax highlighting language" logic to work independently for each post. This is of course possible, but I'm not convinced it's worth the work, since the benefits of this seem pretty small. So maybe: "It is deemed too much work for too little benefit"? – Arjan Dec 16 '11 at 11:04
@Matt, are you saying that the code formatting is not shown? I thought it was just missing the highlighting, but is showing the fixed font formatting? – Arjan Dec 16 '11 at 11:05
@Arjan I think the benefit is worth it. – N.N. Dec 16 '11 at 11:10
Very well. It's just that, to me, "intended" makes it feel like it's done on purpose. Like maybe the highlighting was even explicitly disabled (rather than simply not implemented). (I'm not native English though.) – Arjan Dec 16 '11 at 11:16
There are also cases where someone used a <pre> block instead of a Markdown code block. – Brad Gilbert Dec 16 '11 at 20:25
I am in complete agreement with this. – Xenon Apr 24 '12 at 1:45

You must log in to answer this question.

Browse other questions tagged .