> For the complete documentation index, see [llms.txt](https://docs.santacruzsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.santacruzsoftware.com/bannersui/guides/localization.md).

# Localization

Choose source and target locales, review translations, and resolve layout issues.

The editor can localize package or job text content when the translation workflow is enabled.

### Localization review checklist

| Check                     | Reason                                                 |
| ------------------------- | ------------------------------------------------------ |
| Source and target locales | Ensures the correct language direction.                |
| Translated text           | Confirms copy quality before output.                   |
| Text fit                  | Different languages can change length and line breaks. |
| Fonts                     | Localized text may require different glyph support.    |

### Open localization

Choose the localization option while editing a package or customizing a job. 

The dialog lets you choose a source locale and target locale.

### Translate text content

1. Choose the source locale.
2. Choose the target locale.
3. Start localization.
4. Review translated layer text.
5. Update translations when the source content changes or when you need to refresh target-language copy.

### Review localized output

After localization, inspect every artboard.

Different languages can change text length, line breaks, and font requirements. Check for:

* Overset text.
* Missing fonts.
* Broken line breaks.
* Text that no longer fits the intended visual hierarchy.
* Links or URLs that should be locale-specific.

Use text fitting, frame resizing, or localized copy edits to resolve layout issues before publishing or finishing the job.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.santacruzsoftware.com/bannersui/guides/localization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.