"_{objectsFound} entry available within the provided Base DN_::_{objectsFound} entries available within the provided Base DN_":["{objectsFound} 基础DN中的可用条目"],
"Switching the mode will enable automatic LDAP queries. Depending on your LDAP size they may take a while. Do you still want to switch the mode?":"切换模式将启用自动 LDAP 查询。根据您的 LDAP 规模，可能需要一段时间。是否继续切换模式？",
"User not found. Please check your login attributes and username. Effective filter (to copy-and-paste for command-line validation): <br/>":"找不到用户。请检查您的登录属性和用户名。有效过滤（复制和粘贴命令行验证）：<br/>",
"The search filter is invalid, probably due to syntax issues like uneven number of opened and closed brackets. Please revise.":"搜索的筛选条件无效，可能是由于不完全开闭括号的句法的问题，请检查。",
"Allows login against the LDAP / AD username, which is either \"uid\" or \"sAMAccountName\" and will be detected.":"允许登录 LDAP/AD 用户名，这是“uid”或“sAMAccountName”，并将被检测到。",
"Defines the filter to apply, when login is attempted. \"%%uid\" replaces the username in the login action. Example: \"uid=%%uid\"":"定义登录时采用的过滤规则。登录时用 \"%%uid\" 替换用户名。例如：\"uid=%%uid\"",
"The DN of the client user with which the bind shall be done, e.g. uid=agent,dc=example,dc=com. For anonymous access, leave DN and Password empty.":"客户端使用的 DN 必须与绑定的相同，比如 uid=agent,dc=example,dc=com。如需匿名访问，将 DN 和密码保留为空。",
"The most common object classes for users are organizationalPerson, person, user, and inetOrgPerson. If you are not sure which object class to select, please consult your directory admin.":"用户最常用的对象类为 organizationalPerson，person，user 和 inetOrgPerson。如果您不确定选择哪些对象类，请咨询您的目录管理员。",
"The filter specifies which LDAP users shall have access to the %s instance.":"该筛选条件指定哪些LDAP用户有权访问 %s 的实例。",
"<b>Warning:</b> The PHP LDAP module is not installed, the backend will not work. Please ask your system administrator to install it.":"<b>警告：</b> PHP LDAP 模块未安装，后端将无法工作。请请求您的系统管理员安装该模块。",
"Connection Settings":"连接设置",
"Configuration Active":"现行配置",
"When unchecked, this configuration will be skipped.":"当反选后，此配置将被忽略。",
"Turn off SSL certificate validation.":"关闭 SSL 证书验证",
"Not recommended, use it for testing only! If connection only works with this option, import the LDAP server's SSL certificate in your %s server.":"不推荐，只用于测试！如果连接只使用此选项工作，导入您的%s服务器 LDAP 服务器的 SSL 证书。",
"Optional. An LDAP attribute to be added to the display name in brackets. Results in e.g. »John Doe (john.doe@example.org)«.":"可选项。LDAP 属性被添加到显示名称的括号内。例如 »John Doe (john.doe@example.org)«。",
"The LDAP attribute that on group objects contains an LDAP search URL that determines what objects belong to the group. (An empty setting disables dynamic group membership functionality.)":"LDAP 组对象属性，包含用于确定属于该组对象的 LDAP 搜索 URL。（空设置禁用动态组成员的功能。）",
"When switched on, groups that contain groups are supported. (Only works if the group member attribute contains DNs.)":"当选择后，包含组的组将启用。（只有当组成员属性包含 DN 时有效。）",
"Chunksize used for paged LDAP searches that may return bulky results like user or group enumeration. (Setting it 0 disables paged LDAP searches in those situations.)":"用于在 LDAP 搜索返回如用户或组枚举结果时进行分页显示。（设置它为0时，禁止在这些情况下分页 LDAP 搜索。）",
"Allow LDAP users to change their password and allow Super Administrators and Group Administrators to change the password of their LDAP users. Only works when access control policies are configured accordingly on the LDAP server. As passwords are sent in plaintext to the LDAP server, transport encryption must be used and password hashing should be configured on the LDAP server.":"允许 LDAP 用户更改其密码，并允许超级管理员和组管理员更改 LDAP 用户的密码。仅在 LDAP 服务器上相应配置访问控制策略时有效。由于密码以纯文本形式发送到 LDAP 服务器，因此必须使用传输加密，并在LDAP服务器上配置散列密码。",
"(New password is sent as plain text to LDAP)":"（新的密码将以纯文本形式发送到 LDAP）",
"Default password policy DN":"默认的密码规则 DN",
"The DN of a default password policy that will be used for password expiry handling. Works only when LDAP password changes per user are enabled and is only supported by OpenLDAP. Leave empty to disable password expiry handling.":"用于密码过期处理的默认密码策略的 DN。只有当 LDAP 密码修改并且用户启用的情况下有效，仅支持 OpenLDAP。留空以禁用密码过期处理。",
"By default the internal username will be created from the UUID attribute. It makes sure that the username is unique and characters do not need to be converted. The internal username has the restriction that only these characters are allowed: [ a-zA-Z0-9_.@- ]. Other characters are replaced with their ASCII correspondence or simply omitted. On collisions a number will be added/increased. The internal username is used to identify a user internally. It is also the default name for the user home folder. It is also a part of remote URLs, for instance for all *DAV services. With this setting, the default behavior can be overridden. Leave it empty for default behavior. Changes will have effect only on newly mapped (added) LDAP users.":"默认情况下将从 UUID 属性创建内部用户名。将确保用户名是唯一的字符，并且不需要转换。内部用户名，只允许使用这些字符：[a-zA-Z0-9 _。@ - ]。其他字符被替换为它们的 ASCII 对应或简单地被忽略。如果出现重复，将添加或增加一个数字。内部用户名用于在内部标识用户。它是用户主文件夹的默认名称。它也是远程URL的一部分，例如对于所有 *DAV 服务。使用此设置，可以覆盖默认行为。默认行为为空，则更改只会对新映射（已添加）的LDAP用户有效。",
"By default, the UUID attribute is automatically detected. The UUID attribute is used to doubtlessly identify LDAP users and groups. Also, the internal username will be created based on the UUID, if not specified otherwise above. You can override the setting and pass an attribute of your choice. You must make sure that the attribute of your choice can be fetched for both users and groups and it is unique. Leave it empty for default behavior. Changes will have effect only on newly mapped (added) LDAP users and groups.":"ownCloud 默认会自动检测 UUID 属性。UUID 属性用来无误地识别 LDAP 用户和组。同时，如果上面没有特别设置，内部用户名也基于 UUID 创建。也可以覆盖设置，直接指定一个属性。但一定要确保指定的属性取得的用户和组是唯一的。留空，则执行默认操作。更改只影响新映射（或增加）的 LDAP 用户和组。",
"Usernames are used to store and assign metadata. In order to precisely identify and recognize users, each LDAP user will have an internal username. This requires a mapping from username to LDAP user. The created username is mapped to the UUID of the LDAP user. Additionally the DN is cached as well to reduce LDAP interaction, but it is not used for identification. If the DN changes, the changes will be found. The internal username is used all over. Clearing the mappings will have leftovers everywhere. Clearing the mappings is not configuration sensitive, it affects all LDAP configurations! Never clear the mappings in a production environment, only in a testing or experimental stage.":"用户名用于存储和分配元数据。为了精确的区分和识别用户，每个 LDAP 用户都会有一个内部的用户名。这要求建立一个用户名到 LDAP 用户的映射。创建的用户名会被映射到 LDAP 用户的 UUID。另外为了节省 LDAP 连接开销，DN 会被缓存，但不会用于识别。如果 DN 变了，这些变化会被识别到。在 Nextcloud 各个页面会使用内部用户名。清空映射会造成系统里面有大量的残留信息。清空映射会影响所有的 LDAP 配置，而不仅仅是当前配置。不要在生产环境里面应用清空映射，请仅用于测试环境或者早期验证步骤。",
