Right now the pre tags are mapped to XWiki's verbatim. The content of the verbatim does not support XWiki syntax so the mapping is not quite right because the pre tags seem to support confluence syntax.

We could handle the content of the pre tags as rich content. This way the content of the verbatim will match the content of the pre tag exactly. However, when rendered, the content of the verbatim will be evaluated as plain text rather than XWiki syntax.

This will be the resulting XWiki syntax of the confluence syntax from the issue description:

{{{svn co [[https:~~/~~/example.com/scm/svn/project/trunk>>url:https://example.com/scm/svn/project/trunk||shape="rect"]] Project}}}

{{{The shell scripts (or batch scripts for the Windows platform) in the 

{{code language="none"}}
sh
{{/code}}

 and 

{{code language="none"}}
bat
{{/code}}

 do not implement any advanced logic, but are simply responsible for calling the Python scripts in the 

{{code language="none"}}
lib/python
{{/code}}

 directory.}}} 

With the drawback that the `code` macro and the link will be rendered as plain text.

Alternatively, we could transform the pre tags into some macro that supports xwiki syntax, like `box` macro. Maybe we could also add some class (such as `xwikimodel-verbatim`) to it to have the same font as the verbatim content and the properties of retaining the text format. Or instead of a macro, we could use a group having the said class.

WDYT Michael Hamann Thomas Mortagne