dtdocs - translations are up again :-) !

Hey guys,

I am happy to report that the translations for darktables docs can be maintained again!

Following @martinus hint we were able to register with weblates own hosting in their “libre” tier, which they offer for open source projects.

The translations are in need of some love:

If you want to help out I recommend checking out the translators guide and if you are interested in the general setup of the translations take a look here.

In order to submit translations you have to register with weblate. If you are not registered you can still submit suggestions for registered contributors to accept.

Note: I wrote the translators guide based on my own limited exploration of weblate while setting things up. If you get into translating and feel the guide is lacking please send me a message or open an issue on the dtdocs repository.

@Popanz @manu @kasiura have at it if you want :wink: .

18 Likes

Thank you for your work, great initiative :slight_smile:

2 Likes

Congrats to all involved, this is a very nice achievement !

2 Likes

Hi all, on the road at the moment, back in 3 weeks. I’ll take a look at it then. Thanks for the job done @mino !

2 Likes

I’ll have a look at it next week.

That’s great, we have a race to win against @victoryforce :wink: .

1 Like

I’ve already converted your AgX translation, I’m sorry for having slept on it so long. On the weekend, I’ll get in touch with @mino to get it integrated.

2 Likes

Hi! I started the French translations, anf like everybody else I had to sign in Weblate.

Almost every time I have to give an email address, I use a specific catch-all address. This helps me to identify from where any unattended mail is delivered to me.

Yesterday I received on this catch-all address a mail from “Neon Adventure Lab hello@neoninnovationlab.com” trying to sell me something.

This is spam :rage: and as far as I know I never granted weblate to give my email address to anyone else.

If anyone knows how to prevent further spams on addresses provided to weblate when signing up, please share with us. :pray:

Bad bad point for weblate.

Hey @manu. Thanks for helping with the translations :-). I saw you were busy when I merged the PR yesterday.

Your spam issue could possibly also stem from the commit messages generated for pushing to github. They include the users email addess. I will look into how I can add a notice of this fact for new users helping with the translations.

I think it is highly unlikely that weblate is actually selling your data.

2 Likes

Ok, you may be right, and I often wonder why free software keep relying on github.
But let’s stick here to the topic, i.e. dt doc translation ! :laughing:

1 Like

We now have Laoan translations thanks to a github user named bounkirdni-2025.

3 Likes

Weblate answered after I asked about this situation:

You can view all our security advisories on our GitHub repository here: Security Advisories · WeblateOrg/weblate · GitHub.
The situation you are describing is likely caused by a combination of individual accounts’ settings and the fact that Git publishes contributors’ email addresses with commits. The exposed addresses can then be unfortunately easily retrieved. Weblate provides the option to hide the email address, you can access your individual settings on this link: Registration and user profile - Weblate 2026.8 documentation.
We are in no way affiliated with Neon Innovation Lab and we never shared any data with them.

@popanz @victoryforce @Ulrich_from_Germany maybe also take a look at this setting (direct link to the settings page).

1 Like

I usually use different mail addresses for different services. Many of them are just temporary addresses. Since I registered on Weblate, I didn’t get any Spam. If it starts to spam me, I will whitelist Weblate and block all other incoming mails.

1 Like

Thanks @mino for asking Weblate! I changed to private email.

Yes @Popanz it’s one of the purposes of the catch-all email addresses.

I often use what@mydomain, for instance weblate@mydomain.
So when I receive a mail sent to this email address (which is redirected to a real mailbox), and it’s not coming from weblate.org (in this example), I know where the “leak” is coming from. :blush:

And then I can black/white list the sender, according to what I really need to receive.