Create a Language Pack

Use the Create Language Pack Wizard to create a Language Pack based on a source culture and scope, such as content strings for a specific Business Object or system platform strings.

You can then use the Language Pack Editor to translate strings in a Language Pack or you can export the Language Pack and send it to a vendor for translation. After strings are translated, you can apply translated strings in a Language Pack bundle to a Blueprint that you can publish immediately or save and publish later.

Run the Create a Language Pack Wizard

To run the Create Language Pack Wizard:

  1. Use one of these methods to open the wizard from CSM Administrator :
    • In the Main Window, select the Globalization category, and then select Manage Language Packs. On the Manage Language Packs page, select Create.
    • From a Blueprint or mApp Solution, select Managers > Language Packs, and then select the Create icon.

      To create a Language Pack that will be a part of a consolidated Blueprint, create the Language Pack from a Blueprint. Language Packs created from the Globalization category in the Main Window cannot be consolidated with other Blueprints.

  2. Select Next on the Language Pack Wizard Welcome page.
  3. Select a target culture. This represents the language and locale you want to translate to. Example: Select French (Canada) to translate source strings to Canadian French.

    If you are creating a language pack with an OOTB source and a target that doesn't yet exist, there will not be any values present in the Target column for things like content strings until a translator is ready to apply or manual edits are made. No translated values will be pulled into the language pack with scope “Platform Strings” for the four supported foreign languages.

  4. Select Next.

Select the Language Pack Scope

Identify the scope for your Language Pack.

You can choose one of three options:

  • Content Strings

    Choose one or more of the following options:

    • Definitions

      Select a Business Object scope:

      Option Description
      All Strings for all Business Object definitions.
      Specific Business Objects Strings associated with Business Objects selected on the Identify Specific Business Objects page.
      Blueprint Content Strings for new or modified Business Object definitions only. This option is only available when you create a Language Pack from a Blueprint or a mApp® Solution that contains new or modified definitions.
    • Portal Content Strings

      Extract strings for User-defined labels.

    • Lookup Table Data

      Extract strings for Field values in Lookup Tables.

      You must configure Lookup Tables for localization before you can create a Language Pack that includes Lookup Table data. See Enable Localization Support for a Lookup Table.

  • Platform Strings

    Choose one or both of the following options:

    • System Platform Strings

      Extract strings for application controls, dialogs, etc. for all CSM clients, except for the CSM Portal.

    • Portal Platform Strings

      Extract strings for CSM Portal resources, such as error messages, toolbar definitions, menus, etc.

  • None

    Create an empty Language Pack. Empty Language Packs are useful for merging multiple Language Packs with the same target language. For more information, see Use Small Scopes for Language Packs.

Limit the Scope to Specific Business Objects

If you chose to create the Language Pack with specific Business Objects, the Identify Specific Business Objects page opens.

Select the Business Objects and Views to include in your Language Pack. You can choose from:

  • Major
  • Supporting
  • Lookup
  • Group Leader
  • Group Member

Use the options at the top of the list to filter Business Objects by type. You can also select the Type column to sort the list.

Select the Source Culture for Platform Strings

If you chose to create the Language Pack with platform strings, select the source culture or base language from which strings will be translated.

Initially, you can choose one of the following base languages as your source:

  • English (en)
  • German (de)
  • French (fr)
  • Portuguese (pt)
  • Spanish (es)

After you have translated platform strings in at least one Language Pack, you can select the source culture for that Language Pack. For example, if you translate platform strings into Italian (Italy) (it-IT), you can use that as your source culture for new Language Packs.

Add Lookup Table Strings

If you chose to include Lookup Tables in your Language Pack, the Identify Specific Lookup Tables page opens.

Select the Lookup Tables to apply translations to, and then select Next.

Adding Portal Site Strings

If you chose to include CSM Portal content strings in your Language Pack, the Identify Specific Sites page opens.

Select the Sites to apply translations to.

Define Language Pack Properties

Finalize the Language Pack by defining these properties:

  • On the Order the Source Cultures page, use the arrows to order the selected source cultures to determine the fall-back mechanism for strings that don't exist in a particular language. For more information, refer to Fallback Mechanism.
  • On the Define Properties page, provide a name and description for your Language Pack.

On the Summary page, review the options you selected.

Select Back to change your options; select Finish to complete the wizard.