You are here: Document Designer > Document Designer: Languages and Translations

Document Designer: Languages and Translations

OVERVIEW

The Document Designer supports additional language translations in two ways:

ADMINISTRATION

ClosedExample

In the example below, there are three separate Proposal templates—one for each translation. However, the Contract template is multilingual and contains translations for all necessary languages within the single template.

Whether multiple templates should be used for translations or if a single template should be used for translations must be decided on a customer-by-customer, template-by-template basis.

  Multiple Templates One Template

Advantages

Each Translation template can be worked on simultaneously by multiple admins, and it is easier to make individual language templates different from each other if desired.

All layout, design, property, etc. changes only need to be done once.

Considerations

All layout, design, property, etc. changes must be done for each template file.

Only one language can be translated at a time, and much more administration work is required if outputs for each language need to be different in other ways besides their translations.


ClosedLanguage Attribute

A Commerce attribute type, Language, can be created at the Quote/Transaction-level and placed on the Commerce layout. When linked to a Print or Email action, the value of the Language attribute specifies what language the Document Designer template that is linked to the action should be outputted in upon printing.

A Language Attribute menu exists on the XSL Views tab of Print and Email actions in order to associate a Language attribute with the action.

Attributes in general are discussed in the topic Commerce Attributes.


ClosedCreating a Language attribute

  1. Click Admin to go to the Admin Home Page.
  2. Click Process Definition under Commerce and Documents.

    The Processes page appears.

  1. For the process for which you want to create the Language attribute, confirm that Documents is selected in the Navigation column and click List.
  2. For the Main Document, such as Quote or Transaction, make sure Attributes is selected in the Navigation column and click List.

    The Attribute List page appears.

  1. Click Add.
  2. Enter a Label and Variable Name for the attribute.
  3. Select Language from the Attribute Type drop-down.

  1. Click Add to add the attribute.

The Language attribute can be added to the Commerce Quote/Transaction-level layout, referenced in functions and Formulas, etc.


ClosedLinking a Language attribute to a Print or Email action:

  1. Click Admin to go to the Admin Home Page.
  2. Click Process Definition under Commerce and Documents.

    The Processes page appears.

  1. For the process for which you want to link the Language attribute to a Print or Email action, confirm that Documents is selected in the Navigation column and click List.
  2. For the Main Document, such as Quote or Transaction, make sure Actions is selected in the Navigation column and click List.

    The Action List page appears.

  1. Click the Print or Email action you want to modify.
  2. Click the XSL Views tab.
  3. Select the Language attribute from the Language Attribute drop-down.

  1. Click Apply or Update to save the action.

Creating a Print or Email action is covered in the topic Document Designer Overview.


ClosedMultiple Templates for Translations

When creating multiple templates to handle translations, all templates should be given the same name, but a different language should be chosen for each template upon creation. When all templates are given the same name, only one name must be associated with the Printer Friendly XSL View, so only one XSL View and one Print/Email action must be created and maintained to support multiple templates.

When the Print/Email action is invoked, the system will output the template whose name is associated with the Printer Friendly XSL View and whose language setting matches the value of the Language attribute that is associated with the Print/Email action.

If Document Designer templates have the same name, they cannot have the same language setting.

If multiple templates are being used for Translations, and if there is no template that matches the value of the Language attribute, and there is not a multi-lingual template defined, an error will be shown when the user attempts to output the template.


ClosedTo create multiple Document Designer templates to support translations:

ClosedMulti-Language Template for Translations

When creating multi-language template to handle translations, Multiple should be selected for Language and a default language must be chosen.

When the Print/Email action is invoked, the output of the template will show all translated Elements whose translation language matches the value of the Language attribute that is associated with the Print/Email action.

For example, if the value of the Language attribute is German, all Text and Heading Elements that have German translations associated with them will appear in German in the output. If a Text or Heading Element does not have a translation associated with it, it will appear in the default language in the output unless it is hidden with a Condition that uses the value of the Language attribute to determine in the Element should be shown or hidden.

If no Language attribute is associated with the Print/Email action, if the Language attribute has no value, if the value of the Language attribute does not match a language that exists in the template, or if the template has no translations associated with its Text or Heading Elements, the template will output in its default language.


ClosedTo create a multi-language Document Designer template to handle translations:

ClosedAdding Translations

Text and Heading Elements within multi-language templates can have translations added to them so that the translated content appears in the output when the value of the Language attribute corresponds to the language of the translations.

The Translation window for a Text or Heading Element can be accessed in two ways.


ClosedChanging to the Translation view of the Template Flow and then opening the Element:

ClosedOpening the Element and then changing to the Translation view within the editor window:

NOTES

RELATED TOPICS

Related Topics Link IconSee Also