<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<T3locallangExt>
	<data type="array">
		<languageKey index="ch" type="array">
			<label index=".description">这是对后台用户可用的后台管理员用户组。这决定了后台用户进入的信任。</label>
			<label index=".details">组包含您可为一个后台用户设置的主要的权限设置。
当一个用户是许多组的成员（包括子组），那么该用户所在所有组的权限设置将集合起来，他将有许多权限。</label>
			<label index=".image_descr">在页面树根找到的后台用户组只有“管理”组用户能编辑他们。有此红色图标的用户组是有存取列表开启的其中之一。绿色的是空白组。此组的存取列表开启。在存取列表中您指定了哪个模块，表，数据库区等。组成员能进入TYPO3。（此段不好译）</label>
			<label index="title.description">后台用户组的名称。此名称能描述组并能在以后修改。</label>
			<label index="title.details">后台用户组由其“UID”的值（整数）标识，因此，标题总是能被修改。“UID”不能修改。</label>
			<label index="title.image_descr">用户组标题显示在记录列表中。</label>
			<label index="db_mountpoints.description">为组成员定义页面树根点位置。</label>
			<label index="db_mountpoints.details">TYPO3中的页面树必须定义一些进入点。这里您应该插入对于一个页面的一个或多个参考，该页面为页面树描述一个新的根页。这被叫作 &quot;Database mount&quot; 或 &quot;DB mount&quot;。
数据库挂接点&lt;i&gt;可能&lt;/i&gt;通过是此组中的用户而继承得到。这依靠于用户是否被配置为属于有挂接配置的组的成员。然而，推荐使用像这样的后台用户配置挂接点。特别是需要被许多用户共享的。</label>
			<label index="db_mountpoints.image_descr">这里一个页面被作为“数据库挂接点”添加...
...并且在成员用户的页面树中将成为页面树的开始点。</label>
			<label index="file_mountpoints.description">为文件夹树定义开始点。</label>
			<label index="file_mountpoints.details">文件的文件夹树被所有文件子模块使用作为服务器上文件的文件夹的导航。如果您希望通过TYPO3使用它来存取服务器上的文件系统，那么至少需要一个文件挂接点（及存取到如文件&gt;文件列表模块）。
您可在&quot;fileadmin/&quot; 挂接一个与ＴＹＰＯ３安装有关的路径或挂接一个服务器上其它地方的绝对的的路径（网站根目录之外！）。最后一个要求是定义$TYPO3_CONF_VARS[BE][lockRootPath]。您挂接的路径由您通过此区域提到的文件挂接点记录所定义。因此一个文件挂接点仅指向内部细节已配置的另一个记录。查看下面的屏幕截图。
“管理”用户默认总是有&quot;fileadmin/&quot;文件夹的挂接。注意；像 'DB mounts'一样，文件夹挂接可能通过可能是此组中的用户而继续。</label>
			<label index="file_mountpoints.image_descr">文件Mounts涉及到&quot;Filemounts&quot;表有关的记录。在 Filemount 记录中您定义了路径是否是绝对的（必须在$TYPO3_CONF_VARS[BE][lockRootPath]内部）或 与&quot;fileadmin/&quot;有关。在此例中 Filemount 指向 &quot;fileadmin/user_upload/&quot;，这是管理员用户的页面树。注意，文件夹&quot;user_upload&quot; 是File Mount 记录涉及到的文件夹。
这显示了组中成员看到的mounted文件夹。
Filemount records 总在创建在页面树根。</label>
			<label index="pagetypes_select.description">选择成员可设置的页面的“类型”。</label>
			<label index="pagetypes_select.details">当用户选择一个页面类型时此选项限制了选择的正确值的数。
页面类型的选择(doktype) 与下面是关联的，a) 页面的一个特殊的图标，b) 页面上的表的许可（查看 $PAGES_TYPES 全局变量)和c) 页面是否是网站页面或“系统文件夹”类型。</label>
			<label index="pagetypes_select.image_descr">与CMS相关的可用到的典型的页面类型的列表。为一个用户组选择页面类型（定义这些选项中组成员用户能选择的选项）。</label>
			<label index="tables_modify.description">选择成员能修改的表格。</label>
			<label index="tables_modify.details">设置权限的一个重要部分是定义允许用户修改数据库中哪个表。
允许修改的表也允许用于选择，这样您不需要在“表（列表）”选择框中设置进入的表。
&lt;strong&gt;注意&lt;/strong&gt; 此列表添加到一个在其它组中的用户的选择区域中。</label>
			<label index="tables_modify.image_descr">上面的屏幕截图显示了“创建新记录”会话是如何查找一个限制编辑“页面”及“页面内容”元素的用户的。
这两个表只是添加到“表（修改）”列表中
这是（一个例子）能由“管理员”用户（没有限制地）创建在页面上的元素的总计。</label>
			<label index="tables_select.description">选择成员能在记录列表中（修改表不需要再次进入这里！）看到的表。</label>
			<label index="tables_select.details">这决定了哪个表--in addition to those selected in the &quot;Tables (modify)&quot; box -可为成员用户查看和列出。他不能 &lt;em&gt;编辑&lt;/em&gt; 表--仅选择表记录和查看内容。</label>
			<label index="non_exclude_fields.description">默认情况下某些表区域不可用。这些区域可在此为组成员启用。</label>
			<label index="non_exclude_fields.details">“允许排斥”允许您详细描述表的权限。默认情况下所有这些区域对用户都不可用，但可通过在这里选择以使其可用。
与此相关的一个程序是页面通常默认是隐藏的并且隐藏区域对用户不可用，除非他在“允许排斥”列表中被同意。因此，用户可以创建新页面，但不能隐藏页面--除非他通过他所属的一个组被分派“页面：隐藏页面”排除区域。</label>
			<label index="hidden.description">禁用一个用户组。</label>
			<label index="hidden.details">如果您禁止一个用户组，该组中所有成员用户不再继承此组中的任何特性。</label>
			<label index="lockToDomain.description">输入强迫用户登录的主机名。</label>
			<label index="lockToDomain.details">一个TYPO3系统可能在主机上有多个域名的网站。此选项确保用户登录到特定的主机名。
此设置的一个例子是&quot;www.my-domain.com&quot; 将需要一个用户从该域名登录进去（如果获得此组的成员数）。否则用户将忽略该组。</label>
			<label index="groupMods.description">为组成员选择可用的后台模块。</label>
			<label index="groupMods.details">这决定了哪个‘菜单项’对组成员是可用的。This list of modules is added to any modules selected in other member groups of a user as well as the corresponding field of the user himself.</label>
			<label index="groupMods.image_descr">适合一个用户的后台模块被反映在后台的菜单项上。对于大多数固定使用者来说只在网站和文件主模块里的模块被启用。通常&quot;网站 &gt;页面&quot;用于编辑页面的内容。
从上面屏幕截图可知这是用户的后台模块任务。全部四个网站子模块及两个用户子模块在此配置。但是，文件&gt;文件列表模块必须为此用户所在的另一个组配置（或在用户配置文件中哪个是可能的）。默认情况下，帮助模块都可进入，不需要明确的进入权限。</label>
			<label index="inc_access_lists.description">选择是否页面类型，表格，模块及允许排斥的存取列表都在此组中启用。</label>
			<label index="inc_access_lists.details">如果此选项被禁用，不能为组配置存取列表。
当存取列表被禁用时，组的图标是绿色的，反过来则是红色的。</label>
			<label index="description.description">为用户组输入一个简短的描述，是做什么的，谁是成员。这仅供内部使用。</label>
			<label index="TSconfig.description">用户TSconfig：通过TypoScript 风格值附加配置（高级）。</label>
			<label index="TSconfig.details">使用Tsconfig可为每个后台用户和组设置。为后台用户组设置是通过从是该组的用户那里继承来的。作为代表的用于用户设置的可用的选项可从用户&gt;设置模块找到（事实上从该模块来的选项能强制覆盖用户的Tsconfig选项！），“管理员面板”（前台）的配置，不同于后台的（锁定用户的IP，显示快捷方式框架，允许用户清除所有缓存？，导航框架的宽度等）及后台模块配置（在页面Tsconfig中为用户覆盖任何配置设定）。</label>
			<label index="TSconfig.syntax">没有条件及常量的TypoScript语法。</label>
			<label index="TSconfig.image_descr">在 TSconfig 区域，帮助是正确的-只要点击TS向导图标，将弹出一个窗口。
在弹出窗口中您可看到可能用于配置的值的树。这些是从TSconfig手册中提取的。您通过此向导点击并找到您需要设置的选项。</label>
			<label index="hide_in_lists.description">此选项将防止从此列表中显示的用户组，用户组在哪被选择。</label>
			<label index="hide_in_lists.details">这将影响到计划任务中心的执行的用户组列表及网站&gt;存取模块的消息部分。
如果您有大量的用户组来定义一些全局的参数（该参数允许您的用户是某组的成员），该选项是非常有用的。或许您不喜欢用户通过此用户组的成员人数来看到彼此，例如发送消息或要执行的动作。这是该选项能防止的。</label>
			<label index="subgroup.description">选择成员自动包括到此组中的组。</label>
			<label index="subgroup.details">子组的特性已添加到此组的属性中，基本上，任何此组中的成员都能简单地将他们添加到成员组的列表中。此特性提供了一个创建“Supervisor”用户组的很好的方法。</label>
			<label index="explicit_allowdeny.description">为用户组成员选择明确拒绝或同意的区域值。</label>
			<label index="explicit_allowdeny.details">选择框区能被配置为存取控制值标签。此列表呈现了所有用于存取控制配置的值。每个值都能被配置为要求任一清楚的存取（允许）或任一否定（拒绝），它意味着默认的用户&lt;em&gt;不能&lt;/em&gt;设定此值，除非他们是明确允许此操作的组的成员（通过设置此检查框）。
如果一个值有一个前缀“Deny”（红色图标），它意味着默认的用户能设置此值，除非他们是明确拒绝它的组的成员（通过设置此检查框）。
此列表已进行组织，因此来自相同的选择框的值已在此列出。如果从一个选择框来的值未出现在允许/拒绝列表中，只是意味着它们未经评价并且可由任何进入此区域的人来设置。</label>
			<label index="allowed_languages.description">选择限制组成员编辑的记录语言。If that is the case access to these elements will also be evaluated based on whether the user has the language in question included from this list。如果一个用户没有任何语言列表，这意味着他可编辑 &lt;em&gt;所有&lt;/em&gt;语言！</label>
			<label index="allowed_languages.details">TYPO3中的记录可被配置为携带他们的语言的信息。</label>
			<label index="allowed_languages.image_descr">此例子显示了一个情形，丹麦语和德语这两种语言创建为默认语言的附加语言。</label>
			<label index="custom_options.description">选择自定义的许可选项。</label>
			<label index="custom_options.details">此列表描述了通过不同的后台模块定制权限的介绍（从扩展）。每个选项的意义依靠于后台模块对其的评估。</label>
			<label index="custom_options.image_descr">这是来自内部测试程序的一个例子。它显示了检查框是如何被其页眉下面的模块添加的。您可通过检查框来显示一个描述文字来说明其功能，</label>
		</languageKey>
	</data>
	<orig_hash type="array">
		<languageKey index="ch" type="array">
			<label index="db_mountpoints.description" type="integer">79572288</label>
			<label index="file_mountpoints.description" type="integer">172594607</label>
			<label index="pagetypes_select.description" type="integer">44094257</label>
			<label index="tables_modify.description" type="integer">138526409</label>
			<label index="hidden.description" type="integer">190841262</label>
			<label index="lockToDomain.description" type="integer">139426379</label>
			<label index="groupMods.description" type="integer">249603367</label>
			<label index="custom_options.description" type="integer">233721502</label>
			<label index=".description" type="integer">24692837</label>
			<label index=".details" type="integer">152748622</label>
			<label index=".image_descr" type="integer">13061130</label>
			<label index="title.description" type="integer">122308063</label>
			<label index="title.details" type="integer">131557834</label>
			<label index="title.image_descr" type="integer">254619996</label>
			<label index="db_mountpoints.details" type="integer">43503742</label>
			<label index="db_mountpoints.image_descr" type="integer">217823442</label>
			<label index="file_mountpoints.details" type="integer">65754039</label>
			<label index="pagetypes_select.details" type="integer">266555079</label>
			<label index="pagetypes_select.image_descr" type="integer">59933954</label>
			<label index="description.description" type="integer">189455419</label>
			<label index="TSconfig.description" type="integer">211026111</label>
			<label index="hide_in_lists.description" type="integer">169107711</label>
			<label index="subgroup.description" type="integer">244521906</label>
			<label index="file_mountpoints.image_descr" type="integer">176310322</label>
			<label index="tables_modify.details" type="integer">89351209</label>
			<label index="tables_modify.image_descr" type="integer">125152696</label>
			<label index="tables_select.description" type="integer">79180839</label>
			<label index="tables_select.details" type="integer">95679269</label>
			<label index="non_exclude_fields.description" type="integer">17658287</label>
			<label index="non_exclude_fields.details" type="integer">206989457</label>
			<label index="hidden.details" type="integer">191806419</label>
			<label index="lockToDomain.details" type="integer">85223659</label>
			<label index="groupMods.details" type="integer">250073054</label>
			<label index="groupMods.image_descr" type="integer">193960165</label>
			<label index="explicit_allowdeny.description" type="integer">109000363</label>
			<label index="allowed_languages.description" type="integer">33891430</label>
			<label index="allowed_languages.details" type="integer">48640895</label>
			<label index="allowed_languages.image_descr" type="integer">80725669</label>
			<label index="custom_options.details" type="integer">1101189</label>
			<label index="custom_options.image_descr" type="integer">42996915</label>
			<label index="inc_access_lists.description" type="integer">208224239</label>
			<label index="inc_access_lists.details" type="integer">163860974</label>
			<label index="TSconfig.syntax" type="integer">185290164</label>
			<label index="TSconfig.image_descr" type="integer">230747652</label>
			<label index="TSconfig.details" type="integer">267445991</label>
			<label index="hide_in_lists.details" type="integer">20735693</label>
			<label index="subgroup.details" type="integer">41206182</label>
			<label index="explicit_allowdeny.details" type="integer">242296359</label>
		</languageKey>
	</orig_hash>
	<orig_text type="array">
		<languageKey index="ch" type="array">
			<label index="db_mountpoints.description">Define page tree root points for the group members.</label>
			<label index="file_mountpoints.description">Define startpoints for the file folder tree.</label>
			<label index="pagetypes_select.description">Select which 'Types' of Pages the members may set.</label>
			<label index="tables_modify.description">Select which tables the members may modify.</label>
			<label index="hidden.description">Disables a user group.</label>
			<label index="lockToDomain.description">Enter the host name from which the user is forced to login.</label>
			<label index="groupMods.description">Select available backend modules for the group members.</label>
			<label index="custom_options.description">Select custom permission options.</label>
			<label index=".description">This is the Backend administration user groups available for the Backend users. These determine the access credentials for the Backend users.</label>
			<label index=".details">Groups contain the main permission settings you can set for a backend user. Many users can be members of the same group and thus share permissions.
When a user is a member of many groups (including sub-groups) then the permission settings are added together so that the more groups a user is a member of, the more access is granted to him.</label>
			<label index=".image_descr">Backend Usergroups are found in the root of the page tree where only &quot;admin&quot; users can edit them. The usergroups with red icons in this image are the ones with Access Lists enabled. The blue are just plain usergroups.
This usergroup has Access Lists enabled. In the Access Lists you specify which modules, tables, database fields etc. the group members can access in TYPO3.</label>
			<label index="title.description">Name of the Backend usergroup. The name should be descriptive and can always be changed later.</label>
			<label index="title.details">Backend Usergroups are identified by their &quot;uid&quot; field value (integer) and therefore the title can always be changed. The &quot;uid&quot; can never be changed for a user group.</label>
			<label index="title.image_descr">The usergroup title is shown in the record lists.</label>
			<label index="db_mountpoints.details">The page tree in TYPO3 must have some points-of-entry defined. Here you should insert one or more references to a page which will represent a new root page for the page tree. This is called a &quot;Database mount&quot; or &quot;DB mount&quot;.
DB mounts &lt;i&gt;may&lt;/i&gt; be inherited by the users which are members of this group. This depends on whether the user is configured to include the mounts set in the member groups.
However it's recommended to use backend user groups like this to configure mounts. Especially if they need to be shared among many users.</label>
			<label index="db_mountpoints.image_descr">Here a page is added as a &quot;DB mount&quot;...
... and in the page tree of member users this will become the starting point for the page tree.</label>
			<label index="file_mountpoints.details">The file folder tree is used by all File-submodules to navigate the file folders on the webserver. If you want users to access the servers file system through TYPO3 they need at least one File Mount (and access to eg. File &gt; Filelist module).
You can mount a path in &quot;fileadmin/&quot; relative to the TYPO3 installation or you can mount an absolute path somewhere else on the server (outside webroot!). The last requires that $TYPO3_CONF_VARS[BE][lockRootPath] is defined. The path you mount is defined by the Filemount record you refer to by this field. So a File Mount just points to another record inside of which the details are configured. See screen shots below.
&quot;admin&quot; users always have the &quot;fileadmin/&quot; folder mounted by default.
Notice; as with 'DB mounts' the file folder mounts may be inherited by the users which are members of this group.</label>
			<label index="pagetypes_select.details">This option limits the number of valid choices for the user when he is about to select a page type.
Choice of Page types (doktype) for a page is associated with a) a special icon for the page, b) permitted tables on the page (see $PAGES_TYPES global variable) and c) if the page is a web page or &quot;system folder&quot; type.</label>
			<label index="pagetypes_select.image_descr">The list of typical page types available in a CMS context. Selecting Page types for a usergroup defines which of these options can be selected by member users.</label>
			<label index="description.description">Enter a short description of the user group, what it is for and who should be members. This is for internal use only.</label>
			<label index="TSconfig.description">User TSconfig: Additional configuration through TypoScript style values (Advanced).</label>
			<label index="hide_in_lists.description">This option will prevent the user group from showing up in lists, where user groups are selected.</label>
			<label index="subgroup.description">Select backend user groups which are automatically included for members of this group.</label>
			<label index="file_mountpoints.image_descr">The File Mounts are references to records from the &quot;Filemounts&quot; table.
In the Filemount record you define whether the path should be absolute (must be within $TYPO3_CONF_VARS[BE][lockRootPath]) or relative to &quot;fileadmin/&quot;. In this case the Filemount points to &quot;fileadmin/user_upload/&quot;
This is the page tree of the &quot;admin&quot; user. Notice the folder &quot;user_upload&quot; which is the folder referred to by the File Mount record.
This shows the mounted folder as seen by a user who was member of the group.
Filemount records are also created in the page tree root.</label>
			<label index="tables_modify.details">An important part of setting permissions is to define which database tables a user is allowed to modify.
Tables allowed for modification is automatically also allowed for selection and thus you don't need to set tables entered here in the &quot;Tables (listing)&quot; box.

&lt;strong&gt;Notice&lt;/strong&gt; that this list adds to the fields selected in other member groups of a user.</label>
			<label index="tables_modify.image_descr">The screen shot above shows how the &quot;Create new record&quot; dialog looks for a user limited to editing only &quot;Page&quot; and &quot;Pagecontent&quot; elements.
The two tables are simply added to the list of &quot;Tables (modify)&quot; in the group Access Lists.
This is (an example of) the full amount of elements that can be created on the page by the &quot;admin&quot; user for whom there are no restrictions.</label>
			<label index="tables_select.description">Select which tables the members may see in record lists ('modify' tables does not need to be re-entered here!).</label>
			<label index="tables_select.details">This determines which tables - in addition to those selected in the &quot;Tables (modify)&quot; box - may be viewed and listed for the member users. He is not able to &lt;em&gt;edit&lt;/em&gt; the table - only select the records and view the content.
This list is not very important. It's a pretty rare situation that a user may select tables but not modify them.</label>
			<label index="non_exclude_fields.description">Certain table fields are not available by default. Those fields can be explicitly enabled for the group members here.</label>
			<label index="non_exclude_fields.details">&quot;Allowed excludefields&quot; allows you to detail the permissions granted to tables. By default all these fields are not available to users but must be specifically enabled by being selected here.
One application of this is that pages are usually hidden by default and that the hidden field is not available for a user unless he has been granted access by this list of &quot;Allowed excludefields&quot;. So the user may create a new page, but cannot un-hide the page - unless of course he has been assigned the &quot;Page: Hide page&quot; exclude field through one of his member groups.
Of course it does not make any sense to add fields from tables which are not included in the list of tables allowed to be modified.</label>
			<label index="hidden.details">If you disable a user group all users which are members of the group will in effect not inherit any properties this group may have given them.</label>
			<label index="lockToDomain.details">A TYPO3 system may host multiple websites on multiple domains. Therefore this option secures that users can login only from a certain host name.
Setting this to for example &quot;www.my-domain.com&quot; will require a user to be logged in from that domain if membership of this group should be gained. Otherwise the group will be ignored for the user.</label>
			<label index="groupMods.details">This determines which 'menu items' are available for the group members.
This list of modules is added to any modules selected in other member groups of a user as well as the corresponding field of the user himself.</label>
			<label index="groupMods.image_descr">The Backend Modules available for a user is reflected in the menu items of the backend. For most regular users only modules in the Web and File main modules are enabled. Typically &quot;Web &gt; Page&quot; is used for editing of page content.
This is the assignment of Backend Modules to the user from the screen shot above. All four Web sub-modules and the two User sub-modules are configured here. However the File &gt; Filelist module must have been configured for another member group of this user (or inside the user profile itself which is also possible). The Help modules are all accessible by default and does not require explicit access.</label>
			<label index="explicit_allowdeny.description">Select field values to explicitly deny or allow for user group members.</label>
			<label index="allowed_languages.description">Select which record languages the group members are limited to edit.</label>
			<label index="allowed_languages.details">Records in TYPO3 can be configured to carry information about their language. If that is the case access to these elements will also be evaluated based on whether the user has the language in question included from this list.
If a user has no languages listed all together it simply means that he can edit &lt;em&gt;all&lt;/em&gt; languages!</label>
			<label index="allowed_languages.image_descr">This example shows a situation where two languages, Danish and German, are created in addition to the default language.</label>
			<label index="custom_options.details">This list represents custom permissions introduced by various backend modules (from extensions). The significance of each option depends on the backend module that evaluates it.</label>
			<label index="custom_options.image_descr">This is just an example from an internal test application. It shows how checkboxes are added by a custom module under its own header. You can also show a description text with each checkbox to explain its function.</label>
			<label index="inc_access_lists.description">Select whether the Access Lists for Page type, Tables, Module and Allowed excludefield are enabled for this group.</label>
			<label index="inc_access_lists.details">If this option is disabled the Access Lists cannot be configured for the group.
When Access Lists are disabled the icon for the group is blue while it is red when Access Lists are enabled.</label>
			<label index="TSconfig.syntax">TypoScript syntax without conditions and constants.</label>
			<label index="TSconfig.image_descr">In the TSconfig field help is right at hand - just click the TS wizard icon, then a window will pop up.
In the pop-up window you will see a tree of possible configuration values. These are extracted from the TSconfig manual. You can click around to find the options you need to set through this wizard.</label>
			<label index="TSconfig.details">User TSconfig can be set for each backend user and group. Configuration set for backend groups is inherited by the user who is a member of those groups. The available options typically cover user settings like those found in the User&gt;Setup module (in fact options from that module can be forcibly overridden from User TSconfig!), configuration of the &quot;Admin Panel&quot; (frontend), various backend tweaks (lock user to IP, show shortcut frame, may user clear all cache?, width of the navigation frame etc.) and backend module configuration (overriding any configuration set for backend modules in Page TSconfig).</label>
			<label index="hide_in_lists.details">This will affect the list of user groups in the Task Center To-Do and Messages parts as well as the Web&gt;Access module.
The option is extremely useful if you have general user groups defining some global properties which all your users are members of. Then you would probably not like all those users to 'see' each other through the membership of this group, for instance sending messages or To-Dos to each other. And this is what is option will prevent.</label>
			<label index="subgroup.details">The properties of subgroups are added to the properties of this group and basically they will simply be added to the list of member groups of any user which is a member of this group.
This feature provides a great way to create 'Supervisor' user groups.</label>
			<label index="explicit_allowdeny.details">Selector box fields can be configured for access control on value level. This list represents all values that are configured for access control. 
Each value can be configured to require either explicit access (Allow) or explicit denial (Deny). If a value has the prefix &quot;Allow&quot; (green icon) it means that by default users &lt;em&gt;cannot&lt;/em&gt; set this value unless they are member of a user group which explicitly allows it (by setting this checkbox).
If a value has the prefix &quot;Deny&quot; (red icon) it means that by default users can set this value unless they are member of a user group which explicitly denies it (by setting this checkbox).
The list is organized so values from the same selector box is listed together. If values from a selectorbox is not present in the allow/deny list it simply means they are not evaluated and hence they can be set by anyone having access to the field in general.</label>
		</languageKey>
	</orig_text>
</T3locallangExt>