From 88153a926cb3e096a7e681119e585a5c55ca1d68 Mon Sep 17 00:00:00 2001 From: shankar_mbn <shankar_mbn@localhost> Date: Mon, 30 Mar 2009 06:21:19 +0000 Subject: [PATCH] OpenDS precommit Fixes: Addition of Localized resource files with new translations --- opends/src/messages/messages/backend_es.properties | 52 +++++++++++++++++++++++++++++++++++++++++++++------- 1 files changed, 45 insertions(+), 7 deletions(-) diff --git a/opends/src/messages/messages/backend_es.properties b/opends/src/messages/messages/backend_es.properties index e64cf4b..9cf11fc 100644 --- a/opends/src/messages/messages/backend_es.properties +++ b/opends/src/messages/messages/backend_es.properties @@ -48,7 +48,7 @@ # ORDINAL is an integer unique among other ordinals in this file # FATAL_ERR_BACKEND_CANNOT_REMOVE_MULTIBASE_SUB_SUFFIX_1=An attempt was made to de-register sub-suffix "%s" from the backend with suffix "%s". However, the subordinate backend containing that sub-suffix also contains additional sub-suffixes and may not be de-registered. It may be possible to remove this sub-suffix by editing the configuration for the subordinate backend with which it is associated -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 +FATAL_ERR_ROOTDSE_CONFIG_ENTRY_NULL_2=An attempt was made to configure the root DSE backend without providing a configuration entry. Esto no est\u00e1 permitido INFO_ROOTDSE_SUBORDINATE_BASE_DESCRIPTION_3=El conjunto de ND de base que se utilizar\u00e1 para las b\u00fasquedas "singleLevel" (un solo nivel), "wholeSubtree" (todo el \u00e1rbol) y "subordinateSubtree" (\u00e1rbol subordinado) en funci\u00f3n del DSE ra\u00edz. Si no se especifica esta opci\u00f3n, se utilizar\u00e1 el conjunto de todos los sufijos definidos por el usuario SEVERE_WARN_ROOTDSE_NO_BACKEND_FOR_SUBORDINATE_BASE_4=Base DN "%s" is configured as one of the subordinate base DNs to use for searches below the root DSE. However, this base DN is not handled by any suffix registered with the Directory Server and will therefore not be used SEVERE_WARN_ROOTDSE_SUBORDINATE_BASE_EXCEPTION_5=An unexpected problem occurred while trying to determine the set of subordinate base DNs to use for searches below the root DSE: %s @@ -124,7 +124,7 @@ SEVERE_ERR_SCHEMA_RESTORE_CANNOT_RENAME_CURRENT_DIRECTORY_76=Unable to restore schema backup %s because an error occurred while attempting to rename the current schema directory from %s to %s: %s NOTICE_SCHEMA_RESTORE_RESTORED_OLD_SCHEMA_77=Se ha producido un error que impide que se restablezca correctamente la copia de seguridad del esquema. Sin embargo, los archivos de esquema originales, presentes al inicio del proceso de restablecimiento, se han conservado y se encuentran actualmente en su ubicaci\u00f3n original %s SEVERE_ERR_SCHEMA_RESTORE_CANNOT_RESTORE_OLD_SCHEMA_78=Se ha producido un error que impide que se restablezca correctamente la copia de seguridad del esquema. The original schema files that were in place before the start of the restore process have been preserved and are contained in the %s directory -SEVERE_ERR_SCHEMA_RESTORE_CANNOT_CREATE_SCHEMA_DIRECTORY_79=Unable to restore schema backup %s because an error occurred while attempting to create a new empty directory %s into which the files should be restored: %s +SEVERE_ERR_SCHEMA_RESTORE_CANNOT_CREATE_SCHEMA_DIRECTORY_79=Unable to restore schema backup %s or % s because an error occurred while attempting to create a new empty directory %s into which the files should be restored: %s SEVERE_ERR_SCHEMA_RESTORE_OLD_SCHEMA_SAVED_80=Se ha producido un error que impide que se restablezca correctamente la copia de seguridad del esquema. The original schema files that were in place before the start of the restore process have been preserved in the %s directory SEVERE_ERR_SCHEMA_RESTORE_CANNOT_GET_ZIP_ENTRY_81=Unable to restore or verify schema backup %s because an error occurred while trying to read the next entry from the archive file %s: %s SEVERE_ERR_SCHEMA_RESTORE_CANNOT_CREATE_FILE_82=Unable to restore schema backup %s because an error occurred while trying to recreate file %s: %s @@ -149,10 +149,10 @@ SEVERE_ERR_RECURRINGTASK_MULTIPLE_ID_TYPES_101=The provided recurring task entry contains multiple attributes with type %s, which is used to hold the recurring task ID, but only a single instance is allowed SEVERE_ERR_RECURRINGTASK_NO_ID_102=The provided recurring task entry does not contain any values for the %s attribute, which is used to specify the recurring task ID SEVERE_ERR_RECURRINGTASK_MULTIPLE_ID_VALUES_103=The provided recurring task entry contains multiple values for the %s attribute, which is used to specify the recurring task ID, but only a single value is allowed -SEVERE_ERR_RECURRINGTASK_NO_CLASS_ATTRIBUTE_104=The provided recurring task entry does not contain attribute %s which is needed to specify the fully-qualified name of the class providing the task logic -SEVERE_ERR_RECURRINGTASK_MULTIPLE_CLASS_TYPES_105=The provided recurring task entry contains multiple attributes with type %s, which is used to hold the task class name, but only a single instance is allowed -SEVERE_ERR_RECURRINGTASK_NO_CLASS_VALUES_106=The provided recurring task entry does not contain any values for the %s attribute, which is used to specify the fully-qualified name of the class providing the task logic -SEVERE_ERR_RECURRINGTASK_MULTIPLE_CLASS_VALUES_107=The provided recurring task entry contains multiple values for the %s attribute, which is used to specify the task class name, but only a single value is allowed +SEVERE_ERR_RECURRINGTASK_NO_SCHEDULE_ATTRIBUTE_104=The provided recurring task entry does not contain attribute %s which is needed to specify recurring task schedule +SEVERE_ERR_RECURRINGTASK_MULTIPLE_SCHEDULE_TYPES_105=The provided recurring task entry contains multiple attributes with type %s, which is used to hold recurring task schedule, but only a single instance is allowed +SEVERE_ERR_RECURRINGTASK_NO_SCHEDULE_VALUES_106=The provided recurring task entry does not contain any values for the %s attribute, which is used to specify recurring task schedule +SEVERE_ERR_RECURRINGTASK_MULTIPLE_SCHEDULE_VALUES_107=The provided recurring task entry contains multiple values for the %s attribute, which is used to specify recurring task schedule, but only a single value is allowed SEVERE_ERR_RECURRINGTASK_CANNOT_LOAD_CLASS_108=An error occurred while attempting to load class %s specified in attribute %s of the provided recurring task entry: %s. Does this class exist in the Directory Server classpath? SEVERE_ERR_RECURRINGTASK_CANNOT_INSTANTIATE_CLASS_AS_TASK_109=An error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s? SEVERE_ERR_RECURRINGTASK_CANNOT_INITIALIZE_INTERNAL_110=An error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %s @@ -198,7 +198,7 @@ SEVERE_ERR_TASKSCHED_CANNOT_INSTANTIATE_CLASS_AS_TASK_150=An error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s? SEVERE_ERR_TASKSCHED_CANNOT_INITIALIZE_INTERNAL_151=An error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %s SEVERE_WARN_TASKSCHED_CANNOT_RENAME_CURRENT_BACKING_FILE_152=An error occurred while attempting to rename the current tasks backing file from %s to %s: %s. The previous task configuration (which does not reflect the latest update) may be lost -SEVERE_ERR_TASKSCHED_CANNOT_RENAME_NEW_BACKING_FILE_153=An error occurred while attempting to rename the new tasks backing file from %s to %s: %s. If the Directory Server is restarted, then the task scheduler may not be able to +SEVERE_ERR_TASKSCHED_CANNOT_RENAME_NEW_BACKING_FILE_153=An error occurred while attempting to rename the new tasks backing file from %s to %s: %s. If the Directory Server is restarted, then the task scheduler may not work as expected SEVERE_ERR_TASKSCHED_CANNOT_WRITE_BACKING_FILE_154=An error occurred while attempting to write the new tasks data backing file %s: %s. Configuration information reflecting the latest update may be lost SEVERE_ERR_TASKBE_IMPORT_NOT_SUPPORTED_155=The task backend does not support LDIF import operations INFO_TASKBE_INTERRUPTED_BY_SHUTDOWN_156=Se est\u00e1 cerrando el servidor de fondo de tareas @@ -416,3 +416,41 @@ MILD_ERR_HAS_SUBORDINATES_NOT_SUPPORTED_368=Este servidor de fondo no proporciona compatibilidad con el atributo operativo "hasSubordinates" MILD_ERR_NUM_SUBORDINATES_NOT_SUPPORTED_369=Este servidor de fondo no proporciona compatibilidad con el atributo operativo "numSubordinates" NOTICE_BACKEND_OFFLINE_370=El servidor de fondo %s se ha establecido sin conexi\u00f3n +SEVERE_ERR_RECURRINGTASK_INVALID_N_TOKENS_371=The provided recurring task entry attribute %s holding the recurring task schedule has invalid number of tokens +SEVERE_ERR_RECURRINGTASK_INVALID_MINUTE_TOKEN_372=The provided recurring task entry attribute %s holding the recurring task schedule has invalid minute token +SEVERE_ERR_RECURRINGTASK_INVALID_HOUR_TOKEN_373=The provided recurring task entry attribute %s holding the recurring task schedule has invalid hour token +SEVERE_ERR_RECURRINGTASK_INVALID_DAY_TOKEN_374=The provided recurring task entry attribute %s holding the recurring task schedule has invalid day of the month token +SEVERE_ERR_RECURRINGTASK_INVALID_MONTH_TOKEN_375=The provided recurring task entry attribute %s holding the recurring task schedule has invalid month of the year token +SEVERE_ERR_RECURRINGTASK_INVALID_WEEKDAY_TOKEN_376=The provided recurring task entry attribute %s holding the recurring task schedule has invalid day of the week token +SEVERE_ERR_RECURRINGTASK_INVALID_TOKENS_COMBO_377=The provided recurring task entry attribute %s holding the recurring task schedule has invalid tokens combination yielding a nonexistent calendar date +SEVERE_ERR_TASKS_CANNOT_EXPORT_TO_FILE_378=An error occurred while attempting to export task backend data: %s +SEVERE_ERR_TASKS_BACKUP_CANNOT_GET_MAC_379=An error occurred while attempting to obtain the %s MAC provider to create the signed hash for the backup: %s +SEVERE_ERR_TASKS_BACKUP_CANNOT_GET_DIGEST_380=An error occurred while attempting to obtain the %s message digest to create the hash for the backup: %s +SEVERE_ERR_TASKS_BACKUP_CANNOT_CREATE_ARCHIVE_FILE_381=An error occurred while trying to create the tasks archive file %s in directory %s: %s +SEVERE_ERR_TASKS_BACKUP_CANNOT_GET_CIPHER_382=An error occurred while attempting to obtain the cipher to use to encrypt the backup: %s +SEVERE_ERR_TASKS_BACKUP_ZIP_COMMENT_383=%s tasks backup %s +SEVERE_ERR_TASKS_BACKUP_CANNOT_BACKUP_TASKS_FILE_384=An error occurred while attempting to back up tasks file %s: %s +SEVERE_ERR_TASKS_BACKUP_CANNOT_CLOSE_ZIP_STREAM_385=An error occurred while trying to close the tasks archive file %s in directory %s: %s +SEVERE_ERR_TASKS_BACKUP_CANNOT_UPDATE_BACKUP_DESCRIPTOR_386=An error occurred while attempting to update the backup descriptor file %s with information about the tasks backup: %s +SEVERE_ERR_TASKS_RESTORE_NO_SUCH_BACKUP_387=Unable to restore or verify tasks backup %s in directory %s because no such backup exists +SEVERE_ERR_TASKS_RESTORE_NO_BACKUP_FILE_388=Unable to restore or verify tasks backup %s in directory %s because the archive filename could not be determined +SEVERE_ERR_TASKS_RESTORE_NO_SUCH_FILE_389=Unable to restore or verify tasks backup %s because the specified archive file %s does not exist +SEVERE_ERR_TASKS_RESTORE_CANNOT_CHECK_FOR_ARCHIVE_390=Unable to restore or verify tasks backup %s because an error occurred while trying to determine whether backup archive %s exists: %s +SEVERE_ERR_TASKS_RESTORE_UNKNOWN_DIGEST_391=Unable to restore or verify tasks backup %s because an unsigned hash of this backup is available but the server cannot determine the digest algorithm used to generate this hash +SEVERE_ERR_TASKS_RESTORE_CANNOT_GET_DIGEST_392=Unable to restore or verify tasks backup %s because it has an unsigned hash that uses an unknown or unsupported digest algorithm of %s +SEVERE_ERR_TASKS_RESTORE_UNKNOWN_MAC_393=Unable to restore or verify tasks backup %s because a signed hash of this backup is available but the server cannot determine the MAC algorithm used to generate this hash +SEVERE_ERR_TASKS_RESTORE_CANNOT_GET_MAC_394=Unable to restore or verify tasks backup %s because it has a signed hash that uses an unknown or unsupported MAC algorithm of %s +SEVERE_ERR_TASKS_RESTORE_CANNOT_OPEN_BACKUP_FILE_395=Unable to restore or verify tasks backup %s because an error occurred while attempting to open the backup archive file %s: %s +SEVERE_ERR_TASKS_RESTORE_CANNOT_GET_CIPHER_396=Unable to restore or verify tasks backup %s because it is encrypted using an unknown or unsupported cipher: %s +SEVERE_ERR_TASKS_RESTORE_CANNOT_GET_ZIP_ENTRY_397=Unable to restore or verify tasks backup %s because an error occurred while trying to read the next entry from the archive file %s: %s +SEVERE_ERR_TASKS_RESTORE_CANNOT_CREATE_FILE_398=Unable to restore tasks backup %s because an error occurred while trying to recreate file %s: %s +SEVERE_ERR_TASKS_RESTORE_CANNOT_PROCESS_ARCHIVE_FILE_399=Unable to restore or verify tasks backup %s because an error occurred while processing archived file %s: %s +SEVERE_ERR_TASKS_RESTORE_ERROR_ON_ZIP_STREAM_CLOSE_400=Unable to restore or verify tasks backup %s because an unexpected error occurred while trying to close the archive file %s: %s +NOTICE_TASKS_RESTORE_UNSIGNED_HASH_VALID_401=La recopilaci\u00f3n de mensajes calculada a partir del archivo de copia de seguridad coincide con la recopilaci\u00f3n almacenada en la informaci\u00f3n de copia de seguridad +SEVERE_ERR_TASKS_RESTORE_UNSIGNED_HASH_INVALID_402=Unable to restore or verify tasks backup %s because the message digest calculated from the backup archive does not match the digest stored with the backup information +NOTICE_TASKS_RESTORE_SIGNED_HASH_VALID_403=La recopilaci\u00f3n firmada que se ha calculado a partir del archivo de copia de seguridad coincide con la firma almacenada en la informaci\u00f3n de copia de seguridad +SEVERE_ERR_TASKS_RESTORE_SIGNED_HASH_INVALID_404=Unable to restore or verify tasks backup %s because the signed digest calculated from the backup archive does not match the signature stored with the backup information +NOTICE_TASKS_RESTORE_VERIFY_SUCCESSFUL_405=All tests performed on tasks backup %s from directory %s show that the archive appears to be valid +NOTICE_TASKS_RESTORE_SUCCESSFUL_406=Tasks backup %s was successfully restored from the archive in directory %s +SEVERE_ERR_BACKUP_MISSING_BACKUPID_407=The information for backup %s could not be found in the backup directory %s +SEVERE_ERR_BACKUP_CANNOT_UPDATE_BACKUP_DESCRIPTOR_408=An error occurred while attempting to update the backup descriptor file %s with information about the backup: %s -- Gitblit v1.10.0