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

# Dictionary

Dictionary lets you control how specific words are handled in translations — either locking them so they’re never translated, or defining exactly how they should appear in each language. Use it for company names, product names, or industry-specific terms that AI might otherwise translate inconsistently.

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/qkq9g07u1r>" %}

### How to use the Dictionary:

* Go to Settings > Dictionary
* Click Add term and type it in
* To lock the term, save it as is — it will stay the same in every language
* To translate it your way, toggle on the translation option, pick a language, and type in the term as it should appear in each language
* Repeat for as many languages as you need, then save

<details>

<summary>Supported languages (33)</summary>

* 🇸🇦 Arabic
* 🇧🇬 Bulgarian
* 🇪🇸 Catalan
* 🇨🇿 Czech
* 🇩🇰 Danish
* 🇩🇪 German
* 🇬🇷 Greek
* 🇺🇸 English
* 🇪🇸 Spanish
* 🇫🇮 Finnish
* 🇵🇭 Filipino
* 🇫🇷 French
* 🇮🇳 Hindi
* 🇭🇷 Croatian
* 🇮🇩 Indonesian
* 🇮🇹 Italian
* 🇯🇵 Japanese
* 🇰🇷 Korean
* 🇲🇾 Malay
* 🇳🇱 Dutch
* 🇳🇴 Norwegian
* 🇵🇱 Polish
* 🇵🇹 Portuguese
* 🇧🇷 Portuguese (Brazil)
* 🇷🇴 Romanian
* 🇷🇺 Russian
* 🇸🇰 Slovak
* 🇸🇪 Swedish
* 🇮🇳 Tamil
* 🇹🇷 Turkish
* 🇺🇦 Ukrainian
* 🇨🇳 Chinese (Simplified)
* 🇹🇼 Chinese (Traditional)

</details>


---

# 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.guideflow.com/help/ai/dictionary.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.
