Export text strings for language translation

Export user-editable text strings in a project to a language file to translate the text strings.
To export text strings for language translation
  1. Select
    Tools > Export Languages
    .
  2. In the
    Select current language
    list, select the language in which the project was created.
  3. In the
    Selected language for localization
    box, select one or more languages for translating the strings.
    TIP:
    Tips:
    • View Designer
      does not support the Spanish (Spain, Traditional Sort) language that is supported in
      Studio 5000 Logix Designer®
      .
    • When opening the exported language file in Microsoft Excel, the selected languages appear as column headers. Languages currently in the project are always included in the export operation, and are not available for selection.
  4. In the Export language file to box, select
    Browse
    to select the location to save the language file, and select
    Save
    .
    TIP:
    Tips:
    • The default path and file name is C:\Users\username\Documents\Studio 5000\Projects\Project name_Language.xlsx.
    • View Designer
      supports .xlsx and .txt file formats only.
    • If a file name does not have a file extension, or has an file extension that is not supported,
      View Designer
      appends the file to the default .xlsx format.
    • View Designer
      only exports localizable and unlinked properties.
  5. Select
    Export
    .
  6. Open the exported file using Excel.
    TIP:
    Excel does not size cells automatically to display data in its entirety. To ensure that all of the data displays, auto-size the height and width before editing the spreadsheet.
  7. To add a language that is not in the spreadsheet, in the column next to the last language column, enter the language code for the desired language, such as en-US.
    TIP:
    Reference the Internet Engineering Task Force (IETF®) RFC 5646 for guidelines on formatting language codes.
  8. (optional) Insert a space after the language code and add the applicable contextual information. Content is not case sensitive.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal