oxeron

This plugin creates a XML posts.xml file containing posts from your blog. 
This xml file can then be used to display your posts on another website using PHP or Flash. 
Based on Valentin Karailiev’s karailievs-sitemap plugin
<h4>Changes in version 0.2</h4>
<ul>
<li>Using backend scripts from WP to fetch data from database (@Ludovic)</li>
<li>Display debug error if occurs (@Ludovic)</li>
<li>Redesigned admin panel to add more informations (@Olivier)</li>
<li>User must now check boxes to choose the categories of posts to export, instead of providing an ID list (@Olivier)</li>
<li>User can choose to export xxx posts per category or posts not older than yyy days (@Olivier)</li>
<li>User can choose which items to export (date, url, category name, etc…) (@Olivier)</li>
</ul>

oxyXML generator

This plugin creates a XML file from your posts in order to display them on another website, using PHP or Flash.

Scott Reilly

This plugin preserves formatting of code for display by preventing its modification by WordPress and other plugins while also retaining whitespace.
NOTE: This plugin does NOT handle posts containing blocks. For such posts, use the built-in code or preformatted blocks to format your code for display. However, this plugin would still be needed if you have text-based posts from before using the blocks-based editor.
NOTE: Use of the visual text editor will pose problems as it can mangle your intent in terms of <code>code</code> tags. I strongly suggest you not use the visual editor in conjunction with this plugin as I have taken no effort to make the two compatible.
Notes:
Basically, you can just paste code into <code>code</code>, <code>pre</code>, and/or other tags you additionally specify and this plugin will:
<ul>
<li>Prevent WordPress from HTML-encoding text (i.e. single- and double-quotes will not become curly; “–” and “—” will not become en dash and em dash, respectively; “…” will not become a horizontal ellipsis, etc)</li>
<li>Prevent most other plugins from modifying preserved code</li>
<li>Prevent shortcodes from being processed</li>
<li>Optionally preserve whitespace (in a variety of methods)</li>
<li>Optionally preserve code added in comments</li>
</ul>
Keep these things in mind:
<ul>
<li>ALL embedded HTML tags and HTML entities will be rendered as text to browsers, appearing exactly as you wrote them (including any <code>br</code> tags).</li>
<li>By default this plugin filters ‘the_content’ (post content), ‘the_excerpt’ (post excerpt), and ‘get_comment_text (comment content)’.</li>
</ul>
Example:
A post containing this within <code>code</code> tags:
<pre><code>$wpdb->query("
 INSERT INTO $tablepostmeta
 (post_id,meta_key,meta_value)
 VALUES ('$post_id','link','$extended')
");
</code></pre>
Would, with this plugin enabled, look in a browser pretty much how it does above, instead of like:
<pre><code>$wpdb->query(&#8212;
INSERT INTO $tablepostmeta
(post_id,meta_key,meta_value)
VALUES ('$post_id','link','$extended')
&#8213;);
</code></pre>
Links: <a href="https://coffee2code.com/wp-plugins/preserve-code-formatting/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/preserve-code-formatting/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/preserve-code-formatting/" rel="nofollow ugc">GitHub</a> | <a href="https://coffee2code.com" rel="nofollow ugc">Author Homepage</a>

Preserve Code Formatting

Preserve formatting of code for display by preventing its modification by WordPress and other plugins while also retaining whitespace.

oxyXML generator vs Preserve Code Formatting