Print-friendly Version

Following is a comprehensive list of all I18n testing questions. Selecting the link will take you to the information page for that question, which offers tips for what, how, and where to test components.

7.1

• Does the product install correctly in a non-English environment?
• Are there any warnings that occur while installing in a non-English environment?
• Are messages generated from the installation localized?
• Can the product be removed correctly in a non-English environment?

7.2

• Are all Translatables separate from the source and placed in a locale-specific location?
• Are all Translatables loaded correctly at runtime?
• If translated items do not exist for a locale, are the correct default values used?
• Are all keywords, protocol elements, etc. excluded from message catalogs and not translated?
• Have all messages been extracted from the product into message catalogs?
• Are fixed text items excluded from the message catalogs?
• Have all messages been reviewed for slang terminology, message fragments, and other criteria that cause messages to be difficult to translate?
• Are the message catalogs installed in locale-specific directories?
• If messages have not been provided for a locale, does the correct default message appear?
• Do all non-message textual objects reside in locale-specific directories?
• If a textual object has not been translated into a specific locale, does the correct default text appear?
• Are all non-message textual objects translatable?
• Are the tools which created the text easily available in other countries, or provided to the country where the localization of these items will take place?
• Are all messages in the GUI correctly internationalized?
• Are object positions relative to other objects and/or are the positions configurable via locale-specific resources?
• Does resizing the GUI work correctly?
• Are all messages and GUI objects completely visible after all messages have been localized?
• Are GUI objects aligned correctly after all messages have been localized?
• If GUI positions or configurations, such as menu items, can be saved by the user, are these configurations in locale-specific directories?
• Do configurations saved in one locale cause problems when the product is started in another locale?
• If the GUI positions are not provided for a locale, does the product use default positions?
• Do all non-textual items reside in locale-specific directories and are the items separate from the source product?
• If an item has not been translated into a specific locale, does the correct default item appear?
• Do any textual messages appear in icons? If so, these messages must be translated separately from the icon.
• Are the tools which created the items easily available in other countries, where the localization of these items will take place?

7.3

• When the product is run in the target locale, is the cultural data formatted correctly for that locale?
• Is the Time, Date and Calendar format in a locale-specific format?
• Can the Time, Date or Calendar format contain non-ASCII text?
• Are numbers displayed in the locale-specific format?
• Is the currency symbol ("$" in American English) displayed in the locale-specific format?
• Are currency strings formatted according to locale conventions?
• If using the International three-letter currency code, is the correct one used?
• Does the sort order change in different locales?
• Is non-ASCII text sorted correctly?
• Are the formats for personal names, honorifics and salutations configurable for each locale?
• Are the formats for postal addresses and telephone numbers configurable for each locale?
• Can a user enter their name, etc. in their native language
• Is the paper size configurable?
• Are there cultural differences in page layout?
• Does the text align correctly to the page when printing?
• Does the application correctly break words for word wrap and hyphenation?
• Does double and triple clicking when selecting words or lines work as expected in a given locale?
• Do the input and operations on multibyte and non-multibyte text in canvases implemented as editors display that text properly?
• Do the operations performed in an editor implemented from a canvas or drawing area, using files with mixed text as above, behave appropriately in different locales?

7.4

• Does the application process non-ASCII data correctly?
• Are non-ASCII filenames and pathnames handled correctly?
• For Solaris products, does the application handle 8-bit characters and multibyte characters?
• For Solaris products, are non-EUC encoded character sets (such as those for ja_JP.PCK or zh_TW.BIG5) handled correctly?
• Can non-ASCII characters be saved and loaded correctly from the filesystem?
• If the application transfers data through protocols or networks that strip the 8th bit, does the application encode, decode, and display the data correctly?
• If the product includes a help browser or web browser:
  • Can the browser load files or pages in different encodings?
  • Does the browser properly display files or pages with multibyte text?
  • Once a file is loaded, is it possible to display it in another encoding?
  • Do pages with the encoding indicated in a <META> tag load in that encoding?
  • If allowed, are files saved in the chosen encoding?
  • Do visited pages remember the encoding with which they were loaded?
  • Does viewing HTML source in an editor show the file in the encoding in which the file was loaded?
  • Do files or pages containing multibyte text print correctly?
  • Do bookmarks and menus show filenames with multibyte text correctly?
• Does the application correctly accept, parse and display non-ASCII input in all places where it is appropriate to enter non-ASCII text?
• As non-ASCII text is being entered, does the backspace key correctly delete the non-ASCII text?
• Can all areas of the application display all characters within the current locale?