aboutsummaryrefslogtreecommitdiffstats
path: root/apps/user_ldap/l10n/en_GB.json
diff options
context:
space:
mode:
authorNextcloud bot <bot@nextcloud.com>2018-04-10 00:12:10 +0000
committerNextcloud bot <bot@nextcloud.com>2018-04-10 00:12:10 +0000
commit323ee3cbdc420f1009b6eb64b2df0f878ff39a14 (patch)
treefd370a332259b18c94a7cd5855f157efdfed3da3 /apps/user_ldap/l10n/en_GB.json
parentc4c6943c1ede4fc3f31c08fd52434de4478ea5f5 (diff)
downloadnextcloud-server-323ee3cbdc420f1009b6eb64b2df0f878ff39a14.tar.gz
nextcloud-server-323ee3cbdc420f1009b6eb64b2df0f878ff39a14.zip
[tx-robot] updated from transifex
Diffstat (limited to 'apps/user_ldap/l10n/en_GB.json')
-rw-r--r--apps/user_ldap/l10n/en_GB.json4
1 files changed, 2 insertions, 2 deletions
diff --git a/apps/user_ldap/l10n/en_GB.json b/apps/user_ldap/l10n/en_GB.json
index f45e625b33a..69c29fec259 100644
--- a/apps/user_ldap/l10n/en_GB.json
+++ b/apps/user_ldap/l10n/en_GB.json
@@ -182,11 +182,11 @@
"UUID Attribute for Users:" : "UUID Attribute for Users:",
"UUID Attribute for Groups:" : "UUID Attribute for Groups:",
"Username-LDAP User Mapping" : "Username-LDAP User Mapping",
- "Usernames are used to store and assign (meta) data. 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 (meta) data. In order to precisely identify and recognise 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",
" entries available within the provided Base DN" : " entries available within the provided Base DN",
"LDAP" : "LDAP",
- "<b>Warning:</b> Apps user_ldap and user_webdavauth are incompatible. You may experience unexpected behavior. Please ask your system administrator to disable one of them." : "<b>Warning:</b> Apps user_ldap and user_webdavauth are incompatible. You may experience unexpected behavior. Please ask your system administrator to disable one of them."
+ "<b>Warning:</b> Apps user_ldap and user_webdavauth are incompatible. You may experience unexpected behavior. Please ask your system administrator to disable one of them." : "<b>Warning:</b> Apps user_ldap and user_webdavauth are incompatible. You may experience unexpected behavior. Please ask your system administrator to disable one of them.",
+ "Usernames are used to store and assign (meta) data. 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 (meta) data. In order to precisely identify and recognise 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."
},"pluralForm" :"nplurals=2; plural=(n != 1);"
} \ No newline at end of file