RubyGems - porthole - Versions diffs - 0.99.4 - Mend

porthole 0.99.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (70) hide show

data/LICENSE +20 -0
data/README.md +415 -0
data/Rakefile +89 -0
data/bin/porthole +94 -0
data/lib/porthole.rb +304 -0
data/lib/porthole/context.rb +142 -0
data/lib/porthole/generator.rb +195 -0
data/lib/porthole/parser.rb +263 -0
data/lib/porthole/settings.rb +226 -0
data/lib/porthole/sinatra.rb +205 -0
data/lib/porthole/template.rb +58 -0
data/lib/porthole/version.rb +3 -0
data/lib/rack/bug/panels/mustache_panel.rb +81 -0
data/lib/rack/bug/panels/mustache_panel/mustache_extension.rb +27 -0
data/lib/rack/bug/panels/mustache_panel/view.mustache +46 -0
data/man/porthole.1 +165 -0
data/man/porthole.1.html +213 -0
data/man/porthole.1.ron +127 -0
data/man/porthole.5 +539 -0
data/man/porthole.5.html +422 -0
data/man/porthole.5.ron +324 -0
data/test/autoloading_test.rb +56 -0
data/test/fixtures/comments.porthole +1 -0
data/test/fixtures/comments.rb +14 -0
data/test/fixtures/complex_view.porthole +17 -0
data/test/fixtures/complex_view.rb +34 -0
data/test/fixtures/crazy_recursive.porthole +9 -0
data/test/fixtures/crazy_recursive.rb +31 -0
data/test/fixtures/delimiters.porthole +8 -0
data/test/fixtures/delimiters.rb +23 -0
data/test/fixtures/dot_notation.porthole +10 -0
data/test/fixtures/dot_notation.rb +25 -0
data/test/fixtures/double_section.porthole +7 -0
data/test/fixtures/double_section.rb +14 -0
data/test/fixtures/escaped.porthole +1 -0
data/test/fixtures/escaped.rb +14 -0
data/test/fixtures/inner_partial.porthole +1 -0
data/test/fixtures/inner_partial.txt +1 -0
data/test/fixtures/inverted_section.porthole +7 -0
data/test/fixtures/inverted_section.rb +14 -0
data/test/fixtures/lambda.porthole +7 -0
data/test/fixtures/lambda.rb +31 -0
data/test/fixtures/method_missing.rb +19 -0
data/test/fixtures/namespaced.porthole +1 -0
data/test/fixtures/namespaced.rb +25 -0
data/test/fixtures/nested_objects.porthole +17 -0
data/test/fixtures/nested_objects.rb +35 -0
data/test/fixtures/node.porthole +8 -0
data/test/fixtures/partial_with_module.porthole +4 -0
data/test/fixtures/partial_with_module.rb +37 -0
data/test/fixtures/passenger.conf +5 -0
data/test/fixtures/passenger.rb +27 -0
data/test/fixtures/recursive.porthole +4 -0
data/test/fixtures/recursive.rb +14 -0
data/test/fixtures/simple.porthole +5 -0
data/test/fixtures/simple.rb +26 -0
data/test/fixtures/template_partial.porthole +2 -0
data/test/fixtures/template_partial.rb +18 -0
data/test/fixtures/template_partial.txt +4 -0
data/test/fixtures/unescaped.porthole +1 -0
data/test/fixtures/unescaped.rb +14 -0
data/test/fixtures/utf8.porthole +3 -0
data/test/fixtures/utf8_partial.porthole +1 -0
data/test/helper.rb +7 -0
data/test/parser_test.rb +78 -0
data/test/partial_test.rb +168 -0
data/test/porthole_test.rb +677 -0
data/test/spec_test.rb +68 -0
data/test/template_test.rb +20 -0
metadata +127 -0

data/man/porthole.5.html ADDED

@@ -0,0 +1,422 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>porthole(5) - Logic-less templates.</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#TAG-TYPES">TAG TYPES</a>
+    <a href="#COPYRIGHT">COPYRIGHT</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>porthole(5)</li>
+    <li class='tc'>Porthole Manual</li>
+    <li class='tr'>porthole(5)</li>
+  </ol>
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>porthole</code> - <span class="man-whatis">Logic-less templates.</span>
+</p>
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+<p>A typical Porthole template:</p>
+<pre><code>Hello {{name}}
+You have just won {{value}} dollars!
+{{#in_ca}}
+Well, {{taxed_value}} dollars, after taxes.
+{{/in_ca}}
+</code></pre>
+<p>Given the following hash:</p>
+<pre><code>{
+  "name": "Chris",
+  "value": 10000,
+  "taxed_value": 10000 - (10000 * 0.4),
+  "in_ca": true
+}
+</code></pre>
+<p>Will produce the following:</p>
+<pre><code>Hello Chris
+You have just won 10000 dollars!
+Well, 6000.0 dollars, after taxes.
+</code></pre>
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+<p>Porthole can be used for HTML, config files, source code -
+anything. It works by expanding tags in a template using values
+provided in a hash or object.</p>
+<p>We call it "logic-less" because there are no if statements, else
+clauses, or for loops. Instead there are only tags. Some tags are
+replaced with a value, some nothing, and others a series of
+values. This document explains the different types of Porthole tags.</p>
+<h2 id="TAG-TYPES">TAG TYPES</h2>
+<p>Tags are indicated by the double portholes. <code>{{person}}</code> is a tag, as
+is <code>{{#person}}</code>. In both examples, we'd refer to <code>person</code> as the key
+or tag key. Let's talk about the different types of tags.</p>
+<h3 id="Variables">Variables</h3>
+<p>The most basic tag type is the variable. A <code>{{name}}</code> tag in a basic
+template will try to find the <code>name</code> key in the current context. If
+there is no <code>name</code> key, nothing will be rendered.</p>
+<p>All variables are HTML escaped by default. If you want to return
+unescaped HTML, use the triple porthole: <code>{{{name}}}</code>.</p>
+<p>You can also use <code>&amp;</code> to unescape a variable: <code>{{&amp; name}}</code>. This may be
+useful when changing delimiters (see "Set Delimiter" below).</p>
+<p>By default a variable "miss" returns an empty string. This can usually
+be configured in your Porthole library. The Ruby version of Porthole
+supports raising an exception in this situation, for instance.</p>
+<p>Template:</p>
+<pre><code>* {{name}}
+* {{age}}
+* {{company}}
+* {{{company}}}
+</code></pre>
+<p>Hash:</p>
+<pre><code>{
+  "name": "Chris",
+  "company": "&lt;b&gt;GitHub&lt;/b&gt;"
+}
+</code></pre>
+<p>Output:</p>
+<pre><code>* Chris
+*
+* &amp;lt;b&amp;gt;GitHub&amp;lt;/b&amp;gt;
+* &lt;b&gt;GitHub&lt;/b&gt;
+</code></pre>
+<h3 id="Sections">Sections</h3>
+<p>Sections render blocks of text one or more times, depending on the
+value of the key in the current context.</p>
+<p>A section begins with a pound and ends with a slash. That is,
+<code>{{#person}}</code> begins a "person" section while <code>{{/person}}</code> ends it.</p>
+<p>The behavior of the section is determined by the value of the key.</p>
+<p><strong>False Values or Empty Lists</strong></p>
+<p>If the <code>person</code> key exists and has a value of false or an empty
+list, the HTML between the pound and slash will not be displayed.</p>
+<p>Template:</p>
+<pre><code>Shown.
+{{#nothin}}
+  Never shown!
+{{/nothin}}
+</code></pre>
+<p>Hash:</p>
+<pre><code>{
+  "person": true,
+}
+</code></pre>
+<p>Output:</p>
+<pre><code>Shown.
+</code></pre>
+<p><strong>Non-Empty Lists</strong></p>
+<p>If the <code>person</code> key exists and has a non-false value, the HTML between
+the pound and slash will be rendered and displayed one or more times.</p>
+<p>When the value is a non-empty list, the text in the block will be
+displayed once for each item in the list. The context of the block
+will be set to the current item for each iteration. In this way we can
+loop over collections.</p>
+<p>Template:</p>
+<pre><code>{{#repo}}
+  &lt;b&gt;{{name}}&lt;/b&gt;
+{{/repo}}
+</code></pre>
+<p>Hash:</p>
+<pre><code>{
+  "repo": [
+    { "name": "resque" },
+    { "name": "hub" },
+    { "name": "rip" },
+  ]
+}
+</code></pre>
+<p>Output:</p>
+<pre><code>&lt;b&gt;resque&lt;/b&gt;
+&lt;b&gt;hub&lt;/b&gt;
+&lt;b&gt;rip&lt;/b&gt;
+</code></pre>
+<p><strong>Lambdas</strong></p>
+<p>When the value is a callable object, such as a function or lambda, the
+object will be invoked and passed the block of text. The text passed
+is the literal block, unrendered. <code>{{tags}}</code> will not have been expanded
+- the lambda should do that on its own. In this way you can implement
+filters or caching.</p>
+<p>Template:</p>
+<pre><code>{{#wrapped}}
+  {{name}} is awesome.
+{{/wrapped}}
+</code></pre>
+<p>Hash:</p>
+<pre><code>{
+  "name": "Willy",
+  "wrapped": function() {
+    return function(text) {
+      return "&lt;b&gt;" + render(text) + "&lt;/b&gt;"
+    }
+  }
+}
+</code></pre>
+<p>Output:</p>
+<pre><code>&lt;b&gt;Willy is awesome.&lt;/b&gt;
+</code></pre>
+<p><strong>Non-False Values</strong></p>
+<p>When the value is non-false but not a list, it will be used as the
+context for a single rendering of the block.</p>
+<p>Template:</p>
+<pre><code>{{#person?}}
+  Hi {{name}}!
+{{/person?}}
+</code></pre>
+<p>Hash:</p>
+<pre><code>{
+  "person?": { "name": "Jon" }
+}
+</code></pre>
+<p>Output:</p>
+<pre><code>Hi Jon!
+</code></pre>
+<h3 id="Inverted-Sections">Inverted Sections</h3>
+<p>An inverted section begins with a caret (hat) and ends with a
+slash. That is <code>{{^person}}</code> begins a "person" inverted section while
+<code>{{/person}}</code> ends it.</p>
+<p>While sections can be used to render text one or more times based on the
+value of the key, inverted sections may render text once based
+on the inverse value of the key. That is, they will be rendered
+if the key doesn't exist, is false, or is an empty list.</p>
+<p>Template:</p>
+<pre><code>{{#repo}}
+  &lt;b&gt;{{name}}&lt;/b&gt;
+{{/repo}}
+{{^repo}}
+  No repos :(
+{{/repo}}
+</code></pre>
+<p>Hash:</p>
+<pre><code>{
+  "repo": []
+}
+</code></pre>
+<p>Output:</p>
+<pre><code>No repos :(
+</code></pre>
+<h3 id="Comments">Comments</h3>
+<p>Comments begin with a bang and are ignored. The following template:</p>
+<pre><code>&lt;h1&gt;Today{{! ignore me }}.&lt;/h1&gt;
+</code></pre>
+<p>Will render as follows:</p>
+<pre><code>&lt;h1&gt;Today.&lt;/h1&gt;
+</code></pre>
+<p>Comments may contain newlines.</p>
+<h3 id="Partials">Partials</h3>
+<p>Partials begin with a greater than sign, like <code>{{&gt; box}}</code>.</p>
+<p>Partials are rendered at runtime (as opposed to compile time), so
+recursive partials are possible. Just avoid infinite loops.</p>
+<p>They also inherit the calling context. Whereas in ERB you may have
+this:</p>
+<pre><code>&lt;%= partial :next_more, :start =&gt; start, :size =&gt; size %&gt;
+</code></pre>
+<p>Porthole requires only this:</p>
+<pre><code>{{&gt; next_more}}
+</code></pre>
+<p>Why? Because the <code>next_more.porthole</code> file will inherit the <code>size</code> and
+<code>start</code> methods from the calling context.</p>
+<p>In this way you may want to think of partials as includes, or template
+expansion, even though it's not literally true.</p>
+<p>For example, this template and partial:</p>
+<pre><code>base.porthole:
+&lt;h2&gt;Names&lt;/h2&gt;
+{{#names}}
+  {{&gt; user}}
+{{/names}}
+user.porthole:
+&lt;strong&gt;{{name}}&lt;/strong&gt;
+</code></pre>
+<p>Can be thought of as a single, expanded template:</p>
+<pre><code>&lt;h2&gt;Names&lt;/h2&gt;
+{{#names}}
+  &lt;strong&gt;{{name}}&lt;/strong&gt;
+{{/names}}
+</code></pre>
+<h3 id="Set-Delimiter">Set Delimiter</h3>
+<p>Set Delimiter tags start with an equal sign and change the tag
+delimiters from <code>{{</code> and <code>}}</code> to custom strings.</p>
+<p>Consider the following contrived example:</p>
+<pre><code>* {{default_tags}}
+{{=&lt;% %>=}}
+* &lt;% erb_style_tags %>
+&lt;%={{ }}=%>
+* {{ default_tags_again }}
+</code></pre>
+<p>Here we have a list with three items. The first item uses the default
+tag style, the second uses erb style as defined by the Set Delimiter
+tag, and the third returns to the default style after yet another Set
+Delimiter declaration.</p>
+<p>According to <a href="http://google-ctemplate.googlecode.com/svn/trunk/doc/howto.html">ctemplates</a>, this "is useful for languages like TeX, where
+double-braces may occur in the text and are awkward to use for
+markup."</p>
+<p>Custom delimiters may not contain whitespace or the equals sign.</p>
+<h2 id="COPYRIGHT">COPYRIGHT</h2>
+<p>Porthole is Copyright (C) 2009 Chris Wanstrath</p>
+<p>Original CTemplate by Google</p>
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+<p><a href="porthole.1.ron.html" class="man-ref">porthole<span class="s">(1)</span></a>,
+<a href="http://porthole.github.com/" data-bare-link="true">http://porthole.github.com/</a></p>
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'>DEFUNKT</li>
+    <li class='tc'>August 2011</li>
+    <li class='tr'>porthole(5)</li>
+  </ol>
+  </div>
+</body>
+</html>

data/man/porthole.5.ron ADDED

@@ -0,0 +1,324 @@
+porthole(5) -- Logic-less templates.
+====================================
+## SYNOPSIS
+A typical Porthole template:
+    Hello {{name}}
+    You have just won {{value}} dollars!
+    {{#in_ca}}
+    Well, {{taxed_value}} dollars, after taxes.
+    {{/in_ca}}
+Given the following hash:
+    {
+      "name": "Chris",
+      "value": 10000,
+      "taxed_value": 10000 - (10000 * 0.4),
+      "in_ca": true
+    }
+Will produce the following:
+    Hello Chris
+    You have just won 10000 dollars!
+    Well, 6000.0 dollars, after taxes.
+## DESCRIPTION
+Porthole can be used for HTML, config files, source code -
+anything. It works by expanding tags in a template using values
+provided in a hash or object.
+We call it "logic-less" because there are no if statements, else
+clauses, or for loops. Instead there are only tags. Some tags are
+replaced with a value, some nothing, and others a series of
+values. This document explains the different types of Porthole tags.
+## TAG TYPES
+Tags are indicated by the double portholes. `{{person}}` is a tag, as
+is `{{#person}}`. In both examples, we'd refer to `person` as the key
+or tag key. Let's talk about the different types of tags.
+### Variables
+The most basic tag type is the variable. A `{{name}}` tag in a basic
+template will try to find the `name` key in the current context. If
+there is no `name` key, nothing will be rendered.
+All variables are HTML escaped by default. If you want to return
+unescaped HTML, use the triple porthole: `{{{name}}}`.
+You can also use `&` to unescape a variable: `{{& name}}`. This may be
+useful when changing delimiters (see "Set Delimiter" below).
+By default a variable "miss" returns an empty string. This can usually
+be configured in your Porthole library. The Ruby version of Porthole
+supports raising an exception in this situation, for instance.
+Template:
+    * {{name}}
+    * {{age}}
+    * {{company}}
+    * {{{company}}}
+Hash:
+    {
+      "name": "Chris",
+      "company": "<b>GitHub</b>"
+    }
+Output:
+    * Chris
+    *
+    * &lt;b&gt;GitHub&lt;/b&gt;
+    * <b>GitHub</b>
+### Sections
+Sections render blocks of text one or more times, depending on the
+value of the key in the current context.
+A section begins with a pound and ends with a slash. That is,
+`{{#person}}` begins a "person" section while `{{/person}}` ends it.
+The behavior of the section is determined by the value of the key.
+**False Values or Empty Lists**
+If the `person` key exists and has a value of false or an empty
+list, the HTML between the pound and slash will not be displayed.
+Template:
+    Shown.
+    {{#nothin}}
+      Never shown!
+    {{/nothin}}
+Hash:
+    {
+      "person": true,
+    }
+Output:
+    Shown.
+**Non-Empty Lists**
+If the `person` key exists and has a non-false value, the HTML between
+the pound and slash will be rendered and displayed one or more times.
+When the value is a non-empty list, the text in the block will be
+displayed once for each item in the list. The context of the block
+will be set to the current item for each iteration. In this way we can
+loop over collections.
+Template:
+    {{#repo}}
+      <b>{{name}}</b>
+    {{/repo}}
+Hash:
+    {
+      "repo": [
+        { "name": "resque" },
+        { "name": "hub" },
+        { "name": "rip" },
+      ]
+    }
+Output:
+    <b>resque</b>
+    <b>hub</b>
+    <b>rip</b>
+**Lambdas**
+When the value is a callable object, such as a function or lambda, the
+object will be invoked and passed the block of text. The text passed
+is the literal block, unrendered. `{{tags}}` will not have been expanded
+- the lambda should do that on its own. In this way you can implement
+filters or caching.
+Template:
+    {{#wrapped}}
+      {{name}} is awesome.
+    {{/wrapped}}
+Hash:
+    {
+      "name": "Willy",
+      "wrapped": function() {
+        return function(text) {
+          return "<b>" + render(text) + "</b>"
+        }
+      }
+    }
+Output:
+    <b>Willy is awesome.</b>
+**Non-False Values**
+When the value is non-false but not a list, it will be used as the
+context for a single rendering of the block.
+Template:
+    {{#person?}}
+      Hi {{name}}!
+    {{/person?}}
+Hash:
+    {
+      "person?": { "name": "Jon" }
+    }
+Output:
+    Hi Jon!
+### Inverted Sections
+An inverted section begins with a caret (hat) and ends with a
+slash. That is `{{^person}}` begins a "person" inverted section while
+`{{/person}}` ends it.
+While sections can be used to render text one or more times based on the
+value of the key, inverted sections may render text once based
+on the inverse value of the key. That is, they will be rendered
+if the key doesn't exist, is false, or is an empty list.
+Template:
+    {{#repo}}
+      <b>{{name}}</b>
+    {{/repo}}
+    {{^repo}}
+      No repos :(
+    {{/repo}}
+Hash:
+    {
+      "repo": []
+    }
+Output:
+    No repos :(
+### Comments
+Comments begin with a bang and are ignored. The following template:
+    <h1>Today{{! ignore me }}.</h1>
+Will render as follows:
+    <h1>Today.</h1>
+Comments may contain newlines.
+### Partials
+Partials begin with a greater than sign, like `{{> box}}`.
+Partials are rendered at runtime (as opposed to compile time), so
+recursive partials are possible. Just avoid infinite loops.
+They also inherit the calling context. Whereas in ERB you may have
+this:
+    <%= partial :next_more, :start => start, :size => size %>
+Porthole requires only this:
+    {{> next_more}}
+Why? Because the `next_more.porthole` file will inherit the `size` and
+`start` methods from the calling context.
+In this way you may want to think of partials as includes, or template
+expansion, even though it's not literally true.
+For example, this template and partial:
+    base.porthole:
+    <h2>Names</h2>
+    {{#names}}
+      {{> user}}
+    {{/names}}
+    user.porthole:
+    <strong>{{name}}</strong>
+Can be thought of as a single, expanded template:
+    <h2>Names</h2>
+    {{#names}}
+      <strong>{{name}}</strong>
+    {{/names}}
+### Set Delimiter
+Set Delimiter tags start with an equal sign and change the tag
+delimiters from `{{` and `}}` to custom strings.
+Consider the following contrived example:
+    * {{default_tags}}
+    {{=<% %>=}}
+    * <% erb_style_tags %>
+    <%={{ }}=%>
+    * {{ default_tags_again }}
+Here we have a list with three items. The first item uses the default
+tag style, the second uses erb style as defined by the Set Delimiter
+tag, and the third returns to the default style after yet another Set
+Delimiter declaration.
+According to [ctemplates][ct], this "is useful for languages like TeX, where
+double-braces may occur in the text and are awkward to use for
+markup."
+Custom delimiters may not contain whitespace or the equals sign.
+[ct]: http://google-ctemplate.googlecode.com/svn/trunk/doc/howto.html
+## COPYRIGHT
+Porthole is Copyright (C) 2009 Chris Wanstrath
+Original CTemplate by Google
+## SEE ALSO
+porthole(1),
+<http://porthole.github.com/>