Andrew Parman

<p>This plugin adds a Gutenberg block called <code>IECST Highlighter</code>. After entering a code snippet in the editor,<br />
the output will be rendered with a syntax highlighting style selected in the IECST Highlighter Settings.</p>
<p>This plugin uses the <a href="https://github.com/PhioAutomation/phio-highlighter" rel="nofollow ugc">Phio Highlighter</a> which is distributed<br />
with an MIT License, https://highlighter.phioautomation.com/LICENSE.txt.</p>
<p>Development of this plugin is on <a href="https://github.com/PhioAutomation/phio-highlighter" rel="nofollow ugc">Github</a>.</p>


IECST Highlighter

Display beautiful code snippets using the Phio Highlighter for the IEC 61131-3 Structured Text language

<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

IECST Highlighter vs Highlight Source Pro