# General Translation Integrations: Locales
URL: https://generaltranslation.com/en-US/docs/integrations/google-drive/reference/locales.mdx
Docs index: https://generaltranslation.com/llms.txt
Description: Set the source language of each linked Drive file and choose the languages it is translated into. Reference for Google Drive locale handling.

Each linked file carries its own source language, and the integration creates one translated Drive copy per target language. Files with different source languages are translated in separate batches.

## Overview [#overview]

| Setting | Description | Optional | Default |
| --- | --- | --- | --- |
| [Source language](#source) | The language of a linked file, set per file in the **Source** column. | No | Your current Dashboard language |
| [Target languages](#targets) | The languages chosen under **Translate into**. | No | — |

## Source language [#source]

**Required** · **Default** your current Dashboard language

When you link a file, the integration stamps it with the language the Dashboard is currently displayed in — not the project's default locale. Two teammates browsing the Dashboard in different languages will therefore link the same file with different source languages.

Because of that, always check the **Source** column after adding files. Every row has its own **Source** dropdown, so you can correct a file's source language in place; there is no need to change any project setting. The dropdown lists your current Dashboard language first, then the project default, then the project's target locales, then the remaining supported locales.

Getting this right matters because the Dashboard checks each target language against the file's source language and the source language decides the language used in [translated copy names](/docs/integrations/google-drive/guides/using-translated-content#names).

When the selected files do not all share one source language, the Dashboard starts a separate translation batch for each source language.

## Target languages [#targets]

**Required**

The **Translate into** menu offers the project's configured locales. A locale that conflicts with a selected file's source language stays listed, so the Dashboard can report which file causes the conflict instead of silently skipping it.

Before starting any files, the Dashboard rejects a target that it cannot distinguish from a selected file's source language:

- An exact match, such as `en-GB` to `en-GB`.
- A base locale and one of its regional or script variants, such as `en` to `en-GB` or `zh` to `zh-Hant`.
- A regional or script variant and its base locale, such as `en-US` to `en` or `zh-Hans` to `zh`.

To resolve a conflict, deselect the target or change the file's **Source**. When the source is a base locale such as `en`, choose a more specific source before translating into a regional variant. To translate between variants of one language, use two codes that differ in region or script, such as `en-US` to `en-GB` or `zh-Hans` to `zh-Hant`.

At least one target language is required. When no target language is selected, the primary action reads **Select locales** and opens the locale menu instead of starting a translation; add locales there from the [supported locales](/docs/platform/dashboard/reference/supported-locales) without leaving the integration.

When a linked file already has translations, the languages already used on the integration are preselected.

## Next steps

- /docs/integrations/google-drive/guides/configuring-google-drive
- /docs/integrations/google-drive/guides/translating-content
- /docs/integrations/google-drive/guides/managing-translations

## Sitemap

See the full [sitemap](https://generaltranslation.com/sitemap.md) for all pages.