> For the complete documentation index, see [llms.txt](https://docs.hudson-ai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hudson-ai.com/dubbing-studio-guide-jp/ex/actors-and-dictionary/translation-dictionary.md).

# Translation Dictionary

### #1 Creating a Translation Dictionary

<div><figure><img src="/files/1EjrPek3Zw9u4ZCYPAyz" alt=""><figcaption></figcaption></figure> <figure><img src="/files/FvJPmIDw51ZTEBKKulS7" alt=""><figcaption></figcaption></figure></div>

* To create your own custom Translation Dictionary, click “Create Dictionary” in the sidebar. Choose your source language and target language, then give your dictionary a name.

***

### #2 Managing Dictionary Terms

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

* You can organize your terms into categories like:
  * People
  * Organizations
  * Places
  * Phrases
  * Other
* This lets you define exactly how specific words or names should be translated in your content.

> Example:
>
> If you're working on *Hong Gil-dong* and want “Gil-dong” to always be translated as “John,”\
> add that rule to your dictionary.\
> Now, every time you use this dictionary in an English dubbing project, “Gil-dong” will become “John” consistently.

* Want to support more than one target language? You can create **multilingual dictionaries** by selecting multiple output languages.

***

### #3 Using a Translation Dictionary

<figure><img src="/files/Xhq7EIagVwbBh3GIhy2B" alt="" width="375"><figcaption></figcaption></figure>

* You can select a dictionary when creating a new project.

{% hint style="warning" %}
**(After the project is created, you won’t be able to add or change the dictionary.)**

Only dictionaries that match the project’s source and target languages will be shown in the list.
{% 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://docs.hudson-ai.com/dubbing-studio-guide-jp/ex/actors-and-dictionary/translation-dictionary.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.
