> For the complete documentation index, see [llms.txt](https://syrows-development.gitbook.io/craftventory/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://syrows-development.gitbook.io/craftventory/advanced-concepts/i18n.md).

# I18n

This page describes how to support text internationalization (i18n).

The `I18n` interface was developed as a **bridge** between CraftVentory and any internationalization library. It consists in a single method whose goal is to retrieve a text using a **key** and the **player** who requests it.

```java
public interface I18n {

    String getText(Player player, String key);
}
```

To support text internationalization, the first step is to create a class that implements this interface and that does the mapping with an internationalization library. Then, the created class can be used in inventory descriptors by redefining the `getI18n()` method and everything should be automatically translated.

{% hint style="info" %}
CraftVentory is not an internationalization library. It only provides a bridge to be mapped with one.
{% endhint %}


---

# 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://syrows-development.gitbook.io/craftventory/advanced-concepts/i18n.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.