Android Application resource-localization (IV)

 

Localized checklists

These checklists summarize the process of localized Android applications, not that each item in the list applies to each application.

Planning and Designing Checklist

1	Select a localization policy. What countries and languages do applications support? What is the default country and language of the application? What Should an application do if there are no available resources in a given language environment?
2	Everything that needs to be localized in an application: 1. take into account the specific details of the application-text, images, sounds, music, numbers, currency, date, and time. Not everything needs localization. For example, you do not need to localize the text that you cannot see, images of neutral cultures, or icons that share the same meaning in each language environment. 2. Consider a broad theme style. For example, if you want to sell your applications to two markets with great cultural differences, you need to design completely different UIS and representations for each language environment.
3	Try to design resources outside the Java code as much as possible: 1. Use the R. String and strings. xml files to replace the encoded strings and string constants; 2. Use R. drawable and R. layout to replace hard-coded plotting and layout resources.

 

Content Checklist

1	Create a complete default resource set in RES/values/and other res/folders.
2	Obtain reliable translation of static text, including menu text, button name, error message, and help text. Put the translated string in the corresponding Res/Values-<qualifiers>/strings. xml file.
3	Ensure that the application can properly format dynamic text (such as numbers and dates) for each language environment it supports ). Make sure that the application can correctly process the supported language sentences, punctuation marks, and alphabetic sorting.
4	If necessary, create the graphics and layout versions in the special language environment and put them in the Res/drawable-<qualifiers>/and Res/Layout-<qualifiers>/folders.
5	Any localized content required to create an application, for example, creating a sound record file for each supported language.

 

Test and release Checklist

1	To test applications in each supported language environment, if possible, allow local people in each language environment to test the application and give feedback.
2	Test the validity of default resources by loading Language Environments not supported by applications on the device or simulator.
3	Test the localization string in both the horizontal and vertical display modes.
4	Digitally sign and compile the application.
5	Upload the .apk file to Google Play. When uploading the file, select the appropriate language.