Main Area and Open Discussion > General Software Discussion

OPML single line problems with export

(1/1)

Dormouse:
I have been developing a workflow that involves using OPML to move between markdown files and Dynalist/Workflowy, but I have hit a problem with exporting notes from both outliners. Paragraphs work perfectly, but single lines concatenate and sometimes produce a \ at the end. I have tried a number of converters including MarkText and Typora (which uses Pandoc), and the issues exist in each. The samples below are in Typora (Marktext has occasional issues where an extra line feed slips into the middle of a paragraph).

The simplest answer for me is to always use paragraph breaks. But I can't help wondering what is going on with line breaks and whether there is a simple, automated answer to the problem.
OPML single line problems with exportOPML single line problems with exportOPML single line problems with export

Contro:
It seems very interesting for everybody.

How can I try to help you ? Tell me
 :-* :POPML single line problems with export

Dormouse:
Tell me
-Contro (December 30, 2021, 02:41 PM)
--- End quote ---
What I'd like is to avoid the tail (file conversion glitch) wagging the dog (available programs and workflows).
With any solution being lower friction than moving from lines to paragraphs.

Dynalist and Workflowy appear fine for importing each other's opml exports single lines and all.
The problem comes with conversion to markdown.
Typora import concatenates single lines.
MarkText import concatenates single lines.
As do online converters.

I don't understand OPML, but it seems to be a difference of opinion about a setting relating to single lines. But I don't know the setting or how to change it in a simple way. I assume that if I  learned OPML, and Pandoc, and used Pandoc directly, there might be a solution. But I also suspect that route would be higher friction than using paragraphs only.

Dormouse:
I don't understand OPML, but it seems to be a difference of opinion about a setting relating to single lines
-Dormouse (January 03, 2022, 06:57 AM)
--- End quote ---
I've narrowed it down to this character -
The OPML uses it to indicate new line. x2=new para
But Typora has no new lines, only new paragraphs. So x2 recognised, x1 disappears

This leaves me doubting whether there exists a lower friction solution than simply using paragraphs instead of lines.

Dormouse:
But I also suspect that route would be higher friction than using paragraphs only.
-Dormouse (January 03, 2022, 06:57 AM)
--- End quote ---
Options using paragraphs only instead of lines:

* In programs where Enter=new line, type Enter, Enter;
* If writing a long document in Obsidian, WriteMonkey etc, convert the line breaks to paragraph breaks in Editpad;
* Use Typora, MarkText or word processors instead of Obsidian, WriteMonkey (Copy and paste will include simple formatting such as bold, italics + underline in MarkText but not Typora).The degree of extra friction is not that great, which is why it seems like that this is what I will do.

Navigation

[0] Message Index