1page.title=Localization 2parent.title=Application Resources 3parent.link=index.html 4@jd:body 5 6<div id="qv-wrapper"> 7 <div id="qv"> 8 9<h2>Localization quickview</h2> 10 11<ul> 12 <li>Android lets you create different resource sets for different locales.</li> 13 <li>When your application runs, Android will load the resource set 14that match the device's locale.</li> 15 <li>If locale-specific resources are not available, Android falls back to 16defaults.</li> 17 <li>The emulator has features for testing localized apps. </li> 18</ul> 19 20<h2>In this document</h2> 21<ol> 22 <li><a href="#resource-switching">Overview: Resource-Switching in Android</a> 23 24</li> 25<ol><li><a href="#defaults-r-important">Why Default Resources Are Important</a></li></ol> 26<li><a href="#using-framework">Using Resources for Localization</a> 27 <ol> 28 <li><a href="#creating-defaults">How to Create Default Resources</a></li> 29 <li><a href="#creating-alternatives">How to Create Alternative Resources</a></li> 30 <li><a href="#resource-precedence">Which Resources Take Precedence?</a></li> 31 <li><a href="#referring-to-resources">Referring to Resources in Java</a></li> 32 </ol> 33</li> 34<li><a href="#strategies">Localization Strategies</a></li> 35<li><a href="#testing">Testing Localized Applications</a></li> 36 <ol> 37 <li><a href="#device">Testing on a Device</a></li> 38 <li><a href="#emulator">Testing on an Emulator</a></li> 39 <li><a href="#test-for-default">Testing for Default Resources</a></li> 40 </ol> 41<li><a href="#checklist">Localization Checklists</a></li> 42 <ol> 43 <li><a href="#planning-checklist">Planning and Design Checklist</a></li> 44 <li><a href="#content-checklist">Content Checklist</a></li> 45 <li><a href="#testing-checklist">Testing and Publishing Checklist</a></li> 46 </ol> 47</ol> 48 49<h2>See also</h2> 50 <ol> 51 <li><a 52href="{@docRoot}resources/tutorials/localization/index.html">Hello, L10N Tutorial</a></li> 53 <li><a href="{@docRoot}guide/topics/resources/providing-resources.html">Providing Resources</a></li> 54 <li><a href="{@docRoot}guide/topics/ui/declaring-layout.html">Layouts</a></li> 55 <li><a href="{@docRoot}reference/android/app/Activity.html#ActivityLifecycle">Activity Lifecycle</a></li> 56</ol> 57</div> 58</div> 59 60<p>Android will run on many devices in many regions. To reach the most users, 61your application should handle text, audio files, numbers, currency, and 62graphics in ways appropriate to the locales where your application will be used. 63</p> 64 65<p>This document describes best practices for localizing Android 66applications. The principles apply whether you are developing your application 67using ADT with Eclipse, Ant-based tools, or any other IDE. </p> 68 69<p>You should already have a working knowledge of Java and be familiar with 70Android resource loading, the declaration of user interface elements in XML, 71development considerations such as Activity lifecycle, and general principles of 72internationalization and localization. </p> 73 74<p>It is good practice to use the Android resource framework to separate the 75localized aspects of your application as much as possible from the core Java 76functionality:</p> 77 78<ul> 79 <li>You can put most or all of the <em>contents</em> of your application's 80user interface into resource files, as described in this document and in <a 81href="{@docRoot}guide/topics/resources/providing-resources.html">Providing Resources</a>.</li> 82 <li>The <em>behavior</em> of the user interface, on the other hand, is driven 83by your Java code. 84 For example, if users input data that needs to be formatted or sorted 85differently depending on locale, then you would use Java to handle the data 86programmatically. This document does not cover how to localize your Java code. 87</li> 88</ul> 89 90<p>The <a 91href="{@docRoot}resources/tutorials/localization/index.html">Hello, L10N 92</a> tutorial takes you through the steps of creating a simple localized 93application that uses locale-specific resources in the way described in this 94document. </p> 95 96 97<h2 id="resource-switching">Overview: Resource-Switching in Android</h2> 98 99<p>Resources are text strings, layouts, sounds, graphics, and any other static 100data that your Android application needs. An application can include multiple 101sets of resources, each customized for a different device configuration. When a 102user runs the application, Android automatically selects and loads the 103resources that best match the device.</p> 104 105<p>(This document focuses on localization and locale. For a complete description 106of resource-switching and all the types of configurations that you can 107specify — screen orientation, touchscreen type, and so on — see <a 108href="{@docRoot}guide/topics/resources/providing-resources.html#AlternativeResources">Providing 109Alternative Resources</a>.)</p> 110 111<table border="0" cellspacing="0" cellpadding="0"> 112 <tr border="0"> 113 <td width="180" style="border: 0pt none ;"><p class="special-note"> 114 <strong>When you write your application:</strong> 115 <br><br> 116 You create a set of default resources, plus alternatives to be used in 117 different locales.</p></td> 118 <td style="border: 0pt none; padding:0"> 119 <p style="border:0; padding:0"><img src="../../../images/resources/right-arrow.png" alt="right-arrow" 120 width="51" height="17"></p></td> 121 <td width="180" style="border: 0pt none ;"><p class="special-note"> 122 <strong>When a user runs your application:</strong> 123 <br><br>The Android system selects which resources to load, based on the 124 device's locale.</p></td> 125 </tr> 126</table> 127 128<p>When you write your application, you create default and alternative resources 129for your application to use. To create resources, you place files within 130specially named subdirectories of the project's <code>res/</code> directory. 131</p> 132 133 134 135<h3 id="defaults-r-important">Why Default Resources Are Important</h3> 136 137<p>Whenever the application runs in a locale for which you have not provided 138locale-specific text, Android will load the default strings from 139<code>res/values/strings.xml</code>. If this default file is absent, or if it 140is missing a string that your application needs, then your application will not run 141and will show an error. 142The example below illustrates what can happen when the default text file is incomplete. </p> 143 144<p><em>Example:</em> 145<p>An application's Java code refers to just two strings, <code>text_a</code> and 146 <code>text_b</code>. This application includes a localized resource file 147 (<code>res/values-en/strings.xml</code>) that defines <code>text_a</code> and 148 <code>text_b</code> in English. This application also includes a default 149 resource file (<code>res/values/strings.xml</code>) that includes a 150definition for <code>text_a</code>, but not for <code>text_b</code>: 151<ul> 152 <li>This application might compile without a problem. An IDE such as Eclipse 153 will not highlight any errors if a resource is missing.</li> 154 <li>When this application is launched on a device with locale set to English, 155 the application might run without a problem, because 156 <code>res/values-en/strings.xml</code> contains both of the needed text 157 strings.</li> 158 <li>However, <strong>the user will see an error message and a Force Close 159 button</strong> when this application is launched on a device set to a 160 language other than English. The application will not load.</li> 161</ul> 162 163 164<p>To prevent this situation, make sure that a <code>res/values/strings.xml</code> 165 file exists and that it defines every needed string. The situation applies to 166 all types of resources, not just strings: You 167 need to create a set of default resource files containing all 168 the resources that your application calls upon — layouts, drawables, 169 animations, etc. For information about testing, see <a href="#test-for-default"> 170 Testing for Default Resources</a>.</p> 171 172<h2 id="using-framework">Using Resources for Localization</h2> 173 174<h3 id="creating-defaults">How to Create Default Resources</h3> 175 176<p>Put the application's default text in 177a file with the following location and name:</p> 178<p><code> res/values/strings.xml</code> (required directory)</p> 179 180<p>The text strings in <code>res/values/strings.xml</code> should use the 181default language, which is the language that you expect most of your application's users to 182speak. </p> 183 184<p>The default resource set must also include any default drawables and layouts, 185 and can include other types of resources such as animations. 186<br> 187 <code> res/drawable/</code>(required directory holding at least 188 one graphic file, for the application's icon on Google Play)<br> 189 <code> res/layout/</code> (required directory holding an XML 190 file that defines the default layout)<br> 191 <code> res/anim/</code> (required if you have any 192 <code>res/anim-<em><qualifiers></em></code> folders)<br> 193 <code> res/xml/</code> (required if you have any 194 <code>res/xml-<em><qualifiers></em></code> folders)<br> 195 <code> res/raw/</code> (required if you have any 196 <code>res/raw-<em><qualifiers></em></code> folders) 197</p> 198 199<p class="note"><strong>Tip:</strong> In your code, examine each reference to 200 an Android resource. Make sure that a default resource is defined for each 201 one. Also make sure that the default string file is complete: A <em> 202 localized</em> string file can contain a subset of the strings, but the 203 <em>default</em> string file must contain them all. 204</p> 205 206<h3 id="creating-alternatives">How to Create Alternative Resources</h3> 207 208<p>A large part of localizing an application is providing alternative text for 209different languages. In some cases you will also provide alternative graphics, 210sounds, layouts, and other locale-specific resources. </p> 211 212<p>An application can specify many <code>res/<em><qualifiers></em>/</code> 213directories, each with different qualifiers. To create an alternative resource for 214a different locale, you use a qualifier that specifies a language or a 215language-region combination. (The name of a resource directory must conform 216to the naming scheme described in 217<a href="{@docRoot}guide/topics/resources/providing-resources.html#AlternativeResources">Providing 218Alternative Resources</a>, 219or else it will not compile.)</p> 220 221<p><em>Example:</em></p> 222 223<p>Suppose that your application's default language is English. Suppose also 224that you want to localize all the text in your application to French, and most 225of the text in your application (everything except the application's title) to 226Japanese. In this case, you could create three alternative <code>strings.xml</code> 227files, each stored in a locale-specific resource directory:</p> 228 229<ol> 230 <li><code>res/values/strings.xml</code><br> 231 Contains English text for all the strings that the application uses, 232including text for a string named <code>title</code>.</li> 233 <li><code>res/values-fr/strings.xml</code><br> 234 Contain French text for all the strings, including <code>title</code>.</li> 235 <li><code>res/values-ja/strings.xml</code><br> 236 Contain Japanese text for all the strings <em>except</em> 237<code>title</code>.<br> 238 <code></code></li> 239</ol> 240 241<p>If your Java code refers to <code>R.string.title</code>, here is what will 242happen at runtime:</p> 243 244<ul> 245 <li>If the device is set to any language other than French, Android will load 246<code>title</code> from the <code>res/values/strings.xml</code> file.</li> 247 <li>If the device is set to French, Android will load <code>title</code> from 248the <code>res/values-fr/strings.xml</code> file.</li> 249</ul> 250 251<p>Notice that if the device is set to Japanese, Android will look for 252<code>title</code> in the <code>res/values-ja/strings.xml</code> file. But 253because no such string is included in that file, Android will fall back to the 254default, and will load <code>title</code> in English from the 255<code>res/values/strings.xml</code> file. </p> 256 257<h3 id="resource-precedence">Which Resources Take Precedence?</h3> 258 259<p> If multiple resource files match a device's configuration, Android follows a 260set of rules in deciding which file to use. Among the qualifiers that can be 261specified in a resource directory name, <strong>locale almost always takes 262precedence</strong>. </p> 263<p><em>Example:</em></p> 264 265<p>Assume that an application includes a default set of graphics and two other 266sets of graphics, each optimized for a different device setup:</p> 267 268<ul> 269 <li><code>res/drawable/</code><br> 270 Contains 271 default graphics.</li> 272 <li><code>res/drawable-small-land-stylus/</code><br> 273 Contains graphics optimized for use with a device that expects input from a 274 stylus and has a QVGA low-density screen in landscape orientation.</li> 275 <li><code>res/drawable-ja/</code> <br> 276 Contains graphics optimized for use with Japanese.</li> 277</ul> 278 279<p>If the application runs on a device that is configured to use Japanese, 280Android will load graphics from <code>res/drawable-ja/</code>, even if the 281device happens to be one that expects input from a stylus and has a QVGA 282low-density screen in landscape orientation.</p> 283 284<p class="note"><strong>Exception:</strong> The only qualifiers that take 285precedence over locale in the selection process are MCC and MNC (mobile country 286code and mobile network code). </p> 287 288<p><em>Example:</em></p> 289 290<p>Assume that you have the following situation:</p> 291 292<ul> 293 <li>The application code calls for <code>R.string.text_a</code></li> 294 <li>Two relevant resource files are available: 295 <ul> 296 <li><code>res/values-mcc404/strings.xml</code>, which includes 297<code>text_a</code> in the application's default language, in this case 298English.</li> 299 <li><code>res/values-hi/strings.xml</code>, which includes 300<code>text_a</code> in Hindi.</li> 301 </ul> 302 </li> 303 <li>The application is running on a device that has the following 304configuration: 305 <ul> 306 <li>The SIM card is connected to a mobile network in India (MCC 404).</li> 307 <li>The language is set to Hindi (<code>hi</code>).</li> 308 </ul> 309 </li> 310</ul> 311 312<p>Android will load <code>text_a</code> from 313<code>res/values-mcc404/strings.xml</code> (in English), even if the device is 314configured for Hindi. That is because in the resource-selection process, Android 315will prefer an MCC match over a language match. </p> 316 317<p>The selection process is not always as straightforward as these examples 318suggest. Please read <a 319href="{@docRoot}guide/topics/resources/providing-resources.html#BestMatch">How Android Finds 320the Best-matching Resource</a> for a more nuanced description of the 321process. All the qualifiers are described and listed in order of 322precedence in <a 323href="{@docRoot}guide/topics/resources/providing-resources.html#table2">Table 2 of Providing 324Alternative Resources</a>.</p> 325 326<h3 id="referring-to-resources">Referring to Resources in Java</h3> 327 328<p>In your application's Java code, you refer to resources using the syntax 329<code>R.<em>resource_type</em>.<em>resource_name</em></code> or 330<code>android.R.<em>resource_type</em>.<em>resource_name</em></code><em>.</em> 331For more about this, see <a 332href="{@docRoot}guide/topics/resources/accessing-resources.html">Accessing Resources</a>.</p> 333 334<h2 id="strategies">Localization Strategies</h2> 335 336<h4 id="failing2">Design your application to work in any locale</h4> 337 338<p>You cannot assume anything about the device on which a user will 339run your application. The device might have hardware that you were not 340anticipating, or it might be set to a locale that you did not plan for or that 341you cannot test. Design your application so that it will function normally or fail gracefully no 342matter what device it runs on.</p> 343 344<p class="note"><strong>Important:</strong> Make sure that your application 345includes a full set of default resources.</p> <p>Make sure to include 346<code>res/drawable/</code> and a <code>res/values/</code> folders (without any 347additional modifiers in the folder names) that contain all the images and text 348that your application will need. </p> 349 350<p>If an application is missing even one default resource, it will not run on a 351 device that is set to an unsupported locale. For example, the 352 <code>res/values/strings.xml</code> default file might lack one string that 353 the application needs: When the application runs in an unsupported locale and 354 attempts to load <code>res/values/strings.xml</code>, the user will see an 355 error message and a Force Close button. An IDE such as Eclipse will not 356 highlight this kind of error, and you will not see the problem when you 357 test the application on a device or emulator that is set to a supported locale.</p> 358 359<p>For more information, see <a href="#test-for-default">Testing for Default Resources</a>.</p> 360 361<h4>Design a flexible layout</h4> 362 363<p> If you need to rearrange your layout to fit a certain language (for example 364German with its long words), you can create an alternative layout for that 365language (for example <code>res/layout-de/main.xml</code>). However, doing this 366can make your application harder to maintain. It is better to create a single 367layout that is more flexible.</p> 368 369<p>Another typical situation is a language that requires something different in 370its layout. For example, you might have a contact form that should include two 371name fields when the application runs in Japanese, but three name fields when 372the application runs in some other language. You could handle this in either of 373two ways:</p> 374 375<ul> 376 <li>Create one layout with a field that you can programmatically enable or 377disable, based on the language, or</li> 378 <li>Have the main layout include another layout that includes the changeable 379field. The second layout can have different configurations for different 380languages.</li> 381</ul> 382 383<h4>Avoid creating more resource files and text strings than you need</h4> 384 385<p>You probably do not need to create a locale-specific 386alternative for every resource in your application. For example, the layout 387defined in the <code>res/layout/main.xml</code> file might work in any locale, 388in which case there would be no need to create any alternative layout files. 389</p> 390 391<p>Also, you might not need to create alternative text for every 392string. For example, assume the following:</p> 393 394<ul> 395 <li>Your application's default language is American 396English. Every string that the application uses is defined, using American 397English spellings, in <code>res/values/strings.xml</code>. </li> 398 399 <li>For a few important phrases, you want to provide 400British English spelling. You want these alternative strings to be used when your 401application runs on a device in the United Kingdom. </li> 402</ul> 403 404<p>To do this, you could create a small file called 405<code>res/values-en-rGB/strings.xml</code> that includes only the strings that 406should be different when the application runs in the U.K. For all the rest of 407the strings, the application will fall back to the defaults and use what is 408defined in <code>res/values/strings.xml</code>.</p> 409 410<h4>Use the Android Context object for manual locale lookup</h4> 411 412<p>You can look up the locale using the {@link android.content.Context} object 413that Android makes available:</p> 414 415<pre>String locale = context.getResources().getConfiguration().locale.getDisplayName();</pre> 416 417<h2 id="testing">Testing Localized Applications</h2> 418 419<h3 id="device">Testing on a Device</h3> 420<p>Keep in mind that the device you are testing may be significantly different from 421 the devices available to consumers in other geographies. The locales available 422 on your device may differ from those available on other devices. Also, the 423 resolution and density of the device screen may differ, which could affect 424 the display of strings and drawables in your UI.</p> 425 426<p>To change the locale on a device, use the Settings application (Home > 427Menu > Settings > Locale & text > Select locale). </p> 428 429<h3 id="emulator">Testing on an Emulator</h3> 430 431<p>For details about using the emulator, see See <a 432href="{@docRoot}tools/help/emulator.html">Android Emulator</a>.</p> 433<h4>Creating and using a custom locale</h4> 434 435<p>A "custom" locale is a language/region combination that the Android 436system image does not explicitly support. (For a list of supported locales in 437Android platforms see the Version Notes in the <a 438href="{@docRoot}sdk/index.html">SDK</a> tab). You can test 439how your application will run in a custom locale by creating a custom locale in 440the emulator. There are two ways to do this:</p> 441 442<ul> 443 <li>Use the Custom Locale application, which is accessible from the 444Application tab. (After you create a custom locale, switch to it by 445pressing and holding the locale name.)</li> 446 <li>Change to a custom locale from the adb shell, as described below.</li> 447</ul> 448 449<p>When you set the emulator to a locale that is not available in the Android 450system image, the system itself will display in its default language. Your 451application, however, should localize properly.</p> 452 453<h4>Changing the emulator locale from the adb shell</h4> 454 455<p>To change the locale in the emulator by using the adb shell. </p> 456 457<ol> 458 <li>Pick the locale you want to test and determine its language and region codes, for 459example <code>fr</code> for French and <code>CA</code> for Canada.<br> 460 </li> 461 <li>Launch an emulator.</li> 462 <li>From a command-line shell on the host computer, run the following 463command:<br> 464 <code>adb shell</code><br> 465 or if you have a device attached, specify that you want the emulator by adding 466the <code>-e</code> option:<br> 467 <code>adb -e shell</code></li> 468 <li>At the adb shell prompt (<code>#</code>), run this command: <br> 469 <code>setprop persist.sys.language [<em>language code</em>];setprop 470persist.sys.country [<em>country code</em>];stop;sleep 5;start <br> 471 </code>Replace bracketed sections with the appropriate codes from Step 4721.</li> 473</ol> 474 475<p>For instance, to test in Canadian French:</p> 476 477<p><code>setprop persist.sys.language fr;setprop persist.sys.country 478CA;stop;sleep 5;start </code></p> 479 480<p>This will cause the emulator to restart. (It will look like a full reboot, 481but it is not.) Once the Home screen appears again, re-launch your application (for 482example, click the Run icon in Eclipse), and the application will launch with 483the new locale. </p> 484 485<h3 id="test-for-default">Testing for Default Resources</h3> 486<p>Here's how to test whether an application includes every string resource that it needs: </p> 487<ol><li>Set the emulator or device to a language that your application does not 488 support. For example, if the application has French strings in 489 <code>res/values-fr/</code> but does not have any Spanish strings in 490 <code>res/values-es/</code>, then set the emulator's locale to Spanish. 491 (You can use the Custom Locale application to set the emulator to an 492 unsupported locale.)</li> 493 <li>Run the application.</li> 494<li>If the application shows an error message and a Force Close button, it might 495 be looking for a string that is not available. Make sure that your 496 <code>res/values/strings.xml</code> file includes a definition for 497 every string that the application uses.</li> 498</ol> 499</p> 500 501<p>If the test is successful, repeat it for other types of 502 configurations. For example, if the application has a layout file called 503 <code>res/layout-land/main.xml</code> but does not contain a file called 504 <code>res/layout-port/main.xml</code>, then set the emulator or device to 505 portrait orientation and see if the application will run. 506 507 508<h2 id="checklist">Localization Checklists</h2> 509 510<p>These checklists summarize the process of localizing an Android application. 511Not everything on these lists will apply to every application.</p> 512 513<h3 id="planning-checklist">Planning and Design Checklist</h3> 514 515<table width="100%" border="0" cellpadding="5" cellspacing="0"> 516 <tr> 517 <td valign="top" align="center"><img src="../../../images/resources/arrow.png" alt="arrow" width="26" 518border="0"></td> 519 <td>Choose a localization strategy. Which countries and which languages will 520your application support? What is your application's default country and 521language? How will your application behave when it does not have specific 522resources available for a given locale?</td> 523 </tr> 524 <tr> 525 <td valign="top" align="center"><img src="../../../images/resources/arrow.png" alt="arrow" width="26" 526border="0"></td> 527 <td><p>Identify everything in your application that will need to be 528localized: </p> 529 <ul> 530 <li>Consider specific details of your application — text, images, 531sounds, music, numbers, money, dates and times. You might not need to localize 532everything. For example, you don't need to localize text that the user never 533sees, or images that are culturally neutral, or icons that convey the same 534meaning in every locale. </li> 535 <li>Consider broad themes. For example, if you hope to sell your 536application in two very culturally different markets, you might want to design 537your UI and present your application in an entirely different way for each 538locale.</li> 539 </ul></td> 540 </tr> 541 <tr> 542 <td valign="top" align="center"><img src="../../../images/resources/arrow.png" alt="arrow" width="26" 543border="0"></td> 544 <td><p>Design your Java code to externalize resources wherever possible:</p> 545 <ul> 546 <li>Use <code>R.string</code> and <code>strings.xml</code> files instead 547of hard-coded strings or string constants. </li> 548 <li>Use <code>R.drawable</code> and <code>R.layout</code> instead of 549hard-coded drawables or layouts. </li> 550 </ul></td> 551 </tr> 552</table> 553<h3 id="content-checklist">Content Checklist</h3> 554<table border="0" cellspacing="0" cellpadding="5" width="100%"> 555 <tr> 556 <td valign="top" align="center"><img src="../../../images/resources/arrow.png" alt="arrow" width="26" 557border="0"></td> 558 <td>Create a full set of default resources in <code>res/values/</code> and 559other <code>res/</code> folders, as described in <a 560href="#creating-defaults">Creating Default Resources</a>.</td> 561 </tr> 562 <tr> 563 <td valign="top" align="center"><img src="../../../images/resources/arrow.png" alt="arrow" width="26" 564border="0"></td> 565 <td>Obtain reliable translations of the static text, including menu text, 566button names, error messages, and help text. Place the translated strings in 567<code>res/values-<em><qualifiers></em>/strings.xml</code> files. </td> 568 </tr> 569 <tr> 570 <td valign="top" align="center"><img src="../../../images/resources/arrow.png" alt="arrow" width="26" 571border="0"></td> 572 <td>Make sure that your application correctly formats dynamic text (for 573example numbers and dates) for each supported locale. Make sure that your 574application handles word breaks, punctuation, and alphabetical sorting correctly 575for each supported language.</td> 576 </tr> 577 <tr> 578 <td valign="top" align="center"><img src="../../../images/resources/arrow.png" alt="arrow" width="26" 579border="0"></td> 580 <td>If necessary, create locale-specific versions of your graphics and 581layout, and place them in <code>res/drawable-<em><qualifiers></em>/</code> and 582<code>res/layout-<em><qualifiers></em>/</code> folders.</td> 583 </tr> 584 <tr> 585 <td valign="top" align="center"><img src="../../../images/resources/arrow.png" alt="arrow" width="26" 586border="0"></td> 587 <td>Create any other localized content that your application requires; for 588example, create recordings of sound files for each language, as needed.</td> 589 </tr> 590</table> 591<h3 id="testing-checklist">Testing and Publishing Checklist</h3> 592 <table border="0" cellspacing="0" cellpadding="5" width="100%"> 593 <tr> 594 <td valign="top" align="center"><img src="../../../images/resources/arrow.png" alt="arrow" width="26" 595border="0"></td> 596 <td>Test your application for each supported locale. If possible, have a 597person who is native to each locale test your application and give you 598feedback.</td> 599 </tr> 600 <tr> 601 <td valign="top" align="center"><img src="../../../images/resources/arrow.png" alt="arrow" width="26" 602border="0"></td> 603 <td>Test the default resources by loading a locale that is not available on 604 the device or emulator. For instructions, see <a href="#test-for-default"> 605 Testing for Default Resources</a>. </td> 606 </tr> 607 <tr> 608 <td valign="top" align="center"><img src="../../../images/resources/arrow.png" alt="arrow" width="26" 609border="0"></td> 610 <td>Test the localized strings in both landscape and portrait display modes.</td> 611 </tr> 612 <tr> 613 <td valign="top" align="center"><img src="../../../images/resources/arrow.png" alt="arrow" width="26" 614border="0"></td> 615 <td>Sign your application and create your final build or builds.</td> 616 </tr> 617 <tr> 618 <td valign="top" align="center"><img src="../../../images/resources/arrow.png" alt="arrow" width="26" 619border="0"></td> 620 <td>Upload your .apk file or files to Google Play, selecting the appropriate 621languages as 622 you upload.</td> 623 </tr> 624</table>
