QM Criteria for .NET Resources (QM v6.3)
.NET Resources 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.
Example
In this example, the file extension *.acp was mistakenly used in the translation instead of *.cap. Therefore, the QM criterion indicates an error:
.NET resources hotkey check
Makes sure that hotkeys (e.g. Alt&F for opening the File menu) are duly used in dialogs and menus and that they are not used in more than one way.
Example 1
In this example, the hotkey &C, which appears in the source text, is missing in the target text. Therefore, the QM criterion indicates an error:
Example 2
In this example, the hotkey &E appears twice in the target text. Therefore, the QM criterion indicates an error:
.NET resources placeholders
Checks the correctness of printf placeholders like {0}, {1}, {2}, etc. In this context, the QM criterion checks
- the correctness of the actual placeholders, e.g. {1} in the source text vs. {2} in the target text
- ·the correct number of placeholders, e.g. {1} {2} in the source text vs. {1} in the target text
- ·the correct order of the placeholders, e.g. {1} {2} in the source text vs. {2} {1} in the target text
For example, printf placeholders may be contained in status and error messages and stand for certain contents like numbers (e.g. number of users) or names (e.g. name of a particular file) 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 {0} in the error message "The document {0} 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.
Example
In this example, the placeholder {1} has been inserted in the translation mistakenly instead of the placeholder {0}. Therefore, the QM criterion indicates an error:
.NET resources overlapping controls
On the one hand, checks whether there are any controls (e.g. buttons) that overlap with each other, and, on the other hand, if the controls overlap 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.
This criterion can not be checked in .NET resources that do not contain information on the size and position of the control elements but whose size and position are defined via layout definitions (e.g. by means of AutoSize or AutoPosition commands).
Example
In this example, the button Durchsuchen overlaps the frame of the dialog area. Therefore, the QM criterion indicates an error: