diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index e9e6bb0..01d15a1 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -4,6 +4,11 @@
   </component>
   <component name="Translation.States">
     <histories>
+      <item value="The external names referenced by the file." />
+      <item value="Data structure output by PackageMapProvider. This contains both the package map and dependency information." />
+      <item value="A [UriResolver] implementation for the `package:` scheme that uses a map of package names to their directories." />
+      <item value="Information about a file being analyzed, explicitly or implicitly. It provides a consistent view on its properties. The properties are not guaranteed to represent the most recent state of the file system. To update the file to the most recent state, [refresh] should be called." />
+      <item value="A visitor used to traverse the AST structures of all of the compilation units being resolved and build the full set of dependencies for all constant expressions." />
       <item value="visit Library Directive" />
       <item value="Return the result of resolving the file at the given [path]. If a [resourceProvider] is given, it will be used to access the file system. Note that if more than one file is going to be resolved then this function is inefficient. Clients should instead use [AnalysisContextCollection] to create one or more contexts and use those contexts to resolve the files." />
       <item value="Return the result of parsing the file at the given [path]. If a [resourceProvider] is given, it will be used to access the file system. [featureSet] determines what set of features will be assumed by the parser. This parameter is required because the analyzer does not yet have a performant way of computing the correct feature set for a single file to be parsed. Callers that need the feature set to be strictly correct must create an [AnalysisContextCollection], query it to get an [AnalysisContext], query it to get an [AnalysisSession], and then call `getParsedUnit`. Callers that don't need the feature set to be strictly correct can pass in `FeatureSet.latestLanguageVersion()` to enable the default set of features; this is much more performant than using an analysis session, because it doesn't require the analyzer to process the SDK. If [throwIfDiagnostics] is `true` (the default), then if any diagnostics are produced because of syntactic errors in the file an `ArgumentError` will be thrown. If the parameter is `false`, then the caller can check the result to see whether there are any errors." />
@@ -49,16 +54,11 @@
       <item value="The child is forced to fill the available space." />
       <item value="The [Flexible] widget assigns this kind of [FlexFit] to its child." />
       <item value="The [Expanded] widget assigns this kind of [FlexFit] to its child." />
-      <item value="A widget that sizes its child to the child's intrinsic height. This class is useful, for example, when unlimited height is available and you would like a child that would otherwise attempt to expand infinitely to instead size itself to a more reasonable height. The constraints that this widget passes to its child will adhere to the parent's constraints, so if the constraints are not large enough to satisfy the child's maximum intrinsic height, then the child will get less height than it otherwise would. Likewise, if the minimum height constraint is larger than the child's maximum intrinsic height, the child will be given more height than it otherwise would. This class is relatively expensive, because it adds a speculative layout pass before the final layout phase. Avoid using it where possible. In the worst case, this widget can result in a layout that is O(N²) in the depth of the tree." />
-      <item value="remove Material Icons font to reduce deb package size." />
-      <item value="Load Device's Contexts from the iOS SDK. This integration calls the iOS SDK via Message channel to load the Device's contexts before sending the event back to the iOS SDK via Message channel (already enriched with all the information). The Device's contexts are: App, Device and OS. ps. This integration won't be run on Android because the Device's Contexts is set on Android when the event is sent to the Android SDK via the Message channel. We intend to unify this behaviour in the future. This integration is only executed on iOS &amp; MacOS Apps." />
-      <item value="Integration which handles communication with native frameworks in order to enrich [SentryTransaction] objects with app start data for mobile vitals." />
-      <item value="We need to check the platform after we checked for web, because the OS checks return true when the browser runs on the checked platform. Example: platform.isAndroid return true if the browser is used on an Android device." />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="144" />
-        <entry key="ENGLISH" value="145" />
+        <entry key="CHINESE" value="149" />
+        <entry key="ENGLISH" value="150" />
         <entry key="POLISH" value="1" />
         <entry key="ROMANIAN" value="1" />
       </map>