Leverage MT merge for project versions


I would like to use MT as another source of translations to copy from when performing TM merge or copy trans. I should be able to tell the source of the translations when looking at its history.


  • filter of MT translation (GWT)

  • restrict to certain permission/role

  • The new modal for MT merge in version level (all languages or single language)

  • option to override fuzzy or not

  • option to save as translated or fuzzy

  • schema change to textflowtarget for MT + engine

  • fix 1 MT engine from Zanata

  • MT credential in system properties

  • MT translation should be excluded from TM suggestion

  • Any modification will clear the MT flag

  • Include attribution into the translated file and UI in Zanata

  • MT option only available to pot/po, properties and xml file format as part of legal attribution requirement from the backend engine, e.g. Google

UX: https://github.com/zanata/zanata-platform/pull/919


Michelle Kim
July 31, 2018, 4:37 AM

Thanks for promptly creating the NEW JIRA to track the issue. I will wait for the updates. Cheers, Michelle

Alex Eng
July 31, 2018, 4:31 AM
Alex Eng
July 31, 2018, 3:23 AM

Thanks for your feedback . We will look into it.

Michelle Kim
July 31, 2018, 12:30 AM

After running the test on MT merge, one issue is found with the missing tags in translation

MT have omitted all the </link> tags in translation, causing the tag error ( For example https://vendors.zanata.redhat.com/webtrans/translate?project=mt-test&iteration=1.0&localeId=ko&locale=en-AU#view:doc;doc:master;textflow:996834;error:show )

Would like to ask for configuration update in MT merge to make sure those opening and closing tags are intact in translation.
Thanks, Michelle

Ludek Janda
July 12, 2018, 7:59 AM

Good point, Yuko, I don’t think the cost estimation step in case of MT makes much sense, given the fact the cost is very minimal. We do need to analyze the total cost of MT in global, or in case of possible Post-edits from the vendor’s side, but it’s not really needed as a step in the translation workflow.

Ready for Release


Sean Flanigan


Alex Eng



Tested Version/s




Fix versions