> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba-metadata-editor/manage-international-locales-pentaho-metadata-editor.md).

# Manage international locales

Pentaho Metadata Editor supports multiple locale entries for any text or string-based metadata property. You must first specify the locales you want to include in your model by using the **Locales Editor**.

Perform the following steps to set up locales:

1. In the Pentaho Metadata Editor, go to **Tools** > **Locales Editor**.
2. Place your cursor in the first column of the first empty row in the **Locales Editor** main table, as shown in the following example:

   ![Locales tab, Pentaho Metadata Editor](/files/DfENVlfbcPDkWIivFkVA)
3. Type the [Java Locale code](https://docs.oracle.com/javase/8/docs/api/java/util/Locale.html) of the language you want to add in the next column.
4. Specify the order in which you want this locale to be used.

   In the example above, `English (American)` is designated as the first language (**Order** = `1`).
5. Type a **Y** in the last column to activate the locale, or an **N** to de-activate it.
6. Click **Apply Changes** when you are done.


---

# 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.pentaho.com/pba-metadata-editor/manage-international-locales-pentaho-metadata-editor.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.