From 555309d7a9194718ed62f5d1ef492b53bde0a236 Mon Sep 17 00:00:00 2001 From: Ludovic Poitou <ludovic.poitou@forgerock.com> Date: Thu, 20 Oct 2011 15:34:00 +0000 Subject: [PATCH] Fix OpenDJ-222: Remove more references to OpenDS. This time we cleanup messages, and localized messages. --- opendj-sdk/opends/src/admin/messages/RootCfgDefn_ko.properties | 14 +++++++------- 1 files changed, 7 insertions(+), 7 deletions(-) diff --git a/opendj-sdk/opends/src/admin/messages/RootCfgDefn_ko.properties b/opendj-sdk/opends/src/admin/messages/RootCfgDefn_ko.properties index 32d040e..daf74e8 100644 --- a/opendj-sdk/opends/src/admin/messages/RootCfgDefn_ko.properties +++ b/opendj-sdk/opends/src/admin/messages/RootCfgDefn_ko.properties @@ -1,6 +1,6 @@ user-friendly-name=Root user-friendly-plural-name=Roots -synopsis=The root configuration provides an entry point to the rest of the OpenDJ configuration. +synopsis=The root configuration provides an entry point to the rest of the OpenDJ configuration. tag.core-server.synopsis=Core server tag.database.synopsis=Caching and back-ends tag.logging.synopsis=Logging @@ -8,8 +8,8 @@ tag.security.synopsis=Authentication and authorization tag.user-management.synopsis=User management relation.access-control-handler.user-friendly-name=Access Control Handler -relation.access-control-handler.synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time. -relation.access-control-handler.description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled. +relation.access-control-handler.synopsis=Access Control Handlers manage the application-wide access control. The OpenDJ access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time. +relation.access-control-handler.description=Note that OpenDJ also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled. relation.account-status-notification-handler.user-friendly-name=Account Status Notification Handler relation.account-status-notification-handler.user-friendly-plural-name=Account Status Notification Handlers relation.account-status-notification-handler.synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change. @@ -45,7 +45,7 @@ relation.extension.synopsis=The Extension allows to extend the configuration with new type of objects. relation.extension.description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object. relation.global-configuration.user-friendly-name=Global Configuration -relation.global-configuration.synopsis=The Global contains properties that affect the overall operation of the OpenDJ . +relation.global-configuration.synopsis=The Global contains properties that affect the overall operation of the OpenDJ. relation.group-implementation.user-friendly-name=Group Implementation relation.group-implementation.user-friendly-plural-name=Group Implementations relation.group-implementation.synopsis=Group Implementations define named collections of users. @@ -102,12 +102,12 @@ relation.root-dse-backend.description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes. relation.sasl-mechanism-handler.user-friendly-name=SASL Mechanism Handler relation.sasl-mechanism-handler.user-friendly-plural-name=SASL Mechanism Handlers -relation.sasl-mechanism-handler.synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDJ . +relation.sasl-mechanism-handler.synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDJ. relation.sasl-mechanism-handler.description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind. relation.synchronization-provider.user-friendly-name=Synchronization Provider relation.synchronization-provider.user-friendly-plural-name=Synchronization Providers -relation.synchronization-provider.synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories. -relation.synchronization-provider.description=The OpenDJ takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments. +relation.synchronization-provider.synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDJ instances or other data repositories. +relation.synchronization-provider.description=The OpenDJ takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDJ, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments. relation.trust-manager-provider.user-friendly-name=Trust Manager Provider relation.trust-manager-provider.user-friendly-plural-name=Trust Manager Providers relation.trust-manager-provider.synopsis=Trust Manager Providers determine whether to trust presented certificates. -- Gitblit v1.10.0