AI-Iguana | 2023.2.1 Patch 2 <debuggerx@debuggerx-PC Update yiiguxing.translation.xml

yiiguxing.translation.xml

@@ -7,6 +7,10 @@
   </component>
   <component name="Translation.States">
     <histories>
+      <item value="NOTIFY" />
+      <item value="SUCCESS" />
+      <item value="SEGMENT" />
+      <item value="SLICE" />
       <item value="last Text" />
       <item value="Ideal for short audio files, since it reduces the impacts on visuals or UI performance. In this mode the backend won't fire any duration, position or playback completion events. This means you are responsible for stopping the player. Also, it is not possible to use the seek method to set the audio to a specific position." />
       <item value="Creates a formatter that only allows characters matching a pattern." />
@@ -53,15 +57,11 @@
       <item value="This contains the response message from a connection. It tells you whether your connection was successful or a failure, in which case will tell you where the failure occurred" />
       <item value="This is the bluetooth device that we get when we have a successful connection. If our bluetooth connection wasn't successful, then null will be returned" />
       <item value="This is likely a mistake, as Provider will not automatically update dependents when AMDHomePageViewModel is updated. Instead, consider changing Provider for more specific implementation that handles the update mechanism, such as:" />
-      <item value="Tried to use Provider with a subtype of ListenableStream (AMDHomePageViewModel)." />
-      <item value="inflate" />
-      <item value="The number of device pixels for each logical pixel for the screen this view is displayed on. This number might not be a power of two. Indeed, it might not even be an integer. For example, the Nexus 6 has a device pixel ratio of 3.5. Device pixels are also referred to as physical pixels. Logical pixels are also referred to as device-independent or resolution-independent pixels. By definition, there are roughly 38 logical pixels per centimeter, or about 96 logical pixels per inch, of the physical display. The value returned by [devicePixelRatio] is ultimately obtained either from the hardware itself, the device drivers, or a hard-coded value stored in the operating system or firmware, and may be inaccurate, sometimes by a significant margin. The Flutter framework operates in logical pixels, so it is rarely necessary to directly deal with this property. When this changes, [PlatformDispatcher.onMetricsChanged] is called. When using the Flutter framework, using [MediaQuery.of] to obtain the device pixel ratio (via [MediaQueryData.devicePixelRatio]), instead of directly obtaining the [devicePixelRatio] from a [FlutterView], will automatically cause any widgets dependent on this value to rebuild when it changes, without having to listen to [PlatformDispatcher.onMetricsChanged]. See also: [WidgetsBindingObserver], for a mechanism at the widgets layer to observe when this value changes. [Display.devicePixelRatio], which reports the DPR of the display. The value here is equal to the value exposed on [display]." />
-      <item value="Subsequent version, remove this deprecated member. ignore: deprecated_member_use" />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="366" />
-        <entry key="ENGLISH" value="367" />
+        <entry key="CHINESE" value="370" />
+        <entry key="ENGLISH" value="371" />
         <entry key="HAWAIIAN" value="1" />
         <entry key="POLISH" value="1" />
         <entry key="ROMANIAN" value="1" />