<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<T3locallangExt>
	<data type="array">
		<languageKey index="ch" type="array">
			<label index=".alttitle">导入/导出</label>
			<label index=".description">TYPO3数据的本地导入/导出模块。能导出单一记录，表格内容，单一页面或页面树的整个分枝。包括附加的媒体文件如图片和记录之间相关的受保护的。导出仅导出为TYPO3的特殊格式，或者是二进制格式（。T3D）或XML格式。这些格式用来在TYPO3系统之间进行交换。</label>
			<label index=".image_descr">导出一个页面配置的预览的例子。注意页面上有多少记录被包括，及有多少附加的东西被找到及包括（屏幕底部）。</label>
			<label index="export.alttitle">从TYPO3中导出记录</label>
			<label index="export.description">要导出TYPO3的T3D/XML文件，您要点击页面树内的任何记录的图标或页面（包括根页面！），选择“更多选项”（要求扩展 &quot;extra_page_cm_options&quot; 已安装），再选择“导出到.t3d”。这将出现导出界面（您可为您的导出会话配置选项）。</label>
			<label index="export.details">这里有几个您可从TYPO3中导出数据的方法：--导出一个单一页面或页面树的分枝（使用页面图标相关菜单）
--从任一页面导出一个单一记录（使用页面图标相关菜单）
--从一个特殊页面的特殊的表中导出所有记录（使用网站&gt;模块列表）
--导出从剪切板中任意选择的记录（使用网站&gt;模块列表）
导出的格式遵守所有TYPO3的方式for relations between the records in the export file。但您可配置这些关系如何维持，至少到一个程度。有时候您可能需要包含涉及到的记录，另外一些时候您要保持原始的计划。这依靠于您的导出的目标。
不管您的导出的配置如何，您总可在导出模块页面底部查看一个完全的所有选择的记录及其内部的关系的预览的反映。
&lt;b&gt;错误信息：&lt;/b&gt;如果有任何的错误信息，记住在导出之前参考消息标签！</label>
			<label index="export.image_descr">要导出一个页面或记录，只要简单地从相关菜单中点击图标并选择“导出”。
在网站&gt;模块列表中您也可通过点击表的标题从一个表中导出所有记录，下一步到CSV导出，您将发现该表格的导出到T3D的按钮。
您可通过选择菜单中的“导出”来导出剪切板中的内容。</label>
			<label index="pageTreeCfg.alttitle">配置页面树导出</label>
			<label index="pageTreeCfg.description">在这里您可配置页面树的一个页面或分枝如何被导出。使用选择框，您可设置导出要包含的子页面的层级数。默认情况下所有属于一个页面的记录都包含在内。</label>
			<label index="pageTreeDisplay.alttitle">页面树</label>
			<label index="pageTreeDisplay.description">基于一个页面树的导出层级的选择，这将显示要导出的结构。由排除选项控制的特定的排除项的页面不会显示。</label>
			<label index="pageTreeMode.alttitle">层</label>
			<label index="pageTreeMode.description">在这您可选择从当前开始点开始导出的页面的深度。</label>
			<label index="pageTreeMode.details">如果您选择“展开树”，它将基于当前页面树展开的层级的导出。另一个特殊的选项是“此页面上的表格”将不包括在页面记录本身，但仅包括页面来自表中的内容，依靠于表的配置流程。</label>
			<label index="pageTreeRecordLimit.alttitle">包含表格</label>
			<label index="pageTreeRecordLimit.description">当您按默认的导出一个页面所有记录。通过此选择器您可挑选哪个表格要包含if there are certain records you are not interested in seeing included.</label>
			<label index="pageTreeRecordLimit.details">在“记录最大数”选择框，您可设置从一个单一表中选择多少个记录。如果您在一个表中有大量的记录，这是一个很好的控制方法。</label>
			<label index="singleRecord.alttitle">仅导出记录</label>
			<label index="singleRecord.description">此总览告诉您哪些独立的记录已被独立选择以导出。</label>
			<label index="singleRecord.image_descr">导出大量记录的方法，像这个就使用了剪切板，如下面所示。</label>
			<label index="tableList.alttitle">表格导出</label>
			<label index="tableList.description">从一个特殊的表中导出一个页面所有的记录。这可从网站&gt;模块列表中配置，在那您可选择table-only view 并点击页面顶部的按钮。</label>
			<label index="tableList.details">提示：您可选择许多表格列表，通过简单地保存每个选择作为框架并最终载入/合并所有的选择。</label>
			<label index="tableList.image_descr">在这里，两个来自不同页面的表格被选择。先选择一个，作为预设保存它，再选择另一个并合并到保存的预设中。
在这里您看到如何使用网站&gt;模块列表以从一个页面的表格中导出所有记录。</label>
			<label index="tableListMaxNumber.alttitle">导出最大数量</label>
			<label index="tableListMaxNumber.description">运行中断能确保大量的记录不充满整个屏幕。默认是100，但您可更改为任何您想要的数字。</label>
			<label index="inclRelations.alttitle">包含相关的</label>
			<label index="inclRelations.description">在主要的导出配置界面配置表格，该表格为您希望包含记录的表格的相关的表格。</label>
			<label index="inclRelations.details">背景：当您在TYPO3中导出一个记录时，它可能包含系统中相关的其它记录。您要告诉导出界面如何处理这些相关的记录。基本上有三个设定：
--如果相关的记录在所有导出配置中找到，就没有问题了：相关的记录会在记录导入时自动标上新的ID。
--如果有关的记录不包含关系，将被丢失（在预览中显示错误信息），除非您（A）此选择框中选择与该记录相关的所有表格或（B）如果您设置表格为静态表格（in which case the relation is untouched and imported as-is - but which will of course break if no record with that UID is found in the import system)
&lt;b&gt;Soft References:&lt;/b&gt;Soft references是当一个记录包含外部文件或记录的指示器，但在此区域中未进行正式的相关配置。一个例子是，当一个内容元素包含&quot;&amp;lt;link 123&amp;gt;&quot; 标签（描绘到页面123的链接）。这没有作为正式的相关记录进行设置，但作为 &quot;soft reference&quot;找到了。同样地&amp;lt;img&amp;gt; 标签及图片如&quot;fileadmin/&quot;。
默认情况下soft references指出记录或文件将作为常规的相关；或者包含引用的项目或显示错误。然而，您可选择排除的个别的soft references操作或 设置值为 &quot;editable&quot; upon import.这在导出预览中可通过选择框来做到。</label>
			<label index="inclRelations.image_descr">此例子显示了涉及的示例树；a)一个图片附加到内容元素， b) 一个与前台用户组UID有关的，c) 在一个记录正文区中发现的相关的，这里是指向页面UID=1的链接标签。
注意，在前一图片中，与前台用户组相关的已丢失。该问题已在此屏幕截图中修正，fe_group 表已在表的列表中被选择。结果是前台用户组已包含作为外部输出的页面树记录。如果您希望保持关联，但不包含用户组，您要设置&quot;fe_groups&quot;为一替代的静态表。查看下面获得细节信息。
此例子显示了一个找到有许多关联的TypoScript模板记录。第一个是个电子信箱地址。这里配置为可编辑。这意味着在这之上的用户有机会在导入实际执行之前编辑其值。这对作为模板导入的文件非常有用。另一个例子包含了一个我们不希望导入的PHP脚本，因此，我们选择排除关联的选项。</label>
			<label index="staticRelations.alttitle">设置静态表格</label>
			<label index="staticRelations.description">选择哪个表格附加到静态TYPO3表格中以保持未改变的关系。配置表格的“包含相关的”的优先权。</label>
			<label index="staticRelations.details">默认情况下，所有到TYPO3静态表的关联都操持不受变动。当然，这些静态表也应该呈现在导入系统以让此工作正确。然而，可能有一种情况，即当您在两个系统之间移动信息时理论上没有静态表能保持关联不受改动。一个例子是&quot;sys_languages&quot;或TemplaVoila 数据结构/模板对象，当您自由地导入页面和内容元素时两个系统在那些表中都包含相同的设置。</label>
			<label index="staticRelations.image_descr">在此例子中您可看到有多少个指向系统语言记录的记录在导入时将丢失其关联，因为记录不包含在导入中。然而；在对象系统中，系统语言同样正确，并且因此您只希望一个关联的静态生成图。静态生成图可通过选择 &quot;sys_language&quot; 并作为静态模板（意味着关联保持它们的值）获得，并在导入到对象系统中有同样正确的值。（注：此段不好译）</label>
			<label index="excludedElements.alttitle">排除的元素</label>
			<label index="excludedElements.description">通过“排除”选择框，您可在导出中排除特殊的记录。这些作为排除的记录在此列表中。您也可清除排除的配置。</label>
			<label index="htmlCssResources.alttitle">从HTML和CSS文件中排除的资源</label>
			<label index="htmlCssResources.description">当一个HTML或CSS文件作为软件相关的文件找到并被解析为涉及到外部的媒体（如图片），并且如果找到任何文件的话，也会被导出。如果您不喜欢此操作，点击此按钮。</label>
			<label index="htmlCssResources.details">注意：在HTML或CSS文件中找到的资源不会进一步地去分析。举个例子，它意味着任何从HTML文件内部涉及到的CSS文件将不会被traversed ，但是CSS文件涉及到的TypoScript模板记录内部的设置或常数区将会被traversed。</label>
			<label index="htmlCssResources.image_descr">在此例子中您可看到一个soft关联已被发现指向了fileadmin/中一个HTML文件Since it was an HTML file it was parsed and further a number of files were found referenced inside it and now included with the export. This feature is specifically created to support export of template configurations where external HTML files play a role.</label>
			<label index="extensionDependencies.alttitle">扩展依靠</label>
			<label index="extensionDependencies.description">选择哪个扩展应该被安装在导入系统中以供您恰当地导出内容。例子中的&quot;templavoila&quot; 用于 templating, &quot;css_styled_content&quot; 用于template, &quot;tt_news&quot; 用于新的文档等等.</label>
			<label index="extensionDependencies.details">在导入过程中，警告将在从此未安装列表中所有选择的扩展中出现。</label>
			<label index="presets.alttitle">配置边框形式</label>
			<label index="presets.description">允许您保存导出设置以供以后使用。如果您有规则地导出相同的配置，这会很有用。</label>
			<label index="presets.details">在“选择预设”框中，您可选择载入任何以前保存的预设。如果您导出一个页面，预设列表将是那些根据开始页面ID找到的。对记录而言，任何预设都能载入。
要载入一个预设，在选择框中选择它并按“载入”。如果您按了“合并”以代替预设的设定，这将被合并到当前配置中。这在您选择许多个别的表格或记录是很有意义的。
要保存预设，只要在标题框输入一个标题并按“保存”。这将创建一个新预设。如果您在已选择一个已存在的预设时按保存，您将覆盖它。要删除旧的预设，只要选中它并按“删除”。
如果您希望共享您的预设给其它系统用户，选择框“公共”项。否则只供您个人使用。
在任务中心，您可看到您的预设的列表，并可直接跳转过去。</label>
			<label index="presets.image_descr">导出界面的预设的选择器。
预设来自计划任务。</label>
			<label index="metadata.alttitle">元数据设置</label>
			<label index="metadata.description">为导出设置元数据。如果您导出内容，强烈推荐您这么做，如一个模板分类的收集。</label>
			<label index="metadata.details">元数据将帮助您的导出文件的用户了解文件的内容以及他们在导入文件时应该注意的事情。
“标题”和“描述”将包含导出文件的基本信息。
“备注”区可用来添加细节信息，特别是必须条件和注意事项等。
缩略图区被用来添加缩略图（如果您希望您的导出文件有缩略图）。这在导出文件被用作页面模板（选择模板人能优先注意到缩略图）是很有用的。该格式将是一个WEB格式如JPG，GIF或PNG格式，并且尺寸必须符合最终显示尺寸的要求；因此不要上传较大图片。</label>
			<label index="fileFormat.alttitle">文件格式选项</label>
			<label index="fileFormat.description">您可将您的记录导出到TYPO3一个特殊的二进制格式（连续的PHP队列）“T3D”。做为选择，您也可选择一个空白文本的XML导出，这可用其它程序支持此格式。然而，XML计划是TYPO3的specific。</label>
			<label index="fileFormat.details">通常，您应该使用T3D格式，该格式更适合压缩。T3D压缩格式正常生成一个文件要约10分之一的XML格式生成时间 which is bloaded due to the plain-text nature of the format.
“包含的文件最大尺寸”项您可设置附加到记录上的文件的尺寸。如果您有一个很大的PDF文件或视频文件要附加到记录上并且您不想附加上（或想附加上）是很有用的。根据最大文件尺寸限制您可调整想要附加及不想要附加的文件。
输入一个文件名以保存，并直接将您的导出直接写成文件（按“保存到文件名”）以代替下载文件（按“下载导出”）。正确的文件扩展名会根据文件格式自动添加。文件保存于 &quot;fileadmin/&quot;内一个适当的文件挂接点。
这向您显示保存。
已存在的文件被覆盖。</label>
			<label index="import.alttitle">导入TYPO3记录</label>
			<label index="import.description">要导入TYPO3的T3D/XML文件到页面树，您可在页面树任何地方（包括根页面）点击页面，选择“更多选项”（要求扩展&quot;extra_page_cm_options&quot;已安装），再选择“从.T3D导入“。这将打开导入页面，在这您可选择导入的文件或上传新的文件。</label>
			<label index="import.details">&lt;b&gt;提示: 导入到系统文件夹&lt;/b&gt;
要确保在导入时没有记录丢失，您可在导入之前先在系统文件夹中创建文件夹以确保安全。在导入之后您可移动所有记录到最终位置。一个相关的设定的例子是如果您配置导出包含关联；在此情况下一些记录将跟随要导出的记录导出到页面树外。要确保这些额外的记录写入到数据库中，导入到一个系统文件夹是个好主意。
&lt;b&gt;错误信息：&lt;/b&gt; 记住在导入之前/之后参考信息标签（如果有错误信息的话）！</label>
			<label index="importFile.alttitle">选择要导入的文件</label>
			<label index="importFile.description">该文件显示从您的fileadmin/, fileadmin/export/ 及您的&quot;TEMP&quot; 文件夹(如果有的话)中扩展T3D或XML文件。</label>
			<label index="update.alttitle">更新代换插入</label>
			<label index="update.description">默认情况下导入操作在系统中插入新的记录。使用此选项将更新已存在的记录。</label>
			<label index="update.details">如果您希望“更新”处理正常工作，则有几个要求要注意。首要的事情是那些要更新的记录的UID与导出时的UID是相同的。Thus an update operation only makes real sense if the export and import systems are somehow related and the same UIDs can be expected in both ends。否则它将被丢失！
当您更新页面结构时，导入操作将自动尝试重新安排记录以让其出现在相同的层次及顺序（与导出文件相同）。该功能可通过检查“忽略与全局不同的PID”的选项以禁用。在任何情况下您可设置个别记录以忽略/考虑PID（通过预览中的选择框）。
在预览显示中您可选择个别记录在导入时是否被忽略或您是否希望它们作为新记录被创建（以代替更新）。
作为管理更新的帮助，预览显示将通知您已存在的该UID的元素的路径。使用此信息以检验您是否获得了您想要的！
&lt;b&gt;强制更改UID：&lt;/b&gt;
如果您想要更新系统并且导入所携带的一些元素are not mappable to a UID already  (ei. 不存在)，您可在预览显示中选择以在创建时强制更新。这是一件正常在数据库中创建UID时的异常情况，在您尝试“同步”另一个系统时该选项会让您有更多的认识。该选项会打乱中心数据库内部的结构，并且该特性仅管理员可用。</label>
			<label index="update.image_descr">在更新模式，您可为每个记录选择不同的设置。当已存在的记录与导入的记录之间存在区别时，您将看到它们之间的不同之处。</label>
			<label index="options.alttitle">导入选项</label>
			<label index="options.description">导入的不同的选项。</label>
			<label index="options.details">&lt;b&gt;不显示记录间的区别&lt;/b&gt;
当一个结构被导入时您将看到所有记录之间的区别，并且这将告诉您写入的内容是否与导入的数据匹配，有哪些更改。在许多情况下，内容&lt;i&gt;应该&lt;/i&gt;改变（如关联和涉及文件），因此如果您看到红色和绿色的值是没有错误的。基本上查看区别是一个您可用来查看导入是否成功的一个特性。It brings piece-of-mind to those who is enlightened to understand what it tells... :-)
绿色字符描述了实际写入的数据，而红色的描述了导入文件中最初的值，黑色描述了相同的数据。
&lt;b&gt;允许写入到禁止的扩展中(如. PHP 脚本), 如果有的话&lt;/b&gt;
同样地，这也是一个管理员可用的选项；允许PHP文件（如 TypoScript 模板中涉及到的）被写入到系统中。正常情况下，该选项因为安全因素被禁止。</label>
			<label index="options.image_descr">导入选项。
在这您被告之此PHP文件不能被允许---因为您未选择“Allow to write banned file extensions （如：PHP脚本）if any”选项。</label>
			<label index="action.alttitle">导入动作</label>
			<label index="action.description">按“预览”以查看导入的文件的内容或更新预览显示依照更改配置。
如果您希望执行真实的导入操作，按“导入”/“更新”。
在导入之前，请确定您更改了在预览数据中显示的任何可编辑的soft references 。</label>
			<label index="action.image_descr">一个导入之后结果显示的例子。当您能看到RTE附加上的图片（soft references）已被写入到新文件名，并且区别的显示告诉您名称已在文本内容主体中被更改。</label>
			<label index="enableLogging.alttitle">开启系统记录</label>
			<label index="enableLogging.description">如果您设置这个，系统后台记录将记录所有导入操作的执行。By default this is left out for the sake of clarity.</label>
			<label index="upload.alttitle">上传导入文件</label>
			<label index="upload.description">选择一个从您本地计算机导入的文件并在此上传。如果上传成功完成，您可立即看到其内容显示在预览上。</label>
			<label index="upload.details">注意服务器上PHP环境有一个常规的限制设置，即上传的文件尺寸小于2MB，以保证不出现问题。</label>
		</languageKey>
	</data>
	<orig_hash type="array">
		<languageKey index="ch" type="array">
			<label index=".alttitle" type="integer">260906242</label>
			<label index="export.alttitle" type="integer">9010103</label>
			<label index="pageTreeCfg.alttitle" type="integer">236227215</label>
			<label index="pageTreeDisplay.alttitle" type="integer">9880458</label>
			<label index="pageTreeMode.alttitle" type="integer">152759754</label>
			<label index="pageTreeRecordLimit.alttitle" type="integer">169123110</label>
			<label index="singleRecord.alttitle" type="integer">128794302</label>
			<label index="tableList.alttitle" type="integer">146883216</label>
			<label index="tableListMaxNumber.alttitle" type="integer">225797227</label>
			<label index="inclRelations.alttitle" type="integer">164484847</label>
			<label index="staticRelations.alttitle" type="integer">1210228</label>
			<label index="excludedElements.alttitle" type="integer">227920200</label>
			<label index="htmlCssResources.alttitle" type="integer">178718927</label>
			<label index="presets.alttitle" type="integer">204662048</label>
			<label index="metadata.alttitle" type="integer">266477806</label>
			<label index="fileFormat.alttitle" type="integer">54960098</label>
			<label index="import.alttitle" type="integer">32716924</label>
			<label index="importFile.alttitle" type="integer">36260242</label>
			<label index="update.alttitle" type="integer">56150550</label>
			<label index="options.alttitle" type="integer">55046973</label>
			<label index="action.alttitle" type="integer">185830356</label>
			<label index="enableLogging.alttitle" type="integer">110785878</label>
			<label index="upload.alttitle" type="integer">182180379</label>
			<label index=".description" type="integer">68307774</label>
			<label index=".image_descr" type="integer">70436675</label>
			<label index="export.description" type="integer">150520112</label>
			<label index="export.details" type="integer">113510702</label>
			<label index="export.image_descr" type="integer">74768430</label>
			<label index="pageTreeCfg.description" type="integer">147952098</label>
			<label index="pageTreeDisplay.description" type="integer">59122430</label>
			<label index="pageTreeMode.description" type="integer">261676486</label>
			<label index="pageTreeMode.details" type="integer">231396751</label>
			<label index="pageTreeRecordLimit.description" type="integer">131668315</label>
			<label index="pageTreeRecordLimit.details" type="integer">221257491</label>
			<label index="singleRecord.description" type="integer">132615781</label>
			<label index="singleRecord.image_descr" type="integer">225220803</label>
			<label index="tableList.description" type="integer">61027651</label>
			<label index="tableList.details" type="integer">207214955</label>
			<label index="tableList.image_descr" type="integer">72114061</label>
			<label index="tableListMaxNumber.description" type="integer">261288618</label>
			<label index="inclRelations.description" type="integer">75889546</label>
			<label index="inclRelations.details" type="integer">21617906</label>
			<label index="staticRelations.description" type="integer">220143778</label>
			<label index="excludedElements.description" type="integer">53727313</label>
			<label index="htmlCssResources.description" type="integer">45106804</label>
			<label index="htmlCssResources.details" type="integer">5219829</label>
			<label index="extensionDependencies.alttitle" type="integer">230544289</label>
			<label index="enableLogging.description" type="integer">42140704</label>
			<label index="upload.description" type="integer">129992522</label>
			<label index="upload.details" type="integer">204986464</label>
			<label index="options.image_descr" type="integer">9245007</label>
			<label index="action.description" type="integer">104527145</label>
			<label index="action.image_descr" type="integer">260289010</label>
			<label index="presets.image_descr" type="integer">191427368</label>
			<label index="metadata.description" type="integer">268196094</label>
			<label index="update.description" type="integer">268353777</label>
			<label index="update.image_descr" type="integer">247229761</label>
			<label index="options.description" type="integer">57482610</label>
			<label index="extensionDependencies.description" type="integer">40923771</label>
			<label index="extensionDependencies.details" type="integer">9362666</label>
			<label index="presets.description" type="integer">76238035</label>
			<label index="fileFormat.description" type="integer">38635585</label>
			<label index="import.description" type="integer">195344023</label>
			<label index="importFile.description" type="integer">46096097</label>
			<label index="inclRelations.image_descr" type="integer">68907185</label>
			<label index="staticRelations.details" type="integer">20475161</label>
			<label index="staticRelations.image_descr" type="integer">235847845</label>
			<label index="htmlCssResources.image_descr" type="integer">72602900</label>
			<label index="presets.details" type="integer">239195638</label>
			<label index="metadata.details" type="integer">31594566</label>
			<label index="fileFormat.details" type="integer">92488672</label>
			<label index="import.details" type="integer">263087661</label>
			<label index="update.details" type="integer">67360881</label>
			<label index="options.details" type="integer">50809709</label>
		</languageKey>
	</orig_hash>
	<orig_text type="array">
		<languageKey index="ch" type="array">
			<label index=".alttitle">Import/Export</label>
			<label index="export.alttitle">Exporting records from TYPO3</label>
			<label index="pageTreeCfg.alttitle">Configuration of page tree export</label>
			<label index="pageTreeDisplay.alttitle">Page Tree</label>
			<label index="pageTreeMode.alttitle">Levels</label>
			<label index="pageTreeRecordLimit.alttitle">Include tables</label>
			<label index="singleRecord.alttitle">Export single record</label>
			<label index="tableList.alttitle">Table export</label>
			<label index="tableListMaxNumber.alttitle">Max number to export</label>
			<label index="inclRelations.alttitle">Include relations</label>
			<label index="staticRelations.alttitle">Set static tables</label>
			<label index="excludedElements.alttitle">Excluded elements</label>
			<label index="htmlCssResources.alttitle">Exclude resources from HTML and CSS files</label>
			<label index="presets.alttitle">Configuration presets</label>
			<label index="metadata.alttitle">Meta data setting</label>
			<label index="fileFormat.alttitle">File format options</label>
			<label index="import.alttitle">Importing TYPO3 records</label>
			<label index="importFile.alttitle">Select file to import</label>
			<label index="update.alttitle">Update instead of Insert</label>
			<label index="options.alttitle">Import options</label>
			<label index="action.alttitle">Import Action</label>
			<label index="enableLogging.alttitle">Enable System Logging</label>
			<label index="upload.alttitle">Upload import file</label>
			<label index=".description">Native Import/Export module for TYPO3 data. Can export single records, content of tables, single pages or whole branches of the page tree. Includes attached media like image and preserves relations between records. Exports only to TYPO3 specific format, either a binary format (.T3D) or XML. The format is meant for exchange between TYPO3 systems.</label>
			<label index=".image_descr">Example of the preview display during export configuration of a page. Notice how records on the page are include plus how references inside the record is found and included as well (bottom of screen).</label>
			<label index="export.description">To export TYPO3 T3D/XML files you click any record icon or page in the page tree (including the root page!), select &quot;More options&quot; (requires the extensions &quot;extra_page_cm_options&quot; to be installed) and then &quot;Export to .t3d&quot;. This will bring up the export interface where you can configure options for your export session.</label>
			<label index="export.details">There are a number of methods by which you can export data from TYPO3:
- Export a single page or branch of the page tree (use page icon context menu)
- Export a single record from any page (use record icon context menu)
- Export all records from a specific table on a specific page (using the Web&gt;List module)
- Export an arbitrary selection of records from the clipboard (using the Web&gt;List module)

The export format observes all TYPO3s methods for relations between the records in the export file. But you will have to configure how these relations are maintained, at least to some degree. Sometimes you would want to include records referred to, at other times you surely want to keep the original mapping. That depends on your objectives with the export.

Regardless of your configuration for export you will always see a complete reflection of all chosen records and their internal relations in the preview display found in the bottom of the export module page.

&lt;b&gt;Error messages:&lt;/b&gt; Remember to consult the Message-tab before exporting if there are any error messages there!</label>
			<label index="export.image_descr">To export a page or record, simply click the icon and select &quot;Export&quot; from the context menu.
With the Web&gt;List module you can also export all records from a table by first clicking the table title to see only this table, then next to the CSV export you will find the export button for a T3D export of the table.
You can export the contents of the clipboard as well by simply selecting &quot;Export&quot; in the menu.</label>
			<label index="pageTreeCfg.description">Here you configure how a page or a branch of the page tree should be exported. Using the selector box you can set the number of levels of subpages to include in the export.
By default all records belonging to a page is included when a page is exported.</label>
			<label index="pageTreeDisplay.description">Based on the levels selected for page tree export this will show the structure that is about to be exported. If any pages are specifically excluded by the exclude option they are not shown either.</label>
			<label index="pageTreeMode.description">Here you select how deeply in the page tree from the current starting point to go for this export.</label>
			<label index="pageTreeMode.details">If you select &quot;Expanded tree&quot; it will base the export on the currently expanded levels of the page tree. Another special option is &quot;Tables on this page&quot; which will not include the page record itself but only include records from tables on the page, depending on the table configuration of course.</label>
			<label index="pageTreeRecordLimit.description">When you export a page all records on the page is included by default. By this selector you can pick which tables to include exclusively if there are certain records you are not interested in seeing included.</label>
			<label index="pageTreeRecordLimit.details">In the box &quot;Max number of records&quot; you can set a limit to how many records are selected from a single table. This is a runaway brake in case you have an unusual large amount of records from a table.</label>
			<label index="singleRecord.description">This overview tells you which independent records has been independently selected for export.</label>
			<label index="singleRecord.image_descr">The way to export multiple records like this is using the clipboard like shown below.</label>
			<label index="tableList.description">Export of all records on a page from a specific table. This is configured from the Web&gt;List module where you will have to select table-only view and click a button in the top of the page.</label>
			<label index="tableList.details">Tip: You can select multiple table lists by simply saving each selecting as a preset and finally load/merge the selections together.</label>
			<label index="tableList.image_descr">Here two tables from different pages are selected. This is done by first selecting the one, saving it as a preset, then select the other and merge with the saved preset.
Here you see how to use the Web&gt;List module to export all records from a table on a page.</label>
			<label index="tableListMaxNumber.description">Run-away brake that will make sure a large amount of records does not halt the interface. Default is 100, but you can change it to anything you like of course.</label>
			<label index="inclRelations.description">Configure the tables from which you want to include records that are found as relations in the main export configuration.</label>
			<label index="inclRelations.details">Background: When you export a record in TYPO3 it might contain relations to other records in the system. You have to tell the export interface what to do with these relations. Basically there are three scenarios:
- If relations are found between records that are all in the export configuration, there is no problem: The relations are automatically mapped to the new id's of those records when imported.
- If the records related to are not included the relation will be lost (indicated with an error message in the preview) unless you a) either select that table in this selector box in which case all relations to that table will be included or b) if you set the table as a static table (in which case the relation is untouched and imported as-is - but which will of course break if no record with that UID is found in the import system).

&lt;b&gt;Soft References:&lt;/b&gt; Soft references are when a record contains pointers to external files or records but in fields where there are no formal relation configured. Examples of this is when a content element contains a &quot;&amp;lt;link 123&amp;gt;&quot; tag that represents a link to the page 123. This is not picked up formally as a reference, but is found anyhow as a &quot;soft reference&quot;. The same goes for &amp;lt;img&amp;gt; tags with images from eg. &quot;fileadmin/&quot;.
By default soft references pointing to records or files will act as normal references; either including the referenced item or showing an error. However you can also choose to exclude the handling of individual soft references or maybe set the value as &quot;editable&quot; upon import. This is done with a selector box in the export preview.</label>
			<label index="staticRelations.description">Select which tables in addition to the static TYPO3 tables to keep relations untouched for. Takes precedence over &quot;Include relations&quot; configured tables.</label>
			<label index="excludedElements.description">By the &quot;Exclude&quot; checkbox you can exclude specific records from the preview display of the export. Which records has been picked for specific exclusion is listed here. You can also clear the exclusion configuration.</label>
			<label index="htmlCssResources.description">When an HTML or CSS file is found as a soft reference the files are parsed for references to external media (such as images) and if any are found they are also exported. If you don't want this behaviour, click this option.</label>
			<label index="htmlCssResources.details">Notice: Resources found inside an HTML or CSS file are not analysed further. For instance it means that any CSS files referred to from within an HTML will not be traversed - but CSS files referred to inside the Setup or Constant field of a TypoScript template record will be!</label>
			<label index="extensionDependencies.alttitle">Extension Dependencies</label>
			<label index="enableLogging.description">If you set this the system backend log will be filled with entries for all the actions that the import actually performs. By default this is left out for the sake of clarity.</label>
			<label index="upload.description">Select a file to import from your local computer and upload it here. If the upload completes succesfully you can immediately see its content displayed in the preview display.</label>
			<label index="upload.details">Notice that there are usually limits set by the server (PHP) to the size of uploaded files at around 2 MB in which case nothing will happen.</label>
			<label index="options.image_descr">Options for import.
Here you are told that this PHP file cannot be allowed - because you didn't select the option &quot;Allow to write banned file extensions (eg. PHP scripts), if any&quot;</label>
			<label index="action.description">Press &quot;Preview&quot; to see the content of the import file or update the preview display according to changed configurations. 
Press &quot;Import&quot;/&quot;Update&quot; if you want to perform the actual import.

Before importing make sure you change any editable soft references that are shown in the preview data.</label>
			<label index="action.image_descr">Example of the result view after importing. As you can see the RTE attached images (soft references) has been written to new file names and the difference view tells you that the names changed in the bodytext content.</label>
			<label index="presets.image_descr">The preset selector in the export interface.
Presets from the task center.</label>
			<label index="metadata.description">Set meta data for the export. This is highly encouraged if your exported content goes into eg. a template collection of sorts.</label>
			<label index="update.description">By default the import operation inserts new records in the system. Using this option will update existing records.</label>
			<label index="update.image_descr">In Update mode you can select various settings for each record. You will also be able to see a diff-view where the differences between the existing record and the one from the import is shown.</label>
			<label index="options.description">Various options for import.</label>
			<label index="extensionDependencies.description">Select which extensions should be installed in the import system in order for your exported content to work correctly. Examples could be &quot;templavoila&quot; for templating, &quot;css_styled_content&quot; for the template, &quot;tt_news&quot; for a news archive etc.</label>
			<label index="extensionDependencies.details">During import warnings will appear for all selected extensions from this list which were not installed.</label>
			<label index="presets.description">Enables you to save an export configuration for later re-use. Useful if you need to export the same configuration with regular intervals.</label>
			<label index="fileFormat.description">You can export your records to a TYPO3 specific binary format (serialized PHP array) called &quot;T3D&quot;. Alternatively you can select a plain-text XML export which potentially can be imported by other applications written to support this format. However the schema of the XML is TYPO3 specific.</label>
			<label index="import.description">To import TYPO3 T3D/XML files into the page tree you click any page in the page tree (including the root page!), select &quot;More options&quot; (requires the extensions &quot;extra_page_cm_options&quot; to be installed) and then &quot;Import from .t3d&quot;. This will bring up the import interface where you can select a file to import or upload a new one.</label>
			<label index="importFile.description">The files displayed are those with an extension T3D or XML from fileadmin/, fileadmin/export/ and your &quot;TEMP&quot; folder (if any).</label>
			<label index="inclRelations.image_descr">This example shows tree examples of references; a) an image attached to a content element, b) a relation to a frontend usergroup UID, and c) a soft reference found in the bodytext field of a record, here it is the link-tag pointing to the page with UID 1. 
Notice in the previous image how the relation to the frontend user group was lost. This has been corrected in this screenshot where the fe_group table has been selected in the list of table for which to include relations. The result is that the frontend usergroup is included as a record outside the exported pagetree. If you wanted to keep the relation but not include the usergroup you have to set &quot;fe_groups&quot; as a static table instead. See below.
This example shows a TypoScript Template Record where multiple soft references has been found. The first one is an email address. Here it is configured to be editable. This means that upon import the user will have a chance to edit the value before the import is actually done. This is very useful when exported files are used as templates. Another example includes a PHP script which we don't want to include in the export and therefore we have selected the exclude option for the soft reference.</label>
			<label index="staticRelations.details">By default all relations to static tables in TYPO3 are kept untouched. Of course those static tables should be present in the import system in order for this to work correctly. However there might be circumstances where you move information between two systems where theoretically non-static tables should just keep relations untouched. Examples could be &quot;sys_languages&quot; or TemplaVoila data structures / template objects where two systems might contain the same set of records in those tables while you are importing pages and content elements freely.</label>
			<label index="staticRelations.image_descr">In this example you see how a number of records are pointing to a System Language record which will become lost relations when imported because the record is not included in the export. However; in the target system the System Languages are exactly the same and therefore you just want a static mapping of the relations.
The static mapping is obtained by selecting the &quot;sys_language&quot; table as a static template meaning that the relations are kept at their current values assuming that they will be exactly the same in the target system when imported.</label>
			<label index="htmlCssResources.image_descr">In this example you can see that a soft reference has been found pointing to an HTML file inside fileadmin/ Since it was an HTML file it was parsed and further a number of files were found referenced inside it and now included with the export. This feature is specifically created to support export of template configurations where external HTML files play a role.</label>
			<label index="presets.details">In the &quot;Select preset&quot; box you can select any previously saved preset to load. If you are exporting a page the presets listed will be those found for the start page ID. For records, any preset can be loaded.
To load a preset, select it in the selector and press &quot;Load&quot;. If you press &quot;Merge&quot; instead the settings from the preset will be merged with the current configuration. This is meaningful in cases where you select multiple individual tables or records.
To save a preset, simply enter a title in the title box and press &quot;Save&quot;. This will create a new preset. If you press save while having selected an existing preset you will overwrite it.
To delete old presets, simply select it and press &quot;Delete&quot;.

The checkbox &quot;Public&quot; can be set if you want to share your preset with other users of the system. Otherwise they are personal to you.

In the Taskcenter you can see a list of your presets and jump directly to them.</label>
			<label index="metadata.details">The meta data will help users of your exported files to know what they can expect to be inside and what things they should be aware of and take into account during import.
The &quot;Title&quot; and &quot;Description&quot; should contain the basic information about the export. 
The &quot;Notes&quot; field can be used for additional details, especially remarks about intensions or requirements that apply.
The thumbnail field is used for thumbnails if you need that for your export. This is very useful when export files are used as page templates where the template selector can take advantage of the thumbnail. The format should be a web-format like jpg, gif or png and the dimensions should fit exactly the final display dimensions intended; so don't upload very large images!</label>
			<label index="fileFormat.details">Generally you should use the T3D format, preferably compressed. The T3D compressed format normally yields a size about 10 times less than the XML format which is bloaded due to the plain-text nature of the format.

With &quot;Max size of files to include&quot; you can set a limit to the size of attached files to records. This is useful if you have large PDF files or videoclips attached to records which you do not desire (or do desire!) to include; then with this limit you can adjust whether they are allowed in or not.

Entering a file name to save to makes it possible to write your export directly to a file (pressing &quot;Save to filename&quot;) instead of downloading it (pressing &quot;Download export&quot;). The correct file extensions depending on file format is automatically applied. Files are saved in a proper filemount in &quot;fileadmin/&quot;. This is shown to you upon saving. Existing files are overwritten.</label>
			<label index="import.details">&lt;b&gt;Tip: Import into a Sys Folder&lt;/b&gt;
To make sure that no records are lost during the import, you can make yourself safe by importing into a SysFolder you create first. After the import you can move all records to the final destinations. An example of such a scenario is if you configured the export to include relations; In that case a number of records may follow the export outside the page tree structure you are exporting. To make sure that all of these external records are written to the database, importing into a SysFolder is a good idea.

&lt;b&gt;Error messages:&lt;/b&gt; Remember to consult the Message-tab before/after importing to see if there are any error messages there!</label>
			<label index="update.details">There are certain requirements you have to meet if you want the &quot;Update&quot; process to work. The main thing is that the records updated are those with the SAME uid as the uid in the export file. Thus an update operation only makes real sense if the export and import systems are somehow related and the same UIDs can be expected in both ends. Otherwise it will be a mess!

When you update page structures the import operation will automatically try to rearrange records so they also appear in the same hierarchy and order as in the export file. This can be disabled by checking the option &quot;Ignore PID differences globally&quot;. In any case you can set individual records to Ignore/Respect the PID with a selectorbox in the preview.

In the preview display you can also select if individual records should be flatly ignored during import or if you want them created as new records instead of being updates.
As a help for managing updates the preview display will inform you about the path where the existing element with that UID is found. Use this to verify that you get what you expect!

&lt;b&gt;Forcing the UID:&lt;/b&gt;
If you intend to update a system and some elements from the import are not mappable to a UID already (ei. does not exist) you can choose in the preview display to force the UID during creation. This is an unorthodox thing to do since UIDs are normally created automatically by the database. The option makes most sense if you are trying to &quot;synchronize&quot; a copy of another system. The option may mess up certain database internals and the feature is therefore only available for admins.</label>
			<label index="options.details">&lt;b&gt;Do not show differences in records&lt;/b&gt;
When a structure has been imported you will see a difference view of all records which tells you whether the written content matched the import data or if not, what changed. In many cases content &lt;i&gt;should&lt;/i&gt; change (eg. relations and file references) so it is not an error if you see red and green values. Basically the difference view is a feature you can use for visual validation of the import success. It brings piece-of-mind to those who is enlightened to understand what it tells... :-)
Green strings represent the actual written data while red represents the original value from the import file and black represents data that is the same.

&lt;b&gt;Allow to write banned file extensions (eg. PHP scripts), if any&lt;/b&gt;
Also an option for admins-only; Allows PHP-files (for example from soft references in TypoScript templates) to be written to the system. This is normally not allowed behavior for security reasons.</label>
		</languageKey>
	</orig_text>
</T3locallangExt>