diff options
| author | Nextcloud bot <bot@nextcloud.com> | 2024-02-14 00:19:31 +0000 |
|---|---|---|
| committer | Nextcloud bot <bot@nextcloud.com> | 2024-02-14 00:19:31 +0000 |
| commit | fea2277b632ff724856bee182ed1ab28e7c446f5 (patch) | |
| tree | 33bf918ea5f6dcba103ba3a5ac3cb73ed650e73b /apps/user_ldap/l10n/ka.json | |
| parent | 6f1d9eb11880efb900370f1e6857f05dbef5f84a (diff) | |
| download | nextcloud-server-fea2277b632ff724856bee182ed1ab28e7c446f5.tar.gz nextcloud-server-fea2277b632ff724856bee182ed1ab28e7c446f5.zip | |
Fix(l10n): Update translations from Transifex
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
Diffstat (limited to 'apps/user_ldap/l10n/ka.json')
| -rw-r--r-- | apps/user_ldap/l10n/ka.json | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/apps/user_ldap/l10n/ka.json b/apps/user_ldap/l10n/ka.json index aa9b0491e0f..bc775eba946 100644 --- a/apps/user_ldap/l10n/ka.json +++ b/apps/user_ldap/l10n/ka.json @@ -61,7 +61,6 @@ "LDAP/AD integration" : "LDAP/AD integration", "Invalid LDAP UUIDs" : "Invalid LDAP UUIDs", "None found" : "None found", - "Invalid UUIDs of LDAP users or groups have been found. Please review your \"Override UUID detection\" settings in the Expert part of the LDAP configuration and use \"occ ldap:update-uuid\" to update them." : "Invalid UUIDs of LDAP users or groups have been found. Please review your \"Override UUID detection\" settings in the Expert part of the LDAP configuration and use \"occ ldap:update-uuid\" to update them.", "_%n group found_::_%n groups found_" : ["%n group found","%n groups found"], "> 1000 groups found" : "> 1000 groups found", "> 1000 users found" : "> 1000 users found", @@ -215,6 +214,7 @@ "Username-LDAP User Mapping" : "Username-LDAP User 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." : "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.", "Clear Username-LDAP User Mapping" : "Clear Username-LDAP User Mapping", - "Clear Groupname-LDAP Group Mapping" : "Clear Groupname-LDAP Group Mapping" + "Clear Groupname-LDAP Group Mapping" : "Clear Groupname-LDAP Group Mapping", + "Invalid UUIDs of LDAP users or groups have been found. Please review your \"Override UUID detection\" settings in the Expert part of the LDAP configuration and use \"occ ldap:update-uuid\" to update them." : "Invalid UUIDs of LDAP users or groups have been found. Please review your \"Override UUID detection\" settings in the Expert part of the LDAP configuration and use \"occ ldap:update-uuid\" to update them." },"pluralForm" :"nplurals=2; plural=(n!=1);" }
\ No newline at end of file |