Markdown syntax doesn't work well from Logseq to Substack

Questions & Help
1

I like using Logseq to write and I also post writings on Substack.

When I copy/paste writings from Logseq to Substack, the markdown syntax didn’t perform well.

Is there a simple way that can make it work?

e.g.
Writing in Logseq
image
Ctrl-C, Ctrl-P to Substack
image

“Copy to clipboard” from Logseq

image
image680×631 8.43 KB

Result on Substack
image

2
  • Logseq is an outliner, so it uses its own flavor of markdown.
  • What do you mean by “didn’t perform well”?
    • Is it the empty line in between the blocks?
    • Have you experimented with the options at the bottom?
3

The Markdown you show in the screenshots is “standard” Markdown (as far as we can talk about standards, but a hashtag for a heading is standard in any MD flavor). In this case, it more looks like the issue is with Substack not parsing Markdown when you paste it.

And as mentaloid said: play around with the exporting options in Logseq (though this won’t solve the issue on the Substack side, so I recommend contacting them and explaining that pasted Markdown isn’t getting parsed).

1 Like
4

I assume if I copy/paste this from Logseq to Substack
image

It will show this on Substack

image
image606×109 5.54 KB

Instaed, it shows these two results
image

image

No, I try coping/pasting h1 Markdown from Notion to Substack, and Substack handled it well.

I did exhaust those exporting options, they didn’t work.

5

Seems like Substack doesn’t officially support markdown:

Maybe Notion provides a non-markdown format when copying.

1 Like
6

This must be it.

@jesse_Chen I just experimented by copy-pasting a bunch of blocks from Logseq into Substack, and the formatting came along. But I selected the blocks directly; I didn’t use the exporting option. It’s important to select the whole block, not just select all of its contents. (pressing Esc when editing a block will select it; selecting multiple blocks will always select the whole blocks).

The downside of this is that the bullets come along, so you’ll have to remove those in the Substack editor.

7

Looks like I had wrong presumption right from the beginning.
Thank you for helping me figuring it out.

@Ramses Exporting option would solve the bullets problem. It’s just the h1 markdown issue bothered me. Yet, it seems like Substack’s issue. I’m thankful for your support.

1 Like
8

If you need to export into other RichText editors try to switch Logseq to Document Mode and copy/paste that rendered HTML as RichText and try to paste that.

There are several nice approaches that can löead to success but are not obvious and need some inbetween steps.

First of all, you need to understand the way the clipboard is treated between different applications.

In the clipboard, different flavours exist next to each other:

  • plain text including csv or tab seperated tables as text
  • Rich text including markup, fonts etc.
  • plain HTML
  • native application specific flavours: markdown, SVG, PDF

These native application-specific flavours feature the information that this code belongs to specific application and only if the receiving application understands this flavour it is used.

The flavour markup has to be included by the providing application.

Extreme situation is offering a text selection as an image.

These useful plugins for Logseq desktop to get a rich export are not available anymore on github

No traces left…

You could export as HTML including a nice TOC and then print to PDF in Chrome preserving the TOC links to skip to the target page.

From this HTML you could also copy paste sometimes better as from Logseq Document Mode, since you had a chance to edit the HTML before proceeding.