More Error Types for User-defined Ignores
We’ve increased the number of error types for User-defined ignores from six to 29. Now, you have more control over the precision of QA results. All you need is to describe your most frequent false positives to filter them out for good.
Still don’t use User-defined ignores? Check out our video tutorial to see how easy it is.
To see the list of all 29 error types, click here.
Display of Carriage Return and Newline
The new version supports two more nonprinting characters: carriage return and newline.
Now you can search for these characters using regular expression characters: \r for a carriage return and \n for a newline. You can go even further by creating User-defined checks to catch errors where these characters are inserted inadvertently. You may also find it useful when, for instance, you have to be sure that the number of these characters is a match, so the content on a device is displayed as intended.
With the Memsource API changed, we are keeping pace by updating our integration. Аll bases are covered.
We’ve added support for TXLF. All tests were passed with flying colors, and now it’s ready for the Wordfast users.
The target length limit check now works with the XLIFF property of max-width set for a segment. The check is renamed to Target max-width limit in characters [ ] and performs verification in two steps:
- First, it checks the max-width property of a segment.
- If it’s not set, it checks the length according to the character limit defined in the number box.
- We’ve improved the algorithm for the Inconsistent spaces around tags in source and target check. Our tests show increased precision in check results and a significant reduction in false positives.
- Spelling and grammar check is fixed for the Norwegian language. We also tackled a problem with the grammar check caused by Office 365 Business incompatibility.
- We’ve corrected the display of context and perfect matches for SDLXLIFF files. Now they are the same as in Trados Studio: CM and PM. The Match column has also been included in the Verifika Excel report.
- Changes also involved the Terminology settings: We’ve added automapping of glossaries columns for tab-delimited and XLXS files. For this to work, the first row of such glossaries should contain a language code in one of the following formats: En, en, en_gb, en-gb, en-GB, Eng, English.
- And we have made a bunch of technical improvements aimed at the operational stability of our application.
Along with the development of the desktop application, we’ve started working on the web version of Verifika QA, focusing on user experience. So far, we are in the middle of its development, having check libraries 97% ready, backend—65%, and UI—20%. Web check libraries contain many new algorithms that were rewritten to produce fewer false positives and tuned to find errors in medical, pharmaceutical, and engineering texts.
Don’t miss our next post on what features are waiting for you in Verifika Web.