Template processor

<h2 id="typical-features">Typical features</h2>
<p>Template engines typically include features common to most <a href="/facts/High-level_programming_language/smjECUhx">high-level programming languages</a>, with an emphasis on features for processing <a href="/facts/Plain_text/TSlSSAg2">plain text</a>.
</p><p>Such features include:
</p>
<ul><li><a href="/facts/Variable_(programming)/VoCKtwml">variables</a> and <a href="/facts/Function_(computer_science)/9vFJrg0A">functions</a></li>
<li>text replacement</li>
<li>file inclusion (or <a href="/facts/Transclusion/QV9bvV3s">transclusion</a>)</li>
<li>conditional evaluation and <a href="/facts/Control_flow/2XTDfErC">loops</a></li></ul>
<h2 id="embedded-template-engines">Embedded template engines</h2>
<p>While template processors are typically a separate piece of software, used as part of a system or framework, simple templating languages are commonly included in the string processing features of <a href="/facts/General-purpose_programming_language/LyA5zR3M">general-purpose programming languages</a>, and in text processing programs, notably <a href="/facts/Text_editor/jPCgtbvN">text editors</a> or <a href="/facts/Word_processor/qAR7lagF">word processors</a>. The templating languages are generally simple substitution-only languages, in contrast to the more sophisticated facilities in full-blown template processors, but may contain some logic.
</p><p>Simple examples include <a href="/facts/Printf_format_string/Sc6Czbp2">‘printf’ print format strings</a>, found in many programming languages, and <a href="/facts/Snippet_(programming)/X3P0GDlq">snippets</a>, found in a number of text editors and <a href="/facts/Source_code_editor/D0hecHMt">source code editors</a>. In word processors, <a href="/facts/Template_(word_processing)/VmDFkSks">templates</a> are a common feature, while automatic filling in of the templates is often referred to as <a href="/facts/Mail_merge/VBBgV65P">mail merge</a>.
</p><p>An illustrative example of the complementary nature of <a href="/facts/Parsing/nRKB01S3">parsing</a> and templating is the s (substitute) command in the <a href="/facts/Sed/5pXUwRdD">sed</a> text processor, originating from search-and-replace in the <a href="/facts/Ed_(text_editor)/a3lSk6Ry">ed</a> text editor. Substitution commands are of the form s/regexp/replacement/, where regexp is a <a href="/facts/Regular_expression/KFL3veHX">regular expression</a>, for parsing input, and replacement is a simple template for output, either literal text, or a format string containing the characters & for "entire match" or the special <a href="/facts/Escape_sequence/r7lISrrw">escape sequences</a> \1 through \9 for the <i>n</i>th sub-expression. For example, s/(cat|dog)s?/\1s/g replaces all occurrences of "cat" or "dog" with "cats" or "dogs", without duplicating an existing "s": (cat|dog) is the 1st (and only) sub-expression in the regexp, and \1 in the format string substitutes this into the output.
</p>
<h2 id="system-elements">System elements</h2>
<p>All template processing systems consist of at least these primary elements:
</p>
<ul><li>an associated data model;</li>
<li>one or more source templates;</li>
<li>a processor or template engine;</li>
<li>generated output in the form of result documents.</li></ul>
<h3>Data model</h3>
<p>This may be a <a href="/facts/Relational_database/pEKGmJLy">relational database</a>, a source file such as <a href="/facts/XML/clNgUfWk">XML</a>, an alternate format of <a href="/facts/Flat_file_database/aNeNVE3h">flat file database</a>, a <a href="/facts/Spreadsheet/0cvc1GeB">spreadsheet</a> or any of other various sources of preformatted data. Some template processing systems are limited in the types of data that can be used. Others are designed for maximum flexibility and allow many different types of data.
</p>
<h3>Source template</h3>
<p>Source templates are traditionally specified:
</p>
<ul><li>according to a pre-existing programming language;</li>
<li>according to a specially-defined template language;</li>
<li>according to the features of a hosting software application; or</li>
<li>according to a hybrid combination of some or all of the above.</li></ul>
<h3>Template engine</h3>
<p>The template engine is responsible for:
</p>
<ul><li>connecting to the data model;</li>
<li>processing the code specified in the source templates; and</li>
<li>directing the output to a specific <a href="/facts/Pipeline_(computing)/xmHjrPMP">pipeline</a>, <a href="/facts/Text_file/zYW4JmES">text file</a>, or <a href="/facts/Stream_(computing)/2jtBAp0U">stream</a>.</li></ul>
<p>Additionally some template engines allow additional configuration options.
</p>
<h3>Result documents</h3>
<p>These may consist of an entire document or a document fragment.
</p>
<h2 id="uses">Uses</h2>
<p>Template processing is used in various contexts for different purposes. The specific purpose is ordinarily contingent upon the <a href="/facts/Software_application/YQuj7Kog">software application</a> or template engine in use. However, the flexibility of template processing systems often enables unconventional uses for purposes not originally intended by the original designers.
</p>
<h3>Template engine</h3>
<p>A template engine is a specific kind of template processing module that exhibits all of the major features of a modern <a href="/facts/Programming_language/cWTYbgWa">programming language</a>. The term <i>template engine</i> evolved as a generalized description of programming languages whose primary or exclusive purpose was to process templates and data to output text. The use of this term is most notably applied to <a href="/facts/Web_development/UW5ypSzj">web development</a> using a <a href="/facts/Web_template_system/zWstHsCF">web template system</a>, and it is also applied to other contexts as well.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a>
</p>
<h3>Document generation</h3>
<p>Document generation frameworks typically use template processing as the central model for generating documents.
</p>
<h3>Source code generation</h3>
<p>Source code generation tools support generation of <a href="/facts/Source_code/o9J6Jv23">source code</a> (as the result documents) from abstract data models (e.g., UML, relational data, domain-specific enterprise data stores) for particular application domains, particular organizations, or in simplifying the production process for <a href="/facts/Computer_programmer/WGTS1Jv9">computer programmers</a>.
</p>
<h3>Software functionality</h3>
<p>A <a href="/facts/World_Wide_Web/wvnTrWFq">web</a> template engine processes web templates and source data (typically from a <a href="/facts/Relational_database/pEKGmJLy">relational database</a>) to produce one or more output <a href="/facts/Web_page/5JK7xQLe">web pages</a> or page fragments. It is ordinarily included as a part of a <a href="/facts/Web_template_system/zWstHsCF">web template system</a> or <a href="/facts/Application_framework/xSzKMgdn">application framework</a>. Currently, template processing software is most frequently used in the context of development for the <a href="/facts/World_Wide_Web/wvnTrWFq">web</a>.
</p>
<h2 id="comparison">Comparison</h2>
<p class="note">Further information: <a href="/facts/Comparison_of_web_template_engines/MDfM0T0a">Comparison of web template engines</a></p>
<p><a href="/facts/XSLT/0gw4WVyJ">XSLT</a> is a template processing model designed by <a href="/facts/W3C/lGWmhF6M">W3C</a>. It is designed primarily for transformations on <a href="/facts/XML/clNgUfWk">XML</a> data (into <a href="/facts/Web_document/5JK7xQLe">web documents</a> or other output).
</p><p><a href="/facts/Programming_languages/cWTYbgWa">Programming languages</a> such as <a href="/facts/Perl/fx31kjlT">Perl</a>, <a href="/facts/Python_(programming_language)/YbuGqofa">Python</a>, <a href="/facts/PHP/vU6YRJX0">PHP</a>, <a href="/facts/Ruby_(programming_language)/BeYSaPSR">Ruby</a>, <a href="/facts/C_Sharp_(programming_language)/UC2gxeyb">C#</a>, <a href="/facts/Java_(programming_language)/9ScgFyAL">Java</a>, and <a href="/facts/Go_(programming_language)/oWlsmAFJ">Go</a> support template processing either natively, or through add-on libraries and modules. <a href="/facts/JavaServer_Pages/LAr4ALkb">JavaServer Pages</a>,<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> <a href="/facts/Active_Server_Pages/um62st21">Active Server Pages</a>,<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> <a href="/facts/Genshi_(templating_language)/8wSDCVsm">Genshi</a> (for Python), and <a href="/facts/ERuby/SfQFc10o">eRuby</a> are examples of template engines designed specifically for web application development.
</p><p>Moreover, template processing is sometimes included as a sub-feature of software packages like <a href="/facts/Text_editors/jPCgtbvN">text editors</a>, <a href="/facts/Integrated_development_environment/jbEINSQf">IDEs</a> and <a href="/facts/Relational_database_management_system/pEKGmJLy">relational database management systems</a>.
</p>
<h2 id="benefits-of-using-template-engines">Benefits of using template engines</h2>
<ul><li>encourages organization of source code into operationally-distinct layers (see e.g., <a href="/facts/Model%E2%80%93view%E2%80%93controller/vRbMXjMm">MVC</a>)</li>
<li>enhances productivity by reducing unnecessary reproduction of effort</li>
<li>enhances teamwork by allowing separation of work based on skill-set (e.g., artistic vs. technical)</li></ul>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Document_automation/uFuGEfrk">Document automation</a></li>
<li><a href="/facts/Document_modelling/Fvg51CRu">Document modelling</a></li>
<li><a href="/facts/Domain-specific_programming_language/n18H1foD">Domain-specific programming language</a></li>
<li><a href="/facts/Glossary_of_operating_systems_terms/R3sBMIEY">Glossary of operating systems terms § Templating</a></li>
<li><a href="/facts/Internationalization_and_localization/IGkl9VBM">Internationalization and localization</a>
<ul><li><a href="/facts/Common_Locale_Data_Repository/sk5wnKHw">Common Locale Data Repository</a></li>
<li><a href="/facts/Gettext/ujpNUjg8">gettext</a></li></ul></li>
<li><a href="/facts/Layout_engines/o6SD3C5r">Layout engines</a></li>
<li><a href="/facts/Macro_(computer_science)/7abAsm1o">Macro (computer science)</a></li>
<li><a href="/facts/Web_template_system/zWstHsCF">Web template system</a>
<ul><li><a href="/facts/Comparison_of_web_template_engines/MDfM0T0a">Comparison of web template engines</a></li></ul></li></ul>

<h2 id="external-links">External links</h2>
<ul><li><a href="http://www.cs.usfca.edu/~parrt/papers/mvc.templates.pdf">Enforcing Strict Model-View Separation in Template Engines</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>Niemeyer, Patrick (2002). Learning Java. Sebastopol: O'Reilly. ISBN 0-596-00285-8. <a href="0-596-00285-8" target="_blank">0-596-00285-8</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>Manolescu, Dragos (2006). Pattern Languages of Program Design 5. Reading: Addison-Wesley Professional. ISBN 0-321-32194-4. <a href="0-321-32194-4" target="_blank">0-321-32194-4</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>Fowler, Martin (2003). Patterns of Enterprise Application Architecture. Boston: Addison-Wesley. ISBN 0-321-12742-0. <a href="0-321-12742-0" target="_blank">0-321-12742-0</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
<li id="fn:4"><p>(see e.g., Velocity, TemplateToolkit, Freemarker ). <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li>
<li id="fn:5"><p>JavaServer Pages is a technology released by Sun for use with the Java programming language.
"JavaServer Pages Technology". 2006-10-10. Retrieved 2006-10-10. <a href="http://java.sun.com/products/jsp/faq.html#1" target="_blank">http://java.sun.com/products/jsp/faq.html#1</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li>
<li id="fn:6"><p>ASP 1.0 was originally released for use with Microsoft VBScript and JScript.
It was an extension to Microsoft IIS. <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li>
</ol>

Template processor open-in-new

Template processor