Consider migrating from Crowdin to Weblate

I am new here, and I am considering participating in translating Privacy Guides. However, I found that Crowdin is used for translations, and Git merge requests to i18n are rejected. I’m not comfortable with using Crowdin, therefore I don’t think I will contribute as a translator while Crowdin is used.

Crowdin is a proprietary, software as a service (SaaS) translation service, in some ways similar to Transifex. Crowdin collects vast personal information from everyone who interacts with its website, heavily tracks visitors including project contributors (with cookies, analytics and other means), and shares information with many third parties. Furthermore, Crowdin’s website frequently blocks Tor users. I believe these would most likely in opposition to what Privacy Guides believes in.

Assuming Crowdin account holders generally can contribute translations to Privacy Guides, I’d also guess that Privacy Guides receives translations from people who have no knowledge of Privacy Guides or privacy.

If Crowdin decides to close down or remove Privacy Guides’s project/access, Privacy Guides may lose translation work (although copied to GitHub) or the tooling required to work on translations.

I suggest migrating from Crowdin to Weblate. Weblate is FOSS (free and open source), and it is both self-hostable and hosts projects at

Maybe Privacy Guides can get a project at as a first step, and then set up self-hosting when there is enough time and resources to do so?

I don’t know about the workflows of Privacy Guides’ translations, Crowdin and Weblate. I also don’t know Privacy Guides’ reasons for choosing Crowdin. Also, I understand that a migration would require significant effort, so I can only make a suggestion. However, I hope it will be given consideration.

As far as I’m aware, Weblate doesn’t do markdown document translations.

Markdown support was added to Weblate 5.0; the relevant GitHub issue is WeblateOrg/weblate/3106 (I couldn’t add the link because of my newbie status). However, their documentation states that Markdown support is under development.

Support for this format is under development.
Some features might not yet be available and
the behavior can change between releases.
Feedback from testing is welcome.


Unlike most other formats, the changes in the
translation files will not be imported to
Weblate because it can not be done reliably.
The source of truth for the translations is
Weblate not the translated file.

Not having looked into the issue in any detail, I don’t know what it means for translation of Privacy Guides. However, ability to use Weblate in the near future appears promising.

Prior to Weblate’s Markdown support, other projects have used po4a or md2po. Before adding Markdown support, Weblate recommended po4a.

1 Like