You are here: User Guides > Connector for Episerver > Sending Assets for Translation

Sending Assets for Translation

When you send out assets for translation, they are part of a translation project.

You can add assets for translation to a new or an existing project.

Note: You can add assets to an existing project only if it is in Draft status. You cannot add assets to a project after it has been submitted for translation.

You can send out the following types of assets for translation:

Asset Type Description Additional Notes
Episerver Blocks Blocks that are referenced on a page in a Content Area or ContentReference fields. If the same block has multiple references, the Connector sends it out for translation once, in the context of the first page where it is referenced.
Episerver page properties

The following page properties are supported:

  • String
  • XHtmlString
  • ContentArea
  • ContentReference

Unsupported page properties will be blank, so you cannot publish the corresponding pages, as described in Publishing Translated Assets.

Tip: Review these pages manually and populate the blank page properties so that you can publish the pages.

custom properties Custom properties created by the customer. The Connector supports sending for translation only custom properties that inherit from the ProperyLongString and PropertyString classes.
How the Connector packages the assets for translation

Either:

  • The Connector sends each page and block for translation as a separate file.
  • The Connector bundles all pages and blocks in the translation project for translation into a single XML file, creating one file for each target language.

You configure this setting using the Use grouped asset handling check box. For detailed instructions, refer to the Lionbridge Connector for Episerver Installation and Configuration Guide.

Recommendation: If Lionbridge Freeway will translate terms for SEO, select this check box.

When sending assets for translation, there are two basic steps:

  1. Creating a translation project, including adding the assets to translate. You do this from the Lionbridge Connector gadget. For detailed instructions, see Creating or Editing a Translation Project.
  2. Sending out the project for translation. You can do this either from the Lionbridge Connector gadget or from the Lionbridge Connector Dashboard. For detailed instructions, see Sending a Project for Translation.