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

# Language Support

This theme is fully translatable to any language. The theme utilizes the {{t}} translate helper for all labels and messages. 

Out of the box, it supports 15 languages, which are:

1. Czech (cs)
2. German (de)
3. English (en)
4. Spanish (es)
5. French (fr)
6. Hindi (hi)
7. Hungarian (hu)
8. Italian (it)
9. Japanese (ja)
10. Dutch (nl)
11. Polish (pl)
12. Portuguese (pt)
13. Russian (ru)
14. Turkish (tr)
15. Chinese (zh)

You can add your language (if not already supported) by creating a locales file under the 'locales' folder in the theme.

<figure><img src="/files/RfyjfciZTbEWEamtpRBp" alt=""><figcaption></figcaption></figure>

To create the locales json file, use the ISO Language code of the new language you want to add. For e.g. for Portuguese, it will be 'pt.json'.

In 'pt.json' add the translations in key:value pair. For e.g. if we want to translate 'Sign In' to Portuguese, then the content in 'pt.json' locales file would be:

```json
{
    "Sign In":"Entrar"
}
```

Similarly, you can add all the translations for multiple labels.&#x20;

Once you create the complete locales JSON file, change your publication language in Settings > General > Publication Language and enter the ISO language code (e.g. 'pt') instead of the default 'en' for English language.

<figure><img src="/files/VCLWOJTltuZrPt7IjYf3" alt=""><figcaption></figcaption></figure>


---

# 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.themeupstudio.com/orchid/internationalization/language-support.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.