<p>Powerful, flexible, XHTML-compliant, server-side code highlighting, credits for everything<br />
but ‘making it a plugin’ go to <a href="http://jpipes.com/index.php?/archives/216-Syntax-Highlighting-and-Allowing-HTML-in-Comments.html" rel="nofollow ugc">Jay Pipes</a><br />
and <a href="http://geshi.org/" rel="nofollow ugc">GeSHi</a>.</p>
<h4>Features</h4>
<ul>
<li>Highlight sources of any language</li>
<li>automatically, server-side (no javascripts)</li>
<li>XHTML-Compliant, <code><div></code>, <code><ul></code>, <code><span></code> with class-attributes and a css-file are used for styling    </li>
<li>optionally add a heading for every code-block</li>
<li>optionally specify line-number offset (BREAKS XHTML COMPLIANCE)</li>
<li>optionally don’t display line-numbers</li>
<li>set per-codeblock if the code is html_entity_encoded or not</li>
<li>only parses <code><pre></code>-tags with the <code>lang=</code>-attribute, thus does not interfere with any regular preformatted contents you might have</li>
<li>degrades beautifully through <code><pre></code>-tags (if you keep the sources clean, that is)</li>
<li>all settings through logical, valid arguments for the main container</li>
<li>comes with generic cross-browser CSS (tested: IE5.5+, FF, Safari, Opera)</li>
</ul>
<h4>Version History</h4>
<ul>
<li>1.3: Thanks to a tipp now the link-path to the stylesheets is correct, sorry for the inconvenience</li>
<li>1.2: Leading whitespace isn’t stripped anymore (indents as well as newlines), when there’s no title the title-div is not being generated anymore</li>
<li>1.1: Solved the issue with single-quotes being changed to typographical quotes</li>
</ul>
<h4>Known Issues</h4>
<p>While the plugin is basically XHTML 1.0 Strict compliant there’s just no way of getting the offset-based line-numbering to display without inadequate (ab)use of javascript and css hacks, so be warned that <em>IF you use the line-number offset, your documents will <strong>NOT</strong> validate</em> because of the forbidden <code>start=</code>-attribute for the <code><ol></code>!</p>
<h3>Documentation</h3>
<p>More on the <a href="http://blog.kno.at/tools/highlight-source-pro/" rel="nofollow ugc">Highlight Source Pro Page</a></p>


Highlight Source Pro

Powerful, XHTML-compliant, server-side code highlighting for pretty much all languages

Koen Van den Wijngaert

PieterC

<p>This small plugin makes it possible to ask your customers where they came from at checkout. You can have a look in your Google Analytics, but it’s easier (and more correct) to ask your customers where they came from by asking one question: “Where did you hear about us?”.</p>
<p>Current features:</p>
<ul>
<li>Define your own question</li>
<li>Set source locations</li>
<li>Saves the location at the customer profile or/and at the order</li>
<li>Mentions the source location on the order emails</li>
<li>Option for a custom “other” field</li>
<li>WPML compatible</li>
</ul>
<h4>WPML compatible</h4>
<p>This plugin is WPML compatible. Multilingual shops can now ask where they came from in the language of the customer.</p>
<h4>About the authors & support</h4>
<p>This plugin is written by the brave and handsome coders of <a href="http://www.siteoptimo.com/?utm_source=hear-about-plugin&utm_medium=wordpress&utm_campaign=wch" rel="nofollow ugc">SiteOptimo</a>.<br />
We made it freely available for the WordPress and WooCommerce community. We might build more custom work in the future.</p>
<p>Issues can be reported in our <a href="https://github.com/siteoptimo/woocommerce-hear-about-us/issues" rel="nofollow ugc">GitHub Repository</a> or in the WordPress support forums.</p>


WooCommerce Hear About Us

Great plugin

Ask where your new customers come from at checkout.

Highlight Source Pro vs WooCommerce Hear About Us