• Documentation
  InstallationUsing the Kentico interfaceDeveloping websitesConfiguring KenticoManaging usersSecuring websitesDeploying websitesManaging website contentMultilingual websitesMacro expressionsExternal utilitiesIntegrating 3rd party systemsCustom developmentE-commerce featuresOn-line marketing featuresIntranet featuresCommunity featuresRunning Kentico on Microsoft AzureUsing Amazon web services with KenticoReferencesRelease notes - Kentico 8 versions
• Tutorial
  Using the Kentico interfaceManaging content - The basicsSite development overviewCreating pages using the portal engineWalkthrough - Creating a new site using the Portal engineCreating pages using ASPX templatesWalkthrough - Creating a new site using ASPX templates

Retrieving translation data from the system

To retrieve page translation data, send an HTTP GET request to a URL in one of the following formats:

• ~/rest/translate/content/currentsite/<culture code>/document/<alias path>
• ~/rest/translate/content/site/<site code name>/<culture code>/document/<alias path>

Set the target language of the translation by adding the corresponding culture code into the targetlanguage URL parameter. The system automatically fills in the source language based on the language version of the specified page.

The request returns a response containing XLIFF data that you can use as the translation source. The REST service only supports retrieval of a single object per request.

Examples:

~/rest/translate/content/site/CorporateSite/en-us/document/Services?targetlanguage=fr-fr
~/rest/translate/content/currentsite/fr-fr/document/Company/Careers?targetlanguage=cs-cz

You can also use the following boolean parameters in the URL:

• TranslateDocCoupledData (true by default)
  If true, the returned translation source data includes the content of the page's coupled data fields (i.e. the fields of the specific page type). The service only exports fields that have the Translate field flag enabled in the page type's form definition.
• TranslateEditableItems (true by default)
  If true, the translation data includes the content of the page's editable regions.
• TranslateWebpartProperties (false by default)
  If true, the translation data includes the properties of web parts placed on the page. The service only exports the values of properties that have the Translate field flag enabled in the web part definition.
• TranslateAttachments (false by default)
  If true, the translation data includes the page's file attachments. Attachment translation must also be allowed in the website's settings.

See also: Configuring content for translation

Submitting completed translations

To import a translation into the system, send a POST request to the root URL of the REST translation service:

~/rest/translate/

Add the XLIFF content of the completed translation into the body of the request.

The root URL of the service is the only access point used for submitting translations. The system automatically identifies the target page based on the XLIFF data. When the system processes the request, it creates the appropriate language version of the page (if necessary) and inserts the translation data.