[
https://issues.apache.org/jira/browse/DOXIA-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909899#comment-17909899
]
Michael Osipov edited comment on DOXIA-767 at 1/5/25 3:09 PM:
--------------------------------------------------------------
Yep, the current behavior is wrong. Line breaks need to be handled according to
the output specification. In other words: Make it consistent!
was (Author: michael-o):
Yep, the current behavior is wrong. Line breaks need to be handled according to
the output specification.
> 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)
