You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- 17Your understanding is perfectly correct. In the revision history we calculate and diff a post's HTML on the fly based on the revision's markdown source. That means that after switching over to CommonMark, even revisions that predate the CommonMark migration will be rendered with the new CommonMark renderer. I know, that's less than stellar but it's all we can do if we don't want to keep the old renderer around forever.Ham Vocke– Ham Vocke StaffMod2020-06-02 08:40:56 +00:00Commented Jun 2, 2020 at 8:40
- 1@HamVocke - perhaps, once the switcheroo has been performed on all the sites, and everything that can go wrong has gone wrong (and subsequently been fixed) - consider running the updated migrator script on the earlier post revisions?Robotnik– Robotnik2020-06-03 05:52:43 +00:00Commented Jun 3, 2020 at 5:52
- 8@Robotnik I think that would make it impossible to audit the changes. While the current way of updating simply makes a new revision, what you suggest will change the revisions themselves, leaving nothing to compare them with. That'd be awful IMO.Ruslan– Ruslan2020-06-03 18:20:58 +00:00Commented Jun 3, 2020 at 18:20
- 2@HamVocke "That means that after switching over to CommonMark, even revisions that predate the CommonMark migration will be rendered with the new CommonMark renderer." In that case, please consider open-sourcing the client-side renderer so that it can be turned into an add-on/userscript for viewing old revisions.kelvin– kelvin2020-06-04 11:39:07 +00:00Commented Jun 4, 2020 at 11:39
- 3@kelvin you can find the source code for our old client-side markdown renderer on GitHub. Note that the published version is missing the latest significant feature addition, which is the ability to handle nested code blocks. I hope this can be helpful nevertheless.Ham Vocke– Ham Vocke StaffMod2020-06-04 12:26:12 +00:00Commented Jun 4, 2020 at 12:26
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. stack-overflow), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you