• State Verified Answer
  • +2 person also asked this people also asked this
  • Replies 31 replies
  • Answers 2 answers
  • Subscribers 3 subscribers
  • Views 12100 views
  • Users 0 members are here
Options

SDLMTCloud Pre-translation

Chris Pulsifer

We have a working application that automates the creation of projects via Trados Studio Automation using FileBasedProject and its related API objects.  This processing include pre-translation and publishing to the GroupShare server.  The current implementation runs on Studio 2019 and uses the BeGLobal engine.  We are upgrading to Studio 2021 and using the SDLMTCloud engine.

We get fully pre-translated projects with BeGLobal and 2019, however now when we run on 2021 using SDL MT Cloud, we successfully generate the project, but no pre-translation occurs.  When opening the project manually and pushing the SDL MT translation everything works well.

In digging through source code in Sdl-Community/SDLMTCloud.Provider at master · RWS/Sdl-Community · GitHub, I see a function IsStudioRunning() being used as a gatekeeper in some of the code.  I don't believe that Studio would be considered to be running in our use case, so trying to find out if this is why we don't get pre-translation.  Does anyone know if that is the logic applied to the processing fro SDLMT CLoud?
emoji
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Hi  ,

    I have added an item on our board to followup on Monday, to confirm if there are any new issues that we are not aware of; internal ref. SDLCOM-3817

    Until then, can you please provide me with some additional info, as follows:

    • Release version of Trados Studio 2021
    • Release version of the SDL MT Cloud plugin
      • Is the plugin signed?
    • Error log or exceptions
    • If possible, also provide me with the source code of the project automation (phartnett@rws.com)
      • I'm mostly interested in the plugin configuration file

    Patrick Andrew Hartnett | RWS Group

    emoji
  • 0 in reply to Patrick Andrew Hartnett
    • Trados Studio: 16.2.9.9198
    • SDL MT Cloud Plugin: 3.1.3.0
      • not sure if it's signed, how do I check?
    • No exceptions logged, everything just seems to work from the code perspective
    • Not allowed to post the source code to a community forum, but it's the same source code I shared a month or two ago when working with you on our prior problem.  No longer calling AddBeGlobal() method in that source, just a new function to push the SDL MT credentials into the project
      • Where would I find the plugin configuration file?
    emoji
  • 0 in reply to Paul

    When I build and run the code that Patrick pointes to get the following:

    Program running emits these status messages:
    Scan: Completed
    ConvertToTranslatableFormatTask: Completed
    CopyToTargetLanguagesTask: Completed
    RunAnalyzeTaskFiles: Failed
    RunPreTranslateFiles: Failed

    When I open the project in Studio, I get a popup message::

    "The language translation provider "Language Weaver provider" could not be opened and has been disabled."

    Tried installing the copy I downloaded today and now I get "Service:"SDL. 'Desktop.Platform.CommandBars.IActionService' could not be started" and Studio shuts down.
    emoji
  • 0 in reply to Chris Pulsifer

    Hi  , sorry to hear you're haveing issues with this setup. 

    This sounds like the version of the plugin installed is not compatible with the version of Trados Studio. can you check and tell me what is the exact version of Trados Studio you have installed / testing against.

    Patrick Andrew Hartnett | RWS Group

    emoji
  • 0 in reply to Chris Pulsifer

     

    On this bit...

    Chris Pulsifer said:
    Tried installing the copy I downloaded today and now I get "Service:"SDL. 'Desktop.Platform.CommandBars.IActionService' could not be started" and Studio shuts down.

    This is a Studio problem, often resolved by using reset window layout.If it doesn't help then reset Studio.  To do this just close Trados Studio and then rename this folder:

    c:\Users\%username%\AppData\Roaming\SDL\SDL Trados Studio\Studio16\

    to c:\Users\%username%\AppData\Roaming\SDL\SDL Trados Studio\Studio16_old\

    Finally restart Trados Studio and try again.

    It might also be worth deleting the plugin from the plugin folders (packed and unpacked) first, then reinstalling after the reset.  Sometimes, depending on how you installed, the unpacked from a previous version can remain in place.  So a proper clean out would be advisable.

    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
  • 0 in reply to Patrick Andrew Hartnett

     

    Trados Studio 16.2.9.9198
    Language Weaver MTCloud 4.2.18.3
    emoji
  • 0 in reply to Chris Pulsifer

    Hi , oki; these should be compatible, however, I'd recommend upgrading to the latest CU 12 for 2021 (i.e. 16.2.12.9338)

    in this case, as suggested, I'd check and clear out any existing versions of the plugin from the roaming directories.  Might be a conflict trying to load two different versions of the same plugin guid into the Studio context

    Patrick Andrew Hartnett | RWS Group

    emoji
  • 0 in reply to Patrick Andrew Hartnett

    Got it built and producing a project with successful pre-translation.  When I open the published project, I get a message that the Language Weaver provider can't be started and will be disabled.  When I view the translation, the segments all show NMT though, so it appears to have worked.  Will try to compare sample code to our application.
    emoji
  • 0 in reply to Chris Pulsifer

    Hi , that's awesome news, thanks for confirming this.  The only thing that comes to mind for the remaining problem is to check that you are using the same version of the Language Weaver plugin (+ studio) on the machine where you are opening the project created from automation.

    Great news that it's working in automation though; well done (y)

    Patrick Andrew Hartnett | RWS Group

    emoji
  • 0 in reply to Patrick Andrew Hartnett

    Unfortunately(?), I am opening the project on the same machine that I am running the code on, so I know the versions are the same.  Checking for other possible issues
    emoji
  • 0 in reply to Chris Pulsifer

      

    Trying to make the sample code work with our processing model.  We use language/project specific templates as part of our workflow.  Our process is to pre-translate as much as possible from our TMs and then use NMT to translate remaining un-processed content.  I have added the following ot the sample code:

    Fullscreen
    1
    2
    ProjectTemplateReference template = new ProjectTemplateReference(@"C:path\to\template");
    var project = new FileBasedProject(projectInfo, template);
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


    When I try to run the sample code with this in place, I get the following error for the Analyze task and similar for the Pre-Translate tasks:

    "Unexpected exception when initializing task 'Analyze Files': Failed to create an instance of translation provider 'sdltm.njp1grpshgd01.corp.bloomberg.com/ - German'.."

    Here is the language direction section of the template:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    <LanguageDirections>
    <LanguageDirection Guid="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" SettingsBundleGuid="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" TargetLanguageCode="de-DE" SourceLanguageCode="en-US">
    <AutoSuggestDictionaries />
    <CascadeItem OverrideParent="true" StopSearchingWhenResultsFound="false">
    <CascadeEntryItem PerformConcordanceSearch="true" Penalty="0" PerformUpdate="true" PerformNormalSearch="true">
    <MainTranslationProviderItem Uri="sdltm.">njp1grpshgd01.corp.bloomberg.com/ Enabled="true" />
    </CascadeEntryItem>
    <CascadeEntryItem PerformConcordanceSearch="true" Penalty="0" PerformUpdate="false" PerformNormalSearch="true">
    <MainTranslationProviderItem Uri="sdltm.">njp1grpshgd01.corp.bloomberg.com/ Enabled="true" />
    </CascadeEntryItem>
    <CascadeEntryItem PerformConcordanceSearch="false" Penalty="0" PerformUpdate="false" PerformNormalSearch="true">
    <MainTranslationProviderItem Uri="sdlmtcloud:///" State="{"AutoSendFeedback":true,"LanguagesSupported":[{"Name":"English (United States) - German (Germany)","SourceTradosCode":"en-US","TargetTradosCode":"de-DE","SelectedSource":{"CodeName":"eng","IsLocale":false},"SelectedTarget":{"CodeName":"ger","IsLocale":false},"SelectedModel":{"DisplayName":"eng-ger Bloomberg","Model":"bloomberg","MTCloudLanguagePair":{"sourceLanguageId":"eng","targetLanguageId":"ger","model":"bloomberg","displayName":"Bloomberg","name":"engger_bloomberg","active":"yes"},"Source":"en-US","Target":"de-DE"},"SelectedDictionary":{"name":"No dictionary available","description":null,"source":null,"target":null,"dictionaryId":""},"SourceLanguages":[{"CodeName":"eng","IsLocale":false}],"TargetLanguages":[{"CodeName":"ger","IsLocale":false}]}],"ResendDraft":true,"SendFeedback":true}" Enabled="true" />
    </CascadeEntryItem>
    </CascadeItem>
    </LanguageDirection>
    </LanguageDirections>
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    The machine url for the sdltm entry is valid and reachable form the machine running the program.
    emoji
  • 0 in reply to Chris Pulsifer

    Hi  ,  I'm not sure if there is a rendering issue with presenting the content in your example above, but those uri strings seems to be broken (e.g. <MainTranslationProviderItem Uri="sdltm.">njp1grpshgd01.corp.bloomberg.com/ Enabled="true" />)

    Can you provide me with the template you are using?  to phartnett@sdl.com

    Patrick Andrew Hartnett | RWS Group

    emoji
Reply Children