[
https://issues.apache.org/jira/browse/DOXIA-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910669#comment-17910669
]
Konrad Windszus commented on DOXIA-767:
---------------------------------------
The problem is that there is no Sink method for linebreaks within the Markup
language of the Sink.
Once both {{Sink.text("\n")}} and {{Sink.lineBreak()}}
(https://maven.apache.org/doxia/doxia/doxia-sink-api/apidocs/org/apache/maven/doxia/sink/Sink.html#lineBreak--)
behave the same, there is no way to keep linebreaks in the source only (not
having an effect on rendering result) when converting from e.g. APT to Markdown.
> Clarify block vs inline semantics with regards to whitespaces in Sink API
> -------------------------------------------------------------------------
>
> Key: DOXIA-767
> URL: https://issues.apache.org/jira/browse/DOXIA-767
> Project: Maven Doxia
> Issue Type: Task
> Components: Documentation
> Reporter: Konrad Windszus
> Priority: Major
>
> The javadoc of
> https://maven.apache.org/doxia/doxia/doxia-sink-api/apidocs/org/apache/maven/doxia/sink/Sink.html
> should be clarified with regards to trimming whitespace behaviour for
> block/inline elements. Not necessarily each block Sink element is a block
> element in the desired output format (e.g. XHTML). Most prominently this is
> the case with
> {{Sink.verbatim(Decoration:source)}} which is a block element in Sink API but
> opens an inline element ({{<pre><code>}}) in XHTML.
> See
> https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model/Whitespace.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
