[
https://issues.apache.org/jira/browse/DOXIA-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated DOXIA-769:
----------------------------------
Description:
If currently a {{Sink.text()}} is followed by a {{Sink.verbatim(...)}} it is
not emitted on a dedicated line through the {{MarkdownSink}}.
However according to https://spec.commonmark.org/0.31.2/#fenced-code-blocks
{quote}A fenced code block begins with a code fence, preceded by up to three
spaces of indentation.{quote}
was:
If currently a {{Sink.text()}} is followed by a {{Sink.sectionTitle(...)}} with
some text it is not emitted on a dedicated line through the {{MarkdownSink}}.
However according to https://spec.commonmark.org/0.31.2/#atx-headings
{quote} The opening # character may be preceded by up to three spaces of
indentation {quote}
> MarkdownSink: Fenced code blocks must be located at the beginning of a line
> ---------------------------------------------------------------------------
>
> Key: DOXIA-769
> URL: https://issues.apache.org/jira/browse/DOXIA-769
> Project: Maven Doxia
> Issue Type: Bug
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: 2.1.0
>
>
> If currently a {{Sink.text()}} is followed by a {{Sink.verbatim(...)}} it is
> not emitted on a dedicated line through the {{MarkdownSink}}.
> However according to https://spec.commonmark.org/0.31.2/#fenced-code-blocks
> {quote}A fenced code block begins with a code fence, preceded by up to three
> spaces of indentation.{quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
