From 03889ce7e5a3006559920ea368b7378b6fb730de Mon Sep 17 00:00:00 2001 From: lfrost <lfrost@localhost> Date: Mon, 26 Nov 2007 08:50:01 +0000 Subject: [PATCH] Fix for Issue #1961 (reviewed by Josu) * Remove instances of "Specifies the..." * Remove instances of "Indicates that..." * Reword instances of "Specifies to..." (which doesn't really make sense anyway) * Change instances of "This utility may be used..." to "This utility can be used..." as discussed in a previous issue * Change some erroneous instances of "may" to "might" or "can". This might sound like a pointless change but it has implications for localization - "may" is generally ambiguous. --- opends/src/messages/messages/backend.properties | 10 +++++----- 1 files changed, 5 insertions(+), 5 deletions(-) diff --git a/opends/src/messages/messages/backend.properties b/opends/src/messages/messages/backend.properties index e1aa9c3..a8e9215 100644 --- a/opends/src/messages/messages/backend.properties +++ b/opends/src/messages/messages/backend.properties @@ -56,7 +56,7 @@ FATAL_ERR_ROOTDSE_CONFIG_ENTRY_NULL_2=An attempt was made to configure the \ root DSE backend without providing a configuration entry. This is not \ allowed -INFO_ROOTDSE_SUBORDINATE_BASE_DESCRIPTION_3=Specifies the set of base DNs \ +INFO_ROOTDSE_SUBORDINATE_BASE_DESCRIPTION_3=Set of base DNs \ that will be used for singleLevel, wholeSubtree, and subordinateSubtree \ searches based at the root DSE. If this is not provided, then the set of all \ user-defined suffixes will be used @@ -152,7 +152,7 @@ SEVERE_ERR_SCHEMA_CONFIG_ENTRY_NULL_38=An attempt was made to configure the \ schema backend without providing a configuration entry. This is not allowed, \ and no schema information will be available over protocol -INFO_SCHEMA_DESCRIPTION_ENTRY_DN_39=Specifies the DN or set of DNs for the \ +INFO_SCHEMA_DESCRIPTION_ENTRY_DN_39=DN or set of DNs for the \ entries that may be retrieved in order to retrieve the Directory Server \ schema information. Multiple values may be provided if the schema is to be \ available in multiple locations for compatibility purposes. If no value is \ @@ -352,14 +352,14 @@ while attempting to decode recurring task base %s as a DN: %s SEVERE_ERR_TASKBE_CANNOT_DECODE_SCHEDULED_TASK_BASE_DN_115=An error occurred \ while attempting to decode scheduled task base %s as a DN: %s -INFO_TASKBE_DESCRIPTION_RETENTION_TIME_116=Specifies the length of time in \ +INFO_TASKBE_DESCRIPTION_RETENTION_TIME_116=Length of time in \ seconds that task information should be retained after processing on that \ task has completed. Once this period has passed, the task information will \ be automatically removed to conserve memory and disk space SEVERE_ERR_TASKBE_CANNOT_INITIALIZE_RETENTION_TIME_117=An unexpected error \ occurred while attempting to initialize the task retention time \ configuration: %s -INFO_TASKBE_DESCRIPTION_BACKING_FILE_118=Specifies the path to the backing \ +INFO_TASKBE_DESCRIPTION_BACKING_FILE_118=Path to the backing \ file for the task backend. This LDIF file will hold all the configuration \ for the defined scheduled tasks and recurring tasks SEVERE_ERR_TASKBE_CANNOT_INITIALIZE_BACKING_FILE_119=An unexpected error \ @@ -519,7 +519,7 @@ SEVERE_ERR_BACKUP_CANNOT_DECODE_BACKUP_ROOT_DN_172=Unable to initialize the \ backup backend because an error occurred while attempting to decode the base \ DN for the backend: %s -INFO_BACKUP_DESCRIPTION_BACKUP_DIR_LIST_173=Specifies the set of directories \ +INFO_BACKUP_DESCRIPTION_BACKUP_DIR_LIST_173=Set of directories \ that will be accessed by default for search operations in the backup backend. \ Backup directories not in this list may still be accessed by directly \ specifying the backup directory in the search base DN. Changes to this \ -- Gitblit v1.10.0