QA functionality in QA Distiller 6.0.0

QA Distiller™ 6.0.0, build 188

Supported checks. This tool supports the widest number of possible checks which still may be extended using regular expressions. However, a serious drawback is that it does not check tags identity. The test file included a hyperlink which was intentionally changed in all translations; however, QA Distiller ignored it.
Additionally, we couldn’t find a way to check untranslatables in Distiller. There are two places where you can set a list of untranslatable items, and our idea was that the tool should make sure they are identical in source and target text. However, Distiller did not report missing untranslatable which existed in the test file.
Another weak point is number formatting check. Distiller only makes sure the number includes separators specified in parameters of the target language, but does not check the order of the separators. So, for example, it will consider 1,222.33 and 1.222,33 to be the same numbers with regard to number formatting.
Multilingual project support. In addition to reporting inconsistencies between different languages, Distiller also handles multilingual batches together with multilingual dictionaries in a strange way. For the first file it encounters, it tries to match all the glossary files in spite of the language indicated in the translated file and the glossary, which results in numerous “ignored terminology” errors. For the second target language, it tries to match it to all the glossaries until it finds the correct one. Then it perfectly matches the rest of the translated files with correct glossaries and doesn’t generate error messages.
Right-to-left language support. While this is the most comprehensive QA tool so far, it definitely lacks right-to-left languages support. Sentences in those languages are still aligned left-to-right, and if a segment ends with non-Arabic/Farsi/Hebrew words or digits, QA Distiller often handles the end of the segment incorrectly which results in a false error message. Additionally, it reports terminology errors in almost every segment because of incorrect RTL text handling. If you open the same file in MS Word and do a simple search for the glossary term you will be able to locate it easily while Distiller insists the term translation is missing.
It does not support Farsi by default, so we had to define a new language which resulted in reporting too many corrupt characters (480 occurrences).
Additional observations. Inability to change error severity may also be considered as a disadvantage (at least it makes the software less flexible and customisable).
Conclusion. At the moment, this is the most comprehensive, yet rather expensive standalone solution on the market.