[%# # IMPORTANT NOTE # This documentation is generated automatically from source # templates. Any changes you make here may be lost. # # The 'docsrc' documentation source bundle is available for download # from http://www.template-toolkit.org/docs.html and contains all # the source templates, XML files, scripts, etc., from which the # documentation for the Template Toolkit is built. -%] [% META book = 'Manual' page = 'Filters' %] [% WRAPPER toc; PROCESS tocitem title ='DESCRIPTION' subs = []; PROCESS tocitem title ='STANDARD FILTERS' subs = [ 'format(format)', 'upper', 'lower', 'ucfirst', 'lcfirst', 'trim', 'collapse', 'html', 'html_para', 'html_break', 'uri', 'indent(pad)', 'truncate(length)', 'repeat(iterations)', 'remove(string) ', 'replace(search, replace) ', 'redirect(file)', 'eval(template_text)', 'perl(perlcode)', 'stdout(binmode)', 'stderr', 'null', 'latex(outputType)' ]; PROCESS tocitem title ='AUTHOR' subs = []; PROCESS tocitem title ='VERSION' subs = []; PROCESS tocitem title ='COPYRIGHT' subs = []; END %] [% WRAPPER section title='DESCRIPTION' -%]

This section lists all the standard filters distributed with the Template Toolkit for post-processing output.

[%- END %] [% WRAPPER section title='STANDARD FILTERS' -%][% WRAPPER subsection title = 'format(format)' -%]

The 'format' filter takes a format string as a parameter (as per printf()) and formats each line of text accordingly.

        [% tt_start_tag %] FILTER format('<!-- %-40s -->') [% tt_end_tag %]
        This is a block of text filtered
        through the above format.
        [% tt_start_tag %] END [% tt_end_tag %]

output:

        <!-- This is a block of text filtered        -->
        <!-- through the above format.               -->

[%- END %] [% WRAPPER subsection title = 'upper' -%]

Folds the input to UPPER CASE.

        [% tt_start_tag %] "hello world" | FILTER upper [% tt_end_tag %]

output:

        HELLO WORLD

[%- END %] [% WRAPPER subsection title = 'lower' -%]

Folds the input to lower case.

        [% tt_start_tag %] "Hello World" | FILTER lower [% tt_end_tag %]

output:

        hello world

[%- END %] [% WRAPPER subsection title = 'ucfirst' -%]

Folds the first character of the input to UPPER CASE.

        [% tt_start_tag %] "hello" | FILTER ucfirst [% tt_end_tag %]

output:

        Hello

[%- END %] [% WRAPPER subsection title = 'lcfirst' -%]

Folds the first character of the input to lower case.

        [% tt_start_tag %] "HELLO" | FILTER lcfirst [% tt_end_tag %]

output:

        hELLO

[%- END %] [% WRAPPER subsection title = 'trim' -%]

Trims any leading or trailing whitespace from the input text. Particularly useful in conjunction with INCLUDE, PROCESS, etc., having the same effect as the TRIM configuration option.

        [% tt_start_tag %] INCLUDE myfile | trim [% tt_end_tag %]

[%- END %] [% WRAPPER subsection title = 'collapse' -%]

Collapse any whitespace sequences in the input text into a single space. Leading and trailing whitespace (which would be reduced to a single space) is removed, as per trim.

        [% tt_start_tag %] FILTER collapse [% tt_end_tag %]

           The   cat

           sat    on

           the   mat

        [% tt_start_tag %] END [% tt_end_tag %]

output:

        The cat sat on the mat

[%- END %] [% WRAPPER subsection title = 'html' -%]

Converts the characters '<', '>' and '&' to '&lt;', '&gt;' and '&amp;', respectively, protecting them from being interpreted as representing HTML tags or entities.

        [% tt_start_tag %] FILTER html [% tt_end_tag %]
        Binary "<=>" returns -1, 0, or 1 depending on...
        [% tt_start_tag %] END [% tt_end_tag %]

output:

        Binary "&lt;=&gt;" returns -1, 0, or 1 depending on...

If the Apache::Util or HTML::Entities modules are installed on your system then these will instead be used to encode the text via the escape_html() or encode_entities() subroutines respectively. Both these modules correctly handle the full gamut of HTML entities and will additionally escape characters like 'é' to '&eacute;'. For further information, see http://www.w3.org/TR/REC-html40/sgml/entities.html.

[%- END %] [% WRAPPER subsection title = 'html_para' -%]

This filter formats a block of text into HTML paragraphs. A sequence of two or more newlines is used as the delimiter for paragraphs which are then wrapped in HTML <p>...</p> tags.

        [% tt_start_tag %] FILTER html_para [% tt_end_tag %]
        The cat sat on the mat.

        Mary had a little lamb.
        [% tt_start_tag %] END [% tt_end_tag %]

output:

        <p>
        The cat sat on the mat.
        </p>

        <p>
        Mary had a little lamb.
        </p>

[%- END %] [% WRAPPER subsection title = 'html_break' -%]

Similar to the html_para filter described above, but uses the HTML tag sequence <br><br> to join paragraphs.

        [% tt_start_tag %] FILTER html_break [% tt_end_tag %]
        The cat sat on the mat.

        Mary had a little lamb.
        [% tt_start_tag %] END [% tt_end_tag %]

output:

        The cat sat on the mat.
        <br>
        <br>
        Mary had a little lamb.

[%- END %] [% WRAPPER subsection title = 'uri' -%]

This filter URI escapes the input text, converting any characters outside of the permitted URI character set (as defined by RFC 2396) into a `'%nn'` hex escape.

        [% tt_start_tag %] 'my file.html' | uri [% tt_end_tag %]

output:

        my%20file.html

Note that URI escaping isn't always enough when generating hyperlinks in an HTML document. The `'&'` character, for example, is valid in a URI and will not be escaped by the URI filter. In this case you should also filter the text through the 'html' filter.

        <a href="[% tt_start_tag %] filename | uri | html [% tt_end_tag %]">click here</a>

[%- END %] [% WRAPPER subsection title = 'indent(pad)' -%]

Indents the text block by a fixed pad string or width. The 'pad' argument can be specified as a string, or as a numerical value to indicate a pad width (spaces). Defaults to 4 spaces if unspecified.

        [% tt_start_tag %] FILTER indent('ME> ') [% tt_end_tag %]
        blah blah blah
        cabbages, rhubard, onions
        [% tt_start_tag %] END [% tt_end_tag %]

output:

        ME> blah blah blah
        ME> cabbages, rhubard, onions

[%- END %] [% WRAPPER subsection title = 'truncate(length)' -%]

Truncates the text block to the length specified, or a default length of 32. Truncated text will be terminated with '...' (i.e. the '...' falls inside the required length, rather than appending to it).

        [% tt_start_tag %] FILTER truncate(21) [% tt_end_tag %]
        I have much to say on this matter that has previously
        been said on more than one occasion.
        [% tt_start_tag %] END [% tt_end_tag %]

output:

        I have much to say...

[%- END %] [% WRAPPER subsection title = 'repeat(iterations)' -%]

Repeats the text block for as many iterations as are specified (default: 1).

        [% tt_start_tag %] FILTER repeat(3) [% tt_end_tag %]
        We want more beer and we want more beer,
        [% tt_start_tag %] END [% tt_end_tag %]
        We are the more beer wanters!

output:

        We want more beer and we want more beer,
        We want more beer and we want more beer,
        We want more beer and we want more beer,
        We are the more beer wanters!

[%- END %] [% WRAPPER subsection title = 'remove(string) ' -%]

Searches the input text for any occurrences of the specified string and removes them. A Perl regular expression may be specified as the search string.

        [% tt_start_tag %] "The  cat  sat  on  the  mat" FILTER remove('\s+') [% tt_end_tag %]

output:

        Thecatsatonthemat

[%- END %] [% WRAPPER subsection title = 'replace(search, replace) ' -%]

Similar to the remove filter described above, but taking a second parameter which is used as a replacement string for instances of the search string.

        [% tt_start_tag %] "The  cat  sat  on  the  mat" | replace('\s+', '_') [% tt_end_tag %]

output:

        The_cat_sat_on_the_mat

[%- END %] [% WRAPPER subsection title = 'redirect(file)' -%]

The 'redirect' filter redirects the output of the block into a separate file, specified relative to the OUTPUT_PATH configuration item.

        [% tt_start_tag %] FOREACH user = myorg.userlist [% tt_end_tag %]
           [% tt_start_tag %] FILTER redirect("users/${user.id}.html") [% tt_end_tag %]
              [% tt_start_tag %] INCLUDE userinfo [% tt_end_tag %]
           [% tt_start_tag %] END [% tt_end_tag %]
        [% tt_start_tag %] END [% tt_end_tag %]

or more succinctly, using side-effect notation:

        [% tt_start_tag %] INCLUDE userinfo
             FILTER redirect("users/${user.id}.html")
    	   FOREACH user = myorg.userlist
        [% tt_end_tag %]

A 'file' exception will be thrown if the OUTPUT_PATH option is undefined.

[%- END %] [% WRAPPER subsection title = 'eval(template_text)' -%]

The 'eval' filter evaluates the block as template text, processing any directives embedded within it. This allows template variables to contain template fragments, or for some method to be provided for returning template fragments from an external source such as a database, which can then be processed in the template as required.

        my $vars  = {
    	fragment => "The cat sat on the [% tt_start_tag %] place [% tt_end_tag %]",
        };
        $template->process($file, $vars);

The following example:

        [% tt_start_tag %] fragment | eval [% tt_end_tag %]

is therefore equivalent to

        The cat sat on the [% tt_start_tag %] place [% tt_end_tag %]

The 'evaltt' filter is provided as an alias for 'eval'.

[%- END %] [% WRAPPER subsection title = 'perl(perlcode)' -%]

The 'perl' filter evaluates the block as Perl code. The EVAL_PERL option must be set to a true value or a 'perl' exception will be thrown.

        [% tt_start_tag %] my_perl_code | perl [% tt_end_tag %]

In most cases, the [% tt_start_tag %] PERL [% tt_end_tag %] ... [% tt_start_tag %] END [% tt_end_tag %] block should suffice for evaluating Perl code, given that template directives are processed before being evaluate as Perl. Thus, the previous example could have been written in the more verbose form:

        [% tt_start_tag %] PERL [% tt_end_tag %]
        [% tt_start_tag %] my_perl_code [% tt_end_tag %]
        [% tt_start_tag %] END [% tt_end_tag %]

as well as

        [% tt_start_tag %] FILTER perl [% tt_end_tag %]
        [% tt_start_tag %] my_perl_code [% tt_end_tag %]
        [% tt_start_tag %] END [% tt_end_tag %]

The 'evalperl' filter is provided as an alias for 'perl' for backwards compatibility.

[%- END %] [% WRAPPER subsection title = 'stdout(binmode)' -%]

The stdout filter prints the output generated by the enclosing block to STDOUT. If binmode is set, binary mode on STDOUT is turned on (see the binmode perl function.

The stdout filter can be used to force binmode on STDOUT, or also inside redirect, null or stderr blocks to make sure that particular output goes to stdout. See the null filter below for an example.

[%- END %] [% WRAPPER subsection title = 'stderr' -%]

The stderr filter prints the output generated by the enclosing block to STDERR.

[%- END %] [% WRAPPER subsection title = 'null' -%]

The null filter prints nothing. This is useful for plugins whose methods return values that you don't want to appear in the output. Rather than assigning every plugin method call to a dummy variable to silence it, you can wrap the block in a null filter:

        [% tt_start_tag %] FILTER null;
            USE im = GD.Image(100,100);
            black = im.colorAllocate(0,   0, 0);
            red   = im.colorAllocate(255,0,  0);
            blue  = im.colorAllocate(0,  0,  255);
            im.arc(50,50,95,75,0,360,blue);
            im.fill(50,50,red);
            im.png | stdout(1);
           END;
        -[% tt_end_tag %]

Notice the use of the stdout filter to ensure that a particular expression generates output to stdout (in this case in binary mode).

[%- END %] [% WRAPPER subsection title = 'latex(outputType)' -%]

Passes the text block to LaTeX and produces either PDF, DVI or PostScript output. The 'outputType' argument determines the output format and it should be set to one of the strings: "pdf" (default), "dvi", or "ps".

The text block should be a complete LaTeX source file.

        [% tt_start_tag %] FILTER latex("pdf") -[% tt_end_tag %]
        \documentclass{article}

        \begin{document}

        \title{A Sample TT2 \LaTeX\ Source File}
        \author{Craig Barratt}
        \maketitle

        \section{Introduction}
        This is some text.

        \end{document}
        [% tt_start_tag %] END -[% tt_end_tag %]

The output will be a PDF file. You should be careful not to prepend or append any extraneous characters or text outside the FILTER block, since this text will wrap the (binary) output of the latex filter. Notice the END directive uses '-[% tt_end_tag %]' for the END_TAG to remove the trailing new line.

One example where you might prepend text is in a CGI script where you might include the Content-Type before the latex output, eg:

        Content-Type: application/pdf

        [% tt_start_tag %] FILTER latex("pdf") -[% tt_end_tag %]
        \documentclass{article}
        \begin{document}
        ...
        \end{document}
        [% tt_start_tag %] END -[% tt_end_tag %]

In other cases you might use the redirect filter to put the output into a file, rather than delivering it to stdout. This might be suitable for batch scripts:

        [% tt_start_tag %] output = FILTER latex("pdf") -[% tt_end_tag %]
        \documentclass{article}
        \begin{document}
        ...
        \end{document}
        [% tt_start_tag %] END; output | redirect("document.pdf", 1) -[% tt_end_tag %]

(Notice the second argument to redirect to force binary mode.)

Note that the latex filter runs one or two external programs, so it isn't very fast. But for modest documents the performance is adequate, even for interactive applications.

A error of type 'latex' will be thrown if there is an error reported by latex, pdflatex or dvips.

[%- END %] [%- END %] [% WRAPPER section title='AUTHOR' -%]

Andy Wardley <abw@kfs.org>

[% ttlink('http://www.andywardley.com/', 'http://www.andywardley.com/') -%]

[%- END %] [% WRAPPER section title='VERSION' -%]

Template Toolkit version 2.06d, released on 22 January 2002.

[%- END %] [% WRAPPER section title='COPYRIGHT' -%]

      Copyright (C) 1996-2001 Andy Wardley.  All Rights Reserved.
      Copyright (C) 1998-2001 Canon Research Centre Europe Ltd.

This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

[%- END %]