diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index 53a0540..65dd2a3 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -6,6 +6,11 @@
     <option name="newTranslationDialogY" value="447" />
     <option name="pinTranslationDialog" value="true" />
     <histories>
+      <item value="time After Framework Init Micros" />
+      <item value="time To First Frame Micros" />
+      <item value="time To First Frame Rasterized Micros" />
+      <item value="time To Framework Init Micros" />
+      <item value="engine Enter Timestamp Micros" />
       <item value="is on waitlist" />
       <item value="problem" />
       <item value="tag" />
@@ -51,16 +56,11 @@
       <item value="Send the caret location instead if there's no marked text yet." />
       <item value="The range of text that is still being composed. Composing regions are created by input methods (IMEs) to indicate the text within a certain range is provisional. For instance, the Android Gboard app's English keyboard puts the current word under the caret into a composing region to indicate the word is subject to autocorrect or prediction changes. Composing regions can also be used for performing multistage input, which is typically used by IMEs designed for phoetic keyboard to enter ideographic symbols. As an example, many CJK keyboards require the user to enter a latin alphabet sequence and then convert it to CJK characters. On iOS, the default software keyboards do not have a dedicated view to show the unfinished latin sequence, so it's displayed directly in the text field, inside of a composing region. The composing region should typically only be changed by the IME, or the user via interacting with the IME. If the range represented by this property is [TextRange.empty], then the text is not currently being composed." />
       <item value="tab切换时背景颜色平滑变化" />
-      <item value="tab切换时背景颜色平滑渐变" />
-      <item value="Whether any listeners are currently registered. Clients should not depend on this value for their behavior, because having one listener's logic change when another listener happens to start or stop listening will lead to extremely hard-to-track bugs. Subclasses might use this information to determine whether to do any work when there are no listeners, however; for example, resuming a [Stream] when a listener is added and pausing it when a listener is removed. Typically this is used by overriding [addListener], checking if [hasListeners] is false before calling `super.addListener()`, and if so, starting whatever work is needed to determine when to call [notifyListeners]; and similarly, by overriding [removeListener], checking if [hasListeners] is false after calling `super.removeListener()`, and if so, stopping that same work." />
-      <item value="feat: send message to cloud function; hide animated emojis when dialog showing." />
-      <item value="implement" />
-      <item value="实现" />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="232" />
-        <entry key="ENGLISH" value="233" />
+        <entry key="CHINESE" value="237" />
+        <entry key="ENGLISH" value="238" />
         <entry key="GERMAN" value="1" />
         <entry key="FRENCH" value="1" />
       </map>