Configuring Language Mapping and Asset Packaging

  2 minute read  

In the Workspace settings tab:

  • You map Episerver languages to Clay Tablet languages in the language mapping.xml file.
  • You configure how the Connector packages multiple assets in a translation project.
To configure language mappings and grouped-asset handling:
  1. In the bottom-right corner of the Lionbridge Connector gadget in the right pane, click the Settings icon , and then select Settings from the context menu.

  1. In the Workspace settings tab, edit the Language Mapping XML field to map each Episerver language code to the corresponding Clay Tablet language code. For a list and description of Clay Tablet language codes, see Appendix: Language Codes.

For example:

<Languages>

<Language>

<EPiServer>sv</EPiServer>

<ClayTablet>sv-SE</ClayTablet>

</Language>

<Language>

<EPiServer>da</EPiServer>

<ClayTablet>da-DK</ClayTablet>

</Language>

</Languages>

Note: If you leave this section empty, the Connector will use the default values.

  1. In the Workspace settings tab, you can configure how the Connector packages multiple assets in a translation project.

  • If you select the Use grouped asset handling check box, then the Connector packages all pages and blocks selected for translation into a single XML file for each target language.

Recommendation: Select this check box, especially if Lionbridge Freeway will translate terms for SEO.

  • If you clear the Use grouped asset handling check box, then the Connector sends each page and block selected for translation as a separate XML file.

Episerver automatically saves your changes.