#720 Add blacklist checking feature

[Samuel Murray]

In WFC there is a blacklist feature that is basically a list of words that should NOT occur in the target text. The WFC blacklist format is a tab delimited file with two columns -- the first column contains the blacklisted word and the second column is freeflow where the translator can write a comment about it.

It would be great if OmT can also have such a feature. It would be a WFC-like text file (or a 1-column file) in the root of the project folder (or somewhere) that OmT checks when the user does tag error checking.

The blacklist is useful because it is not always possible to tie a non-preferred target text word down to a specific source text glossary item. I personally use the blacklist for projects in which the client gives regular feedback about which words he does not want me to use, or for words that he wants me to hyphenate in a different way, or for which compound forms he does not want me to use. These things are difficult to code in a glossary format because there isn't always a single or predictable source text term that will be present.

Later, when OmT gets real-time QA checking, the blacklist can be included in that (so that the translator is warned during the translastion process and not only when he does a tag validation).

[Didier Briel]

There is a partial solution for that:
- Add patterns for text that should be removed and validate
[#753]

Didier

[Aaron Madlon-Kay]

A blacklist issue checker can be implemented per [#1271].

[Jean-Christophe Helary]

I am pretty sure that what we have corresponds to your RFE: a list of "flagged" expressions that appear in the QA check. Can you confirm ?