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