<div class="markdown">
<p>I ran across this when I was testing my reply scripts, but this seems to happen with the regular reply as well. I have an HTML message that has encoded XML in it. Here’s an excerpt. </p>

<pre><code><br>  
&lt;program TMSId=&quot;SP002535400000&quot; rootId=&quot;8893140&quot; connectorId=&quot;SP002535400000&quot; seriesId=&quot;191276&quot;&gt;<br>  
&lt;titles&gt;<br>  
&lt;title size=&quot;120&quot; type=&quot;full&quot; lang=&quot;en&quot;&gt;NBA Basketball&lt;/title&gt;<br>  
&lt;title size=&quot;10&quot; type=&quot;red&quot; lang=&quot;en&quot;&gt;Basketball&lt;/title&gt;<br>  
&lt;/titles&gt;<br>  
&lt;progType&gt;Sports event&lt;/progType&gt;<br>  
&lt;genres&gt;<br>  
&lt;genre genreId=&quot;59&quot;&gt;Basketball&lt;/genre&gt;<br>  
&lt;/genres&gt;<br>  
</code></pre>

<p>When I reply to that message, the HTML that is sent to tidy has all the < characters decoded already. </p>

<pre><code>> <program TMSId="SP002535400000" rootId="8893140" connectorId="SP002535400000" seriesId="191276">  
> <titles>  
> <title size="120" type="full" lang="en">NBA Basketball</title>  
> <title size="10" type="red" lang="en">Basketball</title>  
> </titles>  
> <progType>Sports event</progType>  
> <genres>  
> <genre genreId="59">Basketball</genre>  
> </genres>  
</code></pre>

<p>But then that’s going to get processed by the html to markdown script as though it were html. And when it displays in the mail program, it’s going to be interpreted as HTML as well (what’s left of it). </p>

<p>Incidentally. I found a way to get around having my HTML prefixed by “> ”. </p>

<p><code>"r"     = ( "replyAll:", "selectAll:", "decreaseQuoteLevel:", "deselectAll:", "moveToBeginningOfDocument:", "insertNewline:", "insertNewline:", "moveToBeginningOfDocument:" );</code> </p>

</div>