Skip to main content
Inspiring
December 24, 2020
Answered

Configure Machine Translation

  • December 24, 2020
  • 7 replies
  • 1646 views

Hi

i am trying to use machine translation with Microsoft API.

i configured in Azure, got API-Key, configured it in RH. Checking brings up error with credentials.

Configured endpoint is: https://api.cognitive.microsofttranslator.com/

Perhaps that's wrong/incomplete?

 

Any ideas?

 

Thanks

 

uli

    Correct answer Vivek Kumar

    Hi Gerry,

    Update 5 is released now which has the resolution for Machine Translation APIs.

    Thanks,

    Vivek

    7 replies

    Vivek Kumar
    Adobe Employee
    Vivek KumarCorrect answer
    Adobe Employee
    June 17, 2021

    Hi Gerry,

    Update 5 is released now which has the resolution for Machine Translation APIs.

    Thanks,

    Vivek

    Participating Frequently
    October 10, 2025

    Please explain how this feature works. I have successfully connected DeepL but the translation quality is not good enough for the client. I want to connect to Microsoft but I get the same error at the validation stage as previous users have reported.

    Peter Grainge
    Community Expert
    Community Expert
    October 10, 2025

    @Andy Snape Assuming you have all updates applied and have tried what is suggested here by Adobe, I think you will need to go to Adobe Support. See https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp for your Adobe Support options. The email link tcssup@adobe.com is recommended as it reaches a team dedicated to Technical Communication Suite products including RoboHelp.

     

    The regular supporters of the forum such as myself are not users of the translation feature so we have no more knowledge than what you see above. Maybe Support have more up to date information than is posted here.

     

    If you do find a solution, please come back and post it here as that is what makes the forum work.

    ________________________________________________________

    My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

     

     

    Use menu (bottom right) to mark as Best Answer or to Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    Jeff_Coatsworth
    Community Expert
    Community Expert
    May 20, 2021

    @defaultp0x73367v09i - according to this thread - https://community.adobe.com/t5/robohelp/google-translations-invalid-credentials/m-p/12051317#M138365 - Google changed something that has thrown off RH2020 patch 4 - there's a worksround described until a fix gets into a newer patch.

    Jeff_Coatsworth
    Community Expert
    Community Expert
    May 20, 2021

    @defaultp0x73367v09i (Gerry) - running as a trial makes no difference - it's the full product, just with an expiry. Did you try adding the region info to that Header section in the Profile that got added in patch 4?

    Vivek Kumar
    Adobe Employee
    Adobe Employee
    January 23, 2021

    We are providing a way to configure additional header in the Translation Profile itself. It will be available in  update 4. After that manual workaround is not needed.

     

    Thanks,

    Vivek

    Participant
    May 19, 2021

    I am using 4 on evaluation /free trial and its not working - tried both Microsoft and Google translation APIse and RH wont work with either which means I can't evaluate - Madcap Flare trial version work with both. Shame. 

    Community Manager
    May 19, 2021

    Any specific thing that is not working for you? Do you get any error messages?

    ulibbAuthor
    Inspiring
    January 1, 2021

    Hi 

    i found the reason and have a solution:

     

    If you create the Microsoft Machine Translation service, you can choose the region. Of course, i choosed westeurope.

    i did a little research with postman, and it turned out, that it is NOT sufficient, to have the apikey in the header. It is mandatory, to send the region, too.

    So, the problem is, that i do not know, how to tell Rh, to transmit the api-region in the request header.

     

    I found this workaround: When the Translation Service is created with region "global", it is sufficient to send only the apikey - and then it works in Rh.

    Somebody knows, if it is possible, to configure additional headers to be sent in the request?

     

    uli

    Adobe Employee
    January 5, 2021

    Hi,

    To configure your header for any translation service provider, go to your RoboHelp installation directory, If you're a Windows user, go to this path from there: "resources/data/template/translation/bing/profile_builder.js" (for Microsoft Translation service).

    If you're a Mac user: go to Applications tab in finder, locate Robohelp, right click "Adobe RoboHelp 2020.app" and click on "Show Package Contents". Go to "Contents/Resources/resources/data/template/translation/bing/profile_builder.js"

    You can add additional header data to this file by editing the "headers" where the "API_KEY" is written. In your case, to add region, the headers sections will look like this in your JS file after making the necessary edits:

     

     

     

    headers: {
                  'Ocp-Apim-Subscription-Key': API_KEY,
                  'Content-type': 'application/json',
                  'X-ClientTraceId': uuidv4().toString(),
                  'Ocp-Apim-Subscription-Region':'westeurope'
    },

     

     

     

    Make sure you enter the correct value for your region name that is provided by Microsoft. Restart your Robohelp, open a translation language in your project, and add a profile for bing translation, it will work as expected for all the profiles you will add or have added for bing.

    We shall be fixing this issue in our next update. You can find the documentation for making edits to the existing translation service providers and support custom translation services here

    Thanks,
    Sudhanshu.

    Peter Grainge
    Community Expert
    Community Expert
    December 25, 2020

    That looks like a bug. Please report it using the link below so that it can fixed in an update.

     

    https://tracker.adobe.com

    Post the link to your bug report in this thread and others can vote for it. The more people who do so, the higher it gets prioritised.

    ________________________________________________________
    See www.grainge.org for free Authoring and RoboHelp Information

    Use menu (bottom right) to mark as Best Answer or to Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    Peter Grainge
    Community Expert
    Community Expert
    December 25, 2020

    Your link goes to the Documentation page, I suspect the real target is only visible to you if logged in.

     

    Typically it should simply mean your credentials are not what Microsoft is expecting, obviously.

     

    Check you have the latest updates first. You cannot update from the initial release (2020.0) using Help > Check for Updates. Go to https://www.adobe.com/support/robohelp/downloads.html and download the latest update. You only need to apply the latest as it includes the incremental changes. Once you have applied a later update, Help > Check for Updates will work in the future.

     

    Beyond that I think you will need to take this one to Support after the Christmas period. See https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp for your support contact options.

    ________________________________________________________
    See www.grainge.org for free Authoring and RoboHelp Information

    Use menu (bottom right) to mark as Best Answer or to Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    ulibbAuthor
    Inspiring
    December 25, 2020

    Hi

     

    thanks.

    the URL i provided is the one, Microsoft provided in the Azure portal for this service.

    I wrote a little app and tried - works (URL, API-Key).

    Same data cause error in the RoboHelp-check

     

    Hmmm

     

    uli