---
title: "Update the XLIFF language file with translated content"
slug: "update-the-xliff-language-file-with-translated-content"
updated: 2025-03-03T06:18:25Z
published: 2025-03-03T06:18:25Z
canonical: "support.whatfix.com/update-the-xliff-language-file-with-translated-content"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.whatfix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Update the XLIFF language file with the translated content

Whatfix’s XLIFF language file has a fixed structure representing your content and its details. While it's useful to grasp the general XLIFF file structure and the structure of Whatfix's language file, translators need not be concerned about the complete file structure. To update the language file correctly:

1. Identify the text inside the **source** tags.
2. Insert the translation of that text within the corresponding **target** tag.

However, if you're interested in learning about the basics of the XLIFF file format or the structure of Whatfix's XLIFF language file, see the following information:

Understand the XLIFF format

An XLIFF file comprises **tags** and **attributes**. Tags structure the file, while attributes provide additional information to a specific tag.

Tags are enclosed within **angle brackets** (‘<’, ‘>’). Tags come in pairs, with each tag having an **opening tag** and a **closing tag**.

The following is an example of a pair of **unit** tags:

```
<unit></unit>
```

Here, **unit** is the opening tag, and **/unit** is the closing tag.

Tags located between another opening and closing tag are considered to be nested inside that tag. Here's an example of a **segment** tag nested within a **unit** tag:

```
<unit>
	<segment>
	</segment>
</unit>
```

Attributes of a tag are specified within its opening tag and are assigned a value. Here's an example of a **unit** tag with the **name** attribute having the value "My unit’s name":

```
<unit name="My unit's name">
	<segment>
	</segment>
</unit>
```

Understand Whatfix’s XLIFF language file

The XLIFF language file includes 4 main tags, each representing different parts of Whatfix content.

```
<file id="whatfix_translation">
    <group id="whatfix">
      <unit id="content_id" name="content_name" type="content_type">
        <segment id="field_id">
          <source>Text in the default language</source>
          <target></target>
        </segment>
        
        ...
        
      </unit>
    </group>
  </file>
```

- A **unit** tag represents a single piece of Whatfix content and contains the following attributes:
  - **id**: The ID of the field.
  - **name**: The name of your content.
  - **type**: The content type of your Whatfix content.
- Nested within a unit tag are **segment** tags, representing different **fields** of the content specified in the unit tag. For instance, a Flow contains a title field and fields for its individual steps. These tags include the following attributes:
  - **id**: The ID of the field.
- Each segment tag comprises a **source** and a **target** tag.
  - Within the source tag, you'll find the text of the field specified in the segment. This text is in the default language of your Dashboard.
  - The target tag is left empty for the translator to enter the translation of the text inside the source tag before it.

 

## Translate the content in the XLIFF language file

Use the following steps to update the XLIFF language file:

          Note:

          

Ensure to [download the XLIFF language file](/studio/docs/download-xliff-language-file) from the Dashboard first.

1. Unzip the [downloaded folder](/studio/docs/download-xliff-language-file) and open the extracted folder.
2. Depending on your requirements, open either the **Full.xlf** file containing all content or the **Delta.xlf** file with only [outdated content](/studio/docs/what-does-out-of-date-mean).
3. Update each **target** tag with the translation of the text within the preceding **source** tag.  

![xliff_code.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/xliff_code.png)
4. Save the language file.

Once you've made the necessary updates to the language file, remember to [upload it on the Dashboard](/studio/docs/upload-the-xliff-language-file-on-the-dashboard). This ensures that the translations take effect on the Dashboard.