diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index 1b8887b..023e816 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -12,6 +12,10 @@
     <option name="translationDialogLocationY" value="536" />
     <option name="translationDialogWidth" value="1253" />
     <histories>
+      <item value="- `null` - `true` and `false` - Instances of [int], [double], [String] - Instances created through list, map and set literals - Instances created by constructors of: - [List], [Map], [LinkedHashMap], [Set] and [LinkedHashSet] - [TransferableTypedData] - [Capability] - [SendPort] instances from [ReceivePort.sendPort] or [RawReceivePort.sendPort] where the receive ports are created using those classes' constructors. - Instances of [Type] representing one of the types mentioned above, `Object`, `dynamic`, `void` and `Never` as well as nullable variants of all these types. For generic types type arguments must be sendable types for the whole type to be sendable." />
+      <item value="If the sender and receiver isolate share the same code (e.g. isolates created via [Isolate.spawn]), the transitive object graph of [message] can contain any object, with the following exceptions:" />
+      <item value="Instances of classes that either themselves are marked with `@pragma('vm:isolate-unsendable')`, extend or implement such classes cannot be sent through the ports. Apart from those exceptions any object can be sent. Objects that are identified as immutable (e.g. strings) will be shared whereas all other objects will be copied. The send happens immediately and may have a linear time cost to copy the transitive object graph. The send itself doesn't block (i.e. doesn't wait until the receiver has received the message). The corresponding receive port can receive the message as soon as its isolate's event loop is ready to deliver it, independently of what the sending isolate is doing. Note: Due to an implementation choice the Dart VM made for how closures represent captured state, closures can currently capture more state than they need, which can cause the transitive closure to be larger than needed. Open bug to address this: http:dartbug.com36983" />
+      <item value="Illegal argument in isolate message: object is unsendable - Library:'dart:async' Class: _AsyncCompleter@4048458 (see restrictions listed at `SendPort.send()` documentation for more information)" />
       <item value="Sends an asynchronous [message] through this send port, to its corresponding [ReceivePort]. If the sending and receiving isolates do not share the same code (an isolate created using [Isolate.spawnUri] does not share the code of the isolate that spawned it), the transitive object graph of [message] can only contain the following kinds of objects: - `null` - `true` and `false` - Instances of [int], [double], [String] - Instances created through list, map and set literals - Instances created by constructors of: - [List], [Map], [LinkedHashMap], [Set] and [LinkedHashSet] - [TransferableTypedData] - [Capability] - [SendPort] instances from [ReceivePort.sendPort] or [RawReceivePort.sendPort] where the receive ports are created using those classes' constructors. - Instances of [Type] representing one of the types mentioned above, `Object`, `dynamic`, `void` and `Never` as well as nullable variants of all these types. For generic types type arguments must be sendable types for the whole type to be sendable." />
       <item value="See [SendPort.send] for more information about exceptions as well as a note of warning about sending closures, which can capture more state than needed." />
       <item value="The `callback`, the `message` given to it as well as the result have to be objects that can be sent across isolates (as they may be transitively copied if needed). The majority of objects can be sent across isolates." />
@@ -58,16 +62,12 @@
       <item value="Whether this [State] object is currently in a tree. After creating a [State] object and before calling [initState], the framework &quot;mounts&quot; the [State] object by associating it with a [BuildContext]. The [State] object remains mounted until the framework calls [dispose], after which time the framework will never ask the [State] object to [build] again. It is an error to call [setState] unless [mounted] is true." />
       <item value="Whether the [Widget] this context is associated with is currently mounted in the widget tree. Accessing the properties of the [BuildContext] or calling any methods on it is only valid while mounted is true. If mounted is false, assertions will trigger. Once unmounted, a given [BuildContext] will never become mounted again. {@macro flutter.widgets.BuildContext.asynchronous_gap}" />
       <item value="Unhandled Exception: This widget has been unmounted, so the State no longer has a context (and should be considered defunct). Consider canceling any active work during &quot;dispose&quot; or using the &quot;mounted&quot; getter to determine if the State is still active." />
-      <item value="A general-purpose widget for building animations. [AnimatedBuilder] is useful for more complex widgets that wish to include an animation as part of a larger build function. To use [AnimatedBuilder], construct the widget and pass it a builder function. For simple cases without additional state, consider using [AnimatedWidget]. {@youtube 560 315 https:www.youtube.comwatch?v=N-RiyZlv8v8} Despite the name, [AnimatedBuilder] is not limited to [Animation]s, any subtype of [Listenable] (such as [ChangeNotifier] or [ValueNotifier]) can be used to trigger rebuilds. Although they have identical implementations, if an [Animation] is not being listened to, consider using a [ListenableBuilder] for better readability." />
-      <item value="How wide to make edges drawn when [style] is set to [PaintingStyle.stroke]. The width is given in logical pixels measured in the direction orthogonal to the direction of the path. Defaults to 0.0, which correspond to a hairline width." />
-      <item value="A [Comparator] may compare objects as equal (return zero), even if they are distinct objects. The sort function is not guaranteed to be stable, so distinct objects that compare as equal may occur in any order in the result: ```dart final numbers = &lt;String&gt;['one', 'two', 'three', 'four']; numbers.sort((a, b) =&gt; a.length.compareTo(b.length)); print(numbers); [one, two, four, three] OR [two, one, four, three]" />
-      <item value="The default [List] implementations use [Comparable.compare] if [compare] is omitted. ```dart final numbers = &lt;int&gt;[13, 2, -11, 0]; numbers.sort(); print(numbers); [-11, 0, 2, 13] ``` In that case, the elements of the list must be [Comparable] to each other." />
     </histories>
     <option name="languageScores">
       <map>
         <entry key="CHINESE" value="646" />
-        <entry key="CHINESE_SIMPLIFIED" value="93" />
-        <entry key="ENGLISH" value="738" />
+        <entry key="CHINESE_SIMPLIFIED" value="97" />
+        <entry key="ENGLISH" value="742" />
         <entry key="HAWAIIAN" value="1" />
         <entry key="INDONESIAN" value="1" />
         <entry key="NORWEGIAN" value="1" />