^{rdoc/div}{%{wlang/dummy}{
Standard ruleset are designed to be reusable: including them in your own dialect is made
easy by a typical _wlang_ implementation. Some of them are also included by standard dialects.

=== How to read this cheatsheet?

First of all, focus on the examples; they are written to let you learn _wlang_ quickly and 
deeply. Some of them are a bit difficult to understand but they are representative of _wlang_
powerfulness (don't be affraid: in practice, some constructions are never used). Don't forget
that the <tt>wlang/dummy</tt> dialect does not recognize any tag. We also assume instantiation 
data to be the following hash:
  {"name"     =>  "O'Neil", 
   "author"   =>  "blambeau"
   "authors"  =>  ["blambeau", "llambeau", "ancailliau"]}

Moreover, the dialect column in the examples is important; _wlang_ behaves differently 
in different dialects. When the dialect does not care, we use <tt>wlang/*</tt> which means
'in any dialect that includes this ruleset'.

Next, certain rule definitions are given as shortcuts for longer expressions, involving other tags.
This is somewhat representative of _wlang_ usage, even if these rules are not actually implemented 
this way (mainly for efficiency concerns). Once again, understanding shortcuts will help you 
mastering wlang! In definitions (textual as well as shortcuts), we use #1, #2, and #3 to refer to 
the content of the blocks. Those identifiers are not real _wlang_ constructs, but are only used here for 
easier explanations (for those who know this kind of vocabulary: they are part of the meta-language,
not the language <em>per se</em>).

Lastly, dialect names that appear in rule signatures are to be interpreted as an implicit dialect 
modulation: the corresponding block (often the first one) is not instantiated in the current dialect 
but in the one specified by the signature. In contrast, when we use '...' it means that the 
corresponding block is simply instantiated in the current dialect. Implicit dialect modulation is
in fact natural: if a block expects an uri for example, the easiest way is to give
it exactly: <tt><<{a/file/to/include.txt}</tt>. But you can even compute it using _wlang_, as illustrated
by the example below. In complex situations you will probably be happy to use a dialect that helps you 
doing so (think at all blocks that expect an expression in the hosting language, for example)!

  # Concatenates all files of the 'files' array variable
  *{files as f}{<<{+{f}}}

}}
<<={examples.rb as examples}
*{spec.rulesets as ruleset}{
  <h3 id="${ruleset.name}">${ruleset.name}</h3>
  ^{rdoc/div}{${ruleset.description}}
  <table class="ruleset">
    <tr>
      <th class="signature">signature</th>
      <th class="name">name</th>
      <th class="definition">definition</th>
    </tr>
    *{ruleset.rules as rule}{
      <tr>
        <td class="signature"><tt>${rule.signature}</tt></td>
        <td class="name">+{rule.name}</td>
        <td class="definition">^{rdoc/nop}{+{rule.definition}}</td>
      </tr>
    }
  </table>
  
  ?{ruleset.examples}{
    <br/>
    <h4>Examples:</h4>
    <table class="examples">
      <tr>
        <th>dialect</th>
        <th>wlang expression</th>
        <th>replacement value</th>
      </tr>
      *{ruleset.examples as example}{
        <tr>
          <td class="dialect">
            <tt>${example[0]}</tt>
          </td>
          <td class="expression">
            <tt>${example[1]}</tt>
          </td>
          <td class="replacement">
            #={dialect}{?{example[0] == "wlang/*"}{wlang/xhtml}{+{example[0]}}}{
            <tt>%!{+{dialect} using examples}{+{example[1]}}</tt>
            }
          </td>
        </tr>
      }
    </table>
    <div style="clear: both;"></div>
  }
}