I’ve been doing long-form writing in LogSeq and now need to export to Word for formatting and exchange with others. I played with the “copy / export as” menu, all options end up as ‘unformatted’ text in Word. Meaning, the imported text in Word neither entails the outline nor the heading structure.
Are there good practices or work arounds for export to Word that maintain the nested outline structure, or - better - convert hierarchy levels from LogSeq to Word headline levels ?
I have now converted the Markdown file to docx with pandoc, which preserves the outline structure. However, the conversation generates incredibly long indentations, such that the converted doc is still quite unusable. Every single line needs to be converted manually in suitable format.
Currently, I could only advise against using LogSeq for long form writing if the goal is to later transfer to Word. The overhead created for formatting is insane.
1.- Installed Obsidian
2.- Used the same folder for Obsidian and Logseq, so all Logseq pages are now visible in Obsidian.
3.- Installed the outliner plugin in obsidian (not sure if needed)
4.- Installed the pandoc export plugin in obsidian.
5.- When I want to export to word, I Open in Obsidian the page I made in Logseq
6.- Export it to word
The result is very usable. And i think playing with Obsidian and Logseq on the same files, is not a very bad idea. I think there may be other user cases for having both working toghether.
If you want you can edit the file or add a TOC with Insert and then Table of contents.
Save your file, go to File, then Download and finally Microsoft Word (.docx).
There are several file formats to choose from:
Microsoft Word (.docx)
OpenDocument Format (.odt)
Rich Text Format (.rtf)
PDF Document (.pdf)
Plain Text (.txt)
Web Page (.html, zipped)
EPUB Publication (.epub)
Markdown (md)