• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 432 subscribers
  • Views 2325 views
  • Users 0 members are here
Options
Related

How does Studio select from multiple matches using the Pre-translate batch task?

Andrew Reid

Hi,

Sometimes I have multiple translation units with identical source text but differing target text. When applying the Pre-translate batch task, which parameters does Studio use in this instance to select which translation unit (e.g. date created, date modified etc.)?

Also, when applying the Pre-translate batch task to a new file added to an existing project containing a main TM and subordinated project TM, does Studio give preference to one TM or the other (assuming, as above, that there are multiple units with identical source text)? If so, can this be changed by disabling either TM?

Many thanks for your input!

Andy
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hello Andrew,

    Unknown said:
    Sometimes I have multiple translation units with identical source text but differing target text. When applying the Pre-translate batch task, which parameters does Studio use in this instance to select which translation unit (e.g. date created, date modified etc.)?

    I think Studio will first of all check for context (preceding source and target) and also document structure information, to see whether it can disambiguate the matches.  If it can't then you will probably get a duplicate match penalty applied (by default) and the most recent TU will be used.

    Unknown said:
    Also, when applying the Pre-translate batch task to a new file added to an existing project containing a main TM and subordinated project TM, does Studio give preference to one TM or the other (assuming, as above, that there are multiple units with identical source text)? If so, can this be changed by disabling either TM?

    Studio will use them both.  They will in fact be exactly the same apart from the following:

    - Project TM could contain new TUs from this project only, unless you updated your Main TM

    - Main TM might contain TUs relevant to this new file that are not common with the new TUs in the files you have already translated for the Project.

    Does this help?

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    Hi Paul,

    Many thanks for your response!

    Regarding the first point: it hadn’t occurred to me that Studio would also check for context and document structure, but yes, this would make sense before choosing the most recent TU.

    I’m still a little unclear on the second point, however… If the main TM isn’t updated, and assuming that the above-mentioned context and document structure checks haven’t been met in either the project or main TM, Studio would then presumably first use the TUs from the project TM and then from the main TM, as these would be the most recent. And even if the main TM contained TUs relevant to the new file, if they weren’t common with the new TUs in the previously translated files for the project, Studio would still select the more recent files from the project TM. Have I understood this correctly?

    And can I assume that if I wanted to avoid any TUs being taken from the project TM, I could disable this in the Pre-translate step and Studio would only use the main TM?

    Kind regards

    Andrew
Reply
  • 0 in reply to Paul
    Hi Paul,

    Many thanks for your response!

    Regarding the first point: it hadn’t occurred to me that Studio would also check for context and document structure, but yes, this would make sense before choosing the most recent TU.

    I’m still a little unclear on the second point, however… If the main TM isn’t updated, and assuming that the above-mentioned context and document structure checks haven’t been met in either the project or main TM, Studio would then presumably first use the TUs from the project TM and then from the main TM, as these would be the most recent. And even if the main TM contained TUs relevant to the new file, if they weren’t common with the new TUs in the previously translated files for the project, Studio would still select the more recent files from the project TM. Have I understood this correctly?

    And can I assume that if I wanted to avoid any TUs being taken from the project TM, I could disable this in the Pre-translate step and Studio would only use the main TM?

    Kind regards

    Andrew
Children
No Data