Janis Elsts

Lets you disable automatic formatting like smart quotes and automatic paragraph creation, and use raw HTML/JS/CSS code in your posts without WordPress messing it up.
Features
With this plugin, you can wrap any part of your post in [raw]…[/raw] tags to prevent WordPress from converting newlines to HTML paragraphs, replacing apostrophes with typographic quotes and so on. This is very useful if you need to add a CSS block or JavaScript to your post.
RawHTML will also add new checkboxes to the “Edit Post” screen that let you disable certain WP filters on a per-post basis. This way you can:
<ul>
<li>Disable wptexturize (the function that creates smart quotes and other typographic characters).</li>
<li>Disable automatic paragraph creation.</li>
<li>Disable image smilies. </li>
<li>Disable convert_chars (the function that converts ampersands to HTML entities and “fixes” some Unicode characters).</li>
</ul>
The free version only supports editing posts in the Text tab (called “HTML” in older WordPress versions). <a href="http://rawhtmlpro.com/?utm_source=wordpress.org&utm_medium=readme_link&utm_campaign=RawHTML%20free" rel="nofollow ugc">Get the Pro version</a> if you want to be able to switch between Text and the Visual editor without WordPress messing up your content.
Compatibility
This plugin doesn’t fully support the Gutenberg editor. As of WordPress 5.0, some Raw HTML features will only work if you use the <a href="https://wordpress.org/plugins/classic-editor/" rel="ugc">Classic Editor</a> plugin.
Usage
To prevent a part of your post or page from being filtered by WordPress, switch to the Text/HTML editor and wrap it in <code>[raw]...[/raw]</code> or <code>...</code> tags. These two versions work exactly the same, except that the latter won’t be visible to your visitors even if you deactivate Raw HTML.
Example :
<pre><code>[raw]
This 

is 

a "test"!
[/raw]
</code></pre>
In this case, the tags will prevent WordPress from inserting paragraph breaks between “This”, “is” and “a “test””, as well as ensure that the double quotes arround “test” are not converted to typographic (curly) quotes.
To avoid problems, only edit posts that contain your custom code in Text/HTML mode. If you’d like to be able to also use the Visual editor, <a href="http://rawhtmlpro.com/?utm_source=wordpress.org&utm_medium=readme_link&utm_campaign=RawHTML%20free" rel="nofollow ugc">get the Pro version</a>. It will make the code betwen [raw] tags appear as a read-only placeholder when viewed in Visual mode, ensuring WordPress doesn’t change it.
Combining shortcodes
By default, shortcodes that are inside [raw] tags will not work. They will just show up as plain text. To enable shortcodes, add the <code>shortcodes=1</code> attribute to the tag:
<pre><code>[raw shortcodes=1]This [shortcode] will be run.[/raw]

[raw]This [shortcode] won't work.[/raw]
</code></pre>
Preserving <code>[raw]</code> code in excerpts
By default, the plugin will automatically remove any code that’s inside <code>[raw]...[/raw]</code> tags from post excerpts. You can prevent that by adding the following line to <code>wp-config.php</code>:
<pre><code>define('RAW_HTML_KEEP_RAW_IN_EXCERPTS', true);
</code></pre>
This will ensure that the plugin doesn’t strip <code>[raw]</code> blocks from automatically generated excerpts.
Notes
Some features of Raw HTML will only work for users who have the “unfiltered_html” capability. In a normal WordPress install that includes the Editor and Administrator roles. In a Multisite install, only the Super Admin has this capability by default.

Raw HTML

Simply works

Lets you use raw HTML or any other code in your posts. You can also disable smart quotes and other automatic formatting on a per-post basis.

Steven

WP-Syntax provides clean syntax highlighting using 
<a href="http://qbnz.com/highlighter/" rel="nofollow ugc">GeSHi</a> — supporting a wide range of popular 
languages. It supports highlighting with or without line numbers and maintains formatting while copying snippets of code 
from the browser.
It avoids conflicts with other 3rd party plugins by running an early 
pre-filter and a late post-filter that substitutes and pulls the code snippets 
out first and then pushes them back in with highlighting at the end. The 
result is source code formatted and highlighted the way you intended.
Usage, Supported Languages, Styling Guidelines, and Release Notes are available 
in the <a href="https://wordpress.org/extend/plugins/wp-syntax/other_notes/" rel="ugc">Other Notes</a> section.
Want to contribute? WP-Syntax can be found on GitHub. <a href="https://github.com/shazahm1/WP-Syntax" rel="nofollow ugc">Fork and submit your pull requests today!</a>
<h4>Basic Usage</h4>
Wrap code blocks with <code><pre lang="LANGUAGE" line="1"></code> and <code></pre></code> where “LANGUAGE” 
is a <a href="http://qbnz.com/highlighter/" rel="nofollow ugc">GeSHi</a> supported language syntax. 
The <code>line</code> attribute is optional. <a href="https://wordpress.org/extend/plugins/wp-syntax/other_notes/" rel="ugc">More usage examples</a>
<h3>Usage</h3>
Wrap code blocks with <code><pre lang="LANGUAGE" line="1"></code> and <code></pre></code> where “LANGUAGE” is a <a href="http://qbnz.com/highlighter/" rel="nofollow ugc">GeSHi</a> supported 
language syntax. See below for a full list of supported languages. 
The <code>line</code> attribute is optional.
Example 1: PHP, no line numbers
<pre><code><pre lang="php">
<div id="foo">
<?php
 function foo() {
 echo "Hello World!\\n";
 }
?>
</div>
</pre>
</code></pre>
Example 2: Java, with line numbers
<pre><code><pre lang="java" line="1">
public class Hello {
 public static void main(String[] args) {
 System.out.println("Hello World!");
 }
}
</pre>
</code></pre>
Example 3: Ruby, with line numbers starting at 18
<pre><code><pre lang="ruby" line="18">
class Example
 def example(arg1)
 return "Hello: " + arg1.to_s
 end
end
</pre>
</code></pre>
Example 4: If your code already has html entities escaped, use <code>escaped="true"</code> as an option
<pre><code><pre lang="xml" escaped="true">
&lt;xml&gt;Hello&lt;/xml&gt;
</pre>
</code></pre>
Example 5: PHP, with line numbers and highlighting a specific line
<pre><code><pre lang="php" line="1" highlight="3">
<div id="foo">
<?php
 function foo() {
 echo "Hello World!\\n";
 }
?>
</div>
</pre>
</code></pre>
Example 6: PHP, with a caption (file and/or file path of the source file)
<pre><code><pre lang="php" src"https://github.com/shazahm1/Connections/blob/master/connections.php">
<div id="foo">
<?php
 function foo() {
 echo "Hello World!\\n";
 }
?>
</div>
</pre><h3>Supported Languages</h3>
</code></pre>
The following languages are most supported in the <code>lang</code> attribute:
abap, actionscript, actionscript3, ada, apache, applescript, apt_sources, asm, 
asp, autoit, avisynth, bash, bf, bibtex, blitzbasic, bnf, boo, c, 
c_mac, caddcl, cadlisp, cil, cfdg, cfm, cmake, cobol, cpp-qt, cpp, 
csharp, css, d, dcs, delphi, diff, div, dos, dot, eiffel, email, erlang, 
fo, fortran, freebasic, genero, gettext, glsl, gml, bnuplot, groovy, haskell, 
hq9plus, html4strict, idl, ini, inno, intercal, io, java, java5, 
javascript, kixtart, klonec, klonecpp, latex, lisp, locobasic, lolcode 
lotusformulas, lotusscript, lscript, lsl2, lua, m68k, make, matlab, mirc, 
modula3, mpasm, mxml, mysql, nsis, oberon2, objc, ocaml-brief, ocaml, 
oobas, oracle11, oracle8, pascal, per, pic16, pixelbender, perl, 
php-brief, php, plsql, povray, powershell, progress, prolog, properties, 
providex, python, qbasic, rails, rebol, reg, robots, ruby, sas, 
scala, scheme, scilab, sdlbasic, smalltalk, smarty, sql, tcl, teraterm, 
text, thinbasic, tsql, typoscript, vb, vbnet, verilog, vhdl, vim, 
visualfoxpro, visualprolog, whitespace, whois, winbatch, xml, xorg_conf, 
xpp, z80
See the <a href="http://qbnz.com/highlighter/geshi-doc.html" rel="nofollow ugc">GeSHi Documentation</a> 
for a full list of supported languages.
(Bold languages just highlight the more popular ones.)
<h3>Styling Guidelines</h3>
WP-Syntax colors code using the default GeSHi colors. It also uses inline 
styling to make sure that code highlights still work in RSS feeds. It uses a 
default <code>wp-syntax.css</code> stylesheet for basic layout. To customize your styling, 
copy the default <code>wp-content/plugins/wp-syntax/wp-syntax.css</code> to your theme’s 
template directory and modify it. If a file named <code>wp-syntax.css</code> exists in 
your theme’s template directory, this stylesheet is used instead of the default. 
This allows theme authors to add their own customizations as they see fit.
<h3>Advanced Customization</h3>
WP-Syntax supports a <code>wp_syntax_init_geshi</code> action hook to customize GeSHi 
initialization settings. Blog owners can handle the hook in a hand-made plugin 
or somewhere else like this:
<pre><code><?php
add_action('wp_syntax_init_geshi', 'my_custom_geshi_styles');

function my_custom_geshi_styles(&$geshi)
{
 $geshi->set_brackets_style('color: #000;');
 $geshi->set_keyword_group_style(1, 'color: #22f;');
}
?>
</code></pre>
This allows for a great possibility of different customizations. Be sure to 
review the <a href="http://qbnz.com/highlighter/geshi-doc.html" rel="nofollow ugc">GeSHi Documentation</a>.

WP-Syntax

WP-Syntax provides clean syntax highlighting for embedding source code within pages or posts.

Raw HTML vs WP-Syntax