diff --git a/ProjectCreationInfoService.xml b/ProjectCreationInfoService.xml
index ad645c9..b3d82ff 100644
--- a/ProjectCreationInfoService.xml
+++ b/ProjectCreationInfoService.xml
@@ -1,5 +1,5 @@
 <application>
   <component name="ProjectCreationInfoState"><![CDATA[{
-  "lastCreatedProjectBuilderId": "JAVA_MODULE_io.flutter.module.FlutterModuleBuilder"
+  "lastCreatedProjectBuilderId": "DartModuleBuilder"
 }]]></component>
 </application>
\ No newline at end of file
diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index 690377a..0004e05 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -4,6 +4,7 @@
   </component>
   <component name="Translation.States">
     <histories>
+      <item value="data not valid: fields count should be 13" />
       <item value="Specifies the [SystemUiMode] to have visible when the application is running. The `overlays` argument is a list of [SystemUiOverlay] enum values denoting the overlays to show when configured with [SystemUiMode.manual]. If a particular mode is unsupported on the platform, enabling or disabling that mode will be ignored. The settings here can be overridden by the platform when System UI becomes necessary for functionality. For example, on Android, when the keyboard becomes visible, it will enable the navigation bar and status bar system UI overlays. When the keyboard is closed, Android will not restore the previous UI visibility settings, and the UI visibility cannot be changed until 1 second after the keyboard is closed to prevent malware locking users from navigation buttons. To regain &quot;fullscreen&quot; after text entry, the UI overlays can be set again after a delay of at least 1 second through [restoreSystemUIOverlays] or calling this again. Otherwise, the original UI overlay settings will be automatically restored only when the application loses and regains focus. Alternatively, a [SystemUiChangeCallback] can be provided to respond to changes in the System UI. This will be called, for example, when in [SystemUiMode.leanBack] and the user taps the screen to bring up the system overlays. The callback provides a boolean to represent if the application is currently in a fullscreen mode or not, so that the application can respond to these changes. When `systemOverlaysAreVisible` is true, the application is not fullscreen. See [SystemChrome.setSystemUIChangeCallback] to respond to these changes in a fullscreen application." />
       <item value="Fullscreen display with status and navigation bars presentable by tapping anywhere on the display. Available starting at SDK 16 or Android J. Earlier versions of Android will not be affected by this setting. For applications running on iOS, the status bar and home indicator will be hidden for a similar fullscreen experience. Tapping on the screen displays overlays, this gesture is not received by the application. See also: [SystemUiChangeCallback], used to listen and respond to the change in system overlays." />
       <item value="landscape" />
@@ -25,8 +26,8 @@
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="17" />
-        <entry key="ENGLISH" value="18" />
+        <entry key="CHINESE" value="18" />
+        <entry key="ENGLISH" value="19" />
       </map>
     </option>
   </component>