ANNOUNCEMENT: Weblate as our main translation platform

[rafaelmardojai]

Hey translators!

We're moving to Weblate as our main translation platform to ease contribution!

We're also going to make the calls to update translations there, so make sure to add Dialect to your watched projects.

You can join here: https://hosted.weblate.org/engage/dialect/.

CC @Etamuk, @musicsd, @yarons, @meskobalazs, @cho2, @albanobattistella, @Vistaus, @JulianoSCbah, @xfgusta, @nexeleriot, @eson57, @noteqnil, @milotype, @pervoj.

[mufeedali]

I'm locking Weblate for now because we're making some changes to how the repository is organized, but we'll be back up soon. 😄 Sorry for any inconvenience caused

[mufeedali]

Weblate should be back up now. Translations have now been moved out to dialect-app/po.

[pervoj]

Can we still use file translation method?

[rafaelmardojai]

Can we still use file translation method?

That's what we want if someone wants to, but we're investigating if it causes issues on the Weblate side.

[pervoj]

Czech translation for now updated from Weblate, but GTranslator is still more comfortable in my opinion.

[yarons]

@pervoj It's pretty easy to download and upload files to Weblate, it's a little less cooperative but it's possible, if you want you can add a script with wlc (Weblate CLI Tool) to pull and push the file for you.

I've already suggested integrating the two:
https://gitlab.gnome.org/GNOME/gtranslator/-/issues/127

[mufeedali]

Can we still use file translation method?

@pervoj I've looked into this a bit more and from what I see, it's technically possible to update it from GitHub, unless someone edits it in Weblate at the same time, in which case, it will cause a merge conflict, causing Weblate to lock the repository and wait for us (repository owners) to fix the merge conflict. So it's very risky.

The best solution would be to use the Weblate client wlc from either pip or your package repository of choice.

[mufeedali]

The move to Weblate is now complete :)