From 7fe0d7ee70889351b4d71581a3df6fba64e36905 Mon Sep 17 00:00:00 2001
From: Lilian <lilian.faedi@hotmail.fr>
Date: Wed, 25 May 2022 09:54:30 +0200
Subject: [PATCH] =?UTF-8?q?Translated=20by=20Lilian=20Ajout=C3=A9s=C2=A0:?=
 =?UTF-8?q?=201,=20Supprim=C3=A9s=C2=A0:=200,=20Modifi=C3=A9s=C2=A0:=200?=
 =?UTF-8?q?=20(Conflits=C2=A0:=200)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 omegat/project_save.tmx | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/omegat/project_save.tmx b/omegat/project_save.tmx
index ecae495f..114d1c59 100644
--- a/omegat/project_save.tmx
+++ b/omegat/project_save.tmx
@@ -79029,6 +79029,14 @@ il vaut mieux déterminer l'égalité approximative.</seg>
         <seg>En général nous indiquons le nom de la commande qui fait le travail entre parenthèses après avoir mentionné la séquence qui l'exécute.</seg>
       </tuv>
     </tu>
+    <tu>
+      <tuv lang="en">
+        <seg>Usually, each editing command makes a separate entry in the undo records, but some commands such as @code{query-replace} divide their changes into multiple entries for flexibility in undoing.</seg>
+      </tuv>
+      <tuv lang="fr" changeid="Lilian" changedate="20220525T075429Z" creationid="Lilian" creationdate="20220525T075139Z">
+        <seg>En général, chaque commande de modification crée une entrée séparée dans l'historique d'annulation, mais certaines commandes comme @code{query-replace} divisent leurs modifications en de multiples entrées, ce qui garantit la flexibilité de l'annulation.</seg>
+      </tuv>
+    </tu>
     <tu>
       <tuv lang="en">
         <seg>Usually, there is no need to change it.</seg>