AI-232.10227.8.2321.11231672 <debuggerx@debuggerx-work Update yiiguxing.translation.xml

yiiguxing.translation.xml

@@ -8,6 +8,7 @@
   </component>
   <component name="Translation.States">
     <histories>
+      <item value="feat: add intimacy page and feed page; task act page support h5." />
       <item value="Unsupported App Usage" />
       <item value="context" />
       <item value="Sets up the given animation to play when the animation supplied in the play(Animator) call that created this Builder object ends. Params: anim – The animation that will play when the animation supplied to the play(Animator) method ends." />
@@ -57,12 +58,11 @@
       <item value="currency Cost" />
       <item value="Reflective access to mCurTextColor will throw an exception when targeting API 30 and above" />
       <item value="API 'android.registerTransform' is obsolete. It will be removed in version 8.0 of the Android Gradle plugin. The Transform API is removed to improve build performance. Projects that use the Transform API force the Android Gradle plugin to use a less optimized flow for the build that can result in large regressions in build times. It’s also difficult to use the Transform API and combine it with other Gradle features; the replacement APIs aim to make it easier to extend the build without introducing performance or correctness issues. There is no single replacement for the Transform API—there are new, targeted APIs for each use case. All the replacement APIs are in the `androidComponents {}` block. The Transform API uses incremental APIs deprecated since Gradle 7.5. Please add `android.experimental.legacyTransform.forceNonIncremental=true` to `gradle.properties` to fix this issue. Note that this will run transforms non-incrementally and may have a build performance impact. For more information, see https:developer.android.comstudioreleasesgradle-plugin-api-updatestransform-api. To determine what is calling android.registerTransform, use -Pandroid.debug.obsoleteApi=true on the command line to display more information." />
-      <item value="CURRENCY TYPE CHIP" />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="254" />
-        <entry key="ENGLISH" value="255" />
+        <entry key="CHINESE" value="255" />
+        <entry key="ENGLISH" value="256" />
         <entry key="HAWAIIAN" value="1" />
         <entry key="POLISH" value="1" />
         <entry key="ROMANIAN" value="1" />