# Language (Locale) mismatch between endpoints

### Case 1: Source and destination have different locales

Assume you have different locales between your source and destination endpoints. For example, see the following:

| Source Language Code | Destination Language Code |
| -------------------- | ------------------------- |
| en-US                | EN-AMERICAS               |
| gsw-CH               | de-CH                     |

This is a very common scenario when syncing content between systems. In this case, the content is the same, but the locale is different.

#### Solution

ImpulseSync can solve this by using the [language manipulator](https://motivlabs.gitbook.io/impulse-user-manual/content-manipulators-motators/language). The language manipulator can be used to change the language code of a content item. In this case, we can use the language manipulator to change the language code of the source content to match the destination language code.

**Step 1: Add the language manipulator to the job**

The content type will be `voyage` and the `language pairs` will be `en-US` to `EN-AMERICAS` and `gsw-CH` to `de-CH`.

![](https://651785290-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnLYwCtfZtrK4s43AVzb4%2Fuploads%2Fgit-blob-1176d51ec2bb08176699e7c3e3c9fb021c044c53%2Frecipe-language-mismatch-01.png?alt=media)