<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<T3locallang>
	<meta type="array">
		<description>CSH for TypoScript Templates table.</description>
		<type>CSH</type>
		<csh_table>sys_template</csh_table>
	</meta>
	<data type="array">
		<languageKey index="default" type="array">
			<label index=".description">TypoScript template record.</label>
			<label index=".details">The 'Template' records are the vital components used to set the design of the webpages. No matter how (almost) you would like to build your website, it must be initiated by a 'Template' record placed in the root of the page tree of the site.
Basically, create a 'Template' record, enter a title and make sure to check of Clear constants, setup and Rootline. Then enter some TypoScript configuration in the Setup field and you're set.
It's very important to read how to do all this in the documents listed below! Also make sure you use the Web&gt;Template module to do all the working with templates. It's a specialized tool to help you with this.</label>
			<label index="_.seeAlso">static_template
TSref | http://typo3.org/documentation/document-library/doc_core_tsref/
TypoScript by Example | http://typo3.org/documentation/document-library/doc_core_tsbyex/</label>
			<label index="_.image">EXT:context_help/cshimages/systemplate.png,
EXT:context_help/cshimages/systemplate1.png</label>
			<label index=".image_descr">A Template Record with constants and setup code.
The Web&gt;Template module contains tools which will help you to edit and validate TypoScript structures.</label>
			<label index="hidden.description">Hiding the template will deactivate the template record.</label>
			<label index="hidden.details">If the Template Record was the first record on a page hiding it will expose the second record on the page instead.</label>
			<label index="starttime.description">Start time. Use this to enable a template on a certain date.</label>
			<label index="endtime.description">End time. Use this to disable a template on a certain date.</label>
			<label index="title.description">The title of the template record is only an internal label and does not have any effect on the output in the frontend.</label>
			<label index="sitetitle.description">Website title. Typically this will automatically be prefixed all page titles in the &lt;title&gt; tag of the frontend pages.</label>
			<label index="constants.description">TypoScript Constants.</label>
			<label index="_constants.seeAlso">static_template:constants</label>
			<label index="config.description">TypoScript Setup code</label>
			<label index="config.details">Read more about TypoScript Templates in TSref, TypoScript by Example and Getting Started.</label>
			<label index="_config.seeAlso">static_template:config,
TSref | http://typo3.org/documentation/document-library/doc_core_tsref/
Getting Started | http://typo3.org/documentation/document-library/doc_tut_quickstart/
TypoScript by Example | http://typo3.org/documentation/document-library/doc_core_tsbyex/
TypoScript Syntax | http://typo3.org/documentation/document-library/doc_core_ts/</label>
			<label index="resources.description">Resource files for the template. For example a logo, a TTF-font etc.</label>
			<label index="resources.details">Resource files can be referenced in TypoScript Template code by [filename]*.[ext] and has the advantage that the reference from TypoScript is not broken if you copy or export a Template Record where the resources ends up with new names.</label>
			<label index="clear.description">Flags that will clear the inheritance of TypoScript code from former templates in the root line. There is a flag for Constants and one for Setup code.</label>
			<label index="clear.details">In the Web &gt; Template / Template Analyser module you can see how far back in the template tree that constants and setup code is inherited.</label>
			<label index="_clear.seeAlso">sys_template:root</label>
			<label index="_clear.image">EXT:context_help/cshimages/systemplate2.png</label>
			<label index="root.description">Defines that the template represents a root of a website.</label>
			<label index="_root.seeAlso">sys_template:clear</label>
			<label index="includeStaticAfterBasedOn.description">If set, static templates will be included after &quot;based-on&quot; templates. It basically swaps the order of inclusion of these external TypoScript sources.</label>
			<label index="includeStaticAfterBasedOn.details">The Web &gt; Template / Template Analyser module allows you to view the order of inclusion of all TypoScript sources your template uses.</label>
			<label index="include_static.description">Static Template records to include.</label>
			<label index="_include_static.seeAlso">static_template</label>
			<label index="include_static_file.description">Static Template files to include.</label>
			<label index="include_static_file.details">Static template files are registered by extensions contrary to Static Template records which come from the static database table, &quot;static_template&quot;.</label>
			<label index="_include_static_file.seeAlso">sys_template:include_static</label>
			<label index="basedOn.description">Other Template Records that are included like &quot;static templates&quot;.</label>
			<label index="static_file_mode.description">Define the mode of inclusion of static template files.</label>
			<label index="static_file_mode.details">If you are in doubt about the inclusion order, make sure to use the Web &gt; Template / Template Analyser to view the order.</label>
			<label index="nextLevel.description">Defines a template record to make active one level out in the page tree of this branch. This can be used to define another template record for the general website while having a special template for the frontpage.</label>
			<label index="description.description">Enter a description of the template if you like.</label>
			<label index="editorcfg.description">Editor Configuration for the stylesheet editor extension.</label>
		</languageKey>
	</data>
</T3locallang>