"_{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/>",
"Consider narrowing your search, as it encompassed many users, only the first one of whom will be able to log in.":"如返回結果太多可考慮進一步縮小搜尋範圍，僅返回的第一個用戶可以登入。",
"The search filter is invalid, probably due to syntax issues like uneven number of opened and closed brackets. Please revise.":"搜尋過濾器無效，可能是由於語法問題引起的，例如，方括號的數量不均勻。 請修改。",
"This application enables administrators to connect Nextcloud to an LDAP-based user directory for authentication and provisioning users, groups and user attributes. Admins can configure this application to connect to one or more LDAP directories or Active Directories via an LDAP interface. Attributes such as user quota, email, avatar pictures, group memberships and more can be pulled into Nextcloud from a directory with the appropriate queries and filters.\n\nA user logs into Nextcloud with their LDAP or AD credentials, and is granted access based on an authentication request handled by the LDAP or AD server. Nextcloud does not store LDAP or AD passwords, rather these credentials are used to authenticate a user and then Nextcloud uses a session for the user ID. More information is available in the LDAP User and Group Backend documentation.":"本應用啟用功能使管理員可將 Nextcloud 與基於 LDAP 的用戶目錄連接，進行身分驗證以及提供用戶、群組和用戶屬性。管理員可配置此程序通過 LDAP 接口連接至一個或多個 LDAP 或 Active Directory 目錄。通過適當的查詢和篩選，可將以下屬性從目錄導入 Nextcloud：用戶磁盤配額、電子郵箱、頭像、所屬群組以及更多。 用戶可以用其LDAP或AD中的身分登入 Nextcloud， 並根據 LDAP 或 AD 服務的身分驗證獲得訪問權限。Nextcloud 僅使用身分驗證隨後為用戶身分使用會話，但不會儲存LDAP或AD的密碼。您可從 LDAP 用戶及群組後台文檔中獲取更多信息。",
"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。如果不確定要選擇哪個對像類，請諮詢您的目錄管理員。",
"<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.":"沒有被勾選時，此設定會被略過。",
"Backup (Replica) Host":"備用主機",
"Give an optional backup host. It must be a replica of the main LDAP/AD server.":"可以選擇性設定備用主機，必須是 LDAP/AD 中央伺服器的複本。",
"Backup (Replica) Port":"備用（複本）連接埠",
"Disable Main Server":"停用主伺服器",
"Only connect to the replica server.":"只能連線至複製伺服器。",
"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.":"不建議，請僅在測試時使用！如果連線只能在此設定下工作，請匯入LDAP伺服器的SSL認證到您的伺服器%s上",
"Cache Time-To-Live":"快取的存活時間",
"in seconds. A change empties the cache.":"以秒為單位。變更後會清空快取。",
"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，該URL確定哪些對象屬於該群組。（空白設置將禁用動態群組成員資格功能。）",
"Nested Groups":"嵌套群組",
"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 搜尋所用的 chunksize 可能會返回大量結果，例如用戶或組枚舉。（在這種情況下，將其設置為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 伺服器上配置密碼 hashing。",
"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. Changes will have effect only on newly mapped (added) LDAP users. Leave it empty for default behavior.":"默認情況下，內部用戶名將從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.":"預設情況下，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配置，同時進行雙向配置。不要在生產環境裡面應用可變映射，請僅用於測試環境或早期驗證步驟。",
"Clear Groupname-LDAP Group Mapping":"清除 群組名稱-LDAP 群組 Mapping",
"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用戶有效。"
