• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 434 subscribers
  • Views 450 views
  • Users 0 members are here
Options
Related

Trados Studio 2024: Majority of segments marked "Not Translated" after Pre-Translation in some files, despite similar files pre-translated correctly with identical Project Settings

Rolf Kleerebezem

Hello,

I'm frequently encountering an issue where a large portion of my pre-translated documents show segment status as "Not translated", despite sharing the same project settings as similar files that pre-translate correctly. Both files show high translation progress in the project folder, and there seems to be no directe correlation with their size or word number. Based on my testing, the problem does not seem related to project settings.

I came across a forum post suggesting this could be caused by a timeout, but the information was limited. Manually clicking each segment does update the status (to NMT or fuzzy matches), but this process is very time-consuming.

Context:

  • I primarily work with .idml InDesign files, translating from French to English.

  • I use a translation memory and the OpenAI provider.

  • I experienced similar behavior in Trados Studio 2021 with DeepL, not only with .idml files but also with large Excel files.

  • Occasionally, I receive an error at the end of the pre-translation process, but it's not consistent.

Questions:

  1. How can I resolve or prevent this issue in the future?

  2. Is there a way to batch-update "Not translated" segments to get translation results, instead of manually selecting each one?

Please see the attached screenshots for reference to a project with two similar files, one filly pre-translated, the other with only empty segments. Thank you for your assistance.

Best regards,
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0

    Probability score: 0.7  

    Question improvement suggestion: Provide specific error messages encountered during the pre-translation process and clarify the exact steps taken before the issue occurred.  

    In the meantime, based on the information you have provided, here is a suggested answer to your question:  

    Hello,  

    It sounds like you're experiencing a frustrating issue with the pre-translation process in Trados Studio 2024. Here are some steps you can take to resolve or prevent this issue in the future:

    **Step 1:** Check your Translation Memory (TM) settings. Ensure that the TM is up-to-date and contains the necessary translations. If the TM was created or updated after the project was initiated, run a Batch Task -> Pre-translate to refresh the TM with the latest translations.

    **Step 2:** Review the Minimum match value settings. In your Project Settings, under Language Pairs > All Language Pairs > Translation Memories and Automated Translation > Search, ensure that the Minimum match value is set appropriately. If it's set to 100, segments without a 100% match will not be pre-populated. Consider lowering this value to allow for fuzzy matches.

    **Step 3:** If you encounter segments marked as "Not Translated," you can batch-update these segments. In the Editor view, select the blank segments, right-click, choose 'Change Segment Status,' and select 'Translated' or 'NMT' as appropriate. This will save you time compared to updating each segment individually.

    **Step 4:** If you receive an error at the end of the pre-translation process, note the error message and check if it is consistent. This could provide insight into the underlying issue.

    **Step 5:** As a workaround, if the Language Weaver is not applying NMT to empty segments, create your project using only the Group Share TMs first, then run the batch task 'Pre-translate' again with the Language Weaver Cloud provider.

    **Step 6:** Lastly, ensure that your Trados Studio software is up-to-date, as updates often include bug fixes that could resolve your issue.

    I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

    RWS Community AI
    emoji
  • 0 in reply to RWS Community AI

    This does not explain the difference between two similar files with opposite pre-translation results, when they share similar project settings as far as I can see. 
    As for step 3, selecting multiple segments and using "Change Segment Status" does not seem to look for translation results. The segment stays blank, empty. 
    emoji
  • 0 in reply to Rolf Kleerebezem

     

    Does this occur without using OpenAI or any MT provider?  So if you only work with your local SDLTM's?

    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

    emoji