diff --git a/find.xml b/find.xml
index 965789e..db3a4b7 100644
--- a/find.xml
+++ b/find.xml
@@ -2,6 +2,8 @@
   <component name="FindSettings">
     <option name="customScope" value="All Places" />
     <option name="defaultScopeName" value="All Places" />
+    <option name="localRegularExpressions" value="true" />
+    <option name="LOCAL_REGULAR_EXPRESSIONS" value="true" />
     <option name="SEARCH_SCOPE" value="All Places" />
   </component>
 </application>
\ No newline at end of file
diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index ec1899a..017a1e7 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -5,6 +5,11 @@
     <option name="newTranslationDialogY" value="624" />
     <option name="pinNewTranslationDialog" value="true" />
     <histories>
+      <item value="exclam" />
+      <item value="exclamation" />
+      <item value="Returns an object representing the logical key that was pressed. {@template flutter.services.RawKeyEvent.logicalKey} This method takes into account the key map and modifier keys (like SHIFT) to determine which logical key to return. If you are looking for the character produced by a key event, use [RawKeyEvent.character] instead. If you are collecting text strings, use the [TextField] or [CupertinoTextField] widgets, since those automatically handle many of the complexities of managing keyboard input, like showing a soft keyboard or interacting with an input method editor (IME). {@endtemplate}" />
+      <item value="Represents the logical &quot;Lang 1&quot; key on the keyboard. See the function [RawKeyEvent.logicalKey] for more information." />
+      <item value="A list of all the predefined constant PhysicalKeyboardKeys so that they can be searched." />
       <item value="skicky" />
       <item value="A widget that manages a [FocusNode] to allow keyboard focus to be given to this widget and its descendants. When the focus is gained or lost, [onFocusChange] is called. For keyboard events, [onKey] is called if [FocusNode.hasFocus] is true for this widget's [focusNode], unless a focused descendant's [onKey] callback returns [KeyEventResult.handled] when called. This widget does not provide any visual indication that the focus has changed. Any desired visual changes should be made when [onFocusChange] is called. To access the [FocusNode] of the nearest ancestor [Focus] widget and establish a relationship that will rebuild the widget when the focus changes, use the [Focus.of] and [FocusScope.of] static methods. To access the focused state of the nearest [Focus] widget, use [FocusNode.hasFocus] from a build method, which also establishes a relationship between the calling widget and the [Focus] widget that will rebuild the calling widget when the focus changes. Managing a [FocusNode] means managing its lifecycle, listening for changes in focus, and re-parenting it when needed to keep the focus hierarchy in sync with the widget hierarchy. This widget does all of those things for you. See [FocusNode] for more information about the details of what node management entails if you are not using a [Focus] widget and you need to do it yourself. To collect a sub-tree of nodes into an exclusive group that restricts focus traversal to the group, use a [FocusScope]. To collect a sub-tree of nodes into a group that has a specific order to its traversal but allows the traversal to escape the group, use a [FocusTraversalGroup]. To move the focus, use methods on [FocusNode] by getting the [FocusNode] through the [of] method. For instance, to move the focus to the next node in the focus traversal order, call `Focus.of(context).nextFocus()`. To unfocus a widget, call `Focus.of(context).unfocus()`. {@tool dartpad --template=stateful_widget_scaffold} This example shows how to manage focus using the [Focus] and [FocusScope] widgets. See [FocusNode] for a similar example that doesn't use [Focus] or [FocusScope]." />
       <item value="LayoutBuilder does not support returning intrinsic dimensions." />
@@ -32,8 +37,8 @@
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="17" />
-        <entry key="ENGLISH" value="18" />
+        <entry key="CHINESE" value="22" />
+        <entry key="ENGLISH" value="23" />
       </map>
     </option>
   </component>