Skip to content

GlobalSight Machine Translation with Bing Translator

GlobalSight have had machine translation support for Microsoft Translator for some time now. However, Microsoft updated their usage terms and the API earlier this year and previous configurations in GlobalSight is no longer valid.  Thanks to the fast response from the development team, GlobalSight 8.2.2 supports the new Microsoft Translator API. Configuration requires a little more effort than before but following the simple steps below, you can be up and running in a few minutes.

Microsoft Translator and the related API is free up to 2 million characters a month.

Microsoft Translator configuration for GlobalSight

1. First step is to register with Windows Azure Marketplace and get your credentials. Go to http://go.microsoft.com/?linkid=9782667 and click the “Sign Up” option under the free tier, 2 million characters a month

2. Log in to the marketplace using your Windows Live ID. You will be asked to provide details such as name, email address and organization. Once you accept the EULA on the next step, you will be ready to go

3. Go to My Account and note the Primary Account Key and Customer ID to use on the next step

3. Then go to this address https://datamarket.azure.com/developer/applications/ and create an application registry.

GlobalSight-Microsoft-Translator

 

 

 

 

 

 

 

 

 

ClientID and Client secret are the values that you copied from My Account. Enter https://api.datamarket.azure.com/Bing/MicrosoftTranslator/ for Redirect URI. Name and Description are up to you. Click Save to register your application.

4. Then go to GlobalSight, Setup > Translation Memory Profiles. Select the profile that you want to use with MT and click MT options. Enter the Primary Account Key to the Client Secret field and Customer ID to the Client ID field and click “Test Host”. Once you get the success message you can save the profile and start using machine translation.

If you translate more than 2 million characters a month through the Microsoft Translator API, you will have to upgrade to a paid option at Microsoft Translator.

 

Categories: GlobalSight.

Comment Feed

4 Responses

  1. Thanks for topic, I have some questions though. You said “ClientID and Client secret are the values that you copied from My Account”, but from my account, I only have ClientID and Primary Account Key, should I use “Primary Account Key” as the Client Secret? Also, in the last step, you said “Enter the same Client Secret and Client ID you used during registry and click “Test Host”.”, I only got a field called “AppID”, should I put the ClientID in it? Where do I put the “Client Secret”? Should I change the default value of “MS Translator URL” on this page? Again, thanks for your help in advance.

    Carter HuMay 31, 2012 @ 2:37 pmReply
    • Hello Carter,
      Primary Account Key goes to Client Secret
      Customer ID goes to Client ID

      I have updated the post to clarify this, thanks for your comment.

      • Thanks, Emre! I have succeeded in making Microsoft translator work with GS,your post helped a lot!

        BTW, this requires 8.2.2 to work properly, 8.2 won’t work . Maybe it’s better to add that in the article.

        Carter HuJune 15, 2012 @ 2:40 pmReply
  2. I use memoQ, but your topic explained what redirect uri to use and saved my life. Thanks a lot.



Some HTML is OK

or, reply to this post via trackback.