# General Translation Integrations: Using translated content
URL: https://generaltranslation.com/en-US/docs/integrations/google-drive/guides/using-translated-content.mdx
---

title: Using translated content
description: How to find, review, and share the Google Drive copies the integration creates for each language.
related:
  links:
    - /docs/integrations/google-drive/guides/configuring-google-drive
    - /docs/integrations/google-drive/guides/translating-content
    - /docs/integrations/google-drive/guides/managing-translations

---

Every translation produces an ordinary Google Doc or Google Slides file, so you review, comment on, share, and publish it with the tools your team already uses. This guide covers where those copies live and what to check before you send one out.

## Find a translated copy [#find]

Open **Project > Integrations > Connected** and select the Google Drive integration. Once a language finishes, open its copy from the progress view, or find it in Google Drive next to the source file — the integration creates each copy in the source file's folder.

## How copies are named [#names]

A copy takes the source file's name followed by the **name of the target language, written in the source file's language**:

```text
<source file name> [<target language>]
```

An English deck named `Launch deck` translated into French becomes `Launch deck [French]`. The same French copy of a *Spanish* source is named `Launch deck [francés]`, and a German copy of that Spanish source is `Launch deck [alemán]`. If the language name cannot be resolved, the integration falls back to the target locale code.

Because the label is written in the source language, changing a file's [source language](/docs/integrations/google-drive/reference/locales#source) changes the label the integration uses for its copies.

<Callout type="info">
  A bracket holding a raw locale code, such as `Launch deck [fr]`, is the legacy naming form. The integration still recognizes it so existing copies keep being reused, but it does not create new copies that way.
</Callout>

## Review before you share [#review]

The integration writes the translation into the copy and leaves the source untouched, so review the copy rather than the original.

For Google Slides, translated text is usually longer or shorter than the original, so the integration runs a formatting pass to fit the new text to each slide. While that pass is editing the deck, the copy is renamed `<source file name> [<target language>, DRAFT]`. A successful pass restores the plain name.

<Callout type="warn">
  **A copy still marked `DRAFT` is not a finished translation.** If the formatting pass leaves the deck recolored, the integration deliberately keeps the `DRAFT` marker and fails the job, so a damaged copy is never presented as complete. Retrying the run usually recovers it. Do not share a deck whose name still ends in `, DRAFT]`.
</Callout>

Once the pass finishes, check slides where text now overflows or wraps differently.

## Keep editing after translation [#edits]

You can edit a translated copy directly. Later **Apply changes** runs update that same file and reuse translations whose source has not changed, so your edits are preserved where the source text still matches.

<Callout type="warn">
  **Force retranslation** replaces the translated text *and any layout changes* in the copy, including edits you made by hand. Use it only when you want to start over. See [Managing translations](/docs/integrations/google-drive/guides/managing-translations#force).
</Callout>

## Next steps

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