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

# Localization

## Introduction

Gum supports localization using CSV files. Gum projects with localization can be loaded and used in FlatRedBall projects. Since FlatRedBall supports its own localization, a wrapper class can be used to share the same localization with Gum at runtime.

For information on setting up localization in the Gum tool, see the Gum Localization docs: <https://docs.flatredball.com/gum/gum-tool/localization>

## Code Example - Sharing Localization

The following code shows how to share localization with Gum using the `LocalizationManagerWrapper` class:

```csharp
// The following code could be called after initializing FlatRedball:
private static void InitializeLocalization()
{
    // Set your language index in FlatRedBall
    LocalizationManager.CurrentLanguage = 4;
    // LocalizationManagerWrapper uses FlatRedBall's LocalizationManager
    CustomSetPropertyOnRenderable.LocalizationService = 
        new LocalizationManagerWrapper();
}

```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flatredball.com/flatredball/gum/localization.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.