From b751e0739ef4407c872c78d79276398b5f3beaa5 Mon Sep 17 00:00:00 2001
From: debuggerx <debuggerx@localhost>
Date: Wed, 3 Dec 2025 20:50:55 +0800
Subject: [PATCH] AI-Otter | 2025.2.1 <debuggerx@debuggerx-PC Update
 yiiguxing.translation.xml

---
 yiiguxing.translation.xml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index 6ca18e0..b929318 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -22,6 +22,9 @@
     <option name="translationDialogLocationY" value="567" />
     <option name="translationDialogWidth" value="1381" />
     <histories>
+      <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." />
       <item value="特征边界" />
       <item value="已知区域" />
       <item value="judge" />
@@ -69,13 +72,10 @@
       <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]." />
-      <item value="If this is null, this widget will display an image that is painted as soon as the first image frame is available (and will appear to &quot;pop&quot; in if it becomes available asynchronously). Callers might use this builder to add effects to the image (such as fading the image in when it becomes available) or to display a placeholder widget while the image is loading." />
-      <item value="A builder function responsible for creating the widget that represents this image." />
-      <item value="The `callback`, the `message` given to it as well as the result have to be objects that can be sent across isolates (as they may be transitively copied if needed). The majority of objects can be sent across isolates." />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE_SIMPLIFIED" value="63" />
+        <entry key="CHINESE_SIMPLIFIED" value="64" />
         <entry key="ENGLISH" value="64" />
       </map>
     </option>