Description: The problem is that, at the moment, there is only one unique file (= one TM) that feeds from Red Hat Translators and Community Translators. Yet, this unique TM is being used to fill up 100% matching pre-translate for new documents, and sometimes, on-going documents. 
While Red Hat Translations are reliable, it is difficult to know about Community Translation reliability. 
The value of a TM is directly linked to its quality. If the TM is spoilt, it delays performance, rather than enhance it, as we will have to check absolutely every pre-translated string.
I suggest creating specific TM along two criteria: 

1)Professional purpose TM (Red Hat Translators) as opposed to Community contributors TM for each language

2)JBoss TM as opposed to RHEL TM fo reach language - since the same words may mean different concepts in these two distinct environments