际化本地化测试I18N and I1N.ppt

Internationalization Localization Objectives of the Presentation What This Presentation IS It provides definitions of terminology. It gives background information about internationalization and localization It identifies the high- risk areas for NLS testing. It gives I18N and I10N checklist. What This Presentation Is NOT It is not an in-depth discussion of all possible aspects. It does not provide solutions to very specific problems.  Questions about internationalization and localization Q1: I only provide English software, so I need not do internationalization?A1: No, even if you didn’t provide localized software, you still need to internationalize your software to guarantee it run successfully on Non-English OS. Q2: Localization is simple, you only need to translate the UI to local language? A2: No, Translation is only part of localization. Q3: Localization testing only to test the UI translation is correct or not? A3: No, we do all unite test as well as system test to guarantee all function works correctly in DBCS OS. Part I: Basic concepts Internationalization Localization Locale Encoding Characters Sets Font Transcoding Translate Table Background of Unicode NLS Terminology Internationalization (I18N): Internationalization abbreviated as i18n, because there are 18 letters between the i and the n. I18N is the process of designing an application so that the feature design and code design do not make assumptions based on a single language or locale. Internationalization also assumes that the source code base simplifies the creation of different language editions of a program. One goal of internationalization is to ensure that international conventions (including rules for sorting strings and for formatting dates, times, numbers, and currencies) are supported. Another goal is to design the product in such a way that users will have a consistent look, feel, and functionality across different language editions of a product. NLS