#335 Microsoft Translator activation

[I T]

I was trying to run the Microsoft Translator API under OmegaT-3.1.8 for Windows, by entering my credentials for #-Dmicrosoft.api.client_id and #-Dmicrosoft.api.client_secret into OmegaT.l4J.ini

My account for the Microsoft Translator API has been newly created at https://datamarket.azure.com/developer/applications/register and should be ok.

However, after opening a Project and selecting Options > Machine Translate > Microsoft Translator, OmegaT-3.1.8 keeps telling me 'Microsoft Translator's Client ID or Client Secret not available. See OmegaT manual for instructions.' Unfortunately, there's nothing for 'Microsoft Translator' in the manual...

Any suggestions what might be wrong?

How can the Microsoft Translator API be run under OmegaT-3.1.8 Beta for Linux?

TIA for your help!

[Kos Ivantsov]

Hi,
OmegaT.l4J.ini isn't used in Linux. You can edit OmegaT launch script located in OmegaT installation folder, or use omegat.kaptn (same location). Here's a little howto on customizing omegat.kapnt
https://libretraduko.wordpress.com/2014/05/21/customizing-omegat-kaptain-launcher-gnulinux/
You can edit it to store your credentials and custom settings by default thus eliminating the need to enter them every time.

--
Kos

[I T]

Hi Kos,
Thanks for the pointer!I customized omegat.kaptn for OmegaT-3.1.8 Beta for Linux by entering my credentials in the following format:
msi "Microsoft Translator API Client ID" -> @password="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" ;msk "Microsoft Translator API Secret Key" -> @password="xxxx/xxxxxxxxxxxxxx+xxxxxxx/xxxxxxxxxxxxxxx=" ;
However, I still receive the error message 'Microsoft Translator's Client ID or Client Secret not available', i.e. same result as with OmegaT-3.1.8 for Windows ;-(
I tested my Client ID & Secret Key using the EXPLORE THIS DATASET option at Microsoft Translator | Microsoft Azure Marketplace, so the problem appears to be with OmegaT (but that's just an assumption...)Best regards,I T 

[Kos Ivantsov]

Hi,
You can use a few other tools to check your MS credential. One of them is Okapi Rainbow (https://bintray.com/okapi/Distribution/Okapi_Applications/view).
When you unpack it, run rainbow.sh/rainbow.exe.

1. There in the main window, either drag a sample text document to the first tab, or press Ctrl+Ins to add a document for the test.
2. Then on the fourth tab, "Languages and Encodings", select appropriate settings.
3. Then click Utilities -> Edit/Execute Pipeline.
4. In the popped up window add 3 steps:
   • Raw Document to filter events
   • Microsoft Batch translation
   • Filter Events to Raw documents (in this order)
5. In MS Batch translation settings enter your Client Id and Client Secret, enable "Generate a TMX document", tell the program where to save it, and enable "Send the TMX doc to the next step"
6. Then click 'Execute", and if everything is Ok, you'll get a TMX file with languages set up on the fourth tab of the main window (step 2).

If there's a mistake, the error message will let you know what it is.

--
Kos

P.S. The best place to discuss this kind of issues is http://groups.yahoo.com/group/omegat as there's a vast and very responsive user base from all over the globe

[I T]

Many thanks again. Rainbow shows indeed a 400 error, but I haven't been able so far to determine the reason for it.
Best regards,I T
From: Kos Ivantsov kosivantsov@users.sf.net
To: [omegat:documentation] 335@documentation.omegat.p.re.sf.net
Sent: Friday, March 6, 2015 11:53 PM
Subject: [omegat:documentation] #335 Microsoft Translator activation

Hi,
You can use a few other tools to check your MS credential. One of them is Okapi Rainbow (https://bintray.com/okapi/Distribution/Okapi_Applications/view).
When you unpack it, run rainbow.sh/rainbow.exe.

• There in the main window, either drag a sample text document to the first tab, or press Ctrl+Ins to add a document for the test.
• Then on the fourth tab, "Languages and Encodings", select appropriate settings.
• Then click Utilities -> Edit/Execute Pipeline.

• In the popped up window add 3 steps:

  • Raw Document to filter events
  • Microsoft Batch translation
  • Filter Events to Raw documents (in this order)

• In MS Batch translation settings enter your Client Id and Client Secret, enable "Generate a TMX document", tell the program where to save it, and enable "Send the TMX doc to the next step"

• Then click 'Execute", and if everything is Ok, you'll get a TMX file with languages set up on the fourth tab of the main window (step 2).
  If there's a mistake, the error message will let you know what it is.--
  KosP.S. The best place to discuss this kind of issues is http://groups.yahoo.com/group/omegat as there's a vast and very responsive user base from all over the globe [documentation:#335] Microsoft Translator activationStatus: open
  Group: www.omegat.org
  Created: Fri Mar 06, 2015 06:51 PM UTC by I T
  Last Updated: Fri Mar 06, 2015 08:15 PM UTC

Owner: nobodyI was trying to run the Microsoft Translator API under OmegaT-3.1.8 for Windows, by entering my credentials for #-Dmicrosoft.api.client_id and #-Dmicrosoft.api.client_secret into OmegaT.l4J.ini My account for the Microsoft Translator API has been newly created at https://datamarket.azure.com/developer/applications/register and should be ok.However, after opening a Project and selecting Options > Machine Translate > Microsoft Translator, OmegaT-3.1.8 keeps telling me 'Microsoft Translator's Client ID or Client Secret not available. See OmegaT manual for instructions.' Unfortunately, there's nothing for 'Microsoft Translator' in the manual...Any suggestions what might be wrong?How can the Microsoft Translator API be run under OmegaT-3.1.8 Beta for Linux?TIA for your help!Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/omegat/documentation/335/To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Didier Briel]

I don't know when it will be possible to update the documentation to add Microsoft Translator (and MyMemory and Yandex), but it is indeed missing from the documentation. On the other hand, it is "auto-documented" in the main launchers, so documenting might "just" be a question of writing "look in your launcher for the details of credentials to add".

Didier

[Kos Ivantsov]

I've updated MachineTranslation.xml and InstallingAndRunning.xml, and I'm attaching them here to be reviewed by Vincent, instead of committing directly. The files seem to validate, but I have very little idea how to compile them into the actual help files.

[Vincent Bidaux]

Thank you Kos,
I've commited your updated files (after very few changes)

Vincent

[Didier Briel]

Contrary to software releases, when use "open-fixed" then "closed-fixed" only when a version containing the fix is released, we usually close the documentation issues/request as soon as they are done in SVN.

Didier