Edit - Meta Stack Exchange

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*

Rev

3

Yes, the migration will fix compatibility issues in a post's Markdown automatically as good as we can. Chances are, there are some fixes that we haven't covered yet but most trivial issues will be fixed automatically. To reiterate: if we can't fix a post automatically and we'll discover that the new HTML would look differently, we will not touch this post at all.

Ham Vocke
– Ham Vocke StaffMod

2020-06-01 14:04:36 +00:00
Commented Jun 1, 2020 at 14:04
3

@HamVocke, what does "not touch this post at all" mean here, exactly? that the source and rendered content would same as they were, and it will blow up then if anyone edits it, when the new parser processes the source? :)

ilkkachu
– ilkkachu

2020-06-01 14:13:02 +00:00
Commented Jun 1, 2020 at 14:13
12

@ilkkachu that's pretty spot on, yes. Whenever we find one of these posts, we'll save it so we can investigate what's going on. I expect that most of these occurrences will be trivial. The next person editing won't even notice that something's changed. For those cases where the post looks fundamentally different, we'll add more automatic fixes and re-run the migration. It's a matter of trade-offs. We could put in the work and fix every single issue carefully or focus on the big ones, ignore the trivial ones and cause mild inconvenience if someone edits a post moving forward.

Ham Vocke
– Ham Vocke StaffMod

2020-06-01 14:42:17 +00:00
Commented Jun 1, 2020 at 14:42
@HamVocke: Thanks for the explanation! That makes sense.

V2Blast
– V2Blast StaffMod

2020-06-02 12:42:26 +00:00
Commented Jun 2, 2020 at 12:42

Add a comment |

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

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>

formatting help »
answering help »