Telephone: +34 93 244 08 80+34 93 244 08 80
Transit NXT - What’s new in SP16. Part 2: Quality Assurance

Transit NXT - What’s new in SP16. Part 2: Quality Assurance
Discover the latest innovations in Transit NXT Service Pack 16 with our series of 13 engaging videos, each under a minute long! In this second post, we highlight the exciting new QA features. Don’t miss out on what’s new—watch now!
QA: “Log as revision” default setting
Transit can log segment revisions to make content changes both transparent and traceable. To do this, the corresponding option must be selected in proofreading mode and when unpacking translations.
With this latest Service Pack, you can preset the options in projects and project templates for:
- Automatically logging revisions in proofreading mode
- Automatically logging revisions when unpacking translations
This prevents the options from being accidentally overlooked and the segment history from being lost.
This is just a default setting: You can still decide whether Transit should log revisions when proofreading and unpacking.
QA: ignore locked segments during checks
Segments that should not be edited can be locked. For these segments, any changes (including corrections) are neither desired nor permitted.
As of this Service Pack, you can exclude locked segments from the following checks:
- Spellcheck
- Terminology check
- Format check
This allows you to concentrate on the segments that you are permitted to edit and to correct in the event of errors.
QA: special MT and fuzzy colours for export
When exporting projects, you can display the segment statuses with different text colours to make it easier to check specific target language documents.
As of this Service Pack, you can also use special colours to indicate machine translations and fuzzy matches that were automatically inserted during import.
QA: evaluation of the editing distance
You can export segment history, i.e. the different revision steps of a segment, to quality reports.
You are now also able to analyse the “editing distance”. This measures the difference between two revision steps.
Transit supports three metrics for this:
- Similarity (fuzzy algorithm): percentage similarity, calculated in the same way as for fuzzy matches (values between 0% and 100%, high value = high similarity = fewer changes)
- Levenshtein distance: number of operations required for the change (values greater than 0, higher value = more changes = more differences)
- Levenshtein similarity: similarity relative to the total number of characters, calculated on the basis of the Levenshtein distance and the segment length (decimal values between 0 and 1, high value = high similarity = fewer changes)
Categories:
Leave a comment