Quality Assurance for Software Localization (QM v6.3)

QM criteria are made use of to ensure that the localized Windows or .NET resources work smoothly after the localization. If, for example, the placeholder %s exists in the source text but not in the target text, the application may be prone to problems such as crashes.

While the task is being processed in crossDesk, the QM criteria continuously check the text for QM errors. Any QM errors are displayed in the QM view of crossView (icn_cDesk_cView_qmv63), where they can easily be corrected. Moreover, an overview of all QM errors is displayed when the task is finished.

  • The following QM criteria are available for Windows and .NET resources:
  • Bounding spaces: Checks the consistent use of white spaces at the beginning and end of a paragraph.
  • Different file extensions: Checks the consistent use of file extensions like *.exe. The criterion considers all file extensions containing the component *., i.e. *.exe as well as other extensions like *.RESOURCE.
  • Hotkey: On the one hand, makes sure that hotkeys (e.g. Alt&F for opening the File menu) are used in dialogs and menus, and, on the other, that these are not used twice.
  • Overlapping controls: Checks whether there are any control elements (e.g. buttons) that overlap with each other or with a group field (dialog area containing several control elements).

    If controls already overlap in the source text and this state is maintained in the target text as well, the QM criterion will not report any error, as overlapping controls in the source text are usually intended and should therefore also be ignored with respect to the corresponding overlapping controls in the target text.

  • Attention

    The criterion can only be checked for .NET resources if they contain information about the size and position of the controls, i.e. if they have not been defined using layout definitions (e.g. AutoSize or AutoPosition command).

  • Placeholders: Checks the correctness of printf placeholders like %d, %s (in Windows resources) or {1}, {2} etc. (in .NET resources). In this context, the QM criterion checks
    • the correctness of the actual placeholders, e.g. %d in the source text vs. %s in the target text.
    • the correct number of placeholders, e.g. %d %s in the source text vs. %d in the target text.
    • the correct order of the placeholders, e.g. %d %s in the source text vs. %s %d in the target text.
  • Tip

    For example, printf placeholders may be contained in status and error messages and stand for certain contents like numbers (number of users) or names (file name) derived from the user's selection or interaction. During the operation of the program, the placeholders are dynamically replaced by the values or designations valid at the respective time. For example, the placeholder %s in the error message "The document %s cannot be opened." stands for a file name. While using the program, the placeholder is replaced by the name of the file that cannot be opened.

  • \n character in string tables (Windows resources only): Checks the consistent use of the \n character in string tables.
  • Attention

    In string tables, the \n character can be used for line breaks. If the source text is short so that the character is not required, it can be omitted without affecting the functionality of the respective software. Moreover, string tables may contain status bar text followed by the text displayed in the associated tooltip. The two texts are separated by the \n character. In this case, the character does not serve as a line break but as a delimiter between the status-bar text and the corresponding tooltip. In this case, the \n character must also be used in the translation in order to ensure the correct function of the software.

  • Text bounds: Makes sure that text within a control element (e.g. button) is not wider than the actual control element.