Re: Unsupported extension in Commonmark_x resulting in alternative output

[Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>]

Obligatory "a Lua filter can help" post:

    function LineBreak ()
      return pandoc.RawInline('markdown', '\\\n')
    end

Save the above to a file and pass it to pandoc via the --lua-filter
command line parameter.

John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> writes:

> This is a bit tricky.  escaped_line_breaks isn't really an
> extension for commonmark, because it is part of the core spec.
> The writer uses two spaces instead; both are supported according
> to the spec, and the writer has to make a choice.
>
> Thomas Byskov Dalgaard <tbdlist-AHfMSizzl90sTMJHDOTzqX9LOBIZ5rWg@public.gmane.org> writes:
>
>> Hi!
>>
>> Think I have found something that is unexpected behaviour when using the commonmark_x format with extensions.
>>
>> Here is the case.
>>
>> I want to convert from Markdown to Commonmark_x. I have read the Commonmark
>> spec, and from here hard line breaks can be inserted either by two spaces or a
>> backslash at the end of a line inside a paragraph.
>>
>> This is fine when I write my Markdown document, but when I convert all
>> backslashes are removed and replaced with two spaces.
>>
>> I have tried to enable the extension escaped_line_breaks but Pandoc says that this extension is not supported.
>>
>> Why is it that Pandoc allows backslashes to be used but not allowed when converting?
>>
>> Best regards Thomas 


-- 
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124