-3

I thought it would be as simple as starting on one and then copy and pasting to the latter; between SE <> Reddit, whichever was first.

But I've found that it does not always turn out the same.

There are lot of tiny differences in layout, formatting and white space handling that happen during the course of such attempts.

How could one get around this?

6
  • 1
    Markdown isn't even standard between comments, posts and answers. Commonmark should have helped but was only really supported on docs. Commented Jul 23, 2018 at 17:38
  • @JourneymanGeek - You mean this - commonmark.org - Thanks I will look into it. I wonder why people give negative to a valid question/ concern.
    – Alex S
    Commented Jul 23, 2018 at 17:43
  • Yup. It was supposed to help get a standard dialect of markdown but never really happened here :( Commented Jul 23, 2018 at 17:46
  • @JourneymanGeek - Is there a minimalist MD dialect (CM or so) that works most places? Or an Editor that helps or constraints one to such a "schema" or so?
    – Alex S
    Commented Jul 23, 2018 at 17:48
  • 1
    Not as far as I know. Else I would be posting an answer, not comments Commented Jul 23, 2018 at 17:48
  • Kinda like the old Browser wars where HTML stuff was not similarly supported in them but the Basics worked everywhere so if you remained compliant with that Subset then you were safe.. any other stuff and you risked browser compliance issues
    – Alex S
    Commented Jul 23, 2018 at 17:49

1 Answer 1

3

The short answer is "you can't".

The long answer is "maybe someday you'll be able to do this, and you can help a little bit in getting to that day", but we'll get back to that later.

I don't use reddit, but from a quick look at their Markdown guide (okay, technically, that link isn't official, but their actual official page links directly to it), it looks like a superset of Stack-flavored Markdown.

The easiest workaround in practice is to not use the following things in reddit, or manually remove them when copying to Stack:

  • ^ for superscripts
  • ~~ for strikethroughs
  • >!secrets!< for spoiler blocks
  • any kind of table formatting (alternatively, do use it, and wrap it all in a code block when it's on Stack, even though that's semantically wrong)

The reason for all of this is that Markdown itself started out as an imperfect spec, according to Jeff Atwood, one of the co-founders of Stack. As a result, different places made up their own variants with the gaps filled in in ways that were helpful for their individual use cases.

To try to deal with this, Atwood and a few others, including people from both Stack and reddit, started an initiative called CommonMark—although it wasn't always called that; there was some unpleasantness with the guy who created Markdown, the venerable John Gruber of Daring Fireball—which is where you can help (see, I didn't forget what I said at the top of this answer).

CommonMark has a "How can I help?" page that (over)simplifies to "write some code" and "use the thing". On top of that, you can try to lobby various places on the Internet to switch their implementations to CommonMark. For CommonMark here on SE, see Will CommonMark be adopted for SE?.

2
  • Note tht there is a spoiler block. ref Commented Jul 24, 2018 at 12:03
  • 1
    Yes there is a spoiler block, but the syntax is different (>! some stuff !< vs. >! other stuff). Similarly, superscripts and strikethroughs are supported, but with different syntax.
    – SOLO
    Commented Jul 24, 2018 at 13:06

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .