You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2024/12/22 16:14:00 UTC
[jira] [Commented] (DOXIA-767) Clarify block vs inline semantics with regards to whitespaces in Sink API
[ https://issues.apache.org/jira/browse/DOXIA-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17907695#comment-17907695 ]
Konrad Windszus commented on DOXIA-767:
---------------------------------------
The above quote does no longer apply to HTML5. It really depends on the actual element, e.g. for {{<pre>}} only the leading newline is stripped the rest of whitespace characters is emitted as is.
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)