Kentico Xperience 13 documentation and ASP.NET Core

Most documentation about running Xperience applications under ASP.NET Core can be found in a dedicated section: Developing Xperience applications using ASP.NET Core. The rest of the documentation still applies, but some code samples and scenarios might need slight modifications for Core projects.

All major differences between the MVC 5 and Core platforms are summarized in Migrating to ASP.NET Core.


Configuring content for translation

Translation services can process the following types of page content:

  • Values of page fields on the Content tab of the Pages application
  • Page file attachments (without their image variants)

    Note: Text added and displayed through page builder widgets is not processed by translation services or included in the resulting translation data.

The system allows you to specify exactly which parts of the content are translated. These settings affect all types of translation services.

Configuring page fields

To choose which page fields are sent for translation, adjust the form definition of individual page types:

  1. Open the Page types application.
  2. Edit () a specific page type.
  3. Switch to the Fields tab.
  4. Select the field that you wish to configure and enable or disable the Translate field flag. Translation is only available for fields with the Text, Long text or File Data type.
  5. Click Save to confirm the changes to the field.

Enabling the Translate field flag for a page type field

When users submit pages of the given type for translation, only the content of fields that have the Translate field flag enabled is included in the translation.

On this page

Enterprise license required

Features described on this page require the Kentico Xperience Enterprise license.

Allowing translation of page attachments

Human translation services allow users to submit file attachments for translation along with the main content of pages. To configure attachment translation for your website:

  1. Open the Settings application and select the Content -> Translation services category.
  2. Enable the Allow attachment translation setting.
  3. Specify which types of files should be translated using the Translation attachments file types setting.
    • Enter a list of all allowed file extensions separated by semicolons (for example: txt;docx;pdf). Leave the setting empty to allow translation for all types of attached files.
  4. Click Save.

Users can enable the Translate attached files option when submitting pages for translation, and the system adds all allowed file attachments into the translation source. When the completed translation is imported, the translated file is attached to the appropriate language version of the page.

File format

The system adds file attachments directly into the XLIFF translation source as binary data encoded in Base64 format.

Was this page helpful?