Skip to main content





Translation management

  • Edit
    Collaborate with us
    Edit this page on GitHub
  • You can export translatable resources to files and send them to a professional translation service. Once you receive the translated files, import them into your app. You can also translate the resources yourself with the translation editor.

    Note: If translatable text has no translation, the app shows the text in the default language of the app.

    Export the text for translation

    To export the translatable text from your module follow these steps in Service Studio:

    1. Go to the Data tab, right-click Multilingual Locales, and then hover the move over Export Language Resources to show a new menu.

    2. In the menu select one of the options to export in the format you want:

      • To Excel. Exports all translatable text to a single Excel file.
      • To .resX (.NET resource format). Exports all translatable text to the .resX files.
    3. Select the export location and click OK.

    For more information about the translation files, see Translation resource file formats.

    To control which text Service Studio exports, see more information about translatable and non-translatable text in Translating with the translation editor.

    Import the translation

    To import the translation back to the module, follow these steps in Service Studio:

    1. Go to the Data tab and right-click Multilingual Locales and select Import Language Resources. A dialog opens.

    2. Select the file for import into Service Studio.

      You can import files in one of the following formats:

      • Excel file. When you import an Excel file, you update translations in all languages.
      • .resX files. After you import a .resX file for a language, you update only the translations in the specific language in that file.

    Translation resource file formats

    What follows is more information about the file formats Service Studio uses to export text for translation and import the translation.


    All translatable text is in a single Excel that consists of these columns:

    • Key: a unique identifier
    • Location: the location of the translatable text in the module
    • Text to be translated: the text for translation
    • ( Locale(s) ): columns for each language locale in your module. Enter the translated text here. If you want to keep using the original text, leave the translation text empty.

    The name of the Excel file is <module name> + Language.xls. For example, if your Module name is Recruitment the file name is RecruitmentLanguage.xls.

    .NET resource format

    All translatable text is in the .resX files, one file for each language locale in your module, plus an additional file for the default language. The content is in XML consisting of the name:value pairs:

    • Name: a unique identifier
    • Value: the field where you should replace existing text with the translation
    • Comment: The location of the translatable text in the module

    Some .NET Framework versions may have more attributes in the translatable resource files than those described here. The extra attributes have no effect on the app interface.

    The name of the .resX files is in the following format: <module name> + Language + .<Language locale>.resX'. For example, if your module name is Recruitment with the locales being French (France) (fr-FR) and French (Canada) (fr-CA), then the three generated files are:,, and RecruitmentLanguage.resX for the default language.

    • Was this article helpful?