> For the complete documentation index, see [llms.txt](https://docs.prestashop-project.org/translating-prestashop/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prestashop-project.org/translating-prestashop/translating-prestashop-software-basics/translating-on-crowdin/the-dos-and-donts-of-crowdin-translation.md).

# The Do's & Don'ts of Crowdin Translation

## ❌ Don't t**ranslate variables:**

Variables are values that can change depending on their context in the program. They are highlighted in <mark style="color:green;">green</mark> and must **not be translated** as they can result in software bugs, for example.

On Crowdin, you can simply click on a variable to copy and paste it into the target language. Make sure to copy and paste the variable exactly as displayed on the original string.

❌ Don't:

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

✅ Do:

<figure><img src="/files/9okQvKbOav9uqwlUASw5" alt=""><figcaption></figcaption></figure>

## ✅ Use the comments and issue features:

If you don't understand a string and need more context, you can **use the comments section to ask for help**. As this section is visible to every other language in the project, every translator will be able to help you.

### Asking for more context:

You can use the comments section to ask for more context on a string that might seem vague or if you're not sure if the string should be translated or not.

<figure><img src="/files/4XBJjHdMWoLo76bvzzlV" alt=""><figcaption></figcaption></figure>

Note that you can also check out the [translation domains](/translating-prestashop/resources/resources/useful-websites.md#translation-domains) page to understand where a string is located in the software.

### Requesting the help of a proofreader

[Proofreaders](/translating-prestashop/translating-prestashop-software-basics/translating-on-crowdin/proofreading-all-you-need-to-know.md) ensure the quality of translations. If you wish to improve pre-existing translations, you can do so by requesting their approval.

<figure><img src="/files/4pm8tCLKFvUBzLifujyM" alt=""><figcaption></figcaption></figure>

### Reporting a typo

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

Sometimes, a source string can contain a typo or misspelled word. Simply open an issue on the relevant string by checking the **"issue"** checkbox and the project managers will have a look at your issue.

<figure><img src="/files/wOt5na4iWdjg47Rgo1sk" 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.prestashop-project.org/translating-prestashop/translating-prestashop-software-basics/translating-on-crowdin/the-dos-and-donts-of-crowdin-translation.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.