Linebreaks in Texteditor do not conform to Markdown-Syntax

[daftmilk]

Steps to reproduce

1. Open or create a Textfile in Nextcloud-Webinterface
2. Start writing a paragraph and insert a manual linebreak via METAKEY + RETURN
3. Inspect the file in an external editor or on the commandline

Expected behaviour

At the end (before the actual break) of the line with the manual linebreak, there should be two spaces:

The big brown fox<SPACE><SPACE>
jumps over…

Actual behaviour

Nextcloud inserts a backslash:

The big brown fox\
jumps over…

Server configuration

Nextcloud version: 19.0.1

Background/Workaround

In order to make Nextcloud-Textfiles usable with other Markdown-sensitive apps, I need to fix the Nextcloud-flavour of Markdown. That sucks.

$markdown = preg_replace("/\\\(\\n|\\Z)/","  \n",$nextcloud_flavored_markdown);

[kesselb]

cc @juliushaertl

[juliusknorr]

We follow the commonmark spec where \\n is a valid line break indicator (see example 631 at https://spec.commonmark.org/0.29/#hard-line-breaks), but I agree that using two spaces might instead might be something to look into as an alternative to make the markdown output a bit more readable in plaintext. I'm not sure how easily we can achieve that yet. Moving to the text repo.

[herrtreffler]

@juliushaertl – TextEdit (on Mac OS 10.12.6) and Joplin (1.0.233) works fine with the backslash output from the Text app (as seen in the referred spec). But struggeled with the html output from the Pico CMS app after modify the content function with the "nl2br" twig filter in the themes index.twig file, which results in a html <br /> tag, but leaves the "\" character on line ends in rendered html pages.

[claell]

Also likely related to #593

[MilorES]

The syntax still doesn't work well, now when you put two spaces, when you open it it joins everything, creating chaos in the markdown files.

Source:

What should be seen:

This is how it looks in TEXT:

source after opening it: