# Manual Translation

Manual TranslationThere are four methods you can use to translate a single message or a block of text:

* use the `Translate this message` shortcut to translate any message.
* &#x20;use the `Translate text` global shortcut to translate any text in any language, and then (optionally) post it to a channel.
* use a form to translate text (very similar to the method above).
* use the `/translate` slash command to to translate any text in any language, and then (optionally) post it to a channel.

For each of the above methods, translations are (initially) shown only to the user requesting the translation.

See below for more info about each method.

{% content-ref url="/pages/w9IFoMiJLxYbqStkvQ0K" %}
[Slash Command](/features/manual-translation/slash-command.md)
{% endcontent-ref %}

{% content-ref url="/pages/5Yzoi8E3ES3r3IIpe4y9" %}
[Translate Text Shortcut](/features/manual-translation/translate-text-shortcut.md)
{% endcontent-ref %}

{% content-ref url="/pages/yuDG1LCSZps9XkLMT3j3" %}
[Translate this Message](/features/manual-translation/translate-this-message.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://docs.translate.technology/features/manual-translation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
