[tx-robot] updated from transifex

Signed-off-by: Nextcloud bot <bot@nextcloud.com>

1 files changed, 1 insertions, 9 deletions

diff --git a/apps/user_ldap/l10n/zh_HK.js b/apps/user_ldap/l10n/zh_HK.js
index d6163b7c5a4..4fa4af97fa4 100644
--- a/apps/user_ldap/l10n/zh_HK.js
+++ b/apps/user_ldap/l10n/zh_HK.js
@@ -189,14 +189,6 @@ OC.L10N.register(
     "Username-LDAP User Mapping" : "用戶名-LDAP 用戶 Mapping",
     "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 Username-LDAP User Mapping" : "清除 用戶名-LDAP 用戶 Mapping",
-    "Clear Groupname-LDAP Group Mapping" : "清除 群組名稱-LDAP 群組 Mapping",
-    "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 伺服器並不支援",
-    "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”。",
-    "LDAP / AD Email Address:" : "LDAP / AD 電郵地址：",
-    "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用戶有效。"
+    "Clear Groupname-LDAP Group Mapping" : "清除 群組名稱-LDAP 群組 Mapping"
 },
 "nplurals=1; plural=0;");