• State Suggested Answer
  • Replies 8 replies
  • Answers 4 answers
  • Subscribers 435 subscribers
  • Views 2739 views
  • Users 0 members are here
Options

DeepL plug-in not working – error message: [segment already translated...source not re-sent]

Daniela Aubeck

Dear all,

I've installed the test version of DeepL Pro for my SDL Trados 2019 instance today. The set-up worked fine, only I get the above error message for my test file (English-German). Only figures are inserted (see screenshot).

Screenshot showing Trados Studio with DeepL Translate provider setup, displaying flags for English and German languages.

Screenshot of Trados Studio error message stating 'DeepL: Error during translation: Not found'.

Does anyone know the cause of this and how the issue can be fixed?

Thank you & best,

Daniela

Generated Image Alt-Text
[edited by: Trados AI at 3:15 PM (GMT 0) on 28 Feb 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    Hello ,

    I think this has been answered before in the following thread-

    community.sdl.com/.../17375

    Did this help?

    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

  • 0 in reply to Lydia Simplicio
    Hello Steven, Thank you for your quick reply. The error message is the same in this thread, however, while I get it right from the start when trying to pre-translate a file, this issue only appears for the other person when merging segments. Best, Daniela
  • 0 in reply to Daniela Aubeck
    Hi @Daniela,

    I am not sure I quite understand.
    This I think is intentional behaviour and to prevent you being billed twice for the same translation.
    Once you confirm segment 1 to your TM - this should then auto populate for segment 2 and not be sent to DeepL.

    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

  • 0 in reply to Daniela Aubeck
    Hi

    Just to add to what Steve already said. I think the 78% is actually coming from your TM. Studio will automatically handle recognised numbers and they will get the AT status. The TM takes preference over an MT provider so as you already have this the default setting for DeepL is to not send the source again (to avoid wasteful billing as Steve mentioned).

    But if you don't ant to see this message anymore then simply check the option in your DeepL settings in the plugin (there is only one option in fact!) to "Re-send draft and translated segments".

    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

    Hello Steve & Paul, Thank you for your replies. There seems to have been a misunderstanding regarding the type of issue, based on the screenshot I used. I receive blank target segments for the entire document I pre-translate using DeepL (s. new screenshot). For confidentiality reasons, only the right column is visible here. This issue occurs both when I use our TM combined with DeepL (then with the above error message for all the segments), but also when using DeepL only (then the error message does NOT show, however). I'm on the 30-days test period of the DeepL Pro subscription, however, I don't think this could be the root cause.

    Thanks in advance for your support and kind regards, Daniela

    Screenshot of Trados Studio showing blank target segments in the right column with 'AT' icons indicating the use of AutoSuggest from Translation Memory.
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 3:15 PM (GMT 0) on 28 Feb 2024]
  • 0 in reply to Daniela Aubeck
    Hi

    This is an issue we have seen in the past but was resolved with the current version of the product. If you can provide the source file we can test it, but if not there is nothing we can do as these things are always related to one of two things:

    1. something in your source file that we need to handle in a different way, or
    2. a problem with the DeepL server which will probably resolve itself as DeepL sometimes make changes

    But it's worth making sure you have the latest version of the plugin. It should be version 4.8.5 which you can see using the plugin manager in the Studio welcome view.

    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, Thanks for this. I've tried another file now (one I translated "the traditional way" last week), and it doesn't work for that one either. The plugin is version 4.8.5. So I'd be happy to accept your offer of your team having a look at the file. Where can I send it? Thanks and best, Daniela
  • 0 in reply to Daniela Aubeck
    Hi

    You can send this to pfilkin@sdl.com

    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