Hi Paul,

Thanks for your reply. I can send you the file and TM/TB via email.

As for my expectation - and please correct me if my interpretation of what batch task support for Fuzzy Repair is wrong - when creating a project, the pre-translation phase of the batch task should result in auto-propagating Repaired Matches in applicable target segments. However, when the editor loads there are no match repaired segments just repair results in Translation Results. I've attached a screenshot showing that the document and TM does render Fuzz Repair result (it was by design to expressly demo Fuzz Repair,so there should be no issues)

Thanks in advance,

Demian

Hi Paul,

Thanks for your reply. I can send you the file and TM/TB via email.

As for my expectation - and please correct me if my interpretation of what batch task support for Fuzzy Repair is wrong - when creating a project, the pre-translation phase of the batch task should result in auto-propagating Repaired Matches in applicable target segments. However, when the editor loads there are no match repaired segments just repair results in Translation Results. I've attached a screenshot showing that the document and TM does render Fuzz Repair result (it was by design to expressly demo Fuzz Repair,so there should be no issues)

Thanks in advance,

Demian

Hi Demian Ichinose 

Thank you for the files.  I created a project with them and I see this:

Fully populated and with repaired matches.  I think your problem is that you are using the defaults for pretranslation which are 100%.  The match values in your test files are all less.  I set mine at 60% as I didn't know what to expect, but looks like you could use 95% and get them all.

Regards

Paul