This file has been truncated. show original
# Translation Guidelines
The Rust website can be translated into multiple languages using [fluent](https://github.com/projectfluent) and on our own [pontoon instance](https://pontoon.rust-lang.org). Note that these features are currently in development.
## What can be translated
All text on the website can be translated. Some texts, especially policies, can be translated, but the English version will be the binding one.
## Forming a translation team
Translation teams for any language need at least _three_ members. This is to avoid translations to "drop out" of support too quickly. If you feel like having a team, please get in touch with the [community team](mailto:email@example.com) to apply for a translation. Have all team members register at the [pontoon](https://pontoon.rust-lang.org) and send us their email addresses. We'll make sure to get you set up as managers. Managers can manage their translation teams through the "permission" tab in the web interface, including appointing new managers.
Please note that as a manager, you work on the representation of the Rust project in your locale. Make sure to understand and act with that responsibility and only promote well-trusted people to a manager role.
Teams ideally consist only of native speakers. Even within one language it can be useful to have editors from multiple backgrounds, to find a consistent language. For translators, strong writing skills matter. For reviewing, a keen eye and a good feeling for oddities is important.
Any language that can muster a constantly working and up to date translation is qualified.
## How to get your translation published