From 08bdb81089caab2656bf2a221b51b726c426fa4d Mon Sep 17 00:00:00 2001
From: debuggerx <debuggerx@debuggerx-e5.lan>
Date: Fri, 28 Oct 2022 12:29:06 +0800
Subject: [PATCH] AI-222.4345.14.2221.9189903 <debuggerx@debuggerx-e5 Update
 yiiguxing.translation.xml

---
 yiiguxing.translation.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index 154f9a6..2a9fe86 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -6,6 +6,7 @@
     <option name="newTranslationDialogY" value="447" />
     <option name="pinTranslationDialog" value="true" />
     <histories>
+      <item value="check Name Exist" />
       <item value="update Soul Avatar" />
       <item value="已修复" />
       <item value="FIXED" />
@@ -55,12 +56,11 @@
       <item value="vibes" />
       <item value="shrink" />
       <item value="Register a closure to be called when the object changes. If the given closure is already registered, an additional instance is added, and must be removed the same number of times it is added before it will stop being called. This method must not be called after [dispose] has been called. {@template flutter.foundation.ChangeNotifier.addListener} If a listener is added twice, and is removed once during an iteration (e.g. in response to a notification), it will still be called again. If, on the other hand, it is removed as many times as it was registered, then it will no longer be called. This odd behavior is the result of the [ChangeNotifier] not being able to determine which listener is being removed, since they are identical, therefore it will conservatively still call all the listeners when it knows that any are still registered. This surprising behavior can be unexpectedly observed when registering a listener on two separate objects which are both forwarding all registrations to a common upstream object. {@endtemplate} See also: [removeListener], which removes a previously registered closure from the list of closures that are notified when the object changes." />
-      <item value="initial" />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="430" />
-        <entry key="ENGLISH" value="431" />
+        <entry key="CHINESE" value="431" />
+        <entry key="ENGLISH" value="432" />
         <entry key="GERMAN" value="1" />
         <entry key="FRENCH" value="1" />
       </map>