Help Center>Foundation Help

Applies to:

Translating Composer forms to other languages

For additional information:

This page describes two different methods of translating Composer form elements (field labels, drop-down options, etc.) into other languages. In addition, it covers Translation Overrides, which you can use to modify the translated values.

Important: The browser language must be set to English when translating solutions. Other browser languages are not supported.

On this page

Option 1: Use a translator service

Back to top

You can translate forms in Composer using either Microsoft Cognitive Services translation or Google translation.

Adding the translator code to Composer

Back to top
  1. Once you have the code, click the Composer Start button , and then click Preferences.

  2. On the Preferences screen, click the General tab, and enter the key for either the Cognitive Services API or the Google API.

    preferences box

    For more information about the Cognitive Services API and to get a key, visit the Microsoft Azure Text API website to create an account.

    For more information about the Google Cloud Translation API and to get a key, see the Google Cloud Platform website. Note that Google released an upgrade for its APIs from version 2 (v2) to version 3 (v3). As a result, APIs v2 no longer works properly with Winshuttle forms. To make Google APIs work again, a small change must be made in the frmCommon.js file. See the instructions on the Support site.

  3. Click OK.
  4. In Composer, click the Start menu, click Translations, and then click Run Translations.

  5. In the Select Languages to Translate screen, under Select Language, click the arrow and then select one or more languages.
  6. Click Translate.
  7. Once the form is successfully compiled, click OK.
  8. On the ribbon, click Desktop to preview your form and view translations.

  9. In the preview, next to Translate, click the arrow and select a language.

Option 2: Export as a text file

Back to top

Composer translation text file example

Composer translation text file example
Another translation option is to export the form elements to a text file. This option creates a file with all of the labels associated with the Form (for all Views), and includes Name=Value pairs for each Label.

  • The Name is the Label ID
  • The Value is the English text of the Label.

The Label text (the Value) can be translated into any language and then imported into the solution by specifying which language to update.

Note: The Name (or Label ID) should never be modified.

Prior to Release 11.1 you would need to keep a copy of any translated files; however with Release 11.1 any previously translated language can now be exported as well. Those labels that are new or have not been translated yet, will be shown in English.

Exporting to a text file

  1. Open your Composer form.
  2. Open the Composer Start Menu, click Translations, and then click Export Translations. This exports the solution file as a text (.TXT) file.

  3. Translate the exported text file. For example, send the file through a translation service.
  4. Import the translated text file. Open the Composer Start Menu, click Translations, and then click Import Translations.

  5. On the Import Translations screen, click Choose File to browse to the translated file, and select the language of the translated text file from the drop-down menu.
  6. Click Import.

    7. Import translations


Using Translation Overrides

Back to top

After you use the Import Translation functionality or the translation service, you can correct any mistakes or make changes to labels by using the Translation Override property.

  1. In your Composer form, click the label of the field (not in the field itself) that you wish to translate.
  2. In the Properties pane, next to Translation Overrides, click the Options [...] button.

  3. In the Translation Override Editor, enter the desired translation(s) for the required language(s), and then click OK.

Note: If you make modifications to DropDown or ComboBoxes for which you've created options manually (i.e. the Range is set Manually), make sure you re-translate the solution before deploying it.