You are currently working on UAT 

  • State Verified Answer
  • Replies 5 replies
  • Subscribers 430 subscribers
  • Views 1216 views
  • Users 0 members are here
Options
Related

Don't add certain segments to the TM

Remy Blaettler

We have segments that need to be translated in Trados, but should not go into the TM.

Is there a feature for that? Those segments could be marked in the source XML file.

 

Alternatively, could we build a plugin that would implement this feature? If yes, could you give us a hint into which direction we have to go?

 

Cheers

 

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

    There isn't a feature for this to allow a translation to take place and then recognise automatically which ones go into the TM and which do not. There are shortcuts to confirm and not add to the TM but then these are easily forgotten when working, and you have the problem of not updating into the TM if you run a batch update task or finalize the project.

    So you probably need to work backwards and think about what prevents the TM from gettng updated. Locked segments can be excluded for example, so perhaps you can create a custom command to replace the normal Confirm shortcut all the time and it does these things:

    1. Looks for specific Document Structure in the XML file that tells Studio not to add it to the TM
    2. Locks the segment after it has been confirmed

    Or something like that maybe...

    Paul Filkin | RWS

    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

Reply
  • 0
    Hi

    There isn't a feature for this to allow a translation to take place and then recognise automatically which ones go into the TM and which do not. There are shortcuts to confirm and not add to the TM but then these are easily forgotten when working, and you have the problem of not updating into the TM if you run a batch update task or finalize the project.

    So you probably need to work backwards and think about what prevents the TM from gettng updated. Locked segments can be excluded for example, so perhaps you can create a custom command to replace the normal Confirm shortcut all the time and it does these things:

    1. Looks for specific Document Structure in the XML file that tells Studio not to add it to the TM
    2. Locks the segment after it has been confirmed

    Or something like that maybe...

    Paul Filkin | RWS

    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

Children
  • 0 in reply to Paul Filkin
    Thanks! Great idea.
    I still hope we'll find a simpler solution, but sounds like this would be doable at least.
  • 0 in reply to Remy Blaettler

    Hi Remy,

    Locking would make handling automatic propagation difficult. It would also make it difficult to go back and make changes during the translation. (For example, if you change your mind about how to translate a term and have to go back and change segments that were previously translated.)

    If you can easily tag the segments in the source file, or if those particular segments can be identified somehow in the sdlxliff file (e.g. by regex), it might be easier just to translate as usual -- using a project TM.

    When you are finished, you could filter the segments using the tags you put in the source segment or by regex, etc. (however you can identify those segments) and change their status from "Translated" to something that is not otherwise used (e.g. "Translation rejected").

    Changing their status allows you to make sure they are not included when the master TM is updated. You might even be able to use SDLToolkit to batch change the segment status (e.g. using regex) when dealing with large files or a large number of files.

    Best regards,
    Bruce Campbell
    ASAP Language Services
  • 0 in reply to Bruce Campbell
    Hey Bruce
    Interesting idea too. The problem with this approach is that we would like to use GroupShare (As soon as SDL fixes our server...) and there the segments go into the TM immediately.

    Nevertheless, you idea is that we mark those segments with a specific Context Info (for example) and then just filter them out. Correct? Or how would you "tag" them?

    Cheers

    Remy
  • 0 in reply to Remy Blaettler

    Hi Remy,

    You mentioned that the "segments could be marked in the source XML file". I am not sure what you meant, but you could mark them by placing an otherwise unused text tag like "TTTTT " at the beginning of each of those segments in the source file. That would make it easy to translate everything normally into a project TM. Then, when finished translating, regex filter on source segments with "^TTTTT ", change their status to "Translation rejected" and then update the main TM.

    If you instead want to label the segments as you are translating, you could have a small AutoHotkey macro to add "TTTTT " to the start of the target for each segment you did not want in the main TM. Then, when finished translating, regex filter on target segments with "^TTTTT ", use a global replace to eliminate the "TTTTT ", change the status of the segments to "Translation rejected" and then update the main TM.

    If you don't want to use a project TM, then you could mark your main TM so that it is not updated, and use a temporary TM to collect all the translations as you go. That would allow you to translate normally, with the segments having "TTTTT " at the beginning added to the temporary TM. Then, when finished translating, filter the segments, eliminate the leading "TTTTT ", change their status to "Translation rejected", mark the main TM so it *will* now be updated, and update the main TM. If you want to share segments with other people, using a shared temporary TM like this might be an easy way to manage that.

    This involves quite a few steps, so Paul's idea might be easier. There is, however, one part of Paul's post that I am unclear on. He mentions that locked segments can be excluded when updating the TM or finalizing a project, but I don't see that option in Studio 2017. That is why I suggest changing the status of the segments to "Translation rejected", as they are (by default) not included when the main TM is updated. Perhaps exclusion based on locking was introduced in Studio 2019.

    In addition, as I mentioned earlier, Paul's idea of locking segments during the course of translation creates problems if you use propagation or want to change previously translated segments that were locked. Using a text tag like "TTTTT " lets you translate (almost) normally, but the trade-off is that you have a more complicated series of actions to perform when finished.

    It is easier, of course, if you use a text tag in the source segment, as you don't have to worry about deleting the tag in the target segment. You can also check the main TM after-the-fact or periodically for segments containing the text tag that have accidentally been added to the main TM (i.e. someone forgets to change their status to "Translation rejected") and delete them from the main TM.

    Best regards,
    Bruce Campbell
    ASAP Language Services