Translation
In order for Mastodon to offer to translate a post into a different language:
- The author of the post must have marked the language
- The language of the post must be different than your language
- The translation engine must be able to process the given combonation.
ex: If a user posts content in Dutch, but the post is marked as being in English and your user interface is set to English, the Mastodon interface will not offer to translate the post.
Translation is done per-post only on-request by a user, as it would be computationally expensive to translate all posts that the server sees.
DeepL is used as the translation API for our main web interface and client API. It is known for its accuracy and ability to grasp nuances in language better than many other translation services. For a list of languages that DeepL is able to process, please refer to their documentation.
DeepL is free for limited use, but we pay for the professional plan which has additional data security standards that delete requests from their servers after they are translated.
The our translation API is also available to other client applications you may download to your devices. These clients may also offer additional translation services which are outside of our control; for example, Ivory will use Apple's on-device translation API first, but then use the server's API if an unsupported language is detected.
Third party web clients like Elk and Phanpy use different translation engines (LibreTranslate and Lingva) and may return different results.