debuggerx/AndroidStudioSettings
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

AI-Hedgehog | 2023.1.1 <debuggerx@debuggerx-work Update yiiguxing.translation.xml

Browse Source
This commit is contained in:
DebuggerX
2023-12-06 19:00:55 +08:00
parent 524d362699
commit fa2d2d6048
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
yiiguxing.translation.xml
+2 -2
View File
@@ -8,6 +8,7 @@
</component> </component>
<component name="Translation.States"> <component name="Translation.States">
<histories> <histories>
<item value="The destinations to be used in navigation items. These are converted to [NavigationRailDestination]s and [BottomNavigationBarItem]s and inserted into the appropriate places. If passing destinations, you must also pass a selected index to be used by the [NavigationRail]." />
<item value="str contect service" /> <item value="str contect service" />
<item value="str contect" /> <item value="str contect" />
<item value="改变心愿钥匙汇率文案" /> <item value="改变心愿钥匙汇率文案" />
@@ -57,12 +58,11 @@
<item value="The area of the flutter view occupied by this display feature, measured in logical pixels. On devices with two screens, the Flutter view spans from the top-left corner of the left or top screen to the bottom-right corner of the right or bottom screen, including the visual area occupied by any display feature. Bounds of display features are reported in this coordinate system. For example, on a dual screen device in portrait mode: [bounds.left] gives you the size of left screen, in logical pixels. [bounds.right] gives you the size of the left screen + the hinge width." /> <item value="The area of the flutter view occupied by this display feature, measured in logical pixels. On devices with two screens, the Flutter view spans from the top-left corner of the left or top screen to the bottom-right corner of the right or bottom screen, including the visual area occupied by any display feature. Bounds of display features are reported in this coordinate system. For example, on a dual screen device in portrait mode: [bounds.left] gives you the size of left screen, in logical pixels. [bounds.right] gives you the size of the left screen + the hinge width." />
<item value="seems not support avahi." /> <item value="seems not support avahi." />
<item value="pragma" /> <item value="pragma" />
<item value="lexeme" />
</histories> </histories>
<option name="languageScores"> <option name="languageScores">
<map> <map>
<entry key="CHINESE" value="227" /> <entry key="CHINESE" value="227" />
<entry key="ENGLISH" value="225" /> <entry key="ENGLISH" value="226" />
<entry key="HAWAIIAN" value="1" /> <entry key="HAWAIIAN" value="1" />
<entry key="POLISH" value="1" /> <entry key="POLISH" value="1" />
<entry key="ROMANIAN" value="1" /> <entry key="ROMANIAN" value="1" />