Consistency Report


Overview

Consistency report is designed to simplify the process of resolving errors. A sample consistency report is shown on the screenshot below. Please see the elements description under the screenshot.
consistency_report

 

  1. Buttons to control the display of non-printable characters and tags in the text, to export the report, to save the project (this button is grayed out if there are no unsaved changes) and to turn comments on/off.
  2. Help button.
  3. The list of detected consistency errors, structured as follows:
    • Type of inconsistency (source or target inconsistency).
    • Error – group of inconsistently translated segments with the same source and different translations (or vice versa).
    • Segments that compose this group.
  4.  Segment editor.
  5. Comment field.

NB! Despite the inconsistency check settings, variant groups are case- and tag-sensitive. This is to make sure you change only identical segments and do not occasionally introduce new errors (such as deleted tags or incorrect case).

Resolving Errors

Working with the consistency report is similar to working with the general report.

  1. Select an error in the consistency error list (see the screenshot above, area 3).
    Review inconsistent translation variants below.
  2. To view the segment in context, double-click the error to open the whole file in the Context Viewer.
  3. If one of the inconsistent translations is correct in the Target inconsistency group, click Apply in this segment line. As a result, all equivalent source segments in all bilingual files will be translated using the selected variant. If you apply a translation that contains different tags or numbers than were in this segment before, the smart replacement feature will locate tags and numbers from the source segment instead of copying them from the applied translation.
  4. If the correct variant is missing from list (or you deal with the Source inconsistency group), type it in the Target segment field in the segment editor (4). If needed, apply the correction to all equivalent source segments (see point 3 above).
  5. If an error does not require correction, right-click it in the list (area 3) to assign it No error status. To assign No error status to all errors in the group, press Ctrl+Shift+Space when any error in this group is active.
    The statuses are saved between editing sessions (i.e. even if you close Verifika and then open it with this project again).
    Errors with No error status will not export to Excel if you don’t select respective checkbox while saving the file.
  6. If you want to add a comment to a segment and the Comment field is not visible, click Comments and insert your comments in the lower field that appears. All comments are saved automatically and exported to Excel reports. In order to delete a comment you will need to manually delete the text from the field.
  7. Repeat the steps above to resolve all the errors in the list. When you resolve an error or assign it No error status the report automatically switches to the next pending error in the list. Once you review the last error in the group, the next group will be expanded. You can also expand all errors by pressing Ctrl+Shift+E (Ctrl+Shift+W to collapse them).

NB! If you change a segment where an inconsistency error was ignored, No error status won’t be automatically deleted in most cases. However, to avoid problems, it is recommended to first resolve all errors from the Common report and then switch to the Consistency report.