---
title: Customizing XLIFF export for translations
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

By default, the XLIFF files exported by [translation services](https://docs.kentico.com/13/multilingual-websites/developing-custom-translation-services.md) use [CDATA](http://en.wikipedia.org/wiki/CDATA) notation. You disable CDATA in exported XLIFF files by adding the _CMSTranslationServicesUseCDATAForTransUnit_ key into your web.config file.

## Example of an XLIFF file with CDATA notation

```html

<xliff version="1.2">
  <file original="cms.document;25" source-language="en-US" target-language="fr-FR" datatype="htmlbody">
    <body>
    ...

      <trans-unit id="newstitle">
        <source><![CDATA[Apple iPad Mini In Stock]]></source>
      </trans-unit>
      <trans-unit id="newssummary">
        <source><![CDATA[Today, we have good news for all fans of the awesome Apple iPad. We are glad to announce that its new version, Apple iPad Mini, is available in our web shop. Furthermore, we keep our reasonable pricing policy, providing the lowest price currently available on the Web.]]></source>
      </trans-unit>

    ...
    </body>
  </file>
</xliff>

```

> **Info:** The CDATA section permits the special characters such as '_&_', '__', etc. to be included in the text without being escaped. If you [disable CDATA](#disabling-cdata-in-exported-xliff-files) via the _CMSTranslationServicesUseCDATAForTransUnit_ web.configkey, special characters in the exported XLIFF files will automatically be escaped.
>
> For example:&#x20;_&#x20;Text to be translated&#x20;_&#x20;becomes _\&lt;p\&gt; Text to be translated \&lt;/p\&gt;_
>
> For more information, see the [XLIFF documentation](http://docs.oasis-open.org/xliff/v1.2/xliff-profile-html/xliff-profile-html-1.2-cd02.html)[.](http://docs.oasis-open.org/xliff/v1.2/xliff-profile-html/xliff-profile-html-1.2-cd02.html)

## Disabling CDATA in exported XLIFF files

1. Edit your Xperience administration project's **web.config** file.
2. Add the _CMSTranslationServicesUseCDATAForTransUnit_ key into the __ section of the file.

   ```html

   <appSettings>
     ...

     <add key="CMSTranslationServicesUseCDATAForTransUnit" value="false" />

     ...
   </appSettings>

   ```
3. Save the web.config file.

Now, whenever you [submit a document for translation](https://docs.kentico.com/13/multilingual-websites/translating-content-using-external-services.md), the system exports it without the CDATA notation.

## Example of an XLIFF file without CDATA notation

```xml

<xliff version="1.2">
  <file original="cms.document;25" source-language="en-US" target-language="fr-FR" datatype="htmlbody">
    <body>
    ...

      <trans-unit id="newstitle">
        <source>Apple iPad Mini In Stock</source>
      </trans-unit>
      <trans-unit id="newssummary">
        <source>Today, we have good news for all fans of the awesome Apple iPad. We are glad to announce that its new version, Apple iPad Mini, is available in our web shop. Furthermore, we keep our reasonable pricing policy, providing the lowest price currently available on the Web.</source>
      </trans-unit>

    ...
    </body>
  </file>
</xliff>

```
