Lilt’s QA checker helps translators and reviewers with proofreading by displaying any potential linguistic issues that may have been missed during translation. This article discusses full QA checks, Batch QA checks, and how project managers can require linguists to run Batch QA check on documents to help catch issues earlier.
About the QA check tool
The QA check tool integrates LanguageTool, an open-source proof-reading tool for many languages that incorporates community-based rules for spelling, grammar, and style. You can browse the language rules on their website, such as the English rules.
Here are some examples of what the QA check tool looks for:
- doubled words
- doubled punctuation
- doubled whitespace
- leading and trailing whitespace
- missing and inserted numbers
Full QA check
To run a QA check on all segments in a document, open the Editor's
File tab and click the
Run Full QA Check option.
To run a QA check on a single segment, click on the QA button on the right of the segment.
After running a QA check, if any potential linguistic issues are found, they will be highlighted in the Editor:
- Red highlight: spelling mistake
- Yellow highlight: grammar or punctuation mistake
Note that the QA check also searches for and displays Tag Errors.
QA actions popup
Click on a highlighted term to bring up a QA actions menu that displays the linguistic issues and suggestions for correction. After you have corrected any mistakes, it is good practice to run the QA check again on the segment to make sure there are no more issues.
The QA actions menu:
- The red text at the top describes the issue.
- The next few options are suggestions for correcting the issue. Click on any of these suggestions to replace the highlighted text with the suggestion.
- Ignore Once: Click to ignore the error once during the user session.
- Ignore All: Click to ignore the error every time it's encountered during the user session.
- Add to QA Rules: Project managers have the ability to add QA rules for terms so the QA check recognizes those terms as correct in the future. Terms added this way show in the Manage QA section of the associated Memory and can be removed or modified if needed.
To run a Batch QA check, open the Editor's
File tab and click the
Run Linguistic Batch QA Check option.
Batch QA runs a full linguistic QA on all segments in a document, regardless of segment state. In addition, Batch QA displays all linguistic errors for all segments (unconfirmed, confirmed, accepted) in a consolidated view, grouped by error type. This allows linguists to compare language usage across all the different segments in a document. Batch QA utilizes the LanguageTool and QA service rules to determine errors.
After running the Batch QA, potential errors are displayed in the Batch QA popup. Each error section is displayed in orange text that describes the error type.
Accept All will accept all segments within the error section, applying all suggested changes to those segments.
Accept on an individual segment will apply the suggested fixes to that segment. You can also click on the suggested text area to edit the text manually before accepting the changes.
If you have accepted a section or segment but still need to make changes, click the
Undo button to revert the changes and allow the segments to be edited again.
Ignore on a QA suggestion will ignore the issue for the current Batch QA session.
Once you have made the changes you want to make, click the
Continue button at the bottom to finish the Batch QA session and return to the editor.
Note: If the document was Pretranslated and the option to
Accept And Lock Exact Matches was selected, any Pretranslated segments will be excluded from Batch QA reviews. If the option to
Accept And Lock Exact Matches was not selected, all segments will be included in the Batch QA review, including 100% TM matches.
Mandatory Batch QA
If you are a project manager, you can turn on Mandatory Batch QA Checks for translators or reviewers in the Organization settings. Enabling this will force reviewers to run a Batch QA check before being able to mark a document as done. This helps to catch errors earlier, saving on overall review time.