Cloud text translation plugin for Wordfast Anywhere

This plugin provides a way for Globalese users to translate files or entire projects from Wordfast Anywher.

Prerequisites and pricing

With this plugin, users can consume Globalese Text translation services in Wordfast Anywhere. For more details about how to enable an engine for text translation, see https://globalese.atlassian.net/wiki/spaces/DOCS/pages/2233761810.

Pricing is based on the number of translated source text characters. The actual price is listed on the Pricing page under “Text translation”. Deploying an engine and keeping an engine deployed is at no additional cost.

Configuring and using the plugin in Wordfast Anywhere

  1. Make sure that your engine has been deployed for Text translation. You can check the status on the engine overview page (menu item Engines).

    If the status is showing On, you can configure the engine for Text translation in Wordfast Anywhere. If the status is showing Off, please deploy the engine as described here: https://globalese.atlassian.net/wiki/spaces/DOCS/pages/2232680449.

  2. Log in to WordFast Anywhere, and choose Wordfast Anywhere Setup WFA → MT.

  3. Choose Add.

  4. Select Custom as MT engine Type

  5. Enter the required parameters

    Name: description of your Globalese engine. It is recommended to enter the language direction in the name.
    URL: the URL can be retrieved from the engine overview page. Please add /api/v1/translations at the end of the url: https://<my_engine_url>/api/v1/translations


    POST: JSON

  6. POST content:

    { "engine_id": "<my_engine_ID>", "sentences": [ "{ss}" ] }

    As the engine_id value, please insert the UUID value from the engine overview page in Globalese

  7. HEADER: Authorization: Bearer <my_api_key>
    You can use either your user API key from your user profile or a generated API key assigned for the engine (https://globalese.atlassian.net/wiki/spaces/DOCS/pages/2233860120).

  8. API key: please leave it empty

  9. JSON key: sentences

  10. Engine timeout in millisecond: 8000

When saving the configuration, you might get a timeout message. This message can be ignored. The reason is that custom Globalese engines have an initial cold run time of 5-10 second if they are not used for a longer period. Please test the engine on the MT engine overview page: