> For the complete documentation index, see [llms.txt](https://learn.mechanic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mechanic.dev/faq/can-task-content-be-translated-into-multiple-languages.md).

# Can task content be translated into multiple languages?

Translate Mechanic task content by using separate task copies per locale or custom task options for locale-specific content.

The tasks in [Mechanic's library](/resources/task-library.md) don't generally include provisions for content translations/localizations – this can be a relevant concern for customer-facing messaging, like email.

To handle translations, some merchants install multiple copies of a task, and tune the options of each task to address specific locales, with locale-specific content.

In other cases, task code can be customized to allow for specifying multiple translations within a single task, switching between them as appropriate. (Typically, this means adding a [keyval option](/core/tasks/options.md#3-flags) allowing the user to specify and identify content as needed.)

{% hint style="info" %}
New to task customization? Start here: [I need something custom!](/custom.md)
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.mechanic.dev/faq/can-task-content-be-translated-into-multiple-languages.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.