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.

David

Brings the cool Javascript syntax highlighter <a href="https://github.com/ccampbell/rainbow" rel="nofollow ugc">Rainbow.js</a> to your WordPress-Blog and allows you to manage code snippets independend from the text editor.
IMPORTANT! – This plugin is no longer testet with PHP 5.2!
<h4>Quick Start</h4>
<ol>
<li>Download the plugin from this page</li>
<li>Follow the instructions on the <a href="https://codex.wordpress.org/Managing_Plugins#Manual_Plugin_Installation" rel="nofollow ugc">WordPress Codex</a> to install the plugin. 
By default, the plugin is ready for use after activation. Some options can be changed on Settings → Writing.</li>
</ol>
For a detailed usage manual refer to the <a href="https://wordpress.org/extend/plugins/wp-colored-coding/other_notes/#usage" rel="ugc">Usage section</a>, or – better than a thousand words – to the <a href="https://wordpress.org/extend/plugins/wp-colored-coding/screenshots/" rel="ugc">screenshots</a>.
If you want to change the behaviour of the plugin see the <a href="https://wordpress.org/extend/plugins/wp-colored-coding/other_notes/#API" rel="ugc">API-Documentation</a>

<h3>Settings</h3>
By default, the plugin is ready for use after activation. Some options can be changed on Settings → Writing.
<h4>Raw output</h4>
This option enables an additional checkbox for each codeblock of a post which allows you to disable the <code>esc_attr()</code> filter for that code snippet. That means, every HTML and Javascript inside this textarea will be parsed by the browser as those. So be carefull with this option.
<h3>Usage</h3>
<h4>Codeblocks</h4>
A single Codeblock is identified (in the posts context) by its name. If you don’t want to specify a name for each block, leave it empty, it will be generated automatically.
The language field is also optional. To use syntax highlighting, write in a rainbow supported language. (It will give you suggestions.) Currently these are 
* C 
* Coffeescript 
* C# 
* CSS 
* Go 
* HTML 
* Java 
* JavaScript 
* Lua 
* PHP 
* Python 
* R 
* Ruby 
* Shell 
* Smalltalk
Each codeblock can be placed anywhere in the text by using the shortcode <code>[cc name="{name}"]</code>. You can use the TinyMCE button »CC« for that.
<h4>Shortcode (in-text code)</h4>
For just a few lines of code you may want to use the shortcode like this:
<pre><code>[cc lang="javascript"]
var str = 'Hello World';
alert( str );
[/cc]
</code></pre>
<h3>Contribution & Bug-Report</h3>
For bug reports or ideas for new features, please use the <a href="https://github.com/dnaber-de/WP-Colored-Coding/issues" rel="nofollow ugc">issue tracker on gitub</a>.
<h3>API</h3>
The following filters are provided:
<ul>
<li><code>wp_cc_rainbow_themes</code></li>
<li><code>wp_cc_rainbow_scripts</code></li>
<li><code>wp_cc_rainbow_languages</code></li>
</ul>
Adding a new Theme is quite easy. Just expend the themes-array by a key like this
<pre><code>/**
 * @param array $themes
 * @return array
 */
function my_new_rainbow_theme( $themes ) {
 $themes[ 'my_theme' ] = array(
 'src' => //the absolute URI to the stylesheet
 'name' => 'My Theme'
 );

 return $themes;
}
add_filter( 'wp_cc_rainbow_themes', 'my_new_rainbow_theme' );
</code></pre>
To add a supported language use
<pre><code>/**
 * @param array $scripts
 * @return array
 */
function my_new_rainbow_script( $scripts ) {
 $scripts[ 'my_new_lang' ] = array(
 'src' => //the absolute URI to the script
 'depth' => array( 'rainbow' ),
 'lang' => 'my_new_lang',
 'in_footer' => TRUE # this must be equal with the script it depends on
 );

 # to override the built-in rainbow version use the key 'rainbow'

 return $scripts;
}
add_filter( 'wp_cc_rainbow_scripts', 'my_new_rainbow_script' );

/**
 * @param array $langs
 * @return array
 */
function my_new_lang( $langs ) {

 $langs[ 'my_new_lang' ] = 'My new lang';

 return $langs;
}
add_filter( 'wp_cc_rainbow_languages', 'my_new_lang' );
</code></pre>
<h4>Deactivation/Uninstallation</h4>
If you deactivate the plugin all settings and codes will be preserved. On uninstallation (delete), all settings and codes will be deleted finally. If this is triggered from the network-admin page, all blogs will be cleaned up.
<h3>Acknowledgement</h3>
<ul>
<li>Thanks to <a href="https://github.com/sparanoid" rel="nofollow ugc">sparanoid</a> for chinese translation</li>
<li>Thanks to <a href="https://twitter.com/Volleyballfisch" rel="nofollow ugc">@volleyballfisch</a> for spanish translation</li>
<li>Thanks to <a href="https://github.com/yonjah" rel="nofollow ugc">yonjah</a> for JS Bugfixing</li>
</ul>

WP-Syntax vs WP Colored Coding