twenty four merry days of Perl Feed

Pretty Pretty Pod

PPI::HTML and Text::VimColor - 2013-12-20

Why is the Advent calendar's code so good looking?

I know some people don't like seeing their code in color. Someone once said to me, "I stopped needing color in my books when I was a child, and I certainly don't need it in my code." This, I thought, was nuts.

If I was going to write a bunch of articles about code (when I started publishing an Advent calendar in 2009) I didn't want to see this:


1: 
2: 
3: 

 

my @animals = ("camel", "llama", "owl");
my @numbers = (23, 42, 69);
my @mixed = ("camel", 42, 1.23);

 

I wanted to see this:


1: 
2: 
3: 

 

my @animals = ("camel", "llama", "owl");
my @numbers = (23, 42, 69);
my @mixed = ("camel", 42, 1.23);

 

…and I really wanted writing article to be like writing normal Pod.

Oh, and sometimes I wanted to do something other than Perl:


1: 
2: 
3: 
4: 
5: 

 

dsn: "dbi:SQLite:/home/rjbs/.awesome-stuff.sqlite"
lbj: { guid: 275dc6e0-6926-11e3-a944-0f63e4cda179 }
alerts:
  hdr_from: 'Alerty <alerts@example.com>'
  hdr_to : '"Ricardo Signes" <rjbs@cpan.org>'

 

Those two blocks above look, in the Pod, like this:


1: 
2: 
3: 
4: 

 

#!perl
my @animals = ("camel", "llama", "owl");
my @numbers = (23, 42, 69);
my @mixed = ("camel", 42, 1.23);

 

and


1: 
2: 
3: 
4: 
5: 
6: 

 

#!vim yaml
dsn: "dbi:SQLite:/home/rjbs/.awesome-stuff.sqlite"
lbj: { guid: 275dc6e0-6926-11e3-a944-0f63e4cda179 }
alerts:
  hdr_from: 'Alerty <alerts@example.com>'
  hdr_to : '"Ricardo Signes" <rjbs@cpan.org>'

 

Those #!perl and #!vim lines are to blame for the garish spread of color! What are they doing?

PPI::HTML

The #!perl marker is picked up by Pod::Elemental::Transformer::PPIHTML, and passes the rest of the code block to PPI::HTML. PPI::HTML uses PPI, a library for mostly-parsing Perl without running it, and turns Perl documents into HTML documents. For example, the simple Perl snippet above becomes this HTML:


1: 
2: 
3: 
4: 
5: 
6: 
7: 
8: 
9: 
10: 
11: 
12: 
13: 
14: 
15: 
16: 
17: 
18: 

 

<span class="keyword">my</span> <span class="symbol">@animals</span>
<span class="operator">=</span> <span class=
"structure">(</span><span class="double">"camel"</span><span class=
"operator">,</span> <span class="double">"llama"</span><span class=
"operator">,</span> <span class="double">"owl"</span><span class=
"structure">);</span><br>
<span class="keyword">my</span> <span class="symbol">@numbers</span>
<span class="operator">=</span> <span class=
"structure">(</span><span class="number">23</span><span class=
"operator">,</span> <span class="number">42</span><span class=
"operator">,</span> <span class="number">69</span><span class=
"structure">);</span><br>
<span class="keyword">my</span> <span class="symbol">@mixed</span>
<span class="operator">=</span> <span class=
"structure">(</span><span class="double">"camel"</span><span class=
"operator">,</span> <span class="number">42</span><span class=
"operator">,</span> <span class="float">1.23</span><span class=
"structure">);</span><br>

 

It's a bit gross, but the key thing is that distinct bit of syntax gets its own <span> with a class indicating what it is. PPI::HTML plus a bit of CSS gives you easy syntax highlighting for Perl.

Getting that HTML is trivial, too:


1: 
2: 
3: 

 

my $ppi_doc = PPI::Document->new( \$source_code );
my $ppi_html = PPI::HTML->new;
print $ppi_html->html( $ppi_doc );

 

Text::VimColor

PPI, of course, only parses Perl documents. For almost everything else, there's Text::VimColor. I spent a lot of time looking for generic, pluggable syntax highlighting before finally realizing that the only thing that ever did a good job for me was my text editor. It turned out that I could get my text editor to do the work for me here, too!

The YAML above becomes roughly this HTML:


1: 
2: 
3: 
4: 
5: 
6: 
7: 
8: 
9: 
10: 
11: 

 

<span class="synIdentifier">dsn</span><span class="synSpecial">:</span>
<span class="synConstant">&quot;dbi:SQLite:/home/rjbs/.awesome-stuff.sqlite&quot;</span>
<span class="synIdentifier">lbj</span><span class="synSpecial">:</span>
<span class="synSpecial">{</span>
  <span class="synIdentifier">guid</span><span class="synSpecial">:</span>
  275dc6e0-6926-11e3-a944-0f63e4cda179 <span class="synSpecial">}</span>
<span class="synIdentifier">alerts</span><span class="synSpecial">:</span>
<span class="synIdentifier">hdr_from</span><span class="synSpecial">:</span>
<span class="synConstant">'Alerty &lt;alerts@example.com&gt;'</span>
<span class="synIdentifier">hdr_to</span><span class="synSpecial"> :</span>
<span class="synConstant">'&quot;Ricardo Signes&quot; &lt;rjbs@cpan.org&gt;'</span>

 

…once again from a trivial program:


1: 
2: 
3: 
4: 
5: 
6: 
7: 
8: 
9: 
10: 

 

use Text::VimColor;
my $syntax = Text::VimColor->new(
  string => $yaml_octets,
  filetype => 'yaml',
  vim_options => [
    qw( -RXZ -i NONE -u NONE -N -n ), "+set nomodeline", '+set fenc=utf-8',
  ],
);

print $syntax->html;

 

The only cryptic thing here might be the Vim options:

  -R       -- read only
  -X       -- no X11
  -Z       -- restricted mode; no running the shell!
  -N       -- not vi-compatible
  -n       -- no swapfile
  -i NONE  -- no viminfo
  -u NONE  -- no vimrc

…and the fact that we need to provide the string of source as octets, not a character string, and provide the encoding to Vim. Otherwise, you may encounter some unwanted cleverness.

The CSS

The CSS used for this is also dead simple:


1: 
2: 
3: 
4: 
5: 
6: 
7: 
8: 
9: 
10: 
11: 
12: 
13: 
14: 
15: 

 

/* PPI HTML Style */

.code-listing .keyword { color: #89f; }
.code-listing .match { color: #ff0; }
/* ... */
.code-listing .single,
.code-listing .double { color: #0cf; }

/* Vim Syntax Style */

.code-listing .synComment { color: #0f0; }
.code-listing .synConstant { color: #0ff; }
/* ... */
.code-listing .synError { color: #f00; }
.code-listing .synTodo { color: #aa0; }

 

It's generated, of course, by Color::Palette.

Highlight everything!

Now that you see how easy it is to get nicely syntax highlighted HTML for any hunk of code you have lying around, do it! It can often help make bland documentation or other writing much easier to skim. Even better, since the output is pretty simple HTML, you can edit the output as needed to fix glitches or add further highlighting.

See Also

Gravatar Image This article contributed by: Ricardo Signes <rjbs@cpan.org>