<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<T3locallangExt>
	<data type="array">
		<languageKey index="ch" type="array">
			<label index=".description">在TYPO3中定义定制工作区可允许组中的用户在处理发布的草稿内容时可在一起工作。关于工作区的更多信息可在文档&quot;Inside TYPO3&quot;中找到。</label>
			<label index="title.description">输入工作区的名称。此值在后台的工作区选择框中显示。</label>
			<label index="description.description">在这里描述工作区的目的。此信息在工作区管理器上显示并可向工作区用户介绍工作区的目的。</label>
			<label index="adminusers.description">工作区的拥有者是被允许添加成员及评论区还有指定页面树的起始点等等的人。</label>
			<label index="adminusers.details">拥有者也能删除或添加其它拥有者。如果一个用户被允许创建他自己的工作区，他将自动成为该工作区最初的拥有者，同样地成为最终的工作区发布者（除了TYPO3的“管理员”用户）以及权限最高的人（除了能进入该工作区的成员/评论家）。</label>
			<label index="members.description">成员能成为后台用户或组,并且能在工作区中工作.他们不能发布内容(除非他们能进入活跃的工作区)，but only edit it after which they will forward it for approval by a reviewer。</label>
			<label index="stagechg_notification.description">当进行内容更改时，工作区中的用户能通过邮件接收到通知信息。Only members/reviewers who are attached to the workspace as users and not through their groups will be notified。</label>
			<label index="db_mountpoints.description">在工作区中工作时，如果被指定的后台页面树的一个或多个数据库挂接点将被锁定到这些根点。</label>
			<label index="db_mountpoints.details">任何在此指定的数据库挂接点必须在已登录的用户的数据库挂接设置内。If that is not the case 工作区数据库挂接点将不仅为用户挂接上。如果没有为工作区指定数据库挂接点，用户将能进入他们自己配置文件的数据库挂接点。</label>
			<label index="file_mountpoints.description">文件挂接点对工作区用户可用。请查看与安全信息有关的细节！</label>
			<label index="file_mountpoints.details">重要：默认情况下，草稿工作区所有的文件挂接都被禁用！这是因为翻译版本未应用到TYPO3中通过文件挂接的任何文件上。因此，对那些文件的任何存取都违反了没有任何在草稿工作区中被管理的内容在发布前是活跃的这一原则。</label>
			<label index="publish_time.description">指定发布工作区内容的时间。</label>
			<label index="publish_time.details">发布和取消发布时间仅在 &quot;mod/user/ws/cli/ws_cli.phpsh&quot;作为 cronjob 并在每分钟都运行的设置起用后激活。一个示例的配置是&quot;* * * * * /[ABSOLUTE PATH TO TYPO3 SITE]/typo3/mod/user/ws/cli/ws_cli.phpsh”</label>
			<label index="unpublish_time.description">指定发布/取消发布工作区内容的附加时间。</label>
			<label index="unpublish_time.details">“附加的”意味着两个发布时间都用于相似的用途，但如果“发布”被指定的话，它优先于“未发布”。总之，the point of two publishing times is that workspace content could be swapped in for a limited period and then out again。但请注意；对这两个工作而言，交换模式必须设置为“Swap-Into-Workspace on Auto-publish”。</label>
			<label index="freeze.description">如果设置的话，工作区不允许任何编辑。</label>
			<label index="live_edit.description">如果设置的话，表中的未激活译本的记录不能依然在工作区中作为“活动的”被编辑。</label>
			<label index="disable_autocreate.description">如果设置的话，记录不会在工作区中编辑时自动创建为新的版本。新版本必须在之前通过手工创建。</label>
			<label index="swap_modes.details">默认情况下，交换是允许的。因此，两个版本都可在工作区“内或外”发布多次，总是取代各自。如果这不是您希望的，它可通过“禁用Swap-Into-Workspace”来关闭它。
另一个模式， &quot;Swap-Into-Workspace on Auto-publish&quot; 将强迫自动发布通过 cronjob来交换版本。This is necessary to use if you specify both a publish AND un-publish time because otherwise the workspace will be empty after the first publish action!</label>
			<label index="vtypes.description">选择您希望为工作区的编辑员/评论员禁用的版本类型（管理员用户和拥有者不受限制）。</label>
			<label index="publish_access.description">精练发布规则</label>
			<label index="publish_access.details">“仅发布处于发布阶段的内容”：仅当文件处于发布阶段时才可发布。
“仅工作区拥有者才能发布”：仅工作区的拥有者能发布工作区的内容，即使是进入到活跃工作区中的成员或评论员也不能。</label>
		</languageKey>
	</data>
	<orig_hash type="array">
		<languageKey index="ch" type="array">
			<label index="freeze.description" type="integer">134717254</label>
			<label index="live_edit.description" type="integer">186857343</label>
			<label index="publish_access.description" type="integer">79106280</label>
			<label index=".description" type="integer">82101164</label>
			<label index="title.description" type="integer">158098838</label>
			<label index="description.description" type="integer">189422282</label>
			<label index="adminusers.description" type="integer">256927453</label>
			<label index="publish_time.description" type="integer">20570038</label>
			<label index="publish_time.details" type="integer">166719901</label>
			<label index="unpublish_time.description" type="integer">144362633</label>
			<label index="adminusers.details" type="integer">142331935</label>
			<label index="members.description" type="integer">263329389</label>
			<label index="db_mountpoints.description" type="integer">207068827</label>
			<label index="db_mountpoints.details" type="integer">10256613</label>
			<label index="file_mountpoints.description" type="integer">53529306</label>
			<label index="disable_autocreate.description" type="integer">65404858</label>
			<label index="unpublish_time.details" type="integer">12639267</label>
			<label index="stagechg_notification.description" type="integer">111614725</label>
			<label index="file_mountpoints.details" type="integer">211718238</label>
			<label index="publish_access.details" type="integer">130330045</label>
			<label index="vtypes.description" type="integer">252816145</label>
			<label index="swap_modes.details" type="integer">144319789</label>
		</languageKey>
	</orig_hash>
	<orig_text type="array">
		<languageKey index="ch" type="array">
			<label index="freeze.description">If set, no editing is allowed inside workspace.</label>
			<label index="live_edit.description">If set, records from tables where versioning is not enabled can still be edited &quot;live&quot; inside the workspace.</label>
			<label index="publish_access.description">Refines the rules of publishing</label>
			<label index=".description">Defines custom workspaces in TYPO3 which allows for groups of people to work together in a publishing process with draft content. More information about workspaces can be found in the document &quot;Inside TYPO3&quot;.</label>
			<label index="title.description">Enter the name of the workspace. This value is shown in the workspace selector box in the backend.</label>
			<label index="description.description">Make a description of the workspace purpose here. This information is shown in the Workspace Manager and should instruct the workspace users about the purpose of the workspace.</label>
			<label index="adminusers.description">Owners of the workspace are those who are allowed to add members and reviewers to the workspace and pick the page tree starting points etc.</label>
			<label index="publish_time.description">Specify a time of publication of the workspace content.</label>
			<label index="publish_time.details">The publish and unpublish times are active only if &quot;mod/user/ws/cli/ws_cli.phpsh&quot; is set up as a cronjob running every minute. Example configuration could be &quot;* * * * * /[ABSOLUTE PATH TO TYPO3 SITE]/typo3/mod/user/ws/cli/ws_cli.phpsh&quot;</label>
			<label index="unpublish_time.description">Specify an additional time of (un)publication of the workspace content.</label>
			<label index="adminusers.details">Owners can also add and delete other owners. If a user is allowed to create workspaces himself he will automatically become the initial owner user of the workspace. They are also the only ones who can eventually publish the workspace content (except general TYPO3 &quot;admin&quot; users) and thus the highest review authority (unless members/reviewers have access to the Live workspace).</label>
			<label index="members.description">Members can be backend users or groups and will have access to work in the workspace. They cannot publish content (unless they have access to the Live workspace) but only edit it after which they will forward it for approval by a reviewer.</label>
			<label index="db_mountpoints.description">If one or more DB mounts are specified the page tree of the backend will be locked into these root points during work in the workspace.</label>
			<label index="db_mountpoints.details">Any DB mount specified here must be inside the DB mount set for the backend user who logs in. If that is not the case the workspace DB mount will simply not be mounted for the user. If no DB mounts are specified for the workspace the users will access the DB mounts of their user profile.</label>
			<label index="file_mountpoints.description">Filemounts available for workspace users. Please see details for security information!</label>
			<label index="disable_autocreate.description">If set, records are not automatically created as new versions when edited in the workspace. A new version must be manually created first.</label>
			<label index="unpublish_time.details">By &quot;additional&quot; is meant that both publishing times are used in a similar way, but if &quot;Publish&quot; is specified it takes precedence over &quot;Unpublish&quot;. Anyway, the point of two publishing times is that workspace content could be swapped in for a limited period and then out again. But notice; for this to work the Swap mode must be set to &quot;Swap-Into-Workspace on Auto-publish&quot;.</label>
			<label index="stagechg_notification.description">When the stage of content changes, users in the workspace can receive a notification by email. Only members/reviewers who are attached to the workspace as users and not through their groups will be notified.</label>
			<label index="file_mountpoints.details">IMPORTANT: By default a draft workspace has all filemounts disabled! This is because versioning does not apply to any files edited through filemounts in TYPO3. Hence any access to those files would violate the principle that no content managed in a draft workspace will be live before published.
			However, for specific projects this violation might be acceptable or necessary and therefore you can add a filemount. This will be forced upon any user in the workspace regardless of his filemounts inherited from his groups and user profile!</label>
			<label index="publish_access.details">&quot;Publish only content in publish stage&quot; : Only when content is in publish stage can it be published. 
&quot;Only workspace owner can publish&quot; : Only the workspace owner can publish the content in the workspace, even if members or reviewers have access to the Live workspace.</label>
			<label index="vtypes.description">Select versioning types you want to disable for workspace editors/reviewers (admin users and owners are not limited).</label>
			<label index="swap_modes.details">By default swapping is allowed. Thereby two versions can be published &quot;in and out&quot; of a workspace multiple times, always substituting each other. If this is not desired, it can be disabled with &quot;Disable Swap-Into-Workspace&quot;.
Another mode &quot;Swap-Into-Workspace on Auto-publish&quot; will force the automatic publishing through the cronjob to swap versions. This is necessary to use if you specify both a publish AND un-publish time because otherwise the workspace will be empty after the first publish action!</label>
		</languageKey>
	</orig_text>
</T3locallangExt>