> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/glpi-12/advanced-configuration/override-locales.md).

# Override GLPI locales

GLPI uses the [gettext](https://www.gnu.org/software/gettext/) tool to manage its translations. You can override the default. This is the preferred method rather than editing the original po files and risk losing your changes when updating GLPI.

To do so, you need to create a file named `filename.po` in the `files/_locales/core/` directory. You can also create overrides for plugins with the same method in `files/_locales/pluginkey/` directory where `pluginkey` matches the plugin folder name.

{% hint style="info" %}
Depending on your GLPI configuration, the `_locales` directory can be located elsewhere (if you provided a `local_define.php` file with a `GLPI_LOCAL_I18N_DIR` constant). It's possible to have multiple files, to manage several languages for example.
{% endhint %}

The file must be a valid `gettext` file. You can use [Poedit](https://poedit.net/) to create it.

```po
# Override PO file
#
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-04-13 10:43+0200\n"
"PO-Revision-Date: 2019-04-13 10:43+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
"Language: en_GB\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

msgid "Login"
msgstr "Login from local gettext"
```

`msgid` is the source string, `msgstr` is the translation. You can find the correct source sentences to use in the `locales/glpi.pot` file.

Next you need to compile your .po file into a .mo file readable by GLPI. To do so, you can use the following command:

```
$ cd files/_locales/core/
$ msgfmt -o filename.mo filename.po
```

Finally, GLPI uses a cache system to avoid loading MO files at each request. You need to clear the cache to see your changes. To do so, in Debug mode, go to "Setup > General", "Performance" tab and click on "Reset" button on the "Translation cache" section. If you have command-line access, you may also clear this cache using the `glpi:cache:clear` CLI command. If you clear the cache with the CLI command, make sure you run the command as the web server user.


---

# 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://help.glpi-project.org/glpi-12/advanced-configuration/override-locales.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.
