Timeline for We're switching to CommonMark
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2020 at 8:18 | history | edited | Mithical | CC BY-SA 4.0 | edited body |
| Jun 2, 2020 at 12:42 | comment | added | V2Blast StaffMod | @HamVocke: Thanks for the explanation! That makes sense. | |
| Jun 1, 2020 at 14:42 | comment | added | Ham Vocke StaffMod | @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. | |
| Jun 1, 2020 at 14:13 | comment | added | ilkkachu | @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? :) | |
| Jun 1, 2020 at 14:04 | comment | added | Ham Vocke StaffMod | 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. | |
| Jun 1, 2020 at 12:16 | history | answered | Christian Rau | CC BY-SA 4.0 |