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/replication_fr.properties | 67 +++++++++++++++++++++++++-------- 1 files changed, 50 insertions(+), 17 deletions(-) diff --git a/opends/src/messages/messages/replication_fr.properties b/opends/src/messages/messages/replication_fr.properties index 0a223c7..77ce590 100644 --- a/opends/src/messages/messages/replication_fr.properties +++ b/opends/src/messages/messages/replication_fr.properties @@ -64,11 +64,11 @@ MILD_ERR_NEED_CHANGELOG_PORT_13=Le port du serveur de r\u00e9plication doit \u00eatre d\u00e9fini DEBUG_ERROR_UPDATING_RUV_14=Error %s when updating server state %s : %s base dn : %s MILD_ERR_ERROR_SEARCHING_RUV_15=Erreur %s lors de la recherche de l'\u00e9tat du serveur %s : %s dn de base : %s -NOTICE_SERVER_DISCONNECT_16=%s s'est d\u00e9connect\u00e9 de ce serveur de r\u00e9plication +NOTICE_SERVER_DISCONNECT_16=%s has disconnected from this replication server %s NOTICE_NO_CHANGELOG_SERVER_LISTENING_17=Aucun serveur de r\u00e9plication n'\u00e9coute sur %s -NOTICE_FOUND_CHANGELOGS_WITH_MY_CHANGES_18=%d serveur(s) de r\u00e9plication trouv\u00e9(s) avec des modifications \u00e0 jour pour le suffixe %s +NOTICE_FOUND_CHANGELOGS_WITH_MY_CHANGES_18=Found %d replication server(s) with up to date changes for suffix %s, in server id %s NOTICE_NEED_MORE_THAN_ONE_CHANGELOG_SERVER_19=Plus d'un serveur de r\u00e9plication doit \u00eatre configur\u00e9 -SEVERE_ERR_EXCEPTION_STARTING_SESSION_20=Caught Exception during initial communication on domain %s with replication server %s : %s +SEVERE_ERR_EXCEPTION_SENDING_TOPO_INFO_20=Caught IOException while sending topology info (for update) on domain %s for %s server %s : %s MILD_ERR_CANNOT_RECOVER_CHANGES_21=Erreur lors de la recherche d'anciennes modifications \u00e0 partir de la base de donn\u00e9es pour le DN de base %s NOTICE_COULD_NOT_FIND_CHANGELOG_WITH_MY_CHANGES_22=Serveur de r\u00e9plication ayant consult\u00e9 toutes les modifications locales sur le suffixe %s introuvable. %d serveur(s) de r\u00e9plication non mis \u00e0 jour trouv\u00e9(s). Relecture des modifications imminente NOTICE_COULD_NOT_FIND_CHANGELOG_23=Impossible de se connecter \u00e0 un serveur de r\u00e9plication sur le suffixe %s, nouvelle tentative... @@ -78,10 +78,10 @@ SEVERE_ERR_IGNORE_BAD_DN_IN_DATABASE_IDENTIFIER_27=A badly formatted DN was found in the list of database known by this Replication Server :%s. This Identifier will be ignored SEVERE_ERR_ERROR_CLOSING_CHANGELOG_ENV_28=Erreur lors de la fermeture de la base de donn\u00e9es du serveur de r\u00e9plication : SEVERE_ERR_EXCEPTION_CHANGELOG_TRIM_FLUSH_29=Error during the Replication Server database trimming or flush process. The Changelog service is going to shutdown -SEVERE_ERR_CHANGELOG_CONNECTION_ERROR_30=Error during Replication server message processing . Connection from %s is rejected +SEVERE_ERR_REPLICATION_SERVER_CONNECTION_ERROR_30=Error in Replication Server handshake processing. Connection from/to %s is aborted SEVERE_ERR_UNKNOWN_MESSAGE_31=%s has sent an unknown message. Closing the connection SEVERE_ERR_WRITER_UNEXPECTED_EXCEPTION_32=An unexpected error happened handling connection with %s. This connection is going to be closed -SEVERE_ERR_CHANGELOG_ERROR_SENDING_ACK_33=An unexpected error occurred while sending an ack to %s. This connection is going to be closed and reopened +SEVERE_ERR_RS_ERROR_SENDING_ACK_33=In replication server %s: an unexpected error occurred while sending an ack to server id %s for change number %s in domain %s . This connection is going to be closed and reopened SEVERE_ERR_EXCEPTION_RECEIVING_REPLICATION_MESSAGE_34=An Exception was caught while receiving replication message : %s MILD_ERR_LOOP_REPLAYING_OPERATION_35=Une boucle a \u00e9t\u00e9 d\u00e9tect\u00e9e lors de la relecture de l'op\u00e9ration : %s erreur %s MILD_ERR_FILE_CHECK_CREATE_FAILED_36=Une exception a \u00e9t\u00e9 d\u00e9tect\u00e9e lors du test de l'existence ou de la tentative de cr\u00e9ation du r\u00e9pertoire pour la base de donn\u00e9es du serveur de r\u00e9plication : %s @@ -102,17 +102,16 @@ SEVERE_ERR_COULD_NOT_SOLVE_HOSTNAME_51=The hostname %s could not be resolved as an IP address NOTICE_READER_NULL_MSG_52=Message null re\u00e7u de %s NOTICE_READER_EXCEPTION_53=Exception lors de la lecture de messages de %s -SEVERE_ERR_DUPLICATE_SERVER_ID_54=Servers %s and %s have the same ServerId : %d -SEVERE_ERR_DUPLICATE_REPLICATION_SERVER_ID_55=Replication Servers %s and %s have the same ServerId : %d +SEVERE_ERR_DUPLICATE_SERVER_ID_54=In Replication server %s: servers %s and %s have the same ServerId : %d +SEVERE_ERR_DUPLICATE_REPLICATION_SERVER_ID_55=In Replication server %s: replication servers %s and %s have the same ServerId : %d SEVERE_ERR_BAD_HISTORICAL_56=Entry %s was containing some unknown historical information, This may cause some inconsistency for this entry MILD_ERR_CANNOT_ADD_CONFLICT_ATTRIBUTE_57=Un conflit a \u00e9t\u00e9 d\u00e9tect\u00e9 mais des informations sur ce conflit n'ont pas pu \u00eatre ajout\u00e9es. Op\u00e9ration : MILD_ERR_CANNOT_RENAME_CONFLICT_ENTRY_58=Une erreur s'est produite lors de la tentative de renommage d'une entr\u00e9e conflictuelle : MILD_ERR_EXCEPTION_RENAME_CONFLICT_ENTRY_59=Une exception s'est produite lors de la tentative de renommage d'une entr\u00e9e conflictuelle : SEVERE_ERR_CHANGELOG_UNSUPPORTED_UTF8_ENCODING_60=The JVM does not support UTF-8. This is required to be able to encode the changes in the database. This replication server will now shutdown SEVERE_ERR_REPLICATION_COULD_NOT_CONNECT_61=The Replication is configured for suffix %s but was not able to connect to any Replication Server -NOTICE_NOW_FOUND_SAME_GENERATION_CHANGELOG_62=La r\u00e9plication est fonctionnelle pour le domaine %s avec le serveur de r\u00e9plication %s - la g\u00e9n\u00e9ration de donn\u00e9es est %s -NOTICE_DISCONNECTED_FROM_CHANGELOG_63=La connexion au serveur de r\u00e9plication %s a \u00e9t\u00e9 coup\u00e9e par le serveur de r\u00e9plication -SEVERE_ERR_CHANGELOG_ERROR_SENDING_INFO_64=An unexpected error occurred while sending a Server Info message to %s. This connection is going to be closed and reopened +NOTICE_NOW_FOUND_SAME_GENERATION_CHANGELOG_62=Replication is up and running for domain %s with replication server id %s %s - local server id is %s - data generation is %s +NOTICE_DISCONNECTED_FROM_CHANGELOG_63=The connection to Replication Server %s %s has been dropped by the Replication Server for %s in local server id %s SEVERE_ERR_CHANGELOG_ERROR_SENDING_ERROR_65=An unexpected error occurred while sending an Error Message to %s. This connection is going to be closed and reopened SEVERE_ERR_CHANGELOG_ERROR_SENDING_MSG_66=An unexpected error occurred while sending a Message to %s. This connection is going to be closed and reopened MILD_ERR_ERROR_REPLAYING_OPERATION_67=Impossible de relire l'op\u00e9ration %s avec l'erreur %s %s de ChangeNumber %s @@ -125,11 +124,11 @@ SEVERE_ERR_SEARCHING_DOMAIN_BACKEND_74=An unexpected error occurred when looking for the replicated backend : %s. It may be not configured or disabled SEVERE_ERR_LOADING_GENERATION_ID_75=An unexpected error occurred when searching in %s for the generation ID : %s SEVERE_ERR_UPDATING_GENERATION_ID_76=An unexpected error %s occurred when updating generation ID for the domain : %s -NOTICE_BAD_GENERATION_ID_77=Sur le suffixe %s. Le serveur %s a fourni l'ID g\u00e9n\u00e9ration =%s alors que l'ID g\u00e9n\u00e9ration attendu \u00e9tait =%s. Par cons\u00e9quent, la r\u00e9plication est endommag\u00e9e pour ce serveur -NOTICE_RESET_GENERATION_ID_78=L'ID g\u00e9n\u00e9ration a \u00e9t\u00e9 r\u00e9initialis\u00e9 pour le domaine %s. La r\u00e9plication est maintenant endommag\u00e9e pour ce domaine -MILD_ERR_ERROR_MSG_RECEIVED_79=L'erreur suivante a \u00e9t\u00e9 re\u00e7ue : <%s> -MILD_ERR_IGNORING_UPDATE_FROM_80=La mise \u00e0 jour <%s> re\u00e7ue du serveur <%s> est ignor\u00e9e en raison d'un ID g\u00e9n\u00e9ration incorrect de ce serveur -MILD_ERR_IGNORING_UPDATE_TO_81=Dans %s, la mise \u00e0 jour <%s> ne va pas \u00eatre envoy\u00e9e au serveur %s avec l'ID g\u00e9n\u00e9ration=%s diff\u00e9rent de l'ID g\u00e9n\u00e9ration attendu =%s +NOTICE_BAD_GENERATION_ID_FROM_RS_77=On suffix %s, replication server %s presented generation ID=%s when expected generation ID=%s +NOTICE_RESET_GENERATION_ID_78=The generation ID has been resetted for domain %s. New reference generation id is %s +MILD_ERR_ERROR_MSG_RECEIVED_79=The following error has been received : %s +MILD_ERR_IGNORING_UPDATE_FROM_RS_80=In RS %s for dn %s, update %s received from RS %s is ignored due to a bad generation id of remote RS (local genid: %s, remote genid: %s) +MILD_ERR_IGNORING_UPDATE_TO_RS_81=In RS %s for dn %s, update %s will not be sent to RS %s with generation id %s different from local generation id %s SEVERE_ERR_INIT_IMPORT_NOT_SUPPORTED_82= Initialization cannot be done because import is not supported by the backend %s SEVERE_ERR_INIT_EXPORT_NOT_SUPPORTED_83= Initialization cannot be done because export is not supported by the backend %s SEVERE_ERR_INIT_CANNOT_LOCK_BACKEND_84= Initialization cannot be done because the following error occurred while locking the backend %s : %s @@ -144,7 +143,7 @@ SEVERE_ERR_BACKEND_SEARCH_ENTRY_93 =An error occurred when searching for %s : %s SEVERE_ERR_REPLICATIONBACKEND_ENTRY_DOESNT_EXIST_94=Entry %s does not exist in the replication server backend SEVERE_ERR_UNKNOWN_DN_95=The base DN %s is not stored by any of the Directory Server backend -NOTICE_NOW_FOUND_BAD_GENERATION_CHANGELOG_96=La r\u00e9plication est op\u00e9rationnelle, mais endommag\u00e9e pour le domaine %s avec le serveur de r\u00e9plication %s - la g\u00e9n\u00e9ration de donn\u00e9es locale est %s - la g\u00e9n\u00e9ration de donn\u00e9es du serveur de r\u00e9plication est %s - Cela peut \u00eatre temporaire uniquement ou n\u00e9cessiter une resynchronisation compl\u00e8te +NOTICE_NOW_FOUND_BAD_GENERATION_CHANGELOG_96=Replication is connected to replication server, but has a different generation id for domain %s than replication server %s - local data generation is %s - replication server data generation is %s - This may be only temporary or requires a full resynchronization NOTICE_HEARTBEAT_FAILURE_97=%s ferme la session car aucune pulsation n'est d\u00e9tect\u00e9e SEVERE_ERR_REPLICATONBACKEND_IMPORT_LDIF_NOT_SUPPORTED_98=The replication server backend does not support the import ldif function SEVERE_ERR_REPLICATONBACKEND_EXPORT_LDIF_FAILED_99=The replication server backend cannot export its entries in LDIF format because the export-ldif command must be run as a task @@ -157,8 +156,42 @@ DEBUG_GOING_TO_SEARCH_FOR_CHANGES_111=The replication server is late regarding our changes: going to send missing ones DEBUG_SENDING_CHANGE_112=Sending change number: %s DEBUG_CHANGES_SENT_113=All missing changes sent to replication server -SEVERE_ERR_PUBLISHING_FAKE_OPS_114=Caught exception publishing fake operations for domain %s to replication server %s : %s +SEVERE_ERR_PUBLISHING_FAKE_OPS_114=Caught exception publishing fake operations for domain %s : %s SEVERE_ERR_COMPUTING_FAKE_OPS_115=Caught exception computing fake operations for domain %s for replication server %s : %s NOTICE_IGNORING_REMOTE_MONITOR_DATA_116=Certaines donn\u00e9es de contr\u00f4le ont \u00e9t\u00e9 re\u00e7ues depuis le serveur avec l'ID serveur %s trop tardivement et sont ignor\u00e9es NOTICE_SERVER_STATE_RECOVERY_117=R\u00e9cup\u00e9ration ServerState pour le domaine %s, mis \u00e0 jour avec changeNumber %s SEVERE_ERR_RESET_GENERATION_CONN_ERR_ID_118=The generation ID could not be reset for domain %s because it is NOT connected to the replication. You should check in the configuration that the domain is enabled +SEVERE_ERR_EXCEPTION_STARTING_SESSION_PHASE_119=Caught Exception during initial communication (phase %s) on domain %s with replication server %s : %s +NOTICE_NEW_SERVER_WITH_SAME_GROUP_ID_120=Disconnecting from replication server as a new one with our group id (%s) just arrived in topology. This is for domain %s and we have server id %s +SEVERE_ERR_RS_DN_DOES_NOT_MATCH_121=DN sent by remote replication server: %s does not match local replication server one: %s +SEVERE_ERR_DS_DN_DOES_NOT_MATCH_122=DN sent by replication server: %s does not match local directory server one: %s +SEVERE_ERR_EXCEPTION_FORWARDING_RESET_GEN_ID_123=Caught IOException while forwarding ResetGenerationIdMsg to peer replication servers for domain %s : %s +SEVERE_ERR_DS_INVALID_INIT_STATUS_124=Computed invalid initial status: %s in DS replication domain %s with server id %s +SEVERE_ERR_RS_INVALID_INIT_STATUS_125=Replication server received invalid initial status: %s for replication domain %s from server id %s +SEVERE_ERR_DS_INVALID_REQUESTED_STATUS_126=Received invalid requested status %s in DS replication domain %s with server id %s +SEVERE_ERR_RS_CANNOT_CHANGE_STATUS_127=Could not compute new status in RS replication domain %s for server id %s. Was in %s status and received %s event +SEVERE_ERR_DS_CANNOT_CHANGE_STATUS_128=Could not compute new status in DS replication domain %s with server id %s. Was in %s status and received %s event +SEVERE_ERR_EXCEPTION_CHANGING_STATUS_AFTER_RESET_GEN_ID_129=Caught IOException while changing status for domain %s and serverId: %s after reset for generation id: %s +SEVERE_ERR_RECEIVED_CHANGE_STATUS_NOT_FROM_DS_130=Received change status message does not come from a directory server (dn: %s, server id: %s, msg: %s) +NOTICE_DIRECTORY_SERVER_CHANGED_STATUS_131=Directory server %s for dn %s changed his status to %s +SEVERE_ERR_RS_INVALID_NEW_STATUS_132=Received invalid new status %s in RS for replication domain %s and directory server id %s +SEVERE_WARN_CONNECTED_TO_SERVER_WITH_WRONG_GROUP_ID_133=Connected to a replication server with wrong group id. We have group id %s and replication server id %s %s has group id %s. This is for domain %s in directory server %s +SEVERE_ERR_EXCEPTION_SENDING_CS_134=Replication broker with dn %s and server id %s failed to signal status change because of: %s +MILD_ERR_IGNORING_UPDATE_FROM_DS_BADGENID_135=In RS %s for dn %s, update %s received from DS %s is ignored due to a bad generation id of DS (local genid: %s, remote genid: %s) +MILD_ERR_IGNORING_UPDATE_TO_DS_BADGENID_136=In RS %s for dn %s, update %s will not be sent to DS %s with generation id %s different from local generation id %s +MILD_ERR_IGNORING_UPDATE_FROM_DS_FULLUP_137=In RS %s for dn %s, update %s received from DS %s is ignored due to DS in full update +MILD_ERR_IGNORING_UPDATE_TO_DS_FULLUP_138=In RS %s for dn %s, update %s will not be sent to DS %s in full update +SEVERE_ERR_EXCEPTION_CHANGING_STATUS_FROM_STATUS_ANALYZER_139=Caught IOException while changing status for domain %s and serverId: %s from status analyzer: %s +NOTICE_BAD_GEN_ID_IN_FULL_UPDATE_140=Replication server %s for dn %s: directory server %s must stay in full update although a generation id reset has been ordered (from %s to %s) +NOTICE_FULL_UPDATE_ENGAGED_FROM_REMOTE_START_141=Local directory server %s is starting online full update for importing suffix %s data from remote directory server %s +NOTICE_FULL_UPDATE_ENGAGED_FROM_REMOTE_END_142=Local directory server %s has finished online full update for importing suffix %s data from remote directory server %s +NOTICE_FULL_UPDATE_ENGAGED_FOR_REMOTE_START_143=Local directory server %s is starting online full update for exporting suffix %s data to remote directory server %s +NOTICE_FULL_UPDATE_ENGAGED_FOR_REMOTE_END_144=Local directory server %s has finished online full update for exporting suffix datat %s to remote directory server %s +NOTICE_TIMEOUT_WHEN_CROSS_CONNECTION_145=Timed out trying to acquire the domain lock for %s. Connection attempt from replication server %s to local replication server %s will be aborted. Simultanate cross connection attempt ? +NOTICE_BAD_GENERATION_ID_FROM_DS_146=On suffix %s, directory server %s presented generation ID=%s when expected generation ID=%s +NOTICE_DS_RECEIVED_ACK_ERROR_147=In replication service %s and server id %s, the assured update message %s was acknowledged with the following errors: %s +NOTICE_DS_ACK_TIMEOUT_148=In replication service %s, timeout after %s ms waiting for the acknowledgement of the assured update message: %s +SEVERE_ERR_DS_UNKNOWN_ASSURED_MODE_149=In directory server %s, received unknown assured update mode: %s, for domain %s. Message: %s +SEVERE_ERR_RS_UNKNOWN_ASSURED_MODE_150=In replication server %s, received unknown assured update mode: %s, for domain %s. Message: %s +SEVERE_ERR_UNKNOWN_ASSURED_SAFE_DATA_LEVEL_151=In replication server %s, received a safe data assured update message with incoherent level: %s, this is for domain %s. Message: %s +SEVERE_ERR_RESET_GENERATION_ID_FAILED_152=The generation ID could not be reset for domain %s -- Gitblit v1.10.0