I formulate this feature request particularly with language sites in mind, but it may also be useful to other Stack Exchanges:
On some, if not all language sites, blockquotes (triggered with a
> at the beginning of the line) are the preferred way to format larger language examples. Now, sometimes, it’s useful to give examples of incorrect language use to illustrate something. In this case it’s desirable that the reader can directly see that the example text is incorrect because:
- Writing that examples are incorrect in the accompanying text can be tedious and break the text flow.
- If the information that an example is incorrect can only be deduced from the accompanying text, it is confusing for readers who only skim a post, e.g., to recapture some information.
- People who are not fluent in the language of the post (which can be English or the language the site is about) may have difficulties understanding the accompanying text and thus might miss that the text is wrong. Since language learners are among these people, they might mislearn aspects of the language due to this.
Right now, there are mainly three options to do this:
- Use HTML strike-through. This has the advantage that it is generally understood, but it makes the text very difficult to read. Also, this is not markdown.
- Use a symbol at the beginning of the example, usually an asterisk (*). This is good to read, but usually only understood by people who know this notation.
- Write “[wrong:]” or similar at the beginning of every example. This is generally understood, but still breaks the reading flow and is somewhat unaesthetic.
Therefore, it would be nice to have a formatting option for such incorrect blockquotes, similar to spoiler markdown. This should be rendered similar to blockquotes but in a way that is generally understood to be negative. To give an example for the blockquote style used by most sites, the background could be tinted red and the left bar could be zigzagged:
While this feature may not be that important, its cost–benefit ratio should be comparable to the spoiler markdown, in particular as its implementation can mostly happen in parallel.