AI-Koala | 2024.1.1 <debuggerx@debuggerx-PC Update yiiguxing.translation.xml

yiiguxing.translation.xml

@@ -11,6 +11,7 @@
     <option name="translationDialogLocationY" value="536" />
     <option name="translationDialogWidth" value="1253" />
     <histories>
+      <item value="on sentence begin" />
       <item value="segment" />
       <item value="reinforce hotword" />
       <item value="SEGMENT" />
@@ -60,12 +61,11 @@
       <item value="The [Navigator] popped `route`. The route immediately below that one, and thus the newly active route, is `previousRoute`." />
       <item value="The [Navigator] pushed `route`. The route immediately below that one, and thus the previously active route, is `previousRoute`." />
       <item value="Resolve debugger issue with the new Dart macro file uri format (7449) Hide deep links window when insufficient SDK version (7478) Fix exceptions out of FlutterSampleNotificationProvider (5634) Additional fixes for deprecation of ActionUpdateThread.OLD_EDT (7330) Exception from EditorPerfDecorations fixed (7432) Exception from FlutterColorProvider fixed (7428) Fix top toolbar for new UI (7423) Update JxBrowser to v7.38.2 (7413) &quot;Open Android Module in Android Studio&quot; action removed (7103) Fix for deprecation of ActionUpdateThread.OLD_EDT (7330) Deprecation of ServiceExtensions.setPubRootDirectories (7142) Fix plugin not opening in Android Studio (7305) Deadlock involving WorkspaceCache.getInstance() (7333) Fix for AlreadyDisposedException from DartVmServiceDebugProcess (7381) Memory leak fix out of DartVmServiceDebugProcess (7380) Memory leak fix in FlutterSettings and JxBrowser (7377) Delete actions specific to legacy inspector (7416)" />
-      <item value="Whether this entry must be included in the tree even if there is a fully [opaque] entry above it. By default, if there is an entirely [opaque] entry over this one, then this one will not be included in the widget tree (in particular, stateful widgets within the overlay entry will not be instantiated). To ensure that your overlay entry is still built even if it is not visible, set [maintainState] to true. This is more expensive, so should be done with care. In particular, if widgets in an overlay entry with [maintainState] set to true repeatedly call [State.setState], the user's battery will be drained unnecessarily. This is used by the [Navigator] and [Route] objects to ensure that routes are kept around even when in the background, so that [Future]s promised from subsequent routes will be handled properly when they complete." />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="499" />
-        <entry key="ENGLISH" value="500" />
+        <entry key="CHINESE" value="500" />
+        <entry key="ENGLISH" value="501" />
         <entry key="HAWAIIAN" value="1" />
         <entry key="POLISH" value="1" />
         <entry key="ROMANIAN" value="1" />