Bug 851886

Summary: RFE: Create separate TM
Product: [Retired] Zanata Reporter: croe <croe>
Component: PerformanceAssignee: Luke Brooker <lbrooker>
Status: CLOSED NOTABUG QA Contact: Zanata-QA Mailling List <zanata-qa>
Severity: low Docs Contact:
Priority: medium    
Version: developmentCC: camunoz, croe, mkim, pahuang, zanata-bugs
Target Milestone: ---Keywords: screened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-06 22:19:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description croe@redhat.com 2012-08-26 22:52:08 UTC 
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
Comment 1 Patrick Huang 2012-11-20 05:33:37 UTC 
More info on the requirement from Runa.
Comment 2 Michelle Kim 2015-02-25 05:29:25 UTC 
Our UX desginer, Luke will talk to Corina to get more input on the scope of this feature.