国际化本地化测试I18N and I10N

1、internationalization hardcoded buffer length can cause system error; hardcoded string length and display position can cause truncated ui; hardcoded text can cause function problem and mixed ui; hardcoded punctuation can cause function and ui showing problem (for example double punctuation). please s

2、ee following example:,i18n check list (cont),dbcs character is garbage in diagram (hardcode font) can not change default shape font (hardcode comma) incorrect string layout (hardcode string length) jsp files hard coded colon(cause ui show double colon) format column color setting does not have effec

3、t (hardcode color name),i18n check list (cont),source localizability: one goal of i18n test is to guarantee software can be localized smoothly, so we need to pay attention of software localizability. we need to check following: extraction of localizable resource, for example, part of srm ui come fro

4、m dataset, this is hard to localize. whether extract un-localizable resource, for example, keywords, variables, formats, delimiters, etc. whether java properties files has incorrect translation common, for example, usually there are date format translation prohibit comments in java properties files,

5、 but date format should be changed to locale specific.,i18n check list (cont),whether string is easy to translate, following situation is hard to translation: - preposition, such as of, on, in, with, for, etc. for example, weeks on, end after, before start date and time,i18n check list (cont),- conc

6、atenate string - using tags in properties string , there maybe display problem, for example, html tag in channel name - using /n to control line length,i18n check list (cont),locale specific character handle: even if we didnt localize software to locale specific ui, we still need to guarantee softwa

7、re can handle locale specific character. for example: user can enter locale specific text in document and dialog user can use locale specific character filename, folder name user can enter locale specific character in graphic, formula, comments, description, label, etc. user can enter dates, times,

8、currencies, and numbers using locale specific formats.,i18n check list (cont),user can successfully print documents that contain locale specific characters. user can successfully cut and paste text that contains locale specific characters to other applications. documents created in locale specific l

9、anguage can be handled successfully. user entered locale specific character can sort correctly.,i18n check list (cont),political sensitive problem: we dont hope our software cause political problem, so must check our copyright and other legal information, and make sure there are no terms that is con

10、flict with local laws. also we should check our maps dataset, and guarantee our maps doesnt have political problem, for example, china map should contain hong kong, macao and taiwan.,i10n check list,during i10n testing, we should check following: localized ui show correctly:first we should guarantee

11、 we can see localized ui , we have problem show localized ui in portal based clients, because we hard coded en_us as default locale. initial language showing is not correct in portal also we should guarantee localized ui show correctly, there are no garbage (odd number words more easy to cause garba

12、ge). localized ui translated correctly:this include date/time changed to locale date/time format, for example, mmm is not acceptable chinese format; currency changed to locale format; data format changed to locale format; telephone number changed to locale format; address changed to locale format, t

13、here are no state in china; special character, such as , , etc.,i10n check list (cont),over translation:over translation can cause function problem, if we translated untranslatable keywords, variables, formats, delimiters, etc, some components maybe doesnt work. for example: format column color sett

14、ing does not have effect (this defect caused by translated color name) can not change default shape font(this defect caused by translated delimiter comma),i10n check list (cont),mixed ui:check the un-translated string, english string and translated string mixed ui is poor ui, we should avoid it. the

15、re are two situations for mixed ui. we forget translate it (maybe project prepare problem) string is hard coded in jsp, xml or sas program, and didnt get extracted.,i10n check list (cont),string layout:check ui string layout, and see there are any overlay string, wrap string, truncated string, verti

16、cal layout string. usually there would be string layout problem initially. for example, string position is incorrect vertical layout string wrapped string string not in same line truncated string,i10n check list (cont),mnemonic:check mnemonic, for mnemonic, we should check it works correctly and dis

17、play according to locale custom. we have known mnemonic problem in dbcs os. for example, underlines for mnemonic keys are misplaced mnemonic key placed in wrong proposition unnecessary mnemonic,i10n check list (cont),sensitive terms:check sensitive terms, sensitive terms include political sensitive

18、terms translation, and personal sensitive terms. we should pay attention to political sensitive terms translation, for example, country name, city name, language name, etc. political sensitive terms we should also pay attention to personal sensitive terms translation, for example, blind, deaf, lame, etc, such words are personal sensitive, we care about their translation.,i10n check list (cont),sorting:check the sorting is locale specific, some document is sorting according to english letters, after translated it sorting is not correct, we had to sort it manually or develop tools