Overview

About Manage Translations Page Tasks

You can use the Manage Translations page to manage all the translatable strings that are displayed throughout Predix Essentials for all Security Users whose Predix Essentials Culture setting corresponds to a set of installed translation files. You can access this page from the Configuration Manager.

You can perform the following tasks on the Manage Translations page:
Note: You must belong to MI Configuration Role Security Group to access this page.

Any changes that you make to a translation file using this tool will be applied wherever the affected translation is used.

The Manage Translations page contains the following workspaces:
  • Metadata : Provides options that you can use to manage metadata string translations.
  • Application : Provides options that you can use to manage application string translations.

About the Microsoft Excel File for Translations

Metadata string and application string translations are stored in Predix Essentials as MTM files. You can download the translations to your local machine, where they will be converted to Microsoft Excel files so that you can work with the translations. After you are finished, you can upload the Microsoft Excel file, and the Predix Essentials system will create or update the MTM files stored in the Predix Essentials as needed.

The name of each Microsoft Excel file appears as <Language>.xlsx, where, <Language> is the language into which the application or metadata content is translated.

Each row in the Microsoft Excel file represents one string that is translated into the language indicated by the file name. For each string, additional information is displayed in the following columns:
  • Word: The default string. This is the string whose translation you can manage in that row.
  • Translated Word: The translation for the string that appears in the Word cell in that row. This is the only value that you should modify in the Microsoft Excel file. Before you customize a translation, you should know how to work with translations in the Microsoft Excel file.
  • Name: This value is used by Predix Essentials system.
  • Path: This value is used by Predix Essentials system.
  • Accessed: This value is used by Predix Essentials system.
  • Fit: This column is not used.
Important: Except for values in the Translated Word column, you should not modify any of the values in the Microsoft Excel file.

About Working with Translations in the Microsoft Excel Files

When you open a Microsoft Excel file containing translations for a language, you should modify only the strings that are stored in the Translated Word column. Before you do so, you should review the following guidelines:

  • If a string includes {0}, {1}, {2}, and so on, you should not modify the numeric value or remove the brackets { }. These values are used by Predix Essentials system.
  • If a string includes an ampersand (&), such as (&S), you should not remove the & symbol, change the letter of the alphabet that appears beside the & symbol, or remove the parentheses that appear around the & symbol and the letter of the alphabet. These values are used by Predix Essentials system.
  • If a string includes special characters such as a colon (:) or ellipsis (...), you should not remove these characters. These characters are used by Predix Essentials system.
Note: If you remove the characters described in the preceding bullet points, when you try to upload the Microsoft Excel file containing that translation, all the translations will be uploaded to thePredix Essentials, with the exception of the translation from which the required characters are missing. In this case, an error message will appear, indicating which translations were skipped for this reason. If you see this message, you can use the list of skipped translations in this message to correct the issues in the Microsoft Excel file, and then upload the translations again. If all the errors are corrected, all of your translations will be uploaded to Predix Essentials.

About the Predix Essentials Culture Setting

The Predix Essentials Culture setting is the value in the Culture drop-down list box in Predix Essentials Security User records. The Predix Essentials system uses this setting to determine which translation files to use when a user logs in to a Predix Essentials. For example, if the Predix Essentials Culture setting of a user is Spanish (Spain), that user will see Spanish translations throughout Predix Essentials.

Before a user can see the translated strings in Predix Essentials, their Security User record must contain a corresponding Culture setting.

The following table provides a mapping from each Predix Essentials Culture settings to the translations that are currently available in Predix Essentials. We recommend that you use this list as a guide for configuring Predix Essentials Security User records.

Non-English Version of Predix Essentials Predix Essentials Culture Setting(s)
Chinese

Chinese (People's Republic of China)

-or-

Chinese (Simplified)

DutchDutch
French French (France)
German German
Italian Italian (Italy)
Portuguese Portuguese (Brazil)
Russian

Russian

-or-

Russian (Russia)

Spanish Spanish (Spain)
Japanese
Note: Japanese is not currently available for Rounds Data Collection on Windows mobile devices.

Japanese

-or-

Japanese (Japan)

PolishPolish (Poland)

About the Translation Files

Translations for Predix Essentials are stored in files with the .MTM extension. By default, two files are provided for each supported language that you purchase:
  • One file stores the baseline translations for application strings.
  • One file stores the baseline translations for metadata strings.

The translation files are named according to the abbreviation for the culture associated with the language that is stored in that file. For example, the Spanish translation file is named es.MTM, where es is the abbreviation for Spanish.

If you customize baseline translations or add new translations, custom translation files will be created automatically to store those translations. For example, suppose that for Spanish, you want to modify the translation for the baseline string Equipment. Suppose that the same string Equipment appears both as a button label (application string) and as a datasheet caption (metadata string).

To modify a translation, you can download to your local machine the translations stored in the appropriate translation file from the Predix Essentials. These translations will be downloaded to a Microsoft Excel file, which you can use to modify the translations. After you modify the translation strings, you can upload the Microsoft Excel file, and the Predix Essentials system will automatically convert that file to a translation file (that is, with the extension MTM) and save it.

The Predix Essentials system will display only the strings that are stored in translation files in Predix Essentials. If you have uploaded custom translation files, the Predix Essentials system will use your custom translations instead of the baseline translations.

About Types of Strings in Predix Essentials

Predix Essentials contains the following types of strings:
  • Application Strings

    Predix Essentials displays textual content on various user interface components such as pages, buttons, links, tiles, and so on. If a translation file is installed, the text will be displayed in the language that is based on the culture setting for the Predix Essentials Security User. You can customize these translations.

  • Database Strings

    Predix Essentials displays the database content, such as asset strategy templates, inspection recommendation content, taxonomy reference tables, help content, APM query results, and so on. The database content is not translated.

    Note: The content within baseline records are not translated (for example, if we have a baseline record that contains a field, Location, and the field contains a value, the string Location is translated, but the value in that field is not translated).
  • Metadata Strings

    Predix Essentials displays the metadata content, such as datasheet captions, family captions, field captions, error messages, system codes, states, and so on. These strings appear throughout Predix Essentials. If the associated translation files are installed, the metadata strings will be displayed in the language based on the culture setting for the Predix Essentials Security User. By default, metadata strings are translated for all supported languages. You can customize these baseline translations.

    If you create your own metadata content (for example, a new family with fields and datasheets), for each string that you use, if a baseline translation does not exist, you must provide the translation in each language in which you want the string to appear. If a string does not exist in the translation file for any language that you have installed, the string will be displayed in English to all users, regardless of their Predix Essentials culture setting.

About Translatable Metadata Strings

When you create or customize metadata string translations, a custom metadata string translation file is created automatically in Predix Essentials. If you want custom translations to appear in Predix Essentials, you will need to upload your custom metadata string translations to the Predix Essentials.

You can translate metadata strings from the following locations:

  • The Manage Translations page in the Configuration Manager: From this location, you can download the baseline metadata string translations to a Microsoft Excel file, modify the translations, and then upload the Microsoft Excel file to the Predix Essentials. You can also use download your custom metadata string translations, customize the translations, and then upload the modified file..
  • The Localize <Strings> window, which is accessible from the buttons that appear throughout Predix Essentials wherever you can translate a metadata string. From this location, you can add or modify metadata string translations using a grid, and they will be uploaded to Predix Essentials automatically.

Custom translation files will be used instead of the baseline translation files. Because only one custom metadata string translation file can exist per language, after you create a custom metadata string translation file, if you want to make further changes, you should download your custom metadata string translation file, customize the translations, and then upload it again. The most recent file that you upload will be the file that is used by the Predix Essentials system.

Metadata strings are case sensitive. This means that if the metadata string translation file contains a translated string that contains a capital letter, and you create a translation for the same string except it contains a lowercase letter, the string with the lowercase letter will be considered a new custom string (because it did not already exist in a translation file). For example, if the string, Produce (capitalized) exists in a translation file, when you create a query named produce (lowercase) and translate it, the string produce and its translations will be added to a custom translation file.

The following lists identify the metadata strings that can be translated. You can use these lists as a reference when you are translating metadata strings.

In Configuration Manager, you can provide translations for the following items:
  • Family captions
  • Field captions
  • Field help text
  • Datasheet captions (standard datasheets and custom-layout datasheets)
  • Datasheet section captions
  • Unit of measure (UOM) captions
  • System Code Table descriptions
  • System Code descriptions
In Predix Essentials, you can provide translations for the following items:
  • Catalog item captions for all Catalog item types
  • Contents of reports that is controlled by report layout (not the underlying data)
  • Labels for links in the shortcut menu in query results
  • Labels for a submenu in the shortcut menu in query results
  • Query aliases
  • Query prompt captions
  • Section names in a dashboard
  • Names of hyperlinks that are displayed in dashboard sections
  • Labels of axes on graphs that are displayed in dashboard sections
  • State captions
  • State roles captions
  • State operations captions

About Application String Translations

You can modify the baseline application string translations using the Manage Translations page in the Configuration Manager. On this page, you can download the baseline application string translations to a Microsoft Excel file, customize the translations, and then upload the Microsoft Excel file to the Predix Essentials. When you do so, a custom application string translation file will be created automatically, and will contain all the application string translations, including your custom translations. This custom translation file will be used instead of the baseline translation file.

Because only one custom application string translation file can exist per language, after you create a custom application string translation file, if you want to make further changes, you should perform the following steps:
  1. Download your custom application string translation file.
  2. Customize the translations.
  3. Upload the translations again. The most recent file that you upload will be the file that is used by the Predix Essentials system.

If you delete a custom application string translation file, the Predix Essentials system will automatically use the baseline application string translation file.

Access the Manage Translations Page

Procedure

In the module navigation menu, select Admin > Configuration Manager > Manage Translations.
The Manage Translations page appears.

About the Manage Translations Application Workspace

The Application workspace on the Manage Translations page contains the following sections:

  • APM Translation: Contains the following items:
    • Installed Languages List: Contains the names of the non-English languages for which there are corresponding baseline application translation files on the Predix Essentials system. You can use this list to determine all the non-English languages in which you can view application strings in Predix Essentials.
    • To download a translation file, select a language, and then in upper-right corner of the section, select . This will download the Microsoft Excel file containing the baseline application string translations, and will then download the translations to that location from Predix Essentials.
  • Custom Translation: Contains the following items:
    • Uploaded Languages List: Contains the names of the non-English languages for which there are custom application translation files on Predix Essentials system. If no custom application translation files exist, this list will be empty. You can use this list to determine the languages for which you have provided custom translations.

      After you upload a custom application string translation file to Predix Essentials, the name of the corresponding language will be added to the Uploaded Languages list. After a language appears in the Uploaded Languages list, subsequent uploads of a custom application string translation file for the same language will overwrite the custom application string translation file on the Predix Essentials system with the newly uploaded file. Note that the previous file is actually moved to a different location in the Predix Essentials, from which it can be restored later, if needed.

    • To download, select a language, and then, in the upper-right corner of the section, select . This will download the Microsoft Excel file containing the custom application translation file for the selected language.
    • To delete a language, select a language, and then in the upper-right corner of the section, select. A confirmation message will appear, and then the custom application translation file for the selected language will be deleted.
    • Upload Custom Translations Button: Allows you to navigate to the custom application translation file containing your custom application string translations, and then upload the file to Predix Essentials. After you upload a custom application string translation file to Predix Essentials, the name of the language that corresponds to that file will be added to the Uploaded Languages list.

About the Manage Translations Metadata Workspace

You can use the Metadata workspace in the Manage Translations page to manage the translations for translatable metadata strings.

The Metadata workspace contains the following sections:
  • APM Translation: Contains the following item:
    • Installed Languages: Contains the names of the non-English languages for which there are corresponding baseline metadata string translation files in the Predix Essentials system. You can use this list to determine all the non-English languages for which you can view metadata strings in Predix Essentials.

    • To download the translation file, select a language, and then in the upper-right corner of the section, select . This will download the Microsoft Excel file containing the baseline metadata string translations, and will then download the translations to that location from Predix Essentials.

  • Custom Translations: Contains the following items:
    • Uploaded languages List: Contains the names of the non-English languages for which custom metadata string translation files exist in the Predix Essentials system. If no custom metadata string translation file has been uploaded to the Predix Essentials, this list will be empty. You can use this list to determine the languages for which you have provided custom metadata string translations.

      After you upload a custom metadata string translation file to Predix Essentials, the name of the corresponding language will be added to the Uploaded Languages list. After a language appears in the Uploaded Languages list, subsequent uploads of a custom metadata string translation file for the same language will overwrite the custom metadata string translation file in the Predix Essentials system with the newly uploaded file.

    • To download a translation file, select a language, and then select . This will download the Microsoft Excel file containing the custom metadata string translations for the selected language.
    • To delete a language, select a language, and then in the upper-right corner of the section, select . A confirmation message will appear, and then the custom metadata string translation file for the selected language will be deleted.
    • Upload Custom Translations button: Allows you to navigate to the custom metadata string translation file containing your custom metadata string translations, and then upload the file to Predix Essentials. After you upload a custom metadata string translation file to Predix Essentials , the name of the language that corresponds to that file will be added to the Uploaded Languages list.
  • Custom Metadata: Contains the following items:
    • Available Languages List: Contains the names of the non-English languages for which metadata string translation files exist in the Predix Essentials system. You can use this list to select the languages in which you want to translate your untranslated custom metadata strings.
    • Export Untranslated Metadata Button : Allows you to export your custom untranslated metadata strings to a Microsoft Excel file. Using this option, you can download and save the Microsoft Excel file containing the untranslated metadata strings.

Baseline Translations Customization Workflow

This workflow provides the basic, high-level steps for using this feature of Configuration Manager. The steps and links in this workflow do not reference every possible procedure. For more procedures, refer to the links in the Related Information section.
  1. Download the baseline metadata string translations or baseline application string translations.
  2. Open the Microsoft Excel file and review the translations.
  3. Make changes to translations as needed.
  4. Upload the Microsoft Excel file containing your metadata string translation changes or application string translation changes to Predix Essentials.

Custom Metadata String Translation Workflow

This workflow provides the basic, high-level steps for using this feature of Configuration Manager. The steps and links in this workflow do not reference every possible procedure. For more procedures, refer to the links in the Related Information section.
  1. Export your untranslated metadata strings to a Microsoft Excel file.
  2. Open the Microsoft Excel file and provide translations as needed.
  3. Upload the Microsoft Excel file containing your translations to Predix Essentials .
Note: As you create custom metadata content in Predix Essentials, you can translate those individual custom metadata strings from the Localize <Strings> window.