Redmine

before pre section

111111111111
code code bold bold italic italic underline underline deleted deleted
222222222222

This issue remains a problem. I'm using Redmine 2.4.3.stable.

I try to display an XML response in a ticket. I use display my xml message nicely, I use the code class="xml" tag for syntax highlighting and the pre tag to keep the indenting. To do so nicely, I need to put the code tag within the pre tag. If I put the pre tag within the code tag, the code is not highlighted. This works well.

However there is no way to escape the code tag if you want to. Maybe since code is not a Textile tag, there is no way to escape it (using e.g. notextile). With or without the code highlighting, If my message itself contains a code tag, I do not manage to display it correctly.

Example:

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Body>
        <test>
            &lt;code&gt;3&lt;/code&gt;
        &lt;test&gt;
    &lt;/soapenv:Body&gt;
&lt;/soapenv:Envelope&gt;

The problem lies IMHO in the fact that in different libraries/plugins are used (CodeRay & RedCloth/Textile) and Redmine does some patching on it, see in the bottom of formatter.rb .

Hello,

I just had the same issue. I need to use the <code> xml tag inside <pre><code class="xml"></code></pre> to correctly describe the issue to our dev team.

The only way to have something "relevant" is to use  , < and > surrounded by @ caracter :

<Response>
    <search>
        <code>3</code>
        <message>OK</message>
        <count>0</count>
        <nextPage>false</nextPage>
        <nextPageUrl/>
    </search>
</Response>

But still, it's not very convenient.

Here is the output when using <code> tag inside <pre><code class="xml"></code></pre>:

<Response>
    <search>
        &lt;code&gt;3&lt;/code&gt;
        &lt;message&gt;OK&lt;/message&gt;
        &lt;count&gt;0&lt;/count&gt;
        &lt;nextPage&gt;false&lt;/nextPage&gt;
        &lt;nextPageUrl/&gt;
    &lt;/search&gt;
&lt;/Response&gt;

Is there any other known workaround? Is it planed to correct this point?

Thanks!