Glossary/Version 0.1/XML

From TYPO3Wiki

Jump to: navigation, search
 List Projects The Glossary Collection-project
list pages
See Current Project Members, Wishlist 
    you can help if you like!

Here is the xml-file of version 0.1 of the glossary of TYPO3 related terms, what you have in the Backend in the moment. Go back to glossary 0.1

it starts after the 4 minus-signs. publish-date: 23.02.2006


<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<T3locallang>
	<meta type="array">
		<description>TYPO3 glossary</description>
		<type>CSH</type>
		<csh_table>xGLOSSARY_t3</csh_table>
	</meta>
	<data type="array">
		<languageKey index="default" type="array">
			<label index=".alttitle">TYPO3 glossary</label>
			<label index=".description">Glossary of TYPO3 related terms.</label>
			<label index="access_control_list.alttitle">access control list</label>
			<label index="access_control_list.description">See "access list"</label>
			<label index="_access_control_list.seeAlso">xGLOSSARY_t3:access_list</label>
			<label index="access_list.alttitle">access list</label>
			<label index="access_list.description">In TYPO3, a list of explicitly assigned permissions within a certain area of the system. For instance access to individual backend modules, database tables and fields is managed by specifically adding these items to an access list for a backend usergroup.</label>
			<label index="access_restricted.alttitle">access restricted</label>
			<label index="access_restricted.description">See "access restriction"</label>
			<label index="_access_restricted.seeAlso">xGLOSSARY_t3:access_restriction</label>
			<label index="access_restriction.alttitle">access restriction</label>
			<label index="access_restriction.description">In TYPO3 frontend, the term for protecting a part of a website with a username/password. More specifically access restriction can work on all database elements in TYPO3, not only pages. Access restriction of pages in TYPO3 provides the means to create intra- and extranets.</label>
			<label index="_access_restriction.seeAlso">http://typo3.org/doc.0.html%26tx_extrepmgm_pi1%5BextUid%5D%3D491%26tx_extrepmgm_pi1%5BtocEl%5D%3D1347%26cHash%3D5327d899a5|How to create access restricted page</label>
			<label index="acl.alttitle">ACL</label>
			<label index="acl.description">See "access list"</label>
			<label index="_acl.seeAlso">xGLOSSARY_t3:access_list</label>
			<label index="active_state.alttitle">active state</label>
			<label index="active_state.description">For website navigation (menu items), active state is when the menu item represents a page that is found in the path (or rootline) of the users current position on the website. Not to be mistaken for current state or CSS a:active. For instance if a user is at "[Home] > [Contact] > [Email addresses]"  then [Home] and [Contact] will be in active state while [Email addresses] will be in current state. Practically you can define how a menu item should be rendered differently in active and current state so that the users position on a website becomes visually clear from the menu.</label>
			<label index="_active_state.seeAlso">http://typo3.org/doc.0.html%26tx_extrepmgm_pi1%5BextUid%5D%3D270%26tx_extrepmgm_pi1%5BtocEl%5D%3D382%26cHash%3Db13af36f98__|Item states described in Typoscript reference</label>
			<label index="admin_panel.alttitle">admin panel</label>
			<label index="admin_panel.description">The admin panel is a very important and often underestimated tool. It is useful to:
* control the HTML-output of TS objects
* publish pages or branches of your website as static pages
* control the frontend editing interface for users
* control the caching behaviour of pages or branches of your website
* show information about the current page</label>
			<label index="_admin_panel.seeAlso">http://typo3.org/documentation/document-library/doc_core_tsconfig/ADMPANEL/|About Admin panel in Typoscript configuration (TSConfig)</label>
			<label index="admin_user.alttitle">admin user</label>
			<label index="admin_user.description">A user having all possible privileges in the backend.</label>
			<label index="administration_interface.alttitle">administration interface</label>
			<label index="administration_interface.description">An alternative term for the backend.</label>
			<label index="_administration_interface.seeAlso">xGLOSSARY_t3:backend</label>
			<label index="administrator.alttitle">administrator</label>
			<label index="administrator.description">In TYPO3 it is a person responsible for maintaining the website(s) and the installation.</label>
			<label index="alias.alttitle">alias</label>
			<label index="alias.description">Every page can be given an alias. It is a unique identification string which can be used as an alternative to the page's UID. The alias field can be found in the page header, by checkmarking the "Show secondary options" checkbox. The length is by default 20 characters. If you are using the simulateStaticDocuments option to include the names of pages in TYPO3 URLs, alias will override the page title, allowing you to have one title in menus and at the top of the web page, and a different title in the URL.</label>
			<label index="alternative_backend.alttitle">Alternative backend</label>
			<label index="alternative_backend.description">The name Alternative backend (AB) was coined with version 3.3b1 of TYPO3. Back then the Alternative backend was an 80% effective alternative to the Classic backend (CB) which has been the trademark of TYPO3 since the dawn of times.
However the Alternative backend denoted a transition which had to be made. And with the final TYPO3 3.0 version the Alternative backend is the new standard. It has finally become the Absolute backend!</label>
			<label index="_alternative_backend.seeAlso">http://typo3.org/documentation/articles/classic-or-alternative/</label>
			<label index="apache.alttitle">Apache</label>
			<label index="apache.description">The most popular open source HTTP web server for Unix platforms (BSD, Linux, and UNIX systems), Microsoft Windows and other platforms.</label>
			<label index="_apache.seeAlso">http://httpd.apache.org/|Apache HTTP Server Project</label>
			<label index="api.alttitle">API</label>
			<label index="api.description">The TYPO3 API (application programming interface) provides a set of commonly-used functions. Extension programmers can make use of the functionality of the API, so they don't have to program everything from scratch. The API is an abstraction layer.</label>
			<label index="attribute.alttitle">attribute</label>
			<label index="attribute.description">An attribute is a part of a HTML tag describing it's properties. These properties may be visible like e.g. text color or the text shown by a text input element but attributes may also describe invisible properties like a name or id (identifier) of a HTML tag.
Attributes are also used in Typoscript; The "sub-values" of Typoscript objects are commonly referred to as attributes.</label>
			<label index="authorisation.alttitle">authorisation</label>
			<label index="authorisation.description">See "permission"</label>
			<label index="_authorisation.seeAlso">xGLOSSARY_t3:permission</label>
			<label index="available_extensions.alttitle">available extensions</label>
			<label index="available_extensions.description">This view in the Extension Manager shows the list of extensions that are located on the webserver. An icon marks the status: installed ("-", green) or not installed ("+", red).</label>
			<label index="backend.alttitle">backend</label>
			<label index="backend.description">TYPO3 is divided into two areas - the backend and the frontend. All the administration of the website is done in the backend, this means only you and your content contributers are allowed access to the backend. A username and password is always required.</label>
			<label index="_backend.seeAlso">http://typo3.org/documentation/document-library/doc_tut_quickstart/Backend_and_frontend/|Getting Started - backend and frontend</label>
			<label index="backend_editor_configuration.alttitle">backend editor configuration</label>
			<label index="backend_editor_configuration.description">Generally a configuration in Typoscript syntax that can determine behaviour of the backend interface, eg. an editor. Specifically used for a stylesheet editor where the configuration was the basis for the style options given by the editor. The concept is considered obsolete.</label>
			<label index="backend_login.alttitle">backend login</label>
			<label index="backend_login.description">This may refer two one of two things. First, it may refer to the backend login credentials, i.e. username and password needed to log in to the backend. Second it may refer to the login form that allows one to enter the backend of TYPO3. This can usually be located at the address of your website by appending "typo3/" to the URL. There you can login as a backend user.</label>
			<label index="backend_modules.alttitle">backend modules</label>
			<label index="backend_modules.description">See "module"</label>
			<label index="_backend_modules.seeAlso">xGLOSSARY_t3:module</label>
			<label index="backend_user.alttitle">backend user</label>
			<label index="backend_user.description">User being able to login to the backend interface of TYPO3. This usually implies editor capabilities, i.e. the permission to change website content through the backend. A backend user may have restricted permissions, though, e.g. he may only be allowed to access visitor statistics.</label>
			<label index="backend_usergroup.alttitle">backend usergroup</label>
			<label index="backend_usergroup.description">A backend usergroup is used to group backend users together. It allows to set access permissions to the page tree (by means of DB mounts), the file system (by means of file mounts) and the other options the backend of TYPO3 offers. To get access to the full range of settings, make sure to enable the use of ACL (access control lists) when creating a backend usergroup.</label>
			<label index="basis_template.alttitle">Basis template</label>
			<label index="basis_template.description">A Basis template is any Typoscript template you create (ie not a Static template) and then include in another Typoscript template.  In other words: create template A, save it in a page/folder, create template B, scroll the new template form down to "Include basis template", then click on the folder icon and find template A.  This will cause template A be included in template B when B is parsed. You may include more than one basis template, giving you the possibility to have a master template that includes different subtemplates.</label>
			<label index="_basis_template.seeAlso">http://typo3.org/documentation/document-library/doc_core_tsbyex/Case_quot_Include/|Typoscript by Example - Include Basis template</label>
			<label index="be.alttitle">BE</label>
			<label index="be.description">See "backend"</label>
			<label index="_be.seeAlso">xGLOSSARY_t3:backend</label>
			<label index="be_user.alttitle">BE user</label>
			<label index="be_user.description">See "backend user"</label>
			<label index="_be_user.seeAlso">xGLOSSARY_t3:backend_user</label>
			<label index="branch.alttitle">branch</label>
			<label index="branch.description">A branch is a part of a tree. In TYPO3 this is usually the page tree. Each page represents a node where the tree can be split up in different branches by filling in additional subpages. It's very important to keep this picture in mind when using things like "leveluid"where Typoscript reference is speaking of "from behind" for negative values (which means "backwards from the branch to the root") and "outermost level"(which means "the place in the branch where I currently am").</label>
			<label index="_branch.seeAlso">http://en.wikipedia.org/wiki/Fork_%28software%29|About forking (software) on Wikipedia</label>
			<label index="cache.alttitle">cache</label>
			<label index="cache.description">The TYPO3 website cache stores parts of the website (pages, generated or changed images, and other data) in special files and cache tables in the database.  It's faster to retrieve pages or data from the cache than it is to build the pages or data from scratch.  This speeds up the access time for the website substantially.</label>
			<label index="cascading_style_sheets.alttitle">Cascading Style Sheets</label>
			<label index="cascading_style_sheets.description">Cascading Style Sheets (CSS) is a system for formatting HTML web pages. When the Cascading Style Sheets are seperated from the HTML being formatted (in separate files or placed in the header section of the HTML text), they effectively separate the document content/structure from the document presentation. Other advantages include great flexibility in layout and the use of CSS improves the readability of HTML code.</label>
			<label index="_cascading_style_sheets.seeAlso">http://www.w3.org/Style/CSS/|W3C style sheet pages</label>
			<label index="children.alttitle">children</label>
			<label index="children.description">Used in context of the page tree, it's a common term in computer-science, when talking about any kind of tree. Every page (except the rootpage) has got exactly one parent and to these parents all direct sub pages are children. In TYPO3 this means that each record or content element is a child of exactly one folder. The parent's uid (unique identifier) will be automatically inserted as the child's pid (parent identifier).</label>
			<label index="class.alttitle">class</label>
			<label index="class.description">In webtechnology a class refers to a property of an HTML-element. Classes on HTML-elements are mainly used to layout a website using CSS.
In object-oriented programming, a class consists of encapsulated instance variables and subprograms (methods). A class describes the rules by which objects behave; these objects are referred to as "instances" of that class. A class specifies the structure of data which each instance contains as well as the methods (functions) which manipulate the data of the object; such methods are sometimes described as "behavior".</label>
			<label index="_class.seeAlso">http://en.wikipedia.org/wiki/Class_%28computer_science%29|About classes on Wikipedia</label>
			<label index="classic_backend.alttitle">Classic backend</label>
			<label index="classic_backend.description">The Classic backend was the only backend interface up to version 3.0 of TYPO3. It had a true multidocument interface, designed to minimize data transfer to the server. However the concept was a monster with 6000 lines of JavaScript involved. The Alternative backend that has superseded the Classic backend is now the standard interface to TYPO3.</label>
			<label index="_classic_backend.seeAlso">http://typo3.org/documentation/articles/classic-or-alternative/</label>
			<label index="clear_cache.alttitle">clear cache</label>
			<label index="clear_cache.description">After making changes to a page you may need to clear the cache in order to see the changes in the frontend. This happens because TYPO3 may have saved the old version of the page in the cache.  You clear a page from the cache by clicking on the "Clear All Cache" link in the backend, or by checking the "No cache" box in the page header form, or by checking the "No caching" box in the Admin Panel.</label>
			<label index="clear_constants.alttitle">clear constants</label>
			<label index="clear_constants.description">See "clear flag"</label>
			<label index="_clear_constants.seeAlso">xGLOSSARY_t3:clear_flag</label>
			<label index="clear_flag.alttitle">clear flag</label>
			<label index="clear_flag.description">Used in template records. There are two clear flags: The "Clear constants" and "Clear setup" flags. It means that no Typoscript configuration code is inherited from template records earlier in the tree (closer to the root), if there are any. These flags should always be set for template records serving as main templates (rootlevel).</label>
			<label index="clear_setup.alttitle">clear setup</label>
			<label index="clear_setup.description">See "clear flag"</label>
			<label index="_clear_setup.seeAlso">xGLOSSARY_t3:clear_flag</label>
			<label index="click-enlarge.alttitle">click-enlarge</label>
			<label index="click-enlarge.description">Option making it possible to click on an image to see an enlarged version in a popup window.</label>
			<label index="clickmenu.alttitle">clickmenu</label>
			<label index="clickmenu.description">See "context sensitive menu"</label>
			<label index="_clickmenu.seeAlso">xGLOSSARY_t3:context_sensitive_menu</label>
			<label index="clip_board.alttitle">clip board</label>
			<label index="clip_board.description">See "clipboard"</label>
			<label index="_clip_board.seeAlso">xGLOSSARY_t3:clipboard</label>
			<label index="clipboard.alttitle">clipboard</label>
			<label index="clipboard.description">A temporary storage space used when you copy or cut information.  To view the clipboard in the backend click on "List" in the left hand column then checkmark the "Show clipboard" box on the right.</label>
			<label index="clipboard_pads.alttitle">clipboard pads</label>
			<label index="clipboard_pads.description">See "numeric pads"</label>
			<label index="_clipboard_pads.seeAlso">xGLOSSARY_t3:numeric_pads</label>
			<label index="cms.alttitle">CMS</label>
			<label index="cms.description">See "web content management system"</label>
			<label index="_cms.seeAlso">xGLOSSARY_t3:web_content_management_system</label>
			<label index="coa.alttitle">COA</label>
			<label index="coa.description">See "content object array"</label>
			<label index="_coa.seeAlso">xGLOSSARY_t3:content_object_array</label>
			<label index="column.alttitle">column</label>
			<label index="column.description">See "content column"</label>
			<label index="_column.seeAlso">xGLOSSARY_t3:content_column</label>
			<label index="condition.alttitle">condition</label>
			<label index="condition.description">In Typoscript conditions is a simple kind of control structure, that validates true or false based on some criteria. The outcome of the validation determines if the following Typoscript code should be parsed, or not.</label>
			<label index="_condition.seeAlso">http://typo3.org/documentation/document-library/doc_core_tstemplates/Conditions-1/|Conditions described in Typoscript templates</label>
			<label index="configuration.alttitle">configuration</label>
			<label index="configuration.description">See "TYPO3_CONF_VARS"</label>
			<label index="_configuration.seeAlso">xGLOSSARY_t3:typo3_conf_vars</label>
			<label index="constant_editor.alttitle">Constant editor</label>
			<label index="constant_editor.description">A view in the template module which provides easy access through form fields to Typoscript constants. Is designed to allow less technical developers to customize Standard templates (or template records which carries meta-information for constants included). Is provided by the extension "tstemplate_ceditor"</label>
			<label index="constants.alttitle">constants</label>
			<label index="constants.description">In programming language some data cannot be altered. They are constants. In PHP constants are identifiers which contain a value that can't be modified after it has been setup. Constants are not prefixed by $ sign and are set by the PHP function define().
In TYPO3 a constant is a predefined TypoScript variable that can be reused in Typoscript setup and/or PHP functions. Constants can be set manually or via the constant editor. Imagine lots of color values in a larger Typoscript setup that are all the same. Instead of writing the value itself a constant is inserted, giving the user the possibility to change these values by only changing the constant value.</label>
			<label index="_constants.seeAlso">http://www.php.net/manual/en/function.define.php|PHP define function</label>
			<label index="content_column.alttitle">content column</label>
			<label index="content_column.description">Content elements are organized in (by default 4) content columns. These columns, however, just represent four configurable placeholders for the content in the frontend. It is possible to add more content columns and to use TemplaVoila to get around the column-limitation.</label>
			<label index="content_default.alttitle">content (default)</label>
			<label index="content_default.description">A Static template that contains predefined Typoscript objects for rendering the content elements on a page.</label>
			<label index="content_element.alttitle">content element</label>
			<label index="content_element.description">Content elements are objects in the backend which cause content to be displayed on the frontend web pages. A page can contain one or more content elements. The information which a content element displays might be text, images, music, video, raw HTML, log in forms or email forms or whatever. Sometimes the content element contains information to be displayed and sometimes it refers to other information records, which are also contained by pages. Certain functions are available to every content element, for example they can be hidden by certain criteria such as time, accessgroups etc, the order of appearance on the web page can be manipulated and a few other things.</label>
			<label index="content_element_type.alttitle">content element type</label>
			<label index="content_element_type.description">The type of a content element decides which content the element may contain and offers different ways of presentation of this content. Common content element types are: image, text, text with image, plugin, etc.</label>
			<label index="content_management_framework.alttitle">Content Management Framework</label>
			<label index="content_management_framework.description">TYPO3 has an open API which allows you to extend TYPO3 in many different directions to tailor it to a particular need. Essentially it is this ability which means that it is more than just a content management system, it is a Content Management Framework (CMF).</label>
			<label index="content_management_system.alttitle">Content Management System</label>
			<label index="content_management_system.description">A Content Management System (CMS) is software, usually a database application, that makes it easy to create and maintain content based publications (such as websites, magazines and newspapers) and to manage publishing formats associated with them.</label>
			<label index="content_object.alttitle">content object</label>
			<label index="content_object.description">A category of Typoscript objects designed to generate and display content. Content objects (cObjects) are what makes Typoscript spin around.</label>
			<label index="_content_object.seeAlso">http://typo3.org/documentation/document-library/doc_core_tsref/PHP_information/|Typooscript Reference, (TSRef),, http://typo3.org/documentation/document-library/doc_core_tsbyex/Introduction-3/|Typoscript by example</label>
			<label index="content_object_array.alttitle">content object array</label>
			<label index="content_object_array.description">In Typoscript a content object used for configuring an array of content objects.  For example, a 'text with image' content element on a page might be configured in Typoscript as an array of three content objects: a title, an image, and some text.</label>
			<label index="context_menu.alttitle">context menu</label>
			<label index="context_menu.description">See "context sensitive menu"</label>
			<label index="_context_menu.seeAlso">xGLOSSARY_t3:context_sensitive_menu</label>
			<label index="context_sensitive_editing.alttitle">context sensitive editing</label>
			<label index="context_sensitive_editing.description">Editing of content at the place it is presented. Also known as "frontend editing". In TYPO3 this is typically implemented as a little pencil-icon shown close to the headline, text, image etc. that the user wants to edit. A click on the icon will bring up a formular where the content can be edited and saved right away. The concept represents a high degree of usability since it is based on intuition while it also introduces some limitations compared to regular backend editing.</label>
			<label index="context_sensitive_help.alttitle">Context Sensitive Help</label>
			<label index="context_sensitive_help.description">Context Sensitive Help (CSH) is a help feature that changes depending on what you are doing in a program. In the TYPO3 backend there are small question mark icons beside form fields. Clicking on one of these icons will open a popup window containing information about the field.
The CSH system reads PHP and XML files which contain form field explainations and word definitions. It reads them from the context_help system extension and other extensions. It stores the definitions in a nested associative array called $TCA_DESCR similar to $TSFE (where Typoscript configuration is stored).</label>
			<label index="_context_sensitive_help.seeAlso">http://typo3.org/documentation/document-library/doc_core_inside/Context_Sensitive_He/|CSH section of Inside TYPO3</label>
			<label index="context_sensitive_menu.alttitle">context sensitive menu</label>
			<label index="context_sensitive_menu.description">A menu which appears in response to a user action (typically a mouse click) and whose contents are
determined by which application window was clicked or has the input focus. The context-sensitive menu provides quick access to a subset of functions that are particularly relevant to the window area clicked on.</label>
			<label index="control_element.alttitle">control element</label>
			<label index="control_element.description">An element which has a controlling function. An example is a domain or Typoscript template record. Domain records control by their position in the page tree where the entry point for a certain domain name will be. A Typoscript record controls the frontend behaviour of the page tree from the point where it is positioned.</label>
			<label index="cookies.alttitle">cookies</label>
			<label index="cookies.description">An HTTP cookie (usually called simply a cookie) is a packet of information sent by a server to a World Wide Web browser and then sent back by the browser each time it accesses that server.
Cookies can contain any arbitrary information the server chooses and are used to maintain state between otherwise stateless HTTP transactions. Typically this is used to authenticate or identify a registered user of a web site as part of their first login process or initial site registration without requiring them to sign in again every time they access that site. Other uses are maintaining a "shopping basket" of goods selected for purchase during a session at a site, site personalisation (presenting different pages to different users), and tracking a particular user's access to a site.</label>
			<label index="_cookies.seeAlso">http://en.wikipedia.org/wiki/HTTP_cookie|Wikipedia about cookies</label>
			<label index="copy.alttitle">copy</label>
			<label index="copy.description">To reproduce information or an object by placing it into the clipboard. The original content stays in place when pasted from the clipboard.</label>
			<label index="core.alttitle">core</label>
			<label index="core.description">The core system of TYPO3 (tslib, t3lib, sysext)</label>
			<label index="csh.alttitle">CSH</label>
			<label index="csh.description">See "Context Sensitive Help"</label>
			<label index="_csh.seeAlso">xGLOSSARY_t3:context_sensitive_help</label>
			<label index="css.alttitle">CSS</label>
			<label index="css.description">See "Cascading Style Sheets"</label>
			<label index="_css.seeAlso">xGLOSSARY_t3:cascading_style_sheets</label>
			<label index="cut.alttitle">cut</label>
			<label index="cut.description">The transfer of information (or objects) to the clipboard, from where it can be pasted into different locations. The original content is removed and remains in the clipboard only.</label>
			<label index="d-mail.alttitle">D-mail</label>
			<label index="d-mail.description">See "direct mail"</label>
			<label index="_d-mail.seeAlso">xGLOSSARY_t3:direct_mail</label>
			<label index="database.alttitle">database</label>
			<label index="database.description">A collection of organized information, stored in one location in a digital format.</label>
			<label index="_database.seeAlso">http://en.wikipedia.org/wiki/Database|Wikipedia about Database</label>
			<label index="database_dump.alttitle">database dump</label>
			<label index="database_dump.description">File storing the contents of a database at a certain time, it's a kind of snapshot of the database.</label>
			<label index="db_mount.alttitle">DB mount</label>
			<label index="db_mount.description">A DB mount (database mount) points to the page in the whole page tree which you want to become the root page in the page tree the user should see. It is used to give a specific user access to only a part of the page tree.</label>
			<label index="debug.alttitle">debug()</label>
			<label index="debug.description">A TYPO3 API function which is used by developers to show the state of variables, etc at a point in time. The output of this function is shown on the webpage.</label>
			<label index="declarational_configuration_language.alttitle">declarational configuration language</label>
			<label index="declarational_configuration_language.description">Typoscript is a declarational configuration language. It creates an information hierarchy used internally to instruct the template engine what to do and in which order - much like the registry does in Windows.</label>
			<label index="developer.alttitle">developer</label>
			<label index="developer.description">A developer is someone who writes code for a computer to understand. In the context of TYPO3 he would be either contributing code to the TYPO3 core or writing an extension to enhance the functionality of TYPO3 in some way.</label>
			<label index="direct_mail.alttitle">direct mail</label>
			<label index="direct_mail.description">Mail sent to large numbers of potential customers advertising a product, service or containing other information. In TYPO3 this is done by using a plugin that can create mails based on TYPO3 pages, determine which parts of the page should be sent to the user and then send personalised mails to each user of a specific recipient list. If the mail is containing links, clicks on these links can be tracked and used for statistics.</label>
			<label index="direct_mailer.alttitle">Direct mailer</label>
			<label index="direct_mailer.description">See "direct mail"</label>
			<label index="_direct_mailer.seeAlso">xGLOSSARY_t3:direct_mail</label>
			<label index="directory_structure.alttitle">directory structure</label>
			<label index="directory_structure.description">You are organising your files in folders or so called directories. The directory structure is the directory tree showing the positions of each directory.</label>
			<label index="document.alttitle">document</label>
			<label index="document.description">In TYPO3, a general expression for the form page used to edit any database element in the system.</label>
			<label index="doktype.alttitle">doktype</label>
			<label index="doktype.description">This is a field in the pages table.  In the page header form it is called "Type:" and is more commonly known as the page type. It controls what the page does and how it looks. It can take on values such as "Standard", "Not in Menu", "sysFolder", "Spacer", etc. Extensions can add additional doktypes.</label>
			<label index="domain_record.alttitle">domain record</label>
			<label index="domain_record.description">A type of record in the backend which includes a domain name (it represents a row in the table "sys_domain"). The record is contained by a page in the page tree, thereby indicating the entry point for HTTP requests to that domain. Used to support the multi-site feature of TYPO3. The TYPO3 equivalent to "virtual hosts" in Apache.</label>
			<label index="dynamic_content.alttitle">dynamic content</label>
			<label index="dynamic_content.description">Often used about content that is selected from a database and formatted by a template when the website user requests it. This is what many CMS do and that is opposite to having a website based on static HTML files. However dynamic in this sense does not mean that the content changes all the time. Dynamic content can also mean that the content is constantly changing/updated. For instance the current time, a chat forum or stock rates.</label>
			<label index="edit_icon.alttitle">edit icon</label>
			<label index="edit_icon.description">The edit icon (a small pencil) can be seen on various places in the backend. Clicking on it opens the form for modifying the associated content element. When using frontend editing the edit icon appears beside content elements the logged in backend user is permitted to work on. By clicking on the edit icon the form for modifying the content is shown (either in the page or in a popup window, depending on configuration).</label>
			<label index="_edit_icon.seeAlso">http://typo3.org/documentation/tips-tricks/frontend-editing/|Tips and tricks about frontend editing</label>
			<label index="edit_panel.alttitle">edit panel</label>
			<label index="edit_panel.description">A text field where you can write and change a text and might use nearly all of your keyboard functions.</label>
			<label index="edit_panels.alttitle">Edit Panels</label>
			<label index="edit_panels.description">See "edit panel"</label>
			<label index="_edit_panels.seeAlso">xGLOSSARY_t3:edit_panel</label>
			<label index="editicon.alttitle">editicon</label>
			<label index="editicon.description">See "edit icon"</label>
			<label index="_editicon.seeAlso">xGLOSSARY_t3:edit_icon</label>
			<label index="element_browser.alttitle">element browser</label>
			<label index="element_browser.description">The element browser allows you to browse through pages, the file system or elements inserted on pages. It's being used to select elements, place links or integrate files.</label>
			<label index="_element_browser.seeAlso">http://typo3.org/documentation/tips-tricks/the-element-browser/|The Element Browser</label>
			<label index="em.alttitle">EM</label>
			<label index="em.description">See "Extension manager"</label>
			<label index="_em.seeAlso">xGLOSSARY_t3:extension_manager</label>
			<label index="enablefields.alttitle">enableFields</label>
			<label index="enablefields.description">enableFields are fields in a table which holds the value for either hidden/visible, start time, end time or user group access. The fields are pointed to by an entry in the "ctrl" section for tables in $TCA.</label>
			<label index="_enablefields.seeAlso">xGLOSSARY_t3:visibility_settings, http://typo3.org/documentation/document-library/doc_tut_templselect2/The_theory_of_quot/|Modern Template Building, Part 2+3 - The Theory of "enableFields"</label>
			<label index="enter_typoscript_code.alttitle">enter Typoscript code</label>
			<label index="enter_typoscript_code.description">See "setup"</label>
			<label index="_enter_typoscript_code.seeAlso">xGLOSSARY_t3:setup</label>
			<label index="example_templates.alttitle">example templates</label>
			<label index="example_templates.description">See "standard template"</label>
			<label index="_example_templates.seeAlso">xGLOSSARY_t3:standard_template</label>
			<label index="ext_localconfphp.alttitle">ext_localconf.php</label>
			<label index="ext_localconfphp.description">This file, if found, contains additional configuration of $TYPO3_CONF_VARS and other PHP class files for the relevant extension.</label>
			<label index="_ext_localconfphp.seeAlso">xGLOSSARY_t3:localconf, http://typo3.org/documentation/document-library/doc_core_api/|TYPO3 Core API's document</label>
			<label index="ext_tablesphp.alttitle">ext_tables.php</label>
			<label index="ext_tablesphp.description">If this file exists in an extension's root directory it adds configuration information about the tables, modules, backend styles, etc. of the extension.  It may be used to modify the table configuration array (TCA) values of any table.</label>
			<label index="_ext_tablesphp.seeAlso">http://typo3.org/documentation/document-library/doc_core_api/|TYPO3 Core API's document</label>
			<label index="extension.alttitle">extension</label>
			<label index="extension.description">A TYPO3 extension is a piece of code adding a certain functionality to TYPO3 without changing the original TYPO3 code ("core"). Extensions can be downloaded from the TER or loaded by hand by copying directly into typo3conf/ext/. They can be either plug-ins or modules. Plug-ins are such extensions that produce frontend material visible on the TYPO3 generated website (for example the News extension), modules are extensions that provide backend functionality (for example the Directmail or PhpMyAdmin extensions).
There are also three types of extensions. Global extensions are standard with every TYPO3 installation and reside in the typo3/ext/ directory. Local extensions are loaded in the typo3conf/ext/ directory. If a local extension and a global extension have the same name the local overrides the global one.  If you modify a global extension it's best to first copy it into the local extensions directory. There are also some system extensions located in typo3/sysext/.</label>
			<label index="_extension.seeAlso">xGLOSSARY_t3:plugin, http://typo3.org/documentation/document-library/doc_core_inside/How_permissions_work/|
Inside TYPO3 - Extensions, http://typo3.org/extensions/|Search the Extension Repository, http://typo3.org/documentation/document-library/player_profile_basic/|Creating a basic extension</label>
			<label index="extension_key.alttitle">extension key</label>
			<label index="extension_key.description">Each extension can be identified by a unique extension key.</label>
			<label index="extension_manager.alttitle">Extension manager</label>
			<label index="extension_manager.description">The Extension manager (EM) is a module in the TYPO3 backend, used for management of extensions. Use it to load extensions from the TYPO3 extension repository (TER), install and uninstall loaded extensions, edit extensions, and delete them.</label>
			<label index="extension_repository.alttitle">extension repository</label>
			<label index="extension_repository.description">See "TYPO3 extension repository"</label>
			<label index="_extension_repository.seeAlso">xGLOSSARY_t3:typo3_extension_repository</label>
			<label index="faq.alttitle">FAQ</label>
			<label index="faq.description">Frequently Asked Questions, list of most common questions and the accompanying answers. You should look at these questions/answers before you ask one yourself.</label>
			<label index="fe.alttitle">FE</label>
			<label index="fe.description">See "frontend"</label>
			<label index="_fe.seeAlso">xGLOSSARY_t3:frontend</label>
			<label index="field.alttitle">field</label>
			<label index="field.description">a) An input control (like a text box or drop down box) in an HTML form.
b) A column in a database table. The nomenclature for relational databases has changed in recent years with the advent of SQL.  What used to be called database "files", "records" and "fields" are now called "tables", "rows" and "columns". The TYPO3 documentation uses the terms "tables", "records" and "fields".
c) In Typoscript field refers a stdWrap function (see stdWrap) which returns one of the values in the associated array $cObj->data (which usually contains the record in the page table of the page currently being rendered).</label>
			<label index="file_mount.alttitle">file mount</label>
			<label index="file_mount.description">See "filemount"</label>
			<label index="_file_mount.seeAlso">xGLOSSARY_t3:filemount</label>
			<label index="filemount.alttitle">filemount</label>
			<label index="filemount.description">Similar to DB mounts, file mounts point to the directory (within the fileadmin directory) which the user will see as their root directory. They cannot then access any directories above this root. Multiple file mounts can be assigned to a user.</label>
			<label index="flexform.alttitle">flexform</label>
			<label index="flexform.description"></label>
			<label index="fork.alttitle">fork</label>
			<label index="fork.description">See "branch"</label>
			<label index="_fork.seeAlso">xGLOSSARY_t3:branch</label>
			<label index="freetype.alttitle">FreeType</label>
			<label index="freetype.description">FreeType is a software font engine which, in TYPO3, is used in conjunction with the GDLib library to render text on images and creating items such as icons and menu items.</label>
			<label index="_freetype.seeAlso">xGLOSSARY_t3:gdlib, http://www.freetype.org|FreeType website</label>
			<label index="frontend.alttitle">frontend</label>
			<label index="frontend.description">The frontend is the website that TYPO3 generates for you. This is what your visitors will see.</label>
			<label index="frontend_editing.alttitle">frontend editing</label>
			<label index="frontend_editing.description">Frontend editing allows you to edit your website content from the frontend. You have to be logged in as a backend user for edit icons to appear by each piece of content, clicking these will open a form to edit that information.</label>
			<label index="frontend_engine.alttitle">frontend engine</label>
			<label index="frontend_engine.description">See "Typoscript frontend"</label>
			<label index="_frontend_engine.seeAlso">xGLOSSARY_t3:typoscript_frontend</label>
			<label index="frontend_user.alttitle">frontend user</label>
			<label index="frontend_user.description">A frontend user can log into the website. They cannot change content (this is for backend users only). Frontend users exist because we can restrict access to information on the website to specific frontend users.</label>
			<label index="ftp_space.alttitle">FTP space</label>
			<label index="ftp_space.description">See "ftpspace"</label>
			<label index="_ftp_space.seeAlso">xGLOSSARY_t3:ftpspace</label>
			<label index="ftpspace.alttitle">ftpspace</label>
			<label index="ftpspace.description">Webspace on a server accessible via File Transfer Protocol (ftp).</label>
			<label index="function.alttitle">function</label>
			<label index="function.description">A named piece of code which returns a value. It is executed from other code giving its name and function parameters.</label>
			<label index="function_menu.alttitle">function menu</label>
			<label index="function_menu.description">The selector-box found in the upper right corner of many backend modules. The selector box represents a menu by which the user chooses the specific function of the module in case a module represents a framework for a number of related functionalities.</label>
			<label index="gdlib.alttitle">GDlib</label>
			<label index="gdlib.description">GDLib is used for drawing boxes and rendering text on images with TrueType fonts. It is also used for creating menu items in GMENU and GMENU_LAYERS. You will need to have GDLib compiled into the version of PHP you are using. If you want TrueType font support, you must also have FreeType compiled in.</label>
			<label index="general_record_storage_page.alttitle">General Record Storage page</label>
			<label index="general_record_storage_page.description">For a branch of the page tree this is a page appointed to contain database elements of a general purpose for the site (opposite to eg. content elements specific for a single page). For instance this could be frontend users or an archive of news elements. The General Record Storage page is the suggested method of defining such an archive page but it depends on support from the extensions used on the site. A General Record Storage page is usually a sysFolder found on the root level of a website.</label>
			<label index="generate.alttitle">generate</label>
			<label index="generate.description">In a CMS, to generate a page, image, menu etc. is to create it from some data source. Another word used for the same is "render".</label>
			<label index="get_method.alttitle">GET method</label>
			<label index="get_method.description">The GET method is the regular way to request a webpage from a webserver. There is a possiblity to add some information to a GET request, which the page you just look at is also using. Within the browser you see this information in the adress field. If you got a "?" or a "&" character there, followed by a name, a "=" character and the value to submit, this value will be added to the GET request. The most common GET request within TYPO3 looks like "index.php?id=10". This request calls the "index.php" script and passes the value "10" named "id" to the script.</label>
			<label index="gifbuilder.alttitle">GIFBUILDER</label>
			<label index="gifbuilder.description">An ImageMagick-based Typoscript object, that allows you to comfortably generate and compose images and text, using the simple syntax of Typoscript while having access to the possibilities ImageMagick offers.</label>
			<label index="gifbuilderobj.alttitle">GIFBUILDERobj</label>
			<label index="gifbuilderobj.description">The type of graphical element used to compose a GIF, JPG or PNG file in TYPO3, using the GIFBUILDER method. It could be of the type TEXT which can print a text string onto the image using a truetype font. Or it could be the IMAGE type which will overlay an image at a certain coordinate. There are also effects, scaling, cropping and other useful things you might want to do with your images.
Notice that the word GIF used in GIFBUILDER is a heritage from the past where only gif files could be produced with TYPO3 (today PNG and JPG are also an option).</label>
			<label index="global.alttitle">global</label>
			<label index="global.description">Mostly in connection with extensions, those can either be installed global (typo3/ext) or local (typo3conf/ext).</label>
			<label index="global_extension.alttitle">global extension</label>
			<label index="global_extension.description">See "extension"</label>
			<label index="_global_extension.seeAlso">xGLOSSARY_t3:extension</label>
			<label index="gnu.alttitle">GNU</label>
			<label index="gnu.description">GNU is a recursive acronym for "GNU's Not Unix". It is pronounced "guh-noo".</label>
			<label index="_gnu.seeAlso">http://www.gnu.org|GNU Project Homepage</label>
			<label index="gnu_gpl.alttitle">GNU GPL</label>
			<label index="gnu_gpl.description">See "license"</label>
			<label index="_gnu_gpl.seeAlso">xGLOSSARY_t3:license</label>
			<label index="gpl.alttitle">GPL</label>
			<label index="gpl.description">GPL stands for General Public Licence. It is the software licence that TYPO3 uses. You can find out more from the Free Software Foundation website</label>
			<label index="_gpl.seeAlso">http://www.fsf.org|Free Software Foundation</label>
			<label index="hard_code.alttitle">hard code</label>
			<label index="hard_code.description">In programming, that a certain value is inserted directly in the programming code instead of being selected from some external data source.</label>
			<label index="hardcode.alttitle">hardcode</label>
			<label index="hardcode.description">See "hard code"</label>
			<label index="_hardcode.seeAlso">xGLOSSARY_t3:hard_code</label>
			<label index="hardcoding.alttitle">hardcoding</label>
			<label index="hardcoding.description">See "hard code"</label>
			<label index="_hardcoding.seeAlso">xGLOSSARY_t3:hard_code</label>
			<label index="hide.alttitle">hide</label>
			<label index="hide.description">In TYPO3, pages, content elements or records can be marked hidden to the frontend output.</label>
			<label index="hide_in_menu.alttitle">hide in menu</label>
			<label index="hide_in_menu.description">See "hide"</label>
			<label index="_hide_in_menu.seeAlso">xGLOSSARY_t3:hide</label>
			<label index="hiearchy.alttitle">hiearchy</label>
			<label index="hiearchy.description">See "information hierarchy"</label>
			<label index="_hiearchy.seeAlso">xGLOSSARY_t3:information_hierarchy</label>
			<label index="hierarchy.alttitle">hierarchy</label>
			<label index="hierarchy.description">The hierarchy is a system to organize items into collections and give them a hierarchy number. The hierarchy on computer systems is the same like it is with people in a company. One person on a higher hiearchy position has a couple of people under him with a lower hiearchy number.</label>
			<label index="hmenu.alttitle">HMENU</label>
			<label index="hmenu.description">A Typoscript cObject; Renders a dynamic menu for the website based on the page tree hierarchy.</label>
			<label index="_hmenu.seeAlso">http://typo3.org/doc.0.html%26tx_extrepmgm_pi1%5BextUid%5D%3D270%26tx_extrepmgm_pi1%5BtocEl%5D%3D358%26cHash%3D5400c1c06a__Creating+a+menu+for+a+template+%28MTB%2F1%29+|HMENU in Typoscript reference</label>
			<label index="hook.alttitle">Hook</label>
			<label index="hook.description">By means of a hook a developer can insert his own program code into an existing program. Hooks are provided where adaptions are expected.</label>
			<label index="hoster.alttitle">hoster</label>
			<label index="hoster.description">See "hosting"</label>
			<label index="_hoster.seeAlso">xGLOSSARY_t3:hosting</label>
			<label index="hosting.alttitle">hosting</label>
			<label index="hosting.description">The service which includes the running of a web server and server applications and connecting it to the internet.</label>
			<label index="html.alttitle">HTML</label>
			<label index="html.description">Hypertext Markup Language, a subset of SGML, is a kind of simple programming language for creating web pages.</label>
			<label index="html_tag.alttitle">HTML tag</label>
			<label index="html_tag.description">See "tag"</label>
			<label index="_html_tag.seeAlso">xGLOSSARY_t3:tag</label>
			<label index="html_template.alttitle">HTML template</label>
			<label index="html_template.description">In TYPO3 an HTML template is a text file containing HTML and TYPO3 markers. Portions of the HTML template are extracted, text is substituted for the markers, and the result is output to web pages. HTML templates are a part of TYPO3's internal templating system.</label>
			<label index="_html_template.seeAlso">xGLOSSARY_t3:template</label>
			<label index="id.alttitle">id</label>
			<label index="id.description">Id is the abbreviation of "identifier". It's a single string (often a unique integer number) which serves as a name for something.
In TYPO3 each page has got a unique number assigned to it (uid = unique id, not to be mistaken for pid = parent id) which is it's identifier. Often you will see URLs like http://www.anydomain.com/index.php?id=123
In this case "123" would be the identifier of a certain page. Identifiers are used in TYPO3 to distinguish between different objects (pages, content elements, etc.) which may have the same name - like two pages named 'My diary'.</label>
			<label index="image_block.alttitle">image block</label>
			<label index="image_block.description">Set of images created with the content element image or text/image (IMGTEXT).</label>
			<label index="image_processing.alttitle">image processing</label>
			<label index="image_processing.description">See "ImageMagick"</label>
			<label index="_image_processing.seeAlso">xGLOSSARY_t3:imagemagick</label>
			<label index="imagemagick.alttitle">ImageMagick</label>
			<label index="imagemagick.description">ImageMagick is a collection of tools and libraries to read, write and manipulate images in over 90 major formats including TIFF, JPEG, PNG, PDF and GIF. With ImageMagick you can create images dynamically and also resize, rotate, sharpen, color reduce, or add special effects to an image or image sequence and save your completed work in the same or differing image format. A 2D renderer is also included, which provides a subset of SVG capabilities.</label>
			<label index="imgresource.alttitle">imgResource</label>
			<label index="imgresource.description">Typoscript content object containing a reference to an image file, i.e. the path and filename.</label>
			<label index="_imgresource.seeAlso">http://typo3.org/documentation/document-library/doc_core_tsref/IMG_RESOURCE-1/|Typoscript Reference (TSref)</label>
			<label index="import.alttitle">import</label>
			<label index="import.description">The import is a mechanism used to input many data into the TYPO3 using a batch process. The import feature allow you to exchange any kind of TYPO3 data, for example a page tree, with an other TYPO3 installation or within the same installation. Import is also used with stdWrap to get i.e. an image from the filesystem instead of creating it dynamically.</label>
			<label index="include_access_lists.alttitle">include access lists</label>
			<label index="include_access_lists.description">See "access list"</label>
			<label index="_include_access_lists.seeAlso">xGLOSSARY_t3:access_list</label>
			<label index="information_hierarchy.alttitle">information hierarchy</label>
			<label index="information_hierarchy.description">The organisation and structure of the computer data.</label>
			<label index="insert_plugin.alttitle">insert plugin</label>
			<label index="insert_plugin.description">Most plugins can be inserted in two ways, either via site-Typoscript or by inserting it as a content element into a concrete page.</label>
			<label index="install_tool.alttitle">Install tool</label>
			<label index="install_tool.description">A graphical user interface to configure TYPO3 system settings. These settings are being stored in the file "typo3conf/localconf.php".</label>
			<label index="_install_tool.seeAlso">xGLOSSARY_t3:localconf</label>
			<label index="installation.alttitle">installation</label>
			<label index="installation.description">The process to copy the files of TYPO3 to your webserver and to make the basic configuration steps. Only after a successful installation you will be able to start with TYPO3.</label>
			<label index="installed_extensions.alttitle">installed extensions</label>
			<label index="installed_extensions.description">Extensions that are ready to be used in your TYPO3 installation. They are located in the local (typo3conf/ext) or in the global (typo3/ext) extension directory. There are also a system (typo3/sysext) extensions directory.</label>
			<label index="integration.alttitle">integration</label>
			<label index="integration.description">Integration means you integrate foreign PHP-applications into TYPO3. For example a discussion forum as a frontend plugin or the database frontend phpMyAdmin as a backend module.</label>
			<label index="jumpurl.alttitle">jumpUrl</label>
			<label index="jumpurl.description">A method that the typolink function of the frontend can use when linking to external URLs or local files (for secure downloads). Basically links using the jumpUrl feature will link to the current page with the GET variable "&jumpUrl=[URL or file reference]". When the link is clicked and reaches the server TYPO3 will redirect to the URL or document while still registering in the statistics that the link was clicked.</label>
			<label index="_jumpurl.seeAlso">http://typo3.org/documentation/document-library/doc_core_tsref/filelink/|Typoscript reference (TSref), .</label>
			<label index="kickstarter.alttitle">kickstarter</label>
			<label index="kickstarter.description">See "kickstarter wizard"</label>
			<label index="_kickstarter.seeAlso">xGLOSSARY_t3:kickstarter_wizard</label>
			<label index="kickstarter_wizard.alttitle">kickstarter wizard</label>
			<label index="kickstarter_wizard.description">Wizard interface for "kickstarting" new extension development. A handy tool for creating a framework for new extensions.</label>
			<label index="lamp.alttitle">LAMP</label>
			<label index="lamp.description">LAMP is an acronym for a set of free software programs commonly used together to run dynamic Web sites: Linux, Apache, MySQL and PHP.</label>
			<label index="_lamp.seeAlso">xGLOSSARY_t3:wamp</label>
			<label index="language_splitted.alttitle">language splitted</label>
			<label index="language_splitted.description">See "languagesplit"</label>
			<label index="_language_splitted.seeAlso">xGLOSSARY_t3:languagesplit</label>
			<label index="languagesplit.alttitle">languagesplit</label>
			<label index="languagesplit.description">Obsolete way of localizing backend labels using a token to split a string into localizations.
Basically a string being "languagesplitted" could look like "Cat|Kat|Katze|..." where each part corresponds to the position of the language key found in the constant "TYPO3_languages" (in this case "default|dk|de|...").
This concept is obsolete and instead the locallang concept should be used.</label>
			<label index="_languagesplit.seeAlso">http://typo3.org/documentation/document-library/doc_core_inside/quot_language_split/|Inside TYPO3</label>
			<label index="languagesplitted.alttitle">languagesplitted</label>
			<label index="languagesplitted.description">See "languagesplit"</label>
			<label index="_languagesplitted.seeAlso">xGLOSSARY_t3:languagesplit</label>
			<label index="level.alttitle">level</label>
			<label index="level.description">Mostly used in context of the pagetree. There are two ways to talk of levels:
a) level means the "depth" in the pagetree, the shortest path from the rootpage to the page talked about. If page talked about is the n-th page in the path, so it is on level n
b) level is also used when applying functions onto a page recursivly (and so also onto its subpages), in this context the given level means that the last page affected by the function will have n-1 children between itself and the page the function is applied to.</label>
			<label index="levels.alttitle">levels</label>
			<label index="levels.description">See "level"</label>
			<label index="_levels.seeAlso">xGLOSSARY_t3:level</label>
			<label index="license.alttitle">license</label>
			<label index="license.description">The legal rights under which the software has been published. The TYPO3 core and most of the extensions are is published under the GPL license. Commercial software usually have licences based on users, processors, etc.</label>
			<label index="_license.seeAlso">http://www.gnu.org/licenses/gpl.html|The GNU GPL license</label>
			<label index="link.alttitle">link</label>
			<label index="link.description">See "shortcut"</label>
			<label index="_link.seeAlso">xGLOSSARY_t3:shortcut</label>
			<label index="list_module.alttitle">List module</label>
			<label index="list_module.description">The List module is a backend-module used to manage both pages, page content elements, template records, domain records, users and groups, guestbook items and whatever elements TYPO3 is capable of managing
In other weords it allows graphical access to all of TYPO3's different types of database records. The List module permits such operations as the editing, copying, pasting, and moving of individual database records, and also provides an overview of all database content associated with a particular page.</label>
			<label index="_list_module.seeAlso">http://typo3.org/documentation/document-library/doc_tut_quickstart/The_List_module_and/|The List module and Clipboard in Getting Started</label>
			<label index="loaded_extensions.alttitle">loaded extensions</label>
			<label index="loaded_extensions.description">Extensions which are installed and currently running in the current TYPO3-instance.</label>
			<label index="local_extension.alttitle">local extension</label>
			<label index="local_extension.description">See "extension"</label>
			<label index="_local_extension.seeAlso">xGLOSSARY_t3:extension</label>
			<label index="local_lang.alttitle">local_lang</label>
			<label index="local_lang.description">See "locallang"</label>
			<label index="_local_lang.seeAlso">xGLOSSARY_t3:locallang</label>
			<label index="localconf.alttitle">localconf</label>
			<label index="localconf.description">Refers to the file "typo3conf/localconf.php" where most of the global configuration values are set for a specific TYPO3 website. Inside that file the database connection information is found, configuration of installed extensions, values in the $TYPO3_CONF_VARS array etc.</label>
			<label index="_localconf.seeAlso">xGLOSSARY_t3:install_tool, xGLOSSARY_t3:ext_tablesphp, xGLOSSARY_t3:ext_localconfphp, http://typo3.org/documentation/document-library/doc_core_inside/localconf_php_and_T/|Inside TYPO3, http://typo3.org/documentation/document-library/doc_core_api/ext_tables_php_and_e/|TYPO3 Core API</label>
			<label index="locallang.alttitle">locallang</label>
			<label index="locallang.description">Refers to the primary localization concept in TYPO3 where a PHP file or XML file (preferred) contains localizations of backend or frontend text labels. A locallang file is normally a collection of labels relevant in the same context, for example a backend module or a database table.
The localizations are added to the locallang files through web interfaces. The PHP version uses the interface on typo3.org where uploaded extensions are automatically subjected to translation. The XML
version uses a TYPO3 extension that allows localization to happen on all installed extensions.
A typical language file can look like this:
$LOCAL_LANG = Array (
	"default" => Array (
		"username" => "User Name:",
		"password" => "User Name:",
	),
	"nl" => Array (
		"username" => "Gebruikers Naam:",
		"password" => "Wachtwoord:",
	),
)</label>
			<label index="_locallang.seeAlso">http://typo3.org/documentation/document-library/doc_core_inside/|Inside TYPO3</label>
			<label index="mailing_list.alttitle">mailing list</label>
			<label index="mailing_list.description">The various mailing lists represent the "nerve system" of the TYPO3 community. Discussion, information and helping others are the main ingredients of these lists. The mailing list can be accessed via mail (the traditional way) or as newsgroups, readable in common newsreaders. (Some are available as mailing lists only for security reasons).</label>
			<label index="_mailing_list.seeAlso">http://typo3.org/documentation/mailing-lists/|typo3.org - Mailinglists, http://lists.netfielders.de/cgi-bin/mailman/listinfo|netfielders.de - Listinfo</label>
			<label index="main_module.alttitle">main module</label>
			<label index="main_module.description">The "first level" in the menu of the TYPO3 backend. Examples are the Web, File, User, Doc, Tools and Help main modules that most TYPO3 users know. However, they are usually only representing submodules (eg. "Web > List" or "Tools > Ext. Manager") but can also be an active module in themselves (like Doc is).</label>
			<label index="marker.alttitle">marker</label>
			<label index="marker.description">See "subpart marker"</label>
			<label index="_marker.seeAlso">xGLOSSARY_t3:subpart_marker</label>
			<label index="markers.alttitle">markers</label>
			<label index="markers.description">A marker defines a certain place in an HTML template where dynamic content can be inserted. In TYPO3, all markers look like ###SOMEWORD### . Using the TYPO3 templating utilities you can: substitute text for a marker, extract the text between two markers,  substitute the text between two markers, or wrap the text between two markers.</label>
			<label index="_markers.seeAlso">xGLOSSARY_t3:subpart_marker</label>
			<label index="mentor.alttitle">mentor</label>
			<label index="mentor.description">The mentor is a teacher who gives you the information and points you out the right way.</label>
			<label index="mentors.alttitle">mentors</label>
			<label index="mentors.description">See "mentor"</label>
			<label index="_mentors.seeAlso">xGLOSSARY_t3:mentor</label>
			<label index="menu.alttitle">menu</label>
			<label index="menu.description">On a website, a set of links systematically organized for navigation and typically displayed on all pages on the site. Often a menu reflects the idea of sections and/or a hierarchy of pages on a website.</label>
			<label index="_menu.seeAlso">http://typo3.org/doc.0.html%26tx_extrepmgm_pi1%5BextUid%5D%3D491%26tx_extrepmgm_pi1%5BtocEl%5D%3D1335%26cHash%3Dbf3aaf4a9a|Explanation of page tree and menus</label>
			<label index="menu_item.alttitle">menu item</label>
			<label index="menu_item.description">A single element in a menu.</label>
			<label index="menu_items.alttitle">menu items</label>
			<label index="menu_items.description">See "menu item"</label>
			<label index="_menu_items.seeAlso">xGLOSSARY_t3:menu_item</label>
			<label index="menu_object.alttitle">MENU object</label>
			<label index="menu_object.description">In Typoscript templates, an object which defines how a menu level of the parent HMENU cObject is rendered.</label>
			<label index="_menu_object.seeAlso">http://typo3.org/doc.0.html%26tx_extrepmgm_pi1%5BextUid%5D%3D270%26tx_extrepmgm_pi1%5BtocEl%5D%3D381%26cHash%3D57589a8079__Creating+menus+|Menu objects in Typoscript reference</label>
			<label index="menu_objects.alttitle">MENU objects</label>
			<label index="menu_objects.description">See "MENU object"</label>
			<label index="_menu_objects.seeAlso">xGLOSSARY_t3:menu_object</label>
			<label index="module.alttitle">module</label>
			<label index="module.description">Also known as backend modules, they are extensions (plugins) for the backend.  They provide some specific functionality to the TYPO3 backend. Examples of common modules are Page, List, Info, Access, Filelist and Images.</label>
			<label index="_module.seeAlso">http://typo3.org/documentation/document-library/doc_core_inside/Backend_interface/|Inside TYPO3 Document</label>
			<label index="multi-site.alttitle">multi-site</label>
			<label index="multi-site.description">See "multi site"</label>
			<label index="_multi-site.seeAlso">xGLOSSARY_t3:multi_site</label>
			<label index="multi_site.alttitle">multi site</label>
			<label index="multi_site.description">Having multiple web sites in the same database and TYPO3 installation. The sites hosted that way can be completely different and not related. The admin has access to all sites but group of users can be setup to belong to each site separately.</label>
			<label index="_multi_site.seeAlso">http://typo3.org/documentation/document-library/doc_tut_quickstart/Controlling_multiple/|Getting Started: 1.9.7 Controlling multiple domains</label>
			<label index="multisite.alttitle">multisite</label>
			<label index="multisite.description">See "multi site"</label>
			<label index="_multisite.seeAlso">xGLOSSARY_t3:multi_site</label>
			<label index="mysql.alttitle">MySQL</label>
			<label index="mysql.description">A very popular SQL database system, which is used in many open source projects for data storage, for example in TYPO3. It has a dual licensing scheme, offering licensing under GPL or under a commercial license.</label>
			<label index="_mysql.seeAlso">http://www.mysql.com|MySQL website</label>
			<label index="name_space.alttitle">name space</label>
			<label index="name_space.description">See "namespace"</label>
			<label index="_name_space.seeAlso">xGLOSSARY_t3:namespace</label>
			<label index="namespace.alttitle">namespace</label>
			<label index="namespace.description">Namespaces allow developers to uniquely qualify element names and relationships to make these names recognizable. This can avoid name collisions on elements that have the same name, but are defined in different vocabularies.</label>
			<label index="_namespace.seeAlso">http://en.wikipedia.org/wiki/Namespace|Wikipedia about namespace</label>
			<label index="navigation.alttitle">navigation</label>
			<label index="navigation.description">This is the name for the user actions to click through the entry tree of a menu or the links a HTML website. It is the same as surfing on the internet.</label>
			<label index="newbee.alttitle">newbee</label>
			<label index="newbee.description">See "newbie"</label>
			<label index="_newbee.seeAlso">xGLOSSARY_t3:newbie</label>
			<label index="newbie.alttitle">newbie</label>
			<label index="newbie.description">The informal term newbie means a newcomer to a particular corner of cyberspace, such as a wiki, newsgroup, the World Wide Web itself or to an operating system. The word itself is likely a corruption of new boy, the equivalent figure in real life - usually observed as a new arrival in a school and who is, therefore, vulnerable to bullying of various kinds</label>
			<label index="nicetext.alttitle">niceText</label>
			<label index="nicetext.description">A Typoscript option which is used to make text generated by FreeType/GDLib look nicer. It takes more CPU to do this but it usually gives a better result.</label>
			<label index="_nicetext.seeAlso">http://typo3.org/documentation/document-library/doc_core_tsbyex/niceText/|Typoscript By Example Document</label>
			<label index="no_cache.alttitle">no_cache</label>
			<label index="no_cache.description">Option that tells TYPO3 not to cache this content element.</label>
			<label index="_no_cache.seeAlso">xGLOSSARY_t3:cache</label>
			<label index="normal_state.alttitle">normal state</label>
			<label index="normal_state.description">For website navigation (menu items), normal state is the default state of a menu item. Other possible states are "active", "current", "roll over", "ifsub", "user" etc or combinations of them. The state of a menu item typically depends on the website users position on the website or whether they move their mouse over the menu item or not. When you define how a menu item looks, you always define the normal state of the item. Then optionally you can also define how the menu item should look differently if some of the other possible states should occur.</label>
			<label index="_normal_state.seeAlso">http://typo3.org/doc.0.html%26tx_extrepmgm_pi1%5BextUid%5D%3D270%26tx_extrepmgm_pi1%5BtocEl%5D%3D382%26cHash%3Db13af36f98__|Item states described in Typoscript reference</label>
			<label index="numeric_pads.alttitle">numeric pads</label>
			<label index="numeric_pads.description">These are the three clipboards that are available in the TYPO3 List module if you have "Show clipboard" ticked. They help you to manage multiple elements effectively in the backend.</label>
			<label index="_numeric_pads.seeAlso">http://typo3.org/documentation/document-library/doc_tut_quickstart/The_numeric_clipboar/|Getting Started Document</label>
			<label index="numerical_array.alttitle">numerical array</label>
			<label index="numerical_array.description">An array is a kind of shelf, in every tray is a peace of information, and every tray has got an adress. If this adress is numerical it's a numerical array.</label>
			<label index="object.alttitle">object</label>
			<label index="object.description">In the world of software development the word object refers to a useful well defined "thing", which doesn't really tell you very much since almost everything ends up being an object (or a class which is very similar).  In TYPO3 there are three different kinds of objects. The first kind are the things you manipulate when you're editing a site from the backend. Backend objects include pages, content elements and records, and the many varieties of each of these types of objects. The second kind of objects in TYPO3 are Typoscript objects. They are defined in Typoscript templates and include things like plugins, frames, typolinks, text, images, etc.  The third kind of objects in TYPO3 are the PHP objects in the code, many of which correspond to Typoscript objects because they are responsible for rendering the Typoscript objects on web pages.</label>
			<label index="object_browser.alttitle">object browser</label>
			<label index="object_browser.description">The Typoscript code is inherited by the underlying templates for a page and can be changed in the setup field for a template. To get an understanding which code will be executed in the end effect for a page you can use the Typoscript object browser from the Template module. In the backend, select "Template" in the left hand column, select a page which contains a template, then in the upper right drop down box select "Typoscript Object Browser".</label>
			<label index="object_path.alttitle">object path</label>
			<label index="object_path.description">The term for a full string identifying a Typoscript object, eg. "lib.myMenu", "page.10.5.file", "config.simulateStaticDocuments", "RTE.default" etc.</label>
			<label index="_object_path.seeAlso">http://typo3.org/documentation/document-library/doc_core_ts/|Typoscript Syntax and In-depth study</label>
			<label index="optionsplit.alttitle">optionSplit</label>
			<label index="optionsplit.description">Complex syntax used in the Typoscript configuration that build HMENU cObjects and while using the stdWrap.split function. All values subjected to "optionSplit" are exploded based on
the tokens "||" and "|*|", combined with the number of items the menu or split is comprised of. The goal of optionSplit is to provide a very flexible way of setting alternative values for eg. first and last
elements in a menu etc. The full meaning is explained in Typoscript reference by a number of examples to go by.</label>
			<label index="_optionsplit.seeAlso">xGLOSSARY_t3:content_object_array, http://typo3.org/documentation/document-library/doc_core_tsref/optionSplit-1/|Typoscript reference (TSref)</label>
			<label index="out-of-the-box.alttitle">out-of-the-box</label>
			<label index="out-of-the-box.description">See "out of the box"</label>
			<label index="_out-of-the-box.seeAlso">xGLOSSARY_t3:out_of_the_box</label>
			<label index="out_of_the_box.alttitle">out of the box</label>
			<label index="out_of_the_box.description">About functionality, that something is delivered by default and ready to use right away without a lot of hassle or procedures to go through.</label>
			<label index="package.alttitle">package</label>
			<label index="package.description">A package is a collection of files which is geared to help you get TYPO3 up and running for a particular purpose as quickly as possible.  They can be found in the Download section on typo3.org</label>
			<label index="_package.seeAlso">http://typo3.org/download/packages/|Download Packages</label>
			<label index="page_content.alttitle">page content</label>
			<label index="page_content.description">A collection of content elements which will be shown when the user browses to a page.</label>
			<label index="page_header.alttitle">page header</label>
			<label index="page_header.description">The form which allows you to edit the properties of a page.</label>
			<label index="page_icon.alttitle">page icon</label>
			<label index="page_icon.description">Within the TYPO3 backend you've got a page tree, which shows you the whole structure of your website. At the left side of every pagetitle is an icon, that's the page icon. If you click on it, a contextmenu appears.</label>
			<label index="page_module.alttitle">page module</label>
			<label index="page_module.description">Refers to the "Web > Page" module in the backend of TYPO3 or a simular module used as the primary environment for editing pages.
(Other examples include the page module provided by the extension "templavoila" which introduces an alternative concept for page composition).</label>
			<label index="page_properties.alttitle">page properties</label>
			<label index="page_properties.description">See "page header"</label>
			<label index="_page_properties.seeAlso">xGLOSSARY_t3:page_header</label>
			<label index="page_title.alttitle">page title</label>
			<label index="page_title.description">A field in the page header which contains a name for the page. It is used in TYPO3 generated menus and also in the web page's HTML  tag.</label>
			<label index="page_tree.alttitle">page tree</label>
			<label index="page_tree.description">The hierarchical structure of pages found in the TYPO3 backend. Used to organize database content in TYPO3 and works conceptually like a file system directory structure. In most cases the page tree also represents the navigation hierarchy of the website managed by TYPO3.</label>
			<label index="_page_tree.seeAlso">http://typo3.org/doc.0.html%26tx_extrepmgm_pi1%5BextUid%5D%3D491%26tx_extrepmgm_pi1%5BtocEl%5D%3D1335%26cHash%3Dbf3aaf4a9a|Explanation of the page Tree in "Getting Started"</label>
			<label index="page_tsconfig.alttitle">page TSconfig</label>
			<label index="page_tsconfig.description">Typoscript that configures the behavior of pages in the backend. You can find it, if you edit the page header.</label>
			<label index="pagetree.alttitle">pagetree</label>
			<label index="pagetree.description">See "page tree"</label>
			<label index="_pagetree.seeAlso">xGLOSSARY_t3:page_tree</label>
			<label index="parameter.alttitle">parameter</label>
			<label index="parameter.description">A parameter is a value which is passed to a PHP script, any kind of function or executable.</label>
			<label index="parent.alttitle">parent</label>
			<label index="parent.description">A parent in a hiearchy structure is the object which is one position higher than the other object.</label>
			<label index="_parent.seeAlso">xGLOSSARY_t3:hierarchy</label>
			<label index="parent_id.alttitle">parent id</label>
			<label index="parent_id.description">See "pid"</label>
			<label index="_parent_id.seeAlso">xGLOSSARY_t3:pid</label>
			<label index="parsefunc.alttitle">parseFunc</label>
			<label index="parsefunc.description">In Typoscript parseFunc allows you to examine and change text that has been entered into forms in the backend before the text is saved into or fetched from the database (usually it's the bodytext field of a content element form). parseFunc lets you deny certain HTML tags, only allow certain tags, substitute for custom tags, substitute for markers, edit links, etc. If you are entering some text into a content element (like ) and every time you save the form the text disappears, it's because of the how the parseFunc is configured.</label>
			<label index="_parsefunc.seeAlso">http://typo3.org/documentation/document-library/doc_core_tsref/parseFunc/|Typoscript reference (TSref)</label>
			<label index="password.alttitle">password</label>
			<label index="password.description">The secret text sequence to get access to the user account. For the install tool use "joh316" and for the TYPO3 dummy.zip file "password" as your standard password. For security reasons you should change the standard passwords as soon as possible.</label>
			<label index="password_protected_pages.alttitle">password protected pages</label>
			<label index="password_protected_pages.description">See "access restriction"</label>
			<label index="_password_protected_pages.seeAlso">xGLOSSARY_t3:access_restriction</label>
			<label index="paste_after.alttitle">paste after</label>
			<label index="paste_after.description">Paste the content of the clipboard at the same level as the selected page. It becomes a child of the parent of the selected page and becomes pasted below the selected page, and the former page that was in this position is moved down.</label>
			<label index="paste_into.alttitle">paste into</label>
			<label index="paste_into.description">Paste the element currently in the clipboard as a subelement of the selected page.</label>
			<label index="permission.alttitle">permission</label>
			<label index="permission.description">The user rights to do some jobs in the backend or frontend.</label>
			<label index="_permission.seeAlso">xGLOSSARY_t3:password</label>
			<label index="php.alttitle">PHP</label>
			<label index="php.description">PHP is an open source scripting language, mostly used for server-side applications and dynamic content for the web. TYPO3 is written in PHP.</label>
			<label index="_php.seeAlso">http://php.net|php.net Official PHP website, http://en.wikipedia.org/wiki/PHP|Wikipedia about PHP</label>
			<label index="php-function.alttitle">PHP-function</label>
			<label index="php-function.description">See "PHP function"</label>
			<label index="_php-function.seeAlso">xGLOSSARY_t3:php_function</label>
			<label index="php_function.alttitle">PHP function</label>
			<label index="php_function.description">A PHP function is a named program code written in a PHP-file (extension .php). All the code in one function belongs together. It gets parameters to be calculated with, does some work and returns a value as the result to the calling line in the PHP program code.</label>
			<label index="pid.alttitle">pid</label>
			<label index="pid.description">Parent id, an unique number representing a single page in the TYPO3 installation. Not to be mistaken for page id which is in fact a uid.</label>
			<label index="plugin.alttitle">plugin</label>
			<label index="plugin.description">A plugin is a type of extension that produce frontend material visible on the TYPO3 generated website (for example the News extension).</label>
			<label index="_plugin.seeAlso">xGLOSSARY_t3:extension</label>
			<label index="pop-up_window.alttitle">Pop-up window</label>
			<label index="pop-up_window.description">A pop-up window is a small window which is shown as soon as you click, or move your mouse cursor above, a special position on the screen. Usually it opens up a text box or an image.</label>
			<label index="popup_window.alttitle">popup window</label>
			<label index="popup_window.description">See "Pop-up window"</label>
			<label index="_popup_window.seeAlso">xGLOSSARY_t3:pop-up_window</label>
			<label index="post_method.alttitle">POST method</label>
			<label index="post_method.description">All websites consist of HTML and mostly JavaScript-code, even if they are written in a programming language like PHP. The POST method is used to pass filled-in data from a dialog form to the web server, when pressing a Send-button. The method is set by the "method=post" attribute in the HTML FORM tag.
This method sends all the form data without showing it in the URL line of the browser. Attached files always has to be sent by the POST method.</label>
			<label index="_post_method.seeAlso">GET|method</label>
			<label index="preview.alttitle">preview</label>
			<label index="preview.description">A preview gives you a cutted or resized glimpse at a document, sound, image or other meta file. In TYPO3 this is the view of a hidden or restricted page, before it is made public. Only backend users can preview hidden or restricted pages.</label>
			<label index="primary_form_fields.alttitle">primary form fields</label>
			<label index="primary_form_fields.description">The most significant fields shown in record editing forms in TYPO3. These fields are always shown to the user. The counterpart are "secondary form fields", which may be hidden from all or some users.</label>
			<label index="property.alttitle">property</label>
			<label index="property.description">A property is the combination of an element name and its textual or numerical value. A property has a name e.g. "color" and a value e.g. "green" or "#234332" (which is a RGB number for a color).</label>
			<label index="publishing_control_fields.alttitle">publishing control fields</label>
			<label index="publishing_control_fields.description">See "visibility settings"</label>
			<label index="_publishing_control_fields.seeAlso">xGLOSSARY_t3:visibility_settings</label>
			<label index="rdct.alttitle">RDCT</label>
			<label index="rdct.description">(index.php hash parameter to make long URLs short for emails etc.)</label>
			<label index="real-time_processing.alttitle">real-time processing</label>
			<label index="real-time_processing.description">A computer program processes in real-time when it does its calculations continuously and is not interrupted by other processes of the computer. This is necessary to be sure that a certain job can be done in a guaranteed time space.</label>
			<label index="record.alttitle">record</label>
			<label index="record.description">A record is an object in the backend used to store any sort of information. Examples are: addresses, products, users, groups, templates, news items, catagories, domain names, etc.  Records are contained by pages. The information stored in a record does not, in and of itself, appear on a web page in the frontend. In order for a record to be displayed in the frontend a page must contain a content element whose job is to display the record(s).  You can add records to any page in the backend by clicking on "List" in the left hand column, selecting the page you want to add to, and then clicking "Create new record" on the right.
In TYPO3 programming, a record represents a row in some table which relates to the page table other than the content elements table (tt_content).</label>
			<label index="recursively.alttitle">recursively</label>
			<label index="recursively.description">If one function calls itself, this means to be recursive. In TYPO3 it means "not limited to the current or selected page(s)". It is used in conjunction with the starting point for different plugins. The starting point marks the base node and recursive is used to determine how many levels you want to dive into the subpages to get records. Possible values are "empty" (only the current page or the starting point is used), 1, 2, 3 or 4 levels and "infinite".</label>
			<label index="resources.alttitle">resources</label>
			<label index="resources.description">A resource could be a text or a graphic file or a collection of other resources. But also human beings, corporations and bound books in a library can also be considered resources.</label>
			<label index="reviewing.alttitle">reviewing</label>
			<label index="reviewing.description">This is the process where several developers examine the source code or document written by another person.</label>
			<label index="rich_text_editor.alttitle">Rich Text Editor</label>
			<label index="rich_text_editor.description">A WYSIWYG ("what you see is what you get") editor for adding content. It's being used in various content elements and extensions.</label>
			<label index="_rich_text_editor.seeAlso">http://typo3.org/documentation/tips-tricks/customizing-the-rich-text-editor/|Customizing the Rich Text Editor, http://typo3.org/documentation/document-library/doc_core_api/Introduction-2f59347d00/|TYPO3 Core APIs - RTE API</label>
			<label index="roll_over.alttitle">roll over</label>
			<label index="roll_over.description">See "rollover state"</label>
			<label index="_roll_over.seeAlso">xGLOSSARY_t3:rollover_state</label>
			<label index="roll_over_state.alttitle">roll over state</label>
			<label index="roll_over_state.description">See "rollover state"</label>
			<label index="_roll_over_state.seeAlso">xGLOSSARY_t3:rollover_state</label>
			<label index="rollover.alttitle">rollover</label>
			<label index="rollover.description">See "rollover state"</label>
			<label index="_rollover.seeAlso">xGLOSSARY_t3:rollover_state</label>
			<label index="rollover_state.alttitle">rollover state</label>
			<label index="rollover_state.description">For website navigation (menu items), the state of a menu item when a website user positions the mouse cursor over the item. Practically the roll over state lets you define how menu items should change their visual appearance when the mouse cursor is moved over the item.</label>
			<label index="_rollover_state.seeAlso">http://typo3.org/doc.0.html%26tx_extrepmgm_pi1%5BextUid%5D%3D270%26tx_extrepmgm_pi1%5BtocEl%5D%3D382%26cHash%3Db13af36f98__|Item states described in Typoscript Reference (TSref)</label>
			<label index="root_level.alttitle">root level</label>
			<label index="root_level.description">A starting point. Websites made with TYPO3 always have a single root page in the page tree; From this point in the page tree and outwards all pages belong to that website. Root points for websites are defined by
the "control element" called a Typoscript template record.</label>
			<label index="root_level_flag.alttitle">root level flag</label>
			<label index="root_level_flag.description">See "rootlevel flag"</label>
			<label index="_root_level_flag.seeAlso">xGLOSSARY_t3:rootlevel_flag</label>
			<label index="root_line.alttitle">root line</label>
			<label index="root_line.description">See "rootline"</label>
			<label index="_root_line.seeAlso">xGLOSSARY_t3:rootline</label>
			<label index="root_of_page_tree.alttitle">root of page tree</label>
			<label index="root_of_page_tree.description">This is the starting point where you begin to create your TYPO3 homepages. The next steps will be to create a new page and a template for that page.</label>
			<label index="root_page.alttitle">root page</label>
			<label index="root_page.description">The first page of your homepage is called the root page. As soon as a client enters the full URL address of your homepage into his browser client, your root page will be loaded and shown.</label>
			<label index="rootlevel_flag.alttitle">rootlevel flag</label>
			<label index="rootlevel_flag.description">In a Typoscript template form, this is a checkbox that defines that the record should start a new website root from that point in the page tree.</label>
			<label index="rootlevel_root_level_flag.alttitle">rootlevel root level flag</label>
			<label index="rootlevel_root_level_flag.description">See "root level"</label>
			<label index="_rootlevel_root_level_flag.seeAlso">xGLOSSARY_t3:root_level</label>
			<label index="rootline.alttitle">rootline</label>
			<label index="rootline.description">The current position or "path" in the page tree hierarchy. The term is normally used technically like "in the rootline" which means that a value is found in one of the page records that are found when going up the page tree to its root. In the backend the rootline normally extends all the way to the physical page tree root. In the frontend the rootline normally stops at the root page of the website indicated by the main template record.</label>
			<label index="_rootline.seeAlso">http://typo3.org/doc.0.html%26encryptionKey%3D%26tx_extrepmgm_pi1%5BextUid%5D%3D277%26tx_extrepmgm_pi1%5BtocEl%5D%3D560%26cHash%3Dd39f3a7d5a__|Rootline explained in Typoscript templates</label>
			<label index="rootpage.alttitle">rootpage</label>
			<label index="rootpage.description">See "root page"</label>
			<label index="_rootpage.seeAlso">xGLOSSARY_t3:root_page</label>
			<label index="rte.alttitle">RTE</label>
			<label index="rte.description">See "Rich Text Editor"</label>
			<label index="_rte.seeAlso">xGLOSSARY_t3:rich_text_editor</label>
			<label index="secondary_form_fields.alttitle">secondary form fields</label>
			<label index="secondary_form_fields.description">The less significant form fields shown in record editing forms in TYPO3. These appear in two ways depending on configuration:
By default they are shown in the vertical top-frame of TYPO3 when a user places the cursor in a primary form field. Alternatively, they are shown under a primary
form field, indented a little (if the "Show secondary options" checkbox is enabled).
The point of this feature is to prioritize a large number of form fields so the interface is not cluttered with more rarely used options.
A group of secondary form fields are always located in relation to a primary field and the group is sometimes referred to as a "palette" (of tools).</label>
			<label index="secondary_options.alttitle">secondary options</label>
			<label index="secondary_options.description">Options normaly hidden because they are not often used.</label>
			<label index="_secondary_options.seeAlso">xGLOSSARY_t3:secondary_form_fields</label>
			<label index="selective_editing.alttitle">selective editing</label>
			<label index="selective_editing.description">Editing only certain parts of a bunch of content elements, like title, visibiltiy, access etc.</label>
			<label index="selector.alttitle">selector</label>
			<label index="selector.description">The selector is an HTML element which is used in a form to enter data. It is drawn as a box with a lot of entries from where you can choose on or more items.</label>
			<label index="setup.alttitle">setup</label>
			<label index="setup.description">This text field contains the raw Typoscript in a Typoscript template. This code can be overwritten by other Typoscript templates which are parsed after this one. The setup field can be changed in the Template module after selecting the Info/Modify popup menu entry.</label>
			<label index="setup_field.alttitle">setup field</label>
			<label index="setup_field.description">See "setup"</label>
			<label index="_setup_field.seeAlso">xGLOSSARY_t3:setup</label>
			<label index="shortcut.alttitle">shortcut</label>
			<label index="shortcut.description">Shortcut is a link from one page to another page in the page tree. This is used to make it possible that the page the link points to, will be shown as soon as a user browses to the page containing the link. In addition to this, shortcuts will appear as a menu entries. They can be used to insert certain pages into a menu even though the are outside the branch the menu currently displays. Comes in handy when you are using parent pages without content just to categorize navigation menu. In this case the shortcut can be set to display the first subpage of the shortcut page.</label>
			<label index="show_subpage.alttitle">show subpage</label>
			<label index="show_subpage.description">See "shortcut"</label>
			<label index="_show_subpage.seeAlso">xGLOSSARY_t3:shortcut</label>
			<label index="simulatestaticdocuments.alttitle">simulateStaticDocuments</label>
			<label index="simulatestaticdocuments.description">A way to use the Apache module mod_rewrite to redirect all requests to index.php and manipulate the links generated by TYPO3 to appear to be static. But in fact they are just being rewritten by mod_rewrite and parsed by index.php.</label>
			<label index="soft_references.alttitle">soft references</label>
			<label index="soft_references.description">The Import/Export extension (impexp) introduce the concept of "soft references" being imported or exported. This term should be explained, since this is a fixed term which has no meaningfull translation.</label>
			<label index="source.alttitle">source</label>
			<label index="source.description">Shortword for sourcecode (of a program) OR the place a certain assert is located.</label>
			<label index="standard_template.alttitle">standard template</label>
			<label index="standard_template.description">TYPO3 comes already with predefined standard templates. You can easily adapt these templates by using the Constant Editor without making a change to the original template files.</label>
			<label index="start_time.alttitle">start time</label>
			<label index="start_time.description">From this time a certain page or content element will be visible in the frontend.</label>
			<label index="starting_point.alttitle">starting point</label>
			<label index="starting_point.description">See "root of page tree"</label>
			<label index="_starting_point.seeAlso">xGLOSSARY_t3:root_of_page_tree</label>
			<label index="state.alttitle">state</label>
			<label index="state.description">The state is the property of a process in a computer program. The same program will work differently under the same conditions when its internal state has changed. E.g. if a serious error occurs the process will get into an error state and output some errror messages.</label>
			<label index="static_template.alttitle">Static template</label>
			<label index="static_template.description">A Static template is a Typoscript template included by default in TYPO3 installations and they cannot be edited. There are around 50 of them. You can use them by including them in your templates using the "Include static:" field on the template form.</label>
			<label index="_static_template.seeAlso">http://typo3.org/documentation/document-library/doc_statictmpl/|Details of Static templates</label>
			<label index="stdwrap.alttitle">stdWrap</label>
			<label index="stdwrap.description">In Typoscript stdWrap is a catch-all for more than 60 functions which can be added as properties to values in Typoscript.  The stdWrap functions do things like: wrapping values (see wrap), retrieving values from the database, setting the value based on conditions, and parsing and formatting the value in lots of different ways.</label>
			<label index="_stdwrap.seeAlso">http://typo3.org/documentation/document-library/doc_core_tsbyex/The_concept_stdWrap/|Typoscript By Example - stdWrap, http://typo3.org/documentation/document-library/doc_core_tsref/stdWrap/|Typoscript reference - stdWrap</label>
			<label index="stop_time.alttitle">stop time</label>
			<label index="stop_time.description">A field in the page header and content element forms. At this time the page or content element will no longer be visible from the frontend.</label>
			<label index="storage_folder.alttitle">Storage folder</label>
			<label index="storage_folder.description">See "SysFolder"</label>
			<label index="_storage_folder.seeAlso">xGLOSSARY_t3:sysfolder</label>
			<label index="stylescontent.alttitle">styles.content</label>
			<label index="stylescontent.description">styles.content is kind of default Typoscript structure to display the content of a page. It serves you with for example styles.content.getLeft to get the whole content of the left column of a page.</label>
			<label index="stylescontent_default.alttitle">styles.content (default)</label>
			<label index="stylescontent_default.description">The name of a certain so called static template that contains predefined Typoscript objects for rendering the content elements on a page. The objects inside serve mostly as a library for the static template "content (default)" which does the overall rendering of content elements.</label>
			<label index="stylescontentget.alttitle">styles.content.get</label>
			<label index="stylescontentget.description">In Typoscript templates making use of content(default), this is a predefined Typoscript object path inserting page content elements from the "NORMAL" column. It will only be available when users have included a static template containing styles.content.get. It's nothing else but a predefined Typoscript object CONTENT providing the user with common stuff for default cObjects.</label>
			<label index="stylesheet.alttitle">stylesheet</label>
			<label index="stylesheet.description">A stylesheet is a file that contains formatting infomation about a Web page. Stylesheets allow for the separation of structure and layout in markup languages such as (X)HTML (-> CSS).</label>
			<label index="_stylesheet.seeAlso">http://w3.org/Style/CSS/|W3C - CSS</label>
			<label index="sub_module.alttitle">sub module</label>
			<label index="sub_module.description">A backend module in TYPO3 which is found under a main module. Typical examples are "Web > Page" or "Tools > Ext. Manager". The distinction between "main" and "sub" modules are purely with reference to the organization in the backend module menu.</label>
			<label index="sub_page.alttitle">sub page</label>
			<label index="sub_page.description">A page that is the child of a parent page is the subpage to this one.</label>
			<label index="subpage.alttitle">subpage</label>
			<label index="subpage.description">See "sub page"</label>
			<label index="_subpage.seeAlso">xGLOSSARY_t3:sub_page</label>
			<label index="subpages.alttitle">subpages</label>
			<label index="subpages.description">See "sub page"</label>
			<label index="_subpages.seeAlso">xGLOSSARY_t3:sub_page</label>
			<label index="subpart_marker.alttitle">subpart marker</label>
			<label index="subpart_marker.description">A set of identifiers surrounded by ### (e.g. ###IDENTIFIER###) which is used in an HTML template file. Each subpart must have two markers for start and stop. These markers and the content between them are then substituted for the final content by TYPO3.</label>
			<label index="subparts.alttitle">subparts</label>
			<label index="subparts.description">A subpart is defined as the (dynamic) content between two similar marker strings wrapped in ### and encapsulated in an HTML-comment (optional).</label>
			<label index="suggest_new_word.alttitle">Suggest new word</label>
			<label index="suggest_new_word.description">Here you can suggest new words for the glossary. Some people think they "help" us by moving (removing?)  words from this section into the alphabetic listing above. Unfortunately they just make our work harder, so please don“t move words from this section!</label>
			<label index="syntax.alttitle">syntax</label>
			<label index="syntax.description">A set of grammatical rules defining valid use of specific commands or instructions in a computer language.</label>
			<label index="sysfolder.alttitle">SysFolder</label>
			<label index="sysfolder.description">Normally you store elements related to a page on the page itself, eg. content elements or maybe even frontend users. However you will often find that for a website you need some general purpose page to place records which are related to the whole site and not just single pages - this is what we call a SysFolder or Storage FolderF A "SysFolder" page defined to be a general purpose storage page for elements related to a website in a branch of the page tree.</label>
			<label index="_sysfolder.seeAlso">http://wiki.typo3.org/index.php/T3Doc:doc_tut_ftb1/The_Storage_Folder/| About Storage Folders in Futuristic Template Building</label>
			<label index="system_extension.alttitle">system extension</label>
			<label index="system_extension.description">See "extension"</label>
			<label index="_system_extension.seeAlso">xGLOSSARY_t3:extension</label>
			<label index="t3lib.alttitle">t3lib&