|
|
The Validation Expert |
|
|
The Validation Expert |
The Validate Expert is used to perform a wide range of checks on localized segments. Some or all of the segments within a project can be validated. Similarly, one or many Project TTKs may be validated at a time. The results of these checks are stored in Validation results window or in an external report file.
Additionally, the Automatic Validation feature allows the selected tests in the Validation Expert to be invoked by a linguist at translation time. When the feature is enabled in the Translator Toolbar using the Automatic Validation button, all selected tests are performed on selecting a segment if the validation error icon is present. On leaving a segment automatic validation of that segment will occur if it has been edited. F5, or clicking the Perform Validation button in the Translator Toolbar, will perform these tests on demand. Automatic Validation results are displayed in the Validation Errors pane of the Translator Toolbar and the segment is marked with a validation error icon 
if errors have been identified.
There are different types of Validation Tests to choose from. Some are pre-defined such as testing for an inconsistent number of leading or trailing spaces, and some are definable. The definable tests take user input to search for invalid conditions. The input can be plain text, or regular expression which opens the door for endless possibilities and power. An example would be to verify that a question mark is translated using an inverted question mark at the beginning and a standard question mark at the end (as used in the Spanish language).
|
|
In addition to the definable Validation Tests the Alchemy CATALYST SDK may be used to develop powerful plug-in Validation Tests that enhance or replace the default tests provided. The SDK can be used to extend the functionality by writing plug-in DLLs. |
|
|
Consistent Pattern Tests |
|
|
Use this test to define text patterns that should remain the same in source and target. One example is to ensure that if a company or product name is in the source, that the same value appears in the target. Another example is to test for consistency of a phone number. If, for example, a phone number format is found in the source, it must be found in the target for a valid translation. While the number may change for a translation, the presence of the number in the translation is what is important and detecting the presence of number of the same format is one way to use this test. More...
|
|
|
Correct Translation Tests |
|
|
This test type is used when a particular source text or pattern must be translated using defined translation. An example is where the translation of the dot decimal separator in English is only valid if translated to a comma for Western European languages. The test fails if the source pattern matches, but the provided translation pattern does not exist in the translation. More...
|
|
|
Invalid Term Tests |
|
|
This test defines terms that should not exist in a translation. Using the define button, the user can specify any term that should not exist in a translation. Examples might be a product or feature name that has been changed and is therefore no longer valid, or a frequently used misspelling. The test fails if the defined term exists in the translation. More... . |
|
|
Inconsistent hotkey count |
||
|
|
Generates an error exception if:-
|
||
|
|
Invalid ampersand (&) position |
||
|
|
Only non-shift keyboard keys should be used as accelerators. This Validation Test is designed to check this. It generates an error if a hotkey cannot be selected by using the [ALT]+ key combination.
In the CATALYST public folder there is a file called Hotkeys.xml. You can exclude valid hotkeys from the validation report by adding them to this file. Please refer to this file for more information.
|
|
|
Inconsistent hotkey character |
|
|
Generates an error exception if:-
|
|
|
Inconsistent printf format specifiers (%d, %s, etc.) |
|
|
Format specifiers are programmatic placeholders. They are defined using the percent (%) symbol. In this test, an error exception is generated if the number of format specifiers differs between the original and translated strings. An error exception is also generated if the order of these format specifier’s change.
|
|
|
Inconsistent control characters ( \n, \r, \t etc.) |
|
|
This Validate Test checks for the same number of control characters in both the source and target segments. An error exception is created if a difference is detected.
|
|
|
Clipped text in dialogs |
|
|
This Validation Test verifies that translated text displays without any clipping on a dialog box.
|
|
|
Duplicate hotkeys in dialogs |
|
|
This Validation Test verifies that each hotkey in a dialog is unique.
|
|
|
Duplicate hotkeys in menus |
|
|
This Validation Test verifies that each hotkey in a menu is unique.
|
|
|
Duplicate accelerators |
|
|
This Validation Test verifies that menu accelerators are unique.
|
|
|
Validate Dialogs for Overlapping Controls |
|
|
This Validation Test verifies that no controls overlap each other in a dialog box.
|
|
|
Changed Dialog Size |
|
|
Reports on any dialog for which the overall dialog size (i.e. the background size) is different to the source. |
|
|
Inconsistent lead/trail spaces |
|
|
Generates an error exception if leading and trailing spaces differ between original and translated strings.
|
|
|
Mismatched empty string |
|
|
Generates an error exception if:-
This check is useful when validating your TTK project files for over/under translations.
|
|
|
Incorrect spelling |
|
|
Spell checks your translation. Alchemy CATALYST comes with several spelling dictionaries. You can select your spelling dictionary by going to the General Options dialog.
|
|
|
Untranslated text marked For Review or Signed Off |
|
|
This Validation Test verifies that a segment that has a translation status of For Review or Signed Off has been translated.
|
|
|
Glossary Consistency Check |
|
|
This Validation Test verifies that each segment that contains glossary terms are translated according to the Active Glossary file(s). More...
|
|
|
Maximum Size Check |
|
|
This Validation Test verifies that a segment does not exceed any of the values set in Maximum Size property.
|
|
|
Proportional size check test |
|
|
Use this test to check the expansion of translation does not exceed a certain size measured in characters or percentage of the source string. More...
|
|
|
Inconsistent translations |
|
|
Highlight all instances of the same source string translated differently.
This Inconsistency check can be performed across multiple TTK projects using the Batch of files mode in the Validation Expert General tab. More...
|
|
|
Inconsistent sources |
|
|
Highlight all instances of the same translation used for different source strings.
This Inconsistency check can be performed across multiple TTK projects using the Batch of files mode in the Validation Expert General tab. More...
|
|
|
Maximum Lines Check |
|
This Validation Test verifies that a segment does not exceed a defined number of lines. |
|
|
|
Acrolinx Validation tests |
|
|
This validation runs the tests currently configured in the Acrolinx Sidebar's Guidance profile. |
|
|
Connection to an Acrolinx server must be configured in the Acrolinx Sidebar prior to running this Validation check, see Overview: Acrolinx Sidebar.
If no user is Signed In within the Acrolinx Sidebar, running this validation test will output a warning in the Results window.
|
|
|
Well-formed Inline Tags |
|
|
This Validation Test verifies that inline tags are always well-formed and is especially useful when working with XML based files.
|
|
|
Inconsistent Inline Tags Check (excluding attributes) |
|
|
This validation test verifies that the number of inline tags in source and target segments are identical. Opt to also check attributes found within the inline tags are matching. More...
|
|
|
Inconsistent Keywords Check |
|
|
This Validation Test verifies that keywords are identical in both the source and target segments.
|
|
|
Missing space around tags |
|
|
Use this validation test to verify the presence of spaces around inline tags. This test checks by default for all self-contained tags. Define any tag which should be checked or ignored, wether the space needs to be present before, after or at either end. More... |
|
|
Shunted placeable |
|
|
Use this test to identify any segment in which inline tags have been moved to the very start of the translation. This occurs during Leverage or Power Translate where fuzzy matches or different inline tags between source and TM force Catalyst to place the inline tags to the front of the translation. |
|
|
The Validate Expert records all error messages and warnings in the Project Results Bar. An XML report can also be created in addition to this. This report is useful as a Regression Script when finalizing the testing of software applications and data content files |
