<link href="prettify.css" type="text/css" rel="stylesheet" /> <script type="text/javascript" src="prettify.js"></script>
onload="prettyPrint()" to your
      document's body tag.
      Put code snippets in <pre class="prettyprint">...</pre> or <code class="prettyprint">...</code> and it will automatically be pretty printed.
| The original | Prettier | 
|---|---|
| class Voila { public: // Voila static const string VOILA = "Voila"; // will not interfere with embedded tags. } | class Voila { public: // Voila static const string VOILA = "Voila"; // will not interfere with embedded tags. } | 
The comments in prettify.js are authoritative but the lexer should work on a number of languages including C and friends, Java, Python, Bash, SQL, HTML, XML, CSS, Javascript, and Makefiles. It works passably on Ruby, PHP, VB, and Awk and a decent subset of Perl and Ruby, but, because of commenting conventions, doesn't work on Smalltalk, or CAML-like languages.
LISPy languages are supported via an extension:
    lang-lisp.js.
And similarly for
    Clojure,
    CSS,
    Go,
    Haskell,
    Lua,
    OCAML, SML, F#,
    Nemerle,
    Protocol Buffers,
    Scala,
    SQL,
    TeX, LaTeX,
    VHDL,
    Visual Basic,
    WikiText,
    XQuery, and
    YAML.
    
If you'd like to add an extension for your favorite language, please look at src/lang-lisp.js and file an issue including your language extension, and a testcase.
You don't need to specify the language since prettyprint()
    will guess.  You can specify a language by specifying the language extension
    along with the prettyprint class like so:
<pre class="prettyprint lang-html">
  The lang-* class specifies the language file extensions.
  File extensions supported by default include
    "bsh", "c", "cc", "cpp", "cs", "csh", "cyc", "cv", "htm", "html",
    "java", "js", "m", "mxml", "perl", "pl", "pm", "py", "rb", "sh",
    "xhtml", "xml", "xsl".
</pre>
    You may also use the
    HTML 5 convention of embedding a code element inside the
    PRE and using language-java style classes.
    E.g. 
...Yes. Prettifying obfuscated code is like putting lipstick on a pig — i.e. outside the scope of this tool.
It's been tested with IE 6, Firefox 1.5 & 2, and Safari 2.0.4. Look at the test page to see if it works in your browser.
See the change log
Apparently wordpress does "smart quoting" which changes close quotes. This causes end quotes to not match up with open quotes.
This breaks prettifying as well as copying and pasting of code samples. See WordPress's help center for info on how to stop smart quoting of code snippets.
You can use the linenums class to turn on line
    numbering.  If your code doesn't start at line number 1, you can
    add a colon and a line number to the end of that class as in
    linenums:52.
    
For example
<pre class="prettyprint linenums:4" >// This is line 4. foo(); bar(); baz(); boo(); far(); faz(); <pre>produces
// This is line 4. foo(); bar(); baz(); boo(); far(); faz();
You can use the nocode class to identify a span of markup
    that is not code.
<pre class=prettyprint> int x = foo(); /* This is a comment <span class="nocode">This is not code</span> Continuation of comment */ int y = bar(); </pre>produces
int x = foo();  /* This is a comment  This is not code
  Continuation of comment */
int y = bar();
    For a more complete example see the issue22 testcase.
If you are calling prettyPrint via an event handler, wrap it in a function.
    Instead of doing
    
      addEventListener('load', prettyPrint, false);
    
    wrap it in a closure like
    
      addEventListener('load', function (event) { prettyPrint() }, false);
    
    so that the browser does not pass an event object to prettyPrint which
    will confuse it.
    
    Prettify adds <span> with classes describing
    the kind of code.  You can create CSS styles to matches these
    classes.
    See the
    
    theme gallery for examples.