<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<T3locallangExt>
	<data type="array">
		<languageKey index="ch" type="array">
			<label index=".alttitle">工具&gt;扩展管理器</label>
			<label index=".description">扩展管理器控制着TYPO3系统的导入,安装及更新.</label>
			<label index=".details">TYPO3在考虑到兼容性的同时可向任何方向扩展。扩展API提供了一个强大的框架，更容易添加，移除，安装和开发TYPO3的扩展。这是TYPO3扩展管理器的详细的功能。
“扩展”是TYPO3中包含其它TERM，插件及模块的TERM。
插件是网站上运行的一个特殊功能的东西。例如，一个board，留言簿，网店等。它通过被附加上PHP的类及能通过TypoScript的USER或USER_INT cObject调用。一个插件就是前台的一个扩展。
一个模块就是后台的一个程序，该程序在管理菜单中有其位置。它要求后台登录及在后台框架中工作。我们也可以把一些东西叫作模块（如果它们是现有模块的扩展），一个模块是后台的一个扩展。</label>
			<label index="loaded.alttitle">载入扩展</label>
			<label index="loaded.description">“装载的扩展”当前在系统中运行。此列表向您显示了按顺序排列的哪些扩展已被载入。“害羞的”扩展总是被载入但在此列表中“隐藏”，因为它们与系统有关，通常您应该让它们单独存在，除非您知道您在做什么 。</label>
			<label index="loaded.details">此列表中按顺序排列的扩展可在$TYPO3_CONF_VARS[EXT][extList]找到。要重新安装一个扩展，您只要点击绿色的 &quot;-&quot; 图标。如果没有可依靠的扩展，它将从安装的扩展列表中移除。
载入的扩展列表中的&quot;Rq&quot; 扩展是“必须的”扩展。这些扩展与系统密切相关，您不能从扩展管理器中禁用它们。</label>
			<label index="loaded.image_descr">载入扩展的列表在载入顺序显示。</label>
			<label index="avail.alttitle">可用的扩展</label>
			<label index="avail.description">可用的扩展是出现在扩展文件夹中的扩展。您可安装任何的扩展到此列表中。当您安装一个扩展后它将由TYPO3在安装时载入。在此列表中的后台隐藏的扩展已安装（载入）--其它可用的（未载入的），已准备好按您的要求安装。</label>
			<label index="avail.details">您可通过点击此列表中的灰色的 &quot;+&quot; 图标来安装扩展。如果您想反安装扩展可点击绿色的 &quot;-&quot; 图标。
当您点击安装按钮(&quot;+&quot;) ，当您确定创建数据库表及区域或被要求“清除所有缓存”，您常常以此会话结束安装。扩展管理器自动操作这些要求以使安装非常容易。</label>
			<label index="avail.image_descr">服务器上可用的扩展的列表。此列表从服务器上的“本地”，“全局”和“系统”文件夹中编译。
如果您点击一个扩展的安装图标 (&quot;+&quot;) ，您可能结束一个像这样的会话。在此例中，一个新的数据库表被要求。扩展管理器将自动探测到它不存在，并建议您创建表。创建动作自动地执行，只需要通过按“进行更新”以同意更改。</label>
			<label index="import.alttitle">导入扩展</label>
			<label index="import.description">这是将扩展的文件带给服务器文件系统的处理过程。您可通过URL从库中导入（通常从TER；typo3.org上的TYPO3扩展库）或上传其他人从另一服务器创建的。&quot;t3x&quot;文件</label>
			<label index="import.details">&lt;b&gt;从TER导入&lt;/b&gt;
要连接到TER，您只要点击“连接到在线扩展库”按钮。这需要按钮上面显示的URL，并且该URL应该返回一个您可导入的扩展库的列表。如果您知道您需要找什么，那么在查找框中输入一个搜索单词。这将帮助您查找明确的扩展关键词。如果您使用这个功能，较少的数据发送到TER，连接将非常快。
&lt;b&gt;从文件上传&lt;/b&gt;
对私人扩展的交换来说，通过发送“T3X”文件可非常容易地从一个系统到另一个系统。在一个TYPO3的安装上，您只要前往一个扩展的“备份/删除”菜单并下载一个扩展的“备份”。文件格式是一个连续的PHP列队，如果可能，则被压缩。如果您想导入它，此文件能在另一个TYPO3系统的扩展管理器中上传。</label>
			<label index="import.image_descr">“导入”屏幕。在您连接到在线扩展库之前，您应该配置TYPO3。ORG的用户名和密码，该用户名和密码将被用来选择TER中的“成员”扩展 ，如果可能，您能启用“仅获得自己的/会员的/选择的扩展”，只要您想限制列表长度的话。</label>
			<label index="import_ter.alttitle">TER的扩展</label>
			<label index="import_ter.description">此列表中的扩展可从TYPO3扩展库直接在线下载.带黑色背景的扩展是已在您服务器上安装的扩展,其它的扩展在您使用之前必须从扩展库导入到您的服务器上。如果您希望从扩展库中使用一个扩展，您应该点击左边带有红色的指向扩展的箭头的“导入”按钮。</label>
			<label index="import_ter.details">&lt;b&gt;导入扩展&lt;/b&gt;
如果一个扩展不在您的服务器上，您将看到一个带红色箭头的扩展。只要点击一下，扩展将下载并解压到您的服务器上。如果您将鼠标移到图标上将显示下载目录。
&lt;b&gt;更新扩展&lt;/b&gt;
您可通过点击绿色箭头的图标的扩展以更新您服务器上的扩展。如果“次要”版本（第二个数字）已增加的话，更新图标将出现。这意味着更新了开发版本号的扩展（第三个数字）将不会显示为“准备好更新”。（您可配置TYPO3以这么做！）
&lt;b&gt;查看TYPO3扩展库中的扩展的细节&lt;/b&gt;
您可点击扩展的标题以查看其细节。这将允许您执行更多的更新操作的细节，您可选择版本号及下载位置（local/global/system）。您也可要求下载最新的翻译。</label>
			<label index="import_ter.image_descr">TYPO3扩展库的扩展的列表。红色箭头是“导入”链接（用于新的扩展），绿色箭头是“更新”链接（用于已存在于您的服务器上的扩展）。如果一个扩展已有许多可用的最近的版本，您不会看到扩展的左边的任何图标。
如果您点击扩展的标题，您将请求扩展库提供扩展的细节。这允许您选择一个特殊的版本以用于导入。您可选择安装位置（global/local）并且您可请求扩展的最新的翻译。</label>
			<label index="info.alttitle">扩展的细节</label>
			<label index="info.description">显示扩展的细节。</label>
			<label index="info.details">在此查看中，一些来自于扩展中的&quot;ext_emconf.php&quot;文件的细节信息的显示。&quot;emconf&quot; 文件包含了扩展管理器的元数据。
扩展管理器将前进得更深一点并在扩展中执行对脚本的分析。列表将包含此分析找到的内容，如果找到任何错误都将显示出来。通常情况下这些错误不会阻止扩展的工作，但会指出一些扩展的开发者应该注意的理论上的错误。</label>
			<label index="info.image_descr">扩展显示从&quot;ext_emconf.php&quot; 文件来的静态数据的分析的活跃的统计的细节的查看。</label>
			<label index="backup_delete.alttitle">将扩展作为文件备份</label>
			<label index="backup_delete.description">点击这儿的“下载”链接，您将把扩展作为一个文件下载（包括连续的PHP队列），如果服务器支持的话，无用的信息和其它任何东西都可能被压缩。用扩展名为&quot;t3x&quot;保存文件。</label>
			<label index="backup_delete.image_descr">扩展“备份”--对一个组中的成员交换扩展非常有用。</label>
			<label index="upload.alttitle">上传扩展到扩展库(TER)</label>
			<label index="upload.description">在这您可上传 个扩展到TER。要这么做的话，您必须输入您的TYPO3.org的用户名和密码。In addition each extension has an upload password you need to add as well。您应该确认您的注册/拥有扩展key！</label>
			<label index="upload.details">&lt;b&gt;更改记录&lt;/b&gt;
在更改记录区您输入的更改操作或上传的原因。这将在新扩展的列表中显示。
&lt;b&gt;版本号&lt;/b&gt;
选择一个版本号增加的方法，对您的扩展的新“版本”，您应该选择“子”或“主”版本，这将在新扩展列表中显示。以维护您上传的&quot;dev&quot;。</label>
			<label index="upload.image_descr">扩展的上传。扩展被提交到选择的扩展库，通常是TYPO3.org（默认）</label>
			<label index="editfiles.alttitle">在扩展中编辑脚本</label>
			<label index="editfiles.description">扩展管理器能被用来编辑扩展的脚本。此特性主要是在网站浏览者没有好的工具时使用。</label>
			<label index="editfiles.details">&lt;b&gt;注意：&lt;/b&gt;
在编辑扩展脚本之前，您应该禁用&quot;localconf.php&quot;中的配置选项&quot;TYPO3_CONF_VARS[EXT][noEdit]&quot; 。</label>
			<label index="editfiles.image_descr">一些文件类型---如PHP脚本--能通过扩展管理器中的文本区来编辑。</label>
			<label index="settings.alttitle">扩展管理器设置</label>
			<label index="settings.description">进入扩展管理器的设置。用户名和密码用来连接扩展库（通常是typo3.org），上传密码是您正常用来上传扩展的。</label>
			<label index="settings.details">&lt;b&gt;注意：&lt;/b&gt;
此信息不能很好地受到保护！它发送并存储在明文中！</label>
			<label index="settings.image_descr">设置TER连接。</label>
			<label index="makenew.alttitle">Kickstarting 新扩展</label>
			<label index="makenew.description">&quot;Kickstarter&quot; 是一个允许您很容易地开始一个新的扩展工作的程序。通过一个界面您可为您的扩展创建一个基本的框架，所有烦琐的原始数据都在初始就配置好，并且您可直接压缩您的程序的原码。</label>
			<label index="makenew.details">扩展库Kickstarter是一个分开的扩展， &quot;extrep_wizard&quot;。请查看kickstarter的更多其它方面的信息。
&lt;b&gt;注意：&lt;/b&gt;
Kickstarter 不是编辑器！当一个新的扩展开始时您不能--作为单凭经验的方法--返回 用kickstarter编辑它！它将覆盖当前期间内您做的任何更改！</label>
			<label index="makenew.image_descr">当&quot;Extension Repository Kickstarter&quot;可用时它将添加其自身到扩展管理器的菜单中。在这里您可开始您的新扩展。在您这么做之前您应该注册一个扩展关键词并输入一个标题及描述作为基本数据。从那个点只需要点击 &quot;+&quot; 图标以添加您需要的不同类型的功能。最后您点击“查看结果”以写入服务器上的扩展。</label>
			<label index="emconf_shy.alttitle">害羞的</label>
			<label index="emconf_shy.description">如果设置，扩展将在扩展管理器中隐藏，因为它可能是默认的扩展或不是非常重要的一些东西。</label>
			<label index="emconf_shy.details">如果一个扩展是&quot;rare interest&quot;（(which is not the same as un-important - just an extension not sought for very often...)使用此标签。
不管其是否被激活都不会受到影响。仅在扩展管理器中显示。
正常情况下，所有依靠TYPO3_CONF_VARS默认的载入的扩展都被设置为 &quot;shy&quot; 。</label>
			<label index="emconf_category.alttitle">分类</label>
			<label index="emconf_category.description">扩展所属的分类。</label>
			<label index="emconf_category.details">&lt;b&gt;be:&lt;/b&gt; 后台 (一般后台导向, 不是模块)

&lt;b&gt;模块：&lt;/b&gt; 后台模块(一些东西是模块或连接到模块)

&lt;b&gt;fe:&lt;/b&gt; 前台 (一般前台向导, 不是 &quot;真实的&quot; 插件)

&lt;b&gt;插件：&lt;/b&gt; 前台插件(作为 &quot;插入的插件&quot;插入的内容元素)

&lt;b&gt;混杂的：&lt;/b&gt; 混合的（不容易放在其它地方的）

&lt;b&gt;服务：&lt;/b&gt; 包含TYPO3 服务。

&lt;b&gt;模板：&lt;/b&gt; 包含网站模板

&lt;b&gt;文档：&lt;/b&gt; 文档 (如指南，FAQ等等)

&lt;b&gt;示例：&lt;/b&gt; 示例扩展(提供一个示例等等)</label>
			<label index="emconf_dependencies.alttitle">依赖于其它扩展?</label>
			<label index="emconf_dependencies.description">这是此扩展依靠的并在其之前被载入的其它扩展的关键词的列表。</label>
			<label index="emconf_dependencies.details">扩展管理器将在扩展列表写入到localconf.php文件中管理dependency。您不可以安装一个其依靠的扩展未安装的扩展。</label>
			<label index="emconf_conflicts.alttitle">与其它扩展冲突?</label>
			<label index="emconf_conflicts.description">不工作的扩展的扩展关键词的列表（并且不能在其它扩展被卸载之前启用）</label>
			<label index="emconf_priority.alttitle">请装载优先权</label>
			<label index="emconf_priority.description">这告诉扩展管理器尝试将扩展放在列表的最前面。默认是在最后面。</label>
			<label index="emconf_module.alttitle">包括的后台模块</label>
			<label index="emconf_module.description">一个扩展包含的后台模块的子文件夹，这些文件夹名称将在此列出。</label>
			<label index="emconf_module.details">这将允许扩展管理器知道存在的模块，这很重要，因为扩展管理器要更新模块的conf.php文件以设置正确的TYPO3_MOD_PATH 常量。</label>
			<label index="emconf_state.alttitle">发展状态</label>
			<label index="emconf_state.description">扩展当前的开发状态。</label>
			<label index="emconf_state.details">&lt;b&gt;alpha&lt;/b&gt;
最初的开发版本. 不能做任何事情.

&lt;b&gt;beta&lt;/b&gt;
当前开发版本. 部分能工作但没有完成.

&lt;b&gt;stable&lt;/b&gt;
稳定版本，在产品中使用。

&lt;b&gt;experimental&lt;/b&gt;
没有人知道它会向什么方向发展... 或许只是个想法。

&lt;b&gt;test&lt;/b&gt;
测试版本，展示观念等。</label>
			<label index="emconf_internal.alttitle">被核心支持</label>
			<label index="emconf_internal.description">此标识指出核心源代码已明确地了解了扩展。</label>
			<label index="emconf_internal.details">换句话说，此标识将传送消息“没有核心源代码的修正，此扩展不能被写入”。
一个扩展不是内部的仅仅是因为它使用TYPO3常规的类，eg. those from t3lib/.
True non-internal extensions are characterized by the fact that they could be written without making core source code changes, but relies only on existing classes in TYPO3 and/or other extensions, plus its own scripts in the extension folder.</label>
			<label index="emconf_clearCacheOnLoad.alttitle">当安装时清除缓存</label>
			<label index="emconf_clearCacheOnLoad.description">如果设置，扩展管理器将在扩展安装后要求清除缓存。</label>
			<label index="emconf_modify_tables.alttitle">现有的表被修改</label>
			<label index="emconf_modify_tables.description">仅修改的表格名的列表--不是完全创建的---通过此扩展。</label>
			<label index="emconf_modify_tables.details">从扩展的ext_tables.sql 文件中找到的表格。</label>
			<label index="emconf_private.alttitle">私有的</label>
			<label index="emconf_private.description">如果设置，此版本不在在线扩展库的公共区列表显示。</label>
			<label index="emconf_private.details">“私人”要求您手工输入特殊的关键词（这将在您上传完成后显示给您）以开启导入及查看上传扩展的细节。
这在您工作于内部并且您不想其它人看到时是很有用的。
您可在任何时间上传您的扩展，并设置并清除私人标识。</label>
			<label index="emconf_download_password.alttitle">下载密码</label>
			<label index="emconf_download_password.description">下载私人的扩展的附加密码。</label>
			<label index="emconf_download_password.details">知道分配给私人上传的“特殊关键词”的任何人都可导入它。指定一个重要的密码允许您分发下载关键词供私人的上传及要求附加的一个密码。密码可在以后更改。</label>
			<label index="emconf_type.alttitle">安装类型</label>
			<label index="emconf_type.description">安装的类型</label>
			<label index="emconf_type.details">扩展的文件定位于由扩展关键字命名的文件夹。此文件夹的位置可位于typo3conf/ext/, typo3/ext/ 或 typo3/sysext/。扩展必须编程以让其自动探测其位置并从所有这些位置工作。
&lt;b&gt;本地位置&quot;typo3conf/ext/&quot;:&lt;/b&gt;
这是在本地安装的TYPO3的放置扩展的位置。typo3conf/ 文件夹总是在本地，包含本地配置（如localconf.php），本地模块等。如果您在这里放一个扩展，它仅对此TYPO3系统可用。这是&quot;per-database&quot; 方式安装一个扩展。
&lt;b&gt;全局位置&quot;typo3/ext/&quot;:&lt;/b&gt;
这是在服务器上TYPO3源代码的全局放置扩展的位置。这些扩展对任何共享TYPO3安装的源代码都可用。当您更新您的TYPO3源代码时，或许您想从以前的typo3/ext/ 目录下复制所有扩展到新的源代码的该目录下，覆盖默认目录。通过此方法，所有您使用的全局扩展将安装在新的源代码下。这样，如果需要，您总是可进入TYPO3并更新版本。这是 &quot;per-server&quot;方式安装一个扩展。
&lt;b&gt;系统位置&quot;typo3/sysext/&quot;:&lt;/b&gt;
这是系统默认的扩展，不能通过扩展管理器更新。它们随着TYPO3的核心发布。
&lt;b&gt;优先装入&lt;/b&gt;
本地扩展具有优先装入权，这意味着如果一个扩展位于 typo3conf/ext/ 和 typo3/ext/下，typo3conf/ext/ 下的被装入。同样地，全局扩展优先权高于系统扩展。这意味着扩展的装入优先权的顺序是本地--全局--系统。
实际上您会说，安装在全局目录(typo3/ext/) 下的“稳定”版扩展是在您的服务器上共享的用于您所有项目的扩展，但在一个单一的试验项目上您可导入相同的扩展的新的&quot;experimental&quot;版本，对此试验项目来说，本地可用的扩展将被替代。</label>
			<label index="emconf_doubleInstall.alttitle">安装两次或多次</label>
			<label index="emconf_doubleInstall.description">告诉您扩展是否已安装超过一个系统，全局或本地位置。</label>
			<label index="emconf_doubleInstall.details">因为一个扩展可位于三个位置，系统，全局和本地，这指出扩展是否在其它位置找到。在此例中您应该了解哪个扩展已被载入。</label>
			<label index="emconf_rootfiles.alttitle">根文件</label>
			<label index="emconf_rootfiles.description">扩展文件夹中的文件列表。不列表子文件夹中的文件。</label>
			<label index="emconf_dbReq.alttitle">数据库需求</label>
			<label index="emconf_dbReq.description">向您显示数据库表及区域的要求，任意的。</label>
			<label index="emconf_dbReq.details">这将从文件ext_tables.sql 及ext_tables_static+adt.sql 载入并向您显示哪个表，区域及静态表被扩展所要求。</label>
			<label index="emconf_dbStatus.alttitle">数据库需求状态</label>
			<label index="emconf_dbStatus.description">显示当前数据库与扩展要求的数据库相比较的结果。</label>
			<label index="emconf_dbStatus.details">如果扩展被载入，将显示出来，并且如果一些表或区域不在数据库中，显示错误信息。</label>
			<label index="emconf_flags.alttitle">标记</label>
			<label index="emconf_flags.description">一个特别的代码的列表将告诉您扩展涉及到TYPO3的哪部分。</label>
			<label index="emconf_flags.details">下面是标记的列表：
&lt;b&gt;模块:&lt;/b&gt;一个真实的后台找到并添加的主模块/子模块。

&lt;b&gt;模块+:&lt;/b&gt; 扩展添加其自己到功能菜单并作为已存在的后台模块。
&lt;b&gt;loadTCA:&lt;/b&gt; 扩展包含一个模块，叫作t3lib_div::loadTCA 以用不定式载入表，这潜在地意味着系统变慢，因为一些完整的表的描述被包含。然而，此现象也有一个很好的解释的理由 ，或许扩展在尝试操作TCA-config 一个已存在的表以扩展它。
&lt;b&gt;TCA:&lt;/b&gt; 扩展包含一个表的配置，位于 $TCA.

&lt;b&gt;插件：&lt;/b&gt; 扩展添加一个前台插件到内容元素类型“插入插件”的插件列表中。

&lt;b&gt;插件/ST43:&lt;/b&gt; T插件的ypoScript 描述代码已添加到静态模板“Content (default)”，“Plugin” 及 “Plugin/ST43&quot;”已合起来使用。

&lt;b&gt;Page-TSconfig:&lt;/b&gt; 默认的Page-TSconfig 已添加。

&lt;b&gt;User-TSconfig:&lt;/b&gt; 默认的 User-TSconfig 已添加。

&lt;b&gt;TS/Setup:&lt;/b&gt;默认的 TypoScript 设置已添加。

&lt;b&gt;TS/Constants:&lt;/b&gt; 默认的 TypoScript 常数已添加。</label>
			<label index="emconf_conf.description">显示是否扩展具有一个更多层级配置的模板。</label>
			<label index="emconf_TSfiles.alttitle">静态TypoScript文件</label>
			<label index="emconf_TSfiles.description">显示哪个 TypoScript 静态文件将被介绍。</label>
			<label index="emconf_TSfiles.details">如果文件ext_typoscript_constants.txt 和/或 ext_typoscript_setup.txt 在扩展文件夹找到，they are included in the hierarchy of all TypoScript templates in TYPO3 right after the inclusion of other static templates.</label>
			<label index="emconf_locallang.alttitle">本地化文件</label>
			<label index="emconf_locallang.description">显示名为&quot;locallang.php&quot;的文件所在的扩展的文件夹（递归搜索）。该文件通常被用来介绍系统中应用的语言的 $LOCAL_LANG 及标签。</label>
			<label index="emconf_moduleNames.alttitle">后台模块名称</label>
			<label index="emconf_moduleNames.description">显示在扩展中找到的模块名称。</label>
			<label index="emconf_classNames.alttitle">PHP类名称</label>
			<label index="emconf_classNames.description">显示在.php和.inc文件中找到的ＰＨＰ类。</label>
			<label index="emconf_errors.alttitle">错误</label>
			<label index="emconf_errors.description">显示发现的任何扩展的错误。</label>
			<label index="emconf_NSerrors.alttitle">名称区错误</label>
			<label index="emconf_NSerrors.description">一些命名适用于扩展，这显示任何找到的错误。</label>
			<label index="emconf_NSerrors.details">The naming convensions are defined in the &quot;Inside TYPO3&quot; document。要使命名尽可能地简单，试试不使用您的扩展关键字的下划线。</label>
		</languageKey>
	</data>
	<orig_hash type="array">
		<languageKey index="ch" type="array">
			<label index=".alttitle" type="integer">217593800</label>
			<label index=".description" type="integer">212219576</label>
			<label index="loaded.alttitle" type="integer">240199548</label>
			<label index="avail.alttitle" type="integer">251693128</label>
			<label index="import.alttitle" type="integer">65383042</label>
			<label index="import_ter.alttitle" type="integer">137151967</label>
			<label index="info.alttitle" type="integer">195885354</label>
			<label index="backup_delete.alttitle" type="integer">213063528</label>
			<label index="upload.alttitle" type="integer">217213386</label>
			<label index="editfiles.alttitle" type="integer">167010666</label>
			<label index="settings.alttitle" type="integer">49620262</label>
			<label index="emconf_category.alttitle" type="integer">61717939</label>
			<label index="emconf_dependencies.alttitle" type="integer">6158334</label>
			<label index="emconf_conflicts.alttitle" type="integer">174778315</label>
			<label index="emconf_priority.alttitle" type="integer">208790249</label>
			<label index="emconf_module.alttitle" type="integer">222311525</label>
			<label index="emconf_state.alttitle" type="integer">8968835</label>
			<label index="emconf_internal.alttitle" type="integer">252258090</label>
			<label index="emconf_clearCacheOnLoad.alttitle" type="integer">26668595</label>
			<label index="emconf_modify_tables.alttitle" type="integer">211801845</label>
			<label index="emconf_private.alttitle" type="integer">75468930</label>
			<label index="emconf_download_password.alttitle" type="integer">102196861</label>
			<label index="emconf_type.alttitle" type="integer">121209022</label>
			<label index="emconf_doubleInstall.alttitle" type="integer">262159324</label>
			<label index="emconf_rootfiles.alttitle" type="integer">234183730</label>
			<label index="emconf_dbReq.alttitle" type="integer">28332369</label>
			<label index="emconf_dbStatus.alttitle" type="integer">204171626</label>
			<label index="emconf_flags.alttitle" type="integer">82475009</label>
			<label index="emconf_TSfiles.alttitle" type="integer">43118947</label>
			<label index="emconf_locallang.alttitle" type="integer">182381040</label>
			<label index="emconf_moduleNames.alttitle" type="integer">70637876</label>
			<label index="emconf_classNames.alttitle" type="integer">155053783</label>
			<label index="emconf_errors.alttitle" type="integer">99552371</label>
			<label index="emconf_errors.description" type="integer">57596160</label>
			<label index="emconf_NSerrors.alttitle" type="integer">190879862</label>
			<label index="emconf_NSerrors.description" type="integer">168628900</label>
			<label index="emconf_dbReq.description" type="integer">93463627</label>
			<label index="emconf_conf.description" type="integer">49196456</label>
			<label index="emconf_TSfiles.description" type="integer">196469558</label>
			<label index="emconf_locallang.description" type="integer">112585123</label>
			<label index="emconf_moduleNames.description" type="integer">24342148</label>
			<label index="emconf_classNames.description" type="integer">83027952</label>
			<label index="emconf_TSfiles.details" type="integer">103067229</label>
			<label index="emconf_NSerrors.details" type="integer">76599956</label>
			<label index="loaded.image_descr" type="integer">182084221</label>
			<label index="info.description" type="integer">59055841</label>
			<label index="backup_delete.description" type="integer">229640855</label>
			<label index="backup_delete.image_descr" type="integer">167423664</label>
			<label index="editfiles.description" type="integer">223875344</label>
			<label index="editfiles.details" type="integer">178826894</label>
			<label index="editfiles.image_descr" type="integer">145835212</label>
			<label index="settings.details" type="integer">33394605</label>
			<label index="settings.image_descr" type="integer">81559812</label>
			<label index="loaded.description" type="integer">171468961</label>
			<label index="loaded.details" type="integer">96891976</label>
			<label index="avail.image_descr" type="integer">37993915</label>
			<label index="avail.description" type="integer">2924649</label>
			<label index="avail.details" type="integer">199115825</label>
			<label index="emconf_dbStatus.description" type="integer">166393559</label>
			<label index="emconf_flags.description" type="integer">42715313</label>
			<label index="emconf_flags.details" type="integer">209778452</label>
			<label index="emconf_doubleInstall.description" type="integer">60133779</label>
			<label index="emconf_doubleInstall.details" type="integer">201896892</label>
			<label index="emconf_rootfiles.description" type="integer">157844662</label>
			<label index="emconf_dbReq.details" type="integer">199359275</label>
			<label index="emconf_download_password.description" type="integer">120757501</label>
			<label index="emconf_type.description" type="integer">113056504</label>
			<label index="upload.description" type="integer">174044654</label>
			<label index="emconf_category.description" type="integer">204987594</label>
			<label index="emconf_category.details" type="integer">78942816</label>
			<label index="emconf_state.description" type="integer">48322308</label>
			<label index="emconf_state.details" type="integer">80752734</label>
			<label index=".details" type="integer">130449459</label>
			<label index="import.description" type="integer">195708810</label>
			<label index="import.details" type="integer">229384067</label>
			<label index="import.image_descr" type="integer">82735007</label>
			<label index="emconf_dependencies.description" type="integer">262753637</label>
			<label index="emconf_dependencies.details" type="integer">209360491</label>
			<label index="emconf_conflicts.description" type="integer">14159431</label>
			<label index="emconf_priority.description" type="integer">261230598</label>
			<label index="emconf_module.description" type="integer">131352939</label>
			<label index="emconf_module.details" type="integer">16797237</label>
			<label index="emconf_internal.description" type="integer">130243565</label>
			<label index="emconf_internal.details" type="integer">150689078</label>
			<label index="emconf_shy.alttitle" type="integer">217108965</label>
			<label index="emconf_shy.description" type="integer">196807582</label>
			<label index="emconf_clearCacheOnLoad.description" type="integer">149991239</label>
			<label index="emconf_modify_tables.description" type="integer">225814359</label>
			<label index="emconf_modify_tables.details" type="integer">250561664</label>
			<label index="emconf_private.description" type="integer">8590515</label>
			<label index="emconf_download_password.details" type="integer">92160698</label>
			<label index="upload.details" type="integer">168581871</label>
			<label index="upload.image_descr" type="integer">202956590</label>
			<label index="settings.description" type="integer">93469888</label>
			<label index="emconf_private.details" type="integer">183041250</label>
			<label index="import_ter.description" type="integer">241131724</label>
			<label index="import_ter.details" type="integer">69101028</label>
			<label index="import_ter.image_descr" type="integer">118689817</label>
			<label index="emconf_dbStatus.details" type="integer">198198907</label>
			<label index="makenew.image_descr" type="integer">81871110</label>
			<label index="info.image_descr" type="integer">228782153</label>
			<label index="makenew.alttitle" type="integer">71667781</label>
			<label index="info.details" type="integer">181502990</label>
			<label index="makenew.description" type="integer">137817259</label>
			<label index="makenew.details" type="integer">255978736</label>
			<label index="emconf_shy.details" type="integer">15892463</label>
			<label index="emconf_type.details" type="integer">153278607</label>
		</languageKey>
	</orig_hash>
	<orig_text type="array">
		<languageKey index="ch" type="array">
			<label index=".alttitle">Tools &gt; Extension Manager (EM)</label>
			<label index=".description">The Extension Manager controls import, installation and upgrading of Extensions in TYPO3.</label>
			<label index="loaded.alttitle">Loaded Extensions</label>
			<label index="avail.alttitle">Available Extensions</label>
			<label index="import.alttitle">Importing Extensions</label>
			<label index="import_ter.alttitle">Extensions in TER</label>
			<label index="info.alttitle">Extension Details</label>
			<label index="backup_delete.alttitle">Backup Extension as a file</label>
			<label index="upload.alttitle">Upload an Extension to the repository (TER)</label>
			<label index="editfiles.alttitle">Editing scripts in an extension</label>
			<label index="settings.alttitle">Extension Manager Settings</label>
			<label index="emconf_category.alttitle">Category</label>
			<label index="emconf_dependencies.alttitle">Dependencies of other extensions?</label>
			<label index="emconf_conflicts.alttitle">Conflicts with other extensions?</label>
			<label index="emconf_priority.alttitle">Requested Loading priority</label>
			<label index="emconf_module.alttitle">Backend modules included</label>
			<label index="emconf_state.alttitle">Development state</label>
			<label index="emconf_internal.alttitle">Internally supported in core</label>
			<label index="emconf_clearCacheOnLoad.alttitle">Clear cache when installed</label>
			<label index="emconf_modify_tables.alttitle">Existing tables modified</label>
			<label index="emconf_private.alttitle">Private</label>
			<label index="emconf_download_password.alttitle">Download password</label>
			<label index="emconf_type.alttitle">Installation type</label>
			<label index="emconf_doubleInstall.alttitle">Installed twice or more?</label>
			<label index="emconf_rootfiles.alttitle">Root files</label>
			<label index="emconf_dbReq.alttitle">Database requirements</label>
			<label index="emconf_dbStatus.alttitle">Database requirements status</label>
			<label index="emconf_flags.alttitle">Flags</label>
			<label index="emconf_TSfiles.alttitle">Static TypoScript files</label>
			<label index="emconf_locallang.alttitle">locallang-files</label>
			<label index="emconf_moduleNames.alttitle">Backend Module names</label>
			<label index="emconf_classNames.alttitle">PHP Class names</label>
			<label index="emconf_errors.alttitle">Errors</label>
			<label index="emconf_errors.description">Displays if any errors with the extension were discovered.</label>
			<label index="emconf_NSerrors.alttitle">Namespace errors</label>
			<label index="emconf_NSerrors.description">Certain naming convensions apply to extensions. This displays any violations found.</label>
			<label index="emconf_dbReq.description">Shows you the requirements to the database tables and fields, if any.</label>
			<label index="emconf_conf.description">Shows if the extension has a template for further lowlevel configuration.</label>
			<label index="emconf_TSfiles.description">Shows which TypoScript static files may be present</label>
			<label index="emconf_locallang.description">Shows which files named &quot;locallang.php&quot; are present in the extension folder (recursive search). Such files are usually used to present an array $LOCAL_LANG with labels for the application in the system languages.</label>
			<label index="emconf_moduleNames.description">Shows which module names were found inside the extension.</label>
			<label index="emconf_classNames.description">Shows which PHP-classes were found in .php and .inc files.</label>
			<label index="emconf_TSfiles.details">If the files ext_typoscript_constants.txt and/or ext_typoscript_setup.txt is found in the extension folder they are included in the hierarchy of all TypoScript templates in TYPO3 right after the inclusion of other static templates.</label>
			<label index="emconf_NSerrors.details">The naming convensions are defined in the &quot;Inside TYPO3&quot; document. To make naming as simple as possible, try to avoid underscores in your extension keys.</label>
			<label index="loaded.image_descr">The list of loaded extensions shown in the loading order.</label>
			<label index="info.description">Shows details about the extension.</label>
			<label index="backup_delete.description">Click the &quot;Download&quot; link here and you will download the extension as a file containing a serialized PHP array, a hash and everything possibly compressed if the server supports it. Save the file with a filename ending on &quot;t3x&quot;.</label>
			<label index="backup_delete.image_descr">&quot;Backup&quot; of extensions - also very useful for exchange of extensions between members of a workgroup.</label>
			<label index="editfiles.description">The Extension Manager can be used for editing scripts in extensions. This feature is mostly for emergencies since a webbrowser is not the ideal tool for programming.</label>
			<label index="editfiles.details">&lt;b&gt;Notice:&lt;/b&gt;
Before editing of extension scripts can be performed you have to disable the configuration option &quot;TYPO3_CONF_VARS[EXT][noEdit]&quot; in &quot;localconf.php&quot;.</label>
			<label index="editfiles.image_descr">Some file types - like PHP scripts - can be edited by a textarea field inside the Extension Manager.</label>
			<label index="settings.details">&lt;b&gt;Notice:&lt;/b&gt;
This information is not very well protected! It is send and stored in clear-text!</label>
			<label index="settings.image_descr">Settings for TER connections.</label>
			<label index="loaded.description">&quot;Loaded extensions&quot; are currently running on the system. This list shows you which extensions are loaded and in which order.
&quot;Shy&quot; extensions are also loaded but &quot;hidden&quot; in this list because they are system related and generally you should just leave them alone unless you know what you are doing.</label>
			<label index="loaded.details">The extensions in this list are shown in the order they are found in $TYPO3_CONF_VARS[EXT][extList].
To de-install an extension you simply click the green &quot;-&quot; icon. If there are no dependencies requiring the extension it will be removed from the list of installed extensions.
The &quot;Rq&quot; extensions in the loaded extensions list are &quot;required extensions&quot;. These are related so deeply to the system that you cannot disable them from the Extension Manager.</label>
			<label index="avail.image_descr">The list of available extension on the server. The list is compiled from extensions found in the &quot;local&quot;, &quot;global&quot; and &quot;system&quot; extension folders.
If you click the install icon (&quot;+&quot;) of an extension you might end in a dialog like this. In this case a new database table is required. The Extension Manager will automatically detect that it does not exist yet and suggest that you create it. The creation automatically takes place as well, simply by accepting the changes when pressing &quot;Make updates&quot;.</label>
			<label index="avail.description">Available extensions are extensions which are present in the extension folders. You can install any of the available extensions in this list. When you install an extension it will be loaded by TYPO3 from that moment.
In this list the extensions with dark background are installed (loaded) - the others just available (not loaded), ready to be installed on your request.</label>
			<label index="avail.details">You can install an extension by clicking the gray &quot;+&quot; icon in this list. If you want to de-install an extension you click the green &quot;-&quot; icon.
When you click the install button (&quot;+&quot;) you will most often end in a dialog where you have to confirm the creation of database tables and fields or maybe you will be asked to &quot;clear all cache&quot;. The Extension Manager automatically handles these requirements for you which makes it extremely easy to install new extensions.</label>
			<label index="emconf_dbStatus.description">Displays the current status of the database compared to the extension requirements.</label>
			<label index="emconf_flags.description">A list of special codes which tells you something about what parts of TYPO3 the extension touches.</label>
			<label index="emconf_flags.details">This is a list of the flags:

&lt;b&gt;Module:&lt;/b&gt; A true backend main/sub module is found to be added.

&lt;b&gt;Module+:&lt;/b&gt; The extension adds itself to the function menu of an existing backend module.

&lt;b&gt;loadTCA:&lt;/b&gt; The extension includes a function call to t3lib_div::loadTCA for loading a table. This potentially means that the system is slowed down, because the full table description of some table is always included. However there probably is a good reason for this to happen. Probably the extension tries to manipulate the TCA-config for an existing table in order to extend it.

&lt;b&gt;TCA:&lt;/b&gt; The extension contains configuration of a table in $TCA.

&lt;b&gt;Plugin:&lt;/b&gt; The extension adds a frontend plugin to the plugin list in Content Element type &quot;Insert Plugin&quot;.

&lt;b&gt;Plugin/ST43:&lt;/b&gt; TypoScript rendering code for the plugin is added to the static template &quot;Content (default)&quot;. &quot;Plugin&quot; and &quot;Plugin/ST43&quot; are commonly used together.

&lt;b&gt;Page-TSconfig:&lt;/b&gt; Default Page-TSconfig is added.

&lt;b&gt;User-TSconfig:&lt;/b&gt; Default User-TSconfig is added.

&lt;b&gt;TS/Setup:&lt;/b&gt; Default TypoScript Setup is added.

&lt;b&gt;TS/Constants:&lt;/b&gt; Default TypoScript Constants is added.</label>
			<label index="emconf_doubleInstall.description">Tells you if the extensions is installed in more than one of the System, Global or Local locations.</label>
			<label index="emconf_doubleInstall.details">Because an extension can reside at three locations, System, Global and Local, this indicates if the extension is found in other locations than the current. In that case you should be aware which one of the extensions is loaded!</label>
			<label index="emconf_rootfiles.description">List of the files in the extension folder. Does not list files in subfolders.</label>
			<label index="emconf_dbReq.details">This will read from the files ext_tables.sql and ext_tables_static+adt.sql and show you which tables, fields and static tables are required with this extension.</label>
			<label index="emconf_download_password.description">Additional password required for download of private extensions.</label>
			<label index="emconf_type.description">The type of the installation</label>
			<label index="upload.description">Here you can upload an extension to TER. In order to do so you must enter your TYPO3.org username and password in the form. In addition each extension has an upload password you need to add as well. You should also make sure you registered / own the extension key!</label>
			<label index="emconf_category.description">Which category the extension belongs to.</label>
			<label index="emconf_category.details">&lt;b&gt;be:&lt;/b&gt; Backend (Generally backend oriented, but not a module)

&lt;b&gt;module:&lt;/b&gt; Backend modules (When something is a module or connects with one)

&lt;b&gt;fe:&lt;/b&gt; Frontend (Generally frontend oriented, but not a &quot;true&quot; plugin)

&lt;b&gt;plugin:&lt;/b&gt; Frontend plugins (Plugins inserted as a &quot;Insert Plugin&quot; content element)

&lt;b&gt;misc:&lt;/b&gt; Miscellaneous stuff (Where not easily placed elsewhere)

&lt;b&gt;services:&lt;/b&gt; Contains TYPO3 services.

&lt;b&gt;templates:&lt;/b&gt; Contains website templates

&lt;b&gt;doc:&lt;/b&gt; Documentation (Eg. tutorials, FAQ's etc.)

&lt;b&gt;example:&lt;/b&gt; Example extension (Which serves as examples etc.)</label>
			<label index="emconf_state.description">Which development state the extension is in.</label>
			<label index="emconf_state.details">&lt;b&gt;alpha&lt;/b&gt;
Very initial development. May do nothing at all.

&lt;b&gt;beta&lt;/b&gt;
Under current development. Should work partly but is not finished yet.

&lt;b&gt;stable&lt;/b&gt;
Stable and used in production.

&lt;b&gt;experimental&lt;/b&gt;
Nobody knows if this is going anywhere yet... Maybe still just an idea.

&lt;b&gt;test&lt;/b&gt;
Test extension, demonstrates concepts etc.</label>
			<label index=".details">TYPO3 can be extended in nearly any direction without loosing backwards compatibility. The Extension API provides a powerful framework for easily adding, removing, installing and developing such extensions to TYPO3. This is in particular powered by the Extension Manager (EM) inside TYPO3.

&quot;Extensions&quot; is a term in TYPO3 which covers two other terms, plugins and modules.

A plugin is something that plays a role on the website itself. For example a board, guestbook, shop etc. It is normally enclosed in a PHP class and invoked through a USER or USER_INT cObject from TypoScript. A plugin is an extension in the frontend.

A module is a backend application which has it's own position in the administration menu. It requires backend login and works inside the framework of the backend. We might also call something a module if it exploits any connectivity of an existing module, that is if it simply adds itself to the function menu of existing modules. A module is an extension in the backend.</label>
			<label index="import.description">This is the process of bringing the files of an extension to the servers filesystem. You can do this either by importing from a repository at a URL (usually from TER; TYPO3 Extension Repository at typo3.org) or by uploading a &quot;t3x&quot; file which someone else created from the Extension Manager on another server.</label>
			<label index="import.details">&lt;b&gt;Import from TER&lt;/b&gt;
To connect to the TER you simply click the button &quot;Connect to online repository&quot;. This will request the URL shown in the text above the button and the URL should return a list of available extension you can import.
If you know what you are looking for then enter a search word in the look-up box. In particular this helps you to look up a specific extension key. The connection to TER will be much faster if you use this since less data is sent over the wire!

&lt;b&gt;Upload from file&lt;/b&gt;
For private projects the exchange of extensions is easily done by sending &quot;t3x&quot; files from system to system. In one TYPO3 installation you simply go to the menu &quot;Backup/Delete&quot; of an extension and download a &quot;Backup&quot; of the extension. The fileformat is a serialized PHP array, compressed if possible. This file can then be uploaded in the Extension Manager of another TYPO3 system where you want to import it.</label>
			<label index="import.image_descr">The &quot;Import&quot; screen. Before you connect to the online repository you might like to configure typo3.org username and password since that will be used to also select &quot;Member&quot; extensions in TER, if any. You can also enable &quot;Get own/member/selected extensions only&quot; if you want to limit the list further.</label>
			<label index="emconf_dependencies.description">This is a list of other extension keys which this extension depends on being loaded BEFORE it self.</label>
			<label index="emconf_dependencies.details">The EM will manage that dependency while writing the extension list  to localconf.php. You cannot install an extension unless its dependencies has been installed already.</label>
			<label index="emconf_conflicts.description">List of extension keys of extensions with which this extension does not work (and so cannot be enabled before those other extensions are un-installed)</label>
			<label index="emconf_priority.description">This tells the EM to try to put the extensions as the very first in the list. Default is last.</label>
			<label index="emconf_module.description">If any subfolders to an extension contains backend modules, those foldernames should be listed here.</label>
			<label index="emconf_module.details">It allows the EM to know about the existence of the module, which is important because the EM has to update the conf.php file of the module in order to set the correct TYPO3_MOD_PATH  constant.</label>
			<label index="emconf_internal.description">This flag indicates that the core source code is specifically aware of the extension.</label>
			<label index="emconf_internal.details">In other words this flag should convey the message that &quot;this extension could not be written without some core source code modifications&quot;.

An extension is not internal just because it uses TYPO3 general classes eg. those from t3lib/.
True non-internal extensions are characterized by the fact that they could be written without making core source code changes, but relies only on existing classes  in TYPO3 and/or other extensions, plus its own scripts in the extension folder.</label>
			<label index="emconf_shy.alttitle">Shy</label>
			<label index="emconf_shy.description">If set, the extension will normally be hidden in the EM because it might be a default extension or otherwise something which is not so important.</label>
			<label index="emconf_clearCacheOnLoad.description">If set, the EM will request the cache to be cleared when this extension is installed.</label>
			<label index="emconf_modify_tables.description">List of tablenames which are only modified - not fully created - by this extension.</label>
			<label index="emconf_modify_tables.details">Tables from this list found in the ext_tables.sql file of the extension</label>
			<label index="emconf_private.description">If set, this version is not shown in the public list in the online repository.</label>
			<label index="emconf_download_password.details">Anybody who knows the &quot;special key&quot; assigned to the private upload will be able to import it. Specifying an import password allows you to give away the download key for private uploads and also require a password given in addition. The password can be changed later on.</label>
			<label index="upload.details">&lt;b&gt;Changelog&lt;/b&gt;
In the changelog field you enter the changes made or the reason for the upload. This will be displayed in the list of new extensions.

&lt;b&gt;Version numbers&lt;/b&gt;
Select a method for incrementation of the version number. For new &quot;versions&quot; of your extension you should select &quot;sub&quot; or &quot;main&quot; which will display your extension in the list of new extensions. For maintenance uploads you select &quot;dev&quot;.</label>
			<label index="upload.image_descr">The upload form for extensions. The extension is submitted to the selected repository, usually TYPO3.org (default).</label>
			<label index="settings.description">Enter settings for the Extension Manager. The username and password is for connections to the repository (usually TYPO3.org) and the upload password is that you would normally use for upload of your extensions.</label>
			<label index="emconf_private.details">&quot;Private&quot; uploads requires you to manually enter a special key (which will be shown to you after an upload has been completed) to be able to import and view details for the uploaded extension.
This is nice when you are working on something internally which you do not want others to look at.
You can set and clear the private flag every time you upload your extension.</label>
			<label index="import_ter.description">Extensions in this list are online for immediate download from the TYPO3 Extension Repository (TER).
Extensions with dark background are those already on your server - the others must be imported from the repository to your server before you can use them.
If you want to use an extension from the repository, you should simply click the &quot;import&quot; button with the red arrow left to the extension.</label>
			<label index="import_ter.details">&lt;b&gt;Import Extensions&lt;/b&gt;
If an extension does not yet exist on your server you will see the icon with the red arrow next to that extension. A single click and the extension will be downloaded and the files extracted on your server. The download directory is seen if you move the mouse over the icon (in the tool-tip text).

&lt;b&gt;Update Extensions&lt;/b&gt;
You can update extensions that are always on your system by clicking the icon with the green arrows. The update icon will appear if the &quot;minor&quot; version number (middle digit) has been incremented. This means that extensions updated on the dev-version number (the third digit) will not be shown as &quot;ready for update&quot;. (You can configure TYPO3 to do that though!).

&lt;b&gt;Seeing details about an extension in TER&lt;/b&gt;
You can also click the title of an extension to see details about it. That will also allow you to perform a more detailed update operation where you can select version number and download location (local/global/system).
You can also ask to have the most recent translations downloaded.</label>
			<label index="import_ter.image_descr">List of extensions from TER. The red arrow icon is the &quot;Import&quot; link (for new extensions), the green arrow icon is the &quot;Update&quot; link (for an extension that is already on your server). If an extension is already available in the most recent version you will not see any icon at all to the left of the extension.
If you clicked the title of an extension you will request the repository for details about the extension. This also allows you to select a specific version for import. You can also select the install location (global/local) and you can request to have the most recent translations merged into the extension upon retrieval.</label>
			<label index="emconf_dbStatus.details">If the extension is loaded which will display and error message if some tables or fields are not present in the database as they should be!</label>
			<label index="makenew.image_descr">When the &quot;Extension Repository Kickstarter&quot; is enabled it adds itself in the menu of the Extension Manager. From here you will be able to start your new extensions. Before you do so you should register an extension key and enter a title and description as base data. From that point it is just clicking the &quot;+&quot; icons to add the various types of functionality you want. Finally you click &quot;View result&quot; to write the extension to the server.</label>
			<label index="info.image_descr">The details view of an extension displays live statistics from analysis as well as static data from the &quot;ext_emconf.php&quot; file.</label>
			<label index="makenew.alttitle">Kickstarting new extensions</label>
			<label index="info.details">In this view some of the details are simply a display of the information from the &quot;ext_emconf.php&quot; file in the extension. The &quot;emconf&quot; file contains meta data for the Extension Manager.

The Extension Manager will also go a bit further and perform some analysis of the scripts in the extension. The list will include the findings of this analysis and if any errors were found they will be displayed. Usually these errors will not prevent the extension from working but more likely point out some theoretical problems that the extension developer should address.</label>
			<label index="makenew.description">The &quot;Kickstarter&quot; is an application which allows you to start up new extension work very quickly. Through an interface you can create a basic framework for your extension where all the boring stuff is configured from the beginning and you can concentrate directly on coding your application.</label>
			<label index="makenew.details">The Extension Repository Kickstarter is a separate extension, &quot;extrep_wizard&quot;. Please see more information about the kickstarter otherwise.

&lt;b&gt;Notice:&lt;/b&gt;
The Kickstarter is NOT an editor! When a new extension is started you cannot - as a rule of thumb - go back an edit it with the kickstarter! It will just overwrite any custom changes you did in the meantime!</label>
			<label index="emconf_shy.details">Use this flag if an extension is of &quot;rare interest&quot; (which is not the same as un-important - just an extension not sought for very often...)
It does not affect whether or not it's enabled. Only display in EM.
Normally &quot;shy&quot; is set for all extensions loaded by default according to TYPO3_CONF_VARS.</label>
			<label index="emconf_type.details">The files for an extension are located in a folder named by the extension key. The location of this folder can be either inside typo3conf/ext/,  typo3/ext/ or typo3/sysext/. The extension must be programmed so that it automatically detects where it is located and can work from all three locations.

&lt;b&gt;Local location &quot;typo3conf/ext/&quot;:&lt;/b&gt; This is where to put extensions which are local for a particular TYPO3 installation. The typo3conf/ directory is always local, containing local configuration (eg. localconf.php), local modules etc. If you put an extension here it will be available for this TYPO3 installation only. This is a &quot;per-database&quot; way to install an extension.

&lt;b&gt;Global location &quot;typo3/ext/&quot;:&lt;/b&gt; This is where to put extensions which are global for the TYPO3 source code on the web server. These extensions will be available for any TYPO3 installation sharing the source code.
When you upgrade your TYPO3 source code you probably want to copy the typo3/ext/ directory from the former source to the new source, overriding the default directory. In this way all global extension you use will be installed inside the new sourcecode. After that you can always enter TYPO3 and upgrade the versions if needed.
This is a &quot;per-server&quot; way to install an extension.

&lt;b&gt;System location &quot;typo3/sysext/&quot;:&lt;/b&gt; This is system default extensions which cannot and should not be updated by the EM. They are distributed with the TYPO3 core.


&lt;b&gt;Loading precedence&lt;/b&gt;
Local extensions take precedence which means that if an extension exists both in typo3conf/ext/ and typo3/ext/ the one in typo3conf/ext/ is loaded. Likewise global extension takes predence over system extensions. This means that extensions are loaded in the order of priority local-global-system.
In effect you can therefore have, say, a &quot;stable&quot; version of an extension installed in the global dir (typo3/ext/) which is used by all your projects on a server sharing source code, but on a single experimental project you can import the same extension in a newer &quot;experimental&quot; version and for that particular project the locally available extension will be used instead.</label>
		</languageKey>
	</orig_text>
</T3locallangExt>