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

# Localization

These features are supported in the release 4.2 (or newer)

## How to add support for a new language <a href="#how-to-add-support-for-a-new-language" id="how-to-add-support-for-a-new-language"></a>

VitaraCharts editors are accessible in English, German, French, and Spanish out of the box. It is possible to add support for new local languages on your own. The steps are as follows:

* Create a file MessageBundle\_\<languagecode>\_\<regioncode>.txt in directory /VitaraCharts/custom/

  ```
  Example: For “fr-fr” as user language, 
  file name should be: MessageBundle_fr_fr.txt
  ```
* Copy the content from file VitaraCharts/custom/MessageBundle\_en\_us.txt in newly created file (MessageBundle\_\<languagecode>\_\<regioncode>.txt)
* Add the respective translation for English string separated by “=” operator

  ```
  Format: \<English_String\>=\<Translated_String\>
  Example: Cell=Zelle
  ```

## Preference Order for how lanugage resources are loaded <a href="#preference-order-for-how-lanugage-resources-are-loaded" id="preference-order-for-how-lanugage-resources-are-loaded"></a>

* Language with regional Code (MessageBundle\_fr\_fr.txt )
* Language Only (MessageBundle\_fr.txt )
* Default (MessageBundle\_en\_us.txt)

**NOTE** : If the translation for some keys are missing in the file then those keys will be displayed in English Language in the Property Editor

**Enhancemen**t: Starting from version 5.3.6, a new tool called the Customization Tool has been introduced. This tool allows users to easily edit configuration files such as global.txt and customStyles.css through a user-friendly interface.\
For more details,[ click here](/customization-guide/customization-tool.md).


---

# 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.vitaracharts.com/customization-guide/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.