[
https://issues.apache.org/jira/browse/DOXIATOOLS-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887139#comment-17887139
]
Konrad Windszus commented on DOXIATOOLS-84:
-------------------------------------------
The SinkWrapper approach does not work, as after parsing the original VLT
statements can no longer be reconstructed (missing new lines, ...).
Even when doing the separation of VLT and regular output before doing the
actual doxia source parsing you might end up with an invalid sequence of Sink
methods (as the VLT semantics are not taken into account there).
> Emit Velocity statements in special Sink events which prevent wrong escaping
> ----------------------------------------------------------------------------
>
> Key: DOXIATOOLS-84
> URL: https://issues.apache.org/jira/browse/DOXIATOOLS-84
> Project: Maven Doxia Tools
> Issue Type: Improvement
> Components: Doxia Converter
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> Velocity is often used together with markup
> (https://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html#Filtering).
> When parsing markup including Velocity statements (directives, references
> and comments) those are included in the regular {{Sink.text(...)}} event.
> Therefore it is often incorrectly escaped when being emitted by a Sink.
> Although usually Velocity is supposed to be executed *before* markup is
> passed to a parser, there are cases where one wants to retain the Velocity
> statements and references in the markup (e.g. for converting from one format
> to another with https://maven.apache.org/doxia/doxia-tools/doxia-converter/).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
