That's a good question... it seems sort of logical that this would work after the copy to target languages.  I added an investigation item to our backlog, SDLCOM-967, so that the team can look at why this is.  The latest version of the plugin and the code is owned by the SDL Community development team these days so it seems to make sense we take a look at this.

Having said that any feedback from Jesse Good is always welcome.

Hello ,

I've investigated the situation you described above and you should run the "Cleanup Source" task after the "Pre-translate Files" batch task: in the "Cleanup Source" task, the operations are made on the segments which are accessible only after the "Pre-translate Files" is executed, this is the reason why you cannot see any changes if you run the batch task in the sequence you want.

Currently, we cannot implement a workaround, because we don't have the needed logic exposed in the public APIs, so you should set the "Cleanup Source" task to run as I've described below, from one of the cases:

      1. During the project creation, defined as last task in the custom batch task sequence , like in the below print screen:

       2. During the project creation, defined in the custom batch task after the "Pre-tranlsated Files" task, like in the following sequence:

• Convert to Translatable Format
• Copy to Target Languages
• Apply PerfectMatch
• Pre-translate Files
• Cleanup Source
• Populate Project Translation Memories
• Analyze Files

       3. Independently, after the project was created

The most important is that the "Cleanup Source" task needs to be executed after the "Pre-traslate Files" task.

With kind regards,

Florentina Caputa

Florentina Caputa said:

The most important is that the "Cleanup Source" task needs to be executed after the "Pre-traslate Files" task.

So in essence you need to run two batch tasks   You almost need the ability to string batch tasks together... sounds like an opportunity for another plugin!

Florentina Caputa said:

you should run the "Cleanup Source" task after the "Pre-translate Files" batch task: in the "Cleanup Source" task, the operations are made on the segments which are accessible only after the "Pre-translate Files" is executed

Hmmm, that's weird... because the reason (or one of the reasons) for running the Cleanup Tasks is to get rid of some unwanted content in source, so that I actually get some matches from TM...
So pretranslating that garbage doesn't make sense... plus, it can be very time consuming too - I've seen pretranslations running for hours due to a slow connection to GroupShare TMs.

It would make sense to run this "preliminary" pretranslation against empty TM... perhaps even created behind the scenes just for this purpose.

All in all, it sounds like a good amount of extra and unwanted work :-\

Hi Florentina Caputa

I agree with Evzen Polenka - that sequence does not make a lot of sense. We need to clean up and THEN pre-translate, because our TMs will be from cleaned up files!

So at the moment the only solution seems to be run CleanUp Tasks after pre-translate and then manually pre-translate another time.

Daniel