Localization Functionality Testing Checklist

Localization Functionality Testing Checklist:-
Cosmetic:

	Text is translated.
	Translations meet the standards of native speakers with respect to grammar and accuracy of terminology.
	Dialog boxes are properly resized and dialog text is hyphenated according to the rules of the user interface language.
	Translated dialog boxes, status bars, toolbars, and menus fit on the screen at different resolutions. They do not wrap and are not cut off.
	Menu and dialog accelerators are unique.
	Visual layout is consistent with the native edition's layout. For example, dialog elements are in the proper tab order.

Functional:

	User can type accented characters and long strings in documents and dialog boxes.
	User can enter text, accelerators, and shortcut-key combinations using international keyboard layouts.
	Documents created in this language edition can be opened successfully in other language editions, and vice versa.
	User can enter dates, times, currencies, and numbers using international formats.
	Sorting and case conversion are culturally accurate.
	Paper size, envelope size, and other defaults are culturally accurate.
	User can save files using filenames that contain accented characters.
	User can successfully print documents that contain accented characters.
	User can successfully cut and paste text that contains accented characters to other applications.
	Application responds to changes in Control Panel's international/locale settings.
	Application works correctly on different types of hardware, particularly on hardware that is sold in the target market.
	Application works correctly on localized editions of Windows, especially on the language edition of Windows that corresponds to the language edition of the application. English language applications work properly on all localized editions of Windows.

The following troubleshooting guide track down cosmetic bugs in localized editions:

Basic Symptom in the Localized Edition	Suggestion
A feature does not work properly.	Check to see whether the feature is also broken in the native-language edition.
Text is cut off.	The string buffer containing the text might need to be larger. If the text is cut off after a single character, the code might be improperly displaying a Unicode string.
Program crashes when, for example, a dialog box is displayed.	A buffer might have overflowed when text was translated. Check the size of the buffers. For Unicode-based programs, make sure that buffers are allocated according to the number of characters as opposed to the number of bytes.
The user cannot enter certain characters using a foreign keyboard layout.	Shortcut-key combinations conflict with combinations used to create characters on the keyboard layout.
Shortcut keys or search keywords features do not function.	Check for hard-coded strings, strings that should be translated but are not, and strings that should not be translated but are. Also check for two strings that should be translated the same way but are not or two strings that must be translated differently but are translated the same way.
Trying to invoke a command via an accelerator or a shortcut-key combination does nothing or invokes the wrong command.	There might be duplicate accelerator or shortcut key combinations.
The user tries to save a file using a filename that contains accented characters but cannot reopen the file with the same name or cannot find the filename in the list of files on the disk.	The file system's character set might be incompatible with the character set the application is using. The application might need to translate filenames to the file system's character set before saving. For filenames, the application should allow the user to type in only characters that are part of the file-system character set. Check to make sure that the code is not stripping the high bit from each letter.
The program cannot find a particular file whose filename contains ideographic characters.	The code might not be properly DBCS enabled. If the trail byte of one of the characters equals a backslash character (\), the code might be misinterpreting the filename as a pathname.
While the program is running on Far East editions of Windows, editing or deleting text causes the program to crash or to display "junk text."	The program is not properly enabled for double-byte character sets.
The space between two words in a message is missing, as in"Error! Cannotprint."	The code is probably concatenating two strings and the translator omitted a trailing or leading space.
A document created in a different language edition of the application does not load correctly.	The two language editions have different file formats or the document was created on an edition of Windows that uses a different default code page and different fonts. Add code to compare the language of the document with available fonts before attempting to display text.