"No object found in the given Base DN. Please revise.":"在 Base DN 中找不到物件。請修改",
"More than 1,000 directory entries available.":"超過 1,000 個目錄項目可用。",
"_{objectsFound} entry available within the provided Base DN_::_{objectsFound} entries available within the provided Base DN_":["提供的 Base DN 中有 {objectsFound} 個項目"],
"An error occurred. Please check the Base DN, as well as connection settings and credentials.":"遇到錯誤。請檢查 Base DN、連線設定與憑證。",
"Error while clearing the mappings.":"清除映射時發生錯誤。",
"Anonymous bind is not allowed. Please provide a User DN and Password.":"不允許匿名綁定。請提供使用者 DN 與密碼。",
"LDAP Operations error. Anonymous bind might not be allowed.":"LDAP 操作錯誤。可能不允許匿名綁定。",
"Saving failed. Please make sure the database is in Operation. Reload before continuing.":"儲存失敗。請確保資料庫可以運作。繼續前請重新載入。",
"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/>",
"User found and settings verified.":"使用者存在，設定值正確。",
"Consider narrowing your search, as it encompassed many users, only the first one of whom will be able to log in.":"考慮縮小範圍，因為其涵蓋了許多使用者，但只有第一個才能登入。",
"An unspecified error occurred. Please check log and settings.":"發生不明錯誤。請檢查紀錄檔與設定。",
"The search filter is invalid, probably due to syntax issues like uneven number of opened and closed brackets. Please revise.":"搜尋過濾條件無效，可能是語法問題引起的，如括號不對稱等。請修改。",
"Please provide a login name to test against":"請提供登入名稱以便再次測試",
"Password change rejected. Hint: ":"密碼變更被拒絕。提示：",
"Please login with the new password":"請以新密碼登入",
"LDAP User backend":"LDAP 使用者後端",
"Your password will expire tomorrow.":"您的密碼將於明天到期。",
"Your password will expire today.":"您的密碼將於今天到期。",
"_Your password will expire within %n day._::_Your password will expire within %n days._":["您的密碼將於%n天後到期。"],
"Could not detect user display name attribute. Please specify it yourself in advanced LDAP settings.":"偵測不到使用者顯示名稱屬性。請在進階 LDAP 設定中自行指定。",
"Could not find the desired feature":"找不到所需的功能",
"Invalid Host":"無效的主機",
"LDAP user and group backend":"LDAP 使用者與群組後端",
"This application enables administrators to connect Nextcloud to an LDAP-based user directory.":"此應用程式讓管理員可以將 Nextcloud 連線到以 LDAP 為基礎的使用者目錄。",
"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 Directories。如使用者配額、電子郵件、大頭照圖片、群組成員資格等屬性可以透過有適當查詢與過濾條件的目錄從 Nextcloud 拉取。\n\n使用者以其 LDAP 或 AD 憑證登入 Nextcloud，並根據 LDAP 或 AD 伺服器處理的身份驗證請求來授予存取權限。Nextcloud 並不儲存 LDAP 或 AD 的密碼，而是使用這些憑證來對使用者進行身份驗證，然後 Nextcloud 會使用工作階段作為使用者 ID。更多資訊在 LDAP 使用者與群組後端文件中提供。",
"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 模組，後端系統將無法運作。請要求您的系統管理員安裝它。",
"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 上。",
"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)«。",
"Dynamic Group Member URL":"Dynamic Group Member URL",
"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":"Nested Groups",
"When switched on, groups that contain groups are supported. (Only works if the group member attribute contains DNs.)":"啟用後，將會支援包含群組的群組。（僅在群組成員屬性包含 DN 時可正常運作。）",
"Paging chunksize":"分頁區塊大小",
"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 搜尋。）",
"Enable LDAP password changes per user":"啟用每個使用者的 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. 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 使用者及群組生效。",
"UUID Attribute for Users:":"使用者的 UUID 屬性：",
"UUID Attribute for Groups:":"群組的 UUID 屬性：",
"Username-LDAP User Mapping":"使用者-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。另外，DN 會被快取以減少 LDAP 互動，但不會用於識別。若 DN 變更，將會找到變更。內部使用者名稱將會全面使用。清除映射將會讓到處都是未連結的項目。清除映射對設定並不敏感，其會影響到所有 LDAP 設定！不要在生產環境中清除映射，僅將其用於測試或實驗階段。",
"Clear Username-LDAP User Mapping":"清除使用者名稱-LDAP 使用者映射",
"A connection error to LDAP / AD occurred, please check host, port and credentials.":"發生 LDAP / AD 的連線錯誤，請檢查主機、連接埠與憑證。",
"The \"%uid\" placeholder is missing. It will be replaced with the login name when querying LDAP / AD.":"「%uid」佔位字串遺失。查詢 LDAP / AD 時將會使用登入名稱取代。",
"The group box was disabled, because the LDAP / AD server does not support memberOf.":"因為 LDAP / AD 伺服器不支援 memberOf，所以停用群組盒。",
"LDAP / AD integration":"LDAP / AD 整合",
"LDAP / AD Username:":"LDAP / AD 使用者名稱：",
"Allows login against the LDAP / AD username, which is either \"uid\" or \"sAMAccountName\" and will be detected.":"允許使用 LDAP / AD 使用者名稱登入，可以是 \"uid\" 或 \"sAMAccountName\"。",
"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 使用者有效。"
