From bcd1b87c8a389b600e951dd75fd8f28476376107 Mon Sep 17 00:00:00 2001
From: debuggerx <debuggerx@localhost>
Date: Mon, 8 Dec 2025 17:35:52 +0800
Subject: [PATCH] AI-Otter | 2025.2.1 <debuggerx@debuggerx-PC 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 b929318..fd46ba4 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -1,6 +1,6 @@
 <application>
   <component name="Translation.Cache">
-    <option name="lastTrimTime" value="1764728255245" />
+    <option name="lastTrimTime" value="1765185885603" />
   </component>
   <component name="Translation.OpenAISettings">
     <option name="OPEN_AI">
@@ -22,6 +22,8 @@
     <option name="translationDialogLocationY" value="567" />
     <option name="translationDialogWidth" value="1381" />
     <histories>
+      <item value="Invoking the setter will notify listeners if [updateShouldNotify] returns true." />
+      <item value="The value currently exposed by this notifier." />
       <item value="The absolute URI of the script being run in this isolate. If the script argument on the command line is relative, it is resolved to an absolute URI before fetching the script, and that absolute URI is returned. URI resolution only does string manipulation on the script path, and this may be different from the file system's path resolution behavior. For example, a symbolic link immediately followed by '..' will not be looked up. If a compiled Dart script is being executed the URI to the compiled script is returned, for example, `file:fullpathtoscript_name.exe`. If running on the Dart VM the URI to the running Dart script is returned, for example, `file:fullpathtoscript_name.dart`. If the executable environment does not support [script], the URI is empty." />
       <item value="The path of the executable used to run the script in this isolate. Usually `dart` when running on the Dart VM or the compiled script name (`script_name.exe`). The literal path used to identify the executable. This path might be relative or just be a name from which the executable was found by searching the system path. Use [resolvedExecutable] to get an absolute path to the executable." />
       <item value="The path of the executable used to run the script in this isolate after it has been resolved by the OS. This is the absolute path, with all symlinks resolved, to the executable used to run the script. See [executable] for the unresolved version." />
@@ -70,8 +72,6 @@
       <item value="Resolves this image provider using the given `configuration`, returning an [ImageStream]. This is the public entry-point of the [ImageProvider] class hierarchy. Subclasses should implement [obtainKey] and [loadImage], which are used by this method. If they need to change the implementation of [ImageStream] used, they should override [createStream]. If they need to manage the actual resolution of the image, they should override [resolveStreamForKey]. See the Lifecycle documentation on [ImageProvider] for more information." />
       <item value="was synchronously loaded" />
       <item value="If a [loadingBuilder] has _also_ been specified for an image, the two builders will be chained together: the _result_ of this builder will be passed as the `child` argument to the [loadingBuilder]. For example, consider the following builders used in conjunction:" />
-      <item value="To have finer-grained control over the way that an image's loading progress is communicated to the user, see [loadingBuilder]." />
-      <item value="For more information on how to interpret the arguments that are passed to this builder, see the documentation on [ImageFrameBuilder]." />
     </histories>
     <option name="languageScores">
       <map>