The untranslated segments after “excluding first occurences” and “pre-translate files”

The untranslated segments after “excluding first occurences” and “pre-translate files”

Sometime, I still find some untranslated segments after “excluding first occurences” and “pre-translate files”.

My precedure is like this:

Phase 1, open for translation for the sdlxliff files;

Phase 2, filter with “excluding first occurences” and lock all the segments, which means all the locked segments are repetive with all the unlocked segments;

Phase 3, translate all the unlocked segments and update the project translation memory;

Phase 4, unlock all the above mentioned “locked segments:

Phase 5, use the above project translation memory to pre-translate all the “ locked segments” that have just been unlocked.

But, sometimes, I still find some segments can not be translated in the whole process. These segments might have numbers or date or some other element.

In practical translation management, translation work is divided into several stages. In phase 3, the translation team has finished translation. The file will move to phase 4 and phase 5, but the person who deals with phase 4 and phase 5 might not know the language and the person just use trados and translation memory to pre-tranlate the file; if the person find the untranslated segments, the person might need to call his international transaltion team to come back and translate again, whici is not convenient and is not efficient.

 

 

In some language, the translation can not be finished merely by replacing different number.

For example:

 source language:15.23 (use dot), target language 15,23 (use comma)

1 year, if we can the number, 2 years. (plural form)

Some time the time and date in the target language should be in speicific form, not just replacing the numbers.

Is there a solution for the problem? Or could you make  “excluding first occurences” of trados with an option that the user can also exclude first occurences based on all the content in the segment including number, capital letters and all the elements.

The aim is that the user can translate all the segments in phase 5,

emoji
  • Hello,

    Based on your description, it seems like you're encountering issues with untranslated segments even after using the "excluding first occurrences" and "pre-translate files" features in Trados Studio. This can happen due to various reasons, including differences in formatting, numbers, or dates between the source and target segments.

    Here's a step-by-step guide to help you resolve this issue:

    Step 1: Check your Missing Formatting Penalty settings. If it's set to "1", try setting it to "0". You can find this under Project Settings > Language Pairs > All Language Pairs > Translation Memory and Automated Translation > Penalties.

    Step 2: Open the translation memory you're using in your project in the Translation Memories view. Search for the source segment that's causing issues.

    Step 3: Look for any discrepancies between the source and target segments in the translation memory. This could be missing tags or different tag ID numbers.

    Step 4: Correct these segments to ensure that the source segment in the translation memory contains the exact same tags as the target segment.

    After following these steps, you should no longer encounter untranslated segments after using the "excluding first occurrences" and "pre-translate files" features.

    Regarding your suggestion to enhance the "excluding first occurrences" feature to consider all content in the segment, including numbers and capital letters, it's a great idea! Trados Studio is always looking for ways to improve and user feedback is invaluable in this process. I recommend submitting this suggestion through the appropriate channels within the application.

    I hope this helps! If you have any other questions or need further clarification, feel free to ask.

    Best regards,

    TradosAI

    emoji
  •  

    I totally understand what you are trying to do.
    All the "duplicated / replicated" segments are excluded / locked.

    Once the initial translation take place you then want to TM to translate the remaining segments.

    The problem you are finding relates to how Studio interprets dates, times, numbers (language resources) as duplicates. 

    Your example of:
    Segment 1 = 1 year
    Segment 2 = 2 years 

    Is not valid because as you pointed the plural form makes the 2 segments different not duplicates 

    2 years. (plural form)

    Your other example of is hard to comment on really.

     source language:15.23 (use dot), target language 15,23 (use comma)

    if you have:
    segment 1 = Source 15.23 | Target 15,23
    segment 2 = Source 00.00 | Target 00,00

    Applying your ideal workflow should work

    However if in your TM you have conflict of target decimal characters meaning . and , 

    TU 1 = Source 15.23 | Target 15,23
    TU 2 = Source 00.00 | Target 00.00

    Then I see it causing problems as it wont know what to apply. It will most likely give you a high fuzzy match.

    Can you elaborate a bit more on your "problem" examples. Perhaps a screen print or small sample file?
    Failing that, do confirm what sort of consistency do you have in your TM when managing numbers - keeping in mind Trados Studio is designed to keep 1 example of each format.

    Looking forward to your feedback

    Lyds

    Lydia Simplicio | 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

    emoji
  • Dear Lyds

    Please see the vedio. 

    Best regards

    Jack

    emoji