strings.xml file for editing
+and clicking the Open editor link, or clicking the globe icon
+
in the Design layout view and
+choosing Edit Translations.
+emulator), and the Dalvik Debug Monitor S
+If your application supports multiple languages, you need to properly manage your +translated string resources. Android Studio provides the Translations Editor to make viewing and +managing your translated resources easier. +
+ ++Translated resources are stored in multiple XML files in multiple directories in your project. +Manually finding and editing resource files across many translations can be difficult. Because of +this, your application might have missing translations that go unnoticed until after your +application has been built and distributed to users. +
+ ++The Translations Editor lets you view and update all your string resources in one convenient +place. The editor gives you a single view of all of your translated resources, making it easy to +change or add translations, and even find missing translations. +
+ +
+Figure 1. Manage locales and strings in the +Translations Editor.
+ ++Follow these steps to start the Translations Editor: +
+ +strings.xml file (not folder) and select Open
+ Translations Editor.
+You can also access the Translations Editor by opening a strings.xml file for editing
+and clicking the Open editor link, or clicking the globe icon
+ in the Design layout view and
+choosing Edit Translations.
+
+The Translations Editor provides a view of all your string resources and current locale +translations. The name of each resource is listed in the Key column, along with a default value +for the key, a checkbox to mark the key as untranslatable, and values for each locale translation. +
+ ++Edit translations by double-clicking on the translation and editing the value directly +in the list view, or selecting the translation and editing the Translation field +value at the bottom of the editor. The default value can be edited by double-clicking on +the default value or selecting the default value and updating the Default Value +field.
+ ++If a resource is missing a translation and isn't marked untranslatable, the key name is +displayed in red. If you hover over a red resource, Android Studio displays details about the +missing translations. +
+ +
+Add a new resource by clicking the add icon 
. Android Studio prompts you for a key name,
+default value, and resource folder that contains the strings.xml file where the new
+resource is added.
+
+Add additional locales by pressing the globe icon
+ and selecting the locale you want
+to add. The Translations Editor adds the new locale column and creates the translation strings XML
+file in the appropriate project directory.
+
+The Translations Editor has +BCP 47 support, and +combines language and region codes into a single selection for targeted localizations. +
+ ++Clicking the Order a translation link opens a page in your browser where you +can upload string resource XML files and order translation services. App translation services are +available from Google Play and other vendors. For more information about Google Play App +Translation Services, see the +Google Play App Translation Service announcement. +
+ diff --git a/docs/html/tools/studio/studio-features.jd b/docs/html/tools/studio/studio-features.jd index 44d6985dfdc6d..46ec79db26ba3 100644 --- a/docs/html/tools/studio/studio-features.jd +++ b/docs/html/tools/studio/studio-features.jd @@ -42,24 +42,24 @@ andMulti-language support is enhanced with the Translations Editor plugin so you can easily add -a variety of locales to the app's translation file. With -BCP 47 support, the editor -combines language and -region codes into a single selection for targeted localizations. Color codes indicate whether a -locale is complete or still missing string translations.
+If your application supports multiple languages, you need to properly manage your +translated string resources. The Translations Editor lets you view and update all your string +resources in one convenient place.
-To access the Translations Editor, open a strings.xml file and click the
-Open Editor link, or click the globe icon
-() in the Design layout view.
+Use the Translations Editor to view all your translated resources, modify translations, and add +new locales. You can provide default values for your resources and mark resources as +untranslatable. The Translations Editor also marks resources with missing translations in red, +and provides a link to a page where you can upload resource files and order translation services. +
+For more details on the Translations Editor, see +Translations Editor.
-
- Figure 1. Add locales and strings in the
+
+
Figure 1. Manage locales and strings in the Translations Editor.
- -Clicking Import Samples from the File menu or Welcome page provides seamless access to Google code samples on GitHub.
diff --git a/docs/html/tools/tools_toc.cs b/docs/html/tools/tools_toc.cs index b7595ce811f0e..80babf46d340b 100644 --- a/docs/html/tools/tools_toc.cs +++ b/docs/html/tools/tools_toc.cs @@ -176,6 +176,9 @@ class="en">Tools Help