Move translations to some translation management system, so non-technical users can contribute, too

[ceskyDJ]

Hi guys, I noticed that @prem-k-r mentioned that we could use some translation management system for this project (#155 (comment)). I think it's an excellent idea as only technically experienced users can now contribute, so contributions don't grow so fast and don't have to be as good as they could be. I have experience from other projects that show that adding support for a translation system could really increase the number of localizations (e.g., a pretty small project https://github.com/lneugebauer/nextcloud-cookbook used to have about four translations for a long time before Weblate and now it's translated to 16 languages).

There are many options you can choose from. I have experience mainly with Crowdin, Weblate, and Tolgee. Tolgee is a system I have known for a very short time, but I've met some of their team members and discussed it with them. They have unique access to translation in contracts to Crawdin and Weblate. They focus on in-context translations (so the translator better knows what text is a subject of translation by seeing texts around it) and on the UX of the translation process (you literally can translate via writing down translations to the web application or browser extension, which is straightforward). Another bonus is that they have a public Slack for its community so that you can get help with anything effortlessly (https://tolg.ee/slack). As it sounds perfect, I'd give them a chance :).

If you don't want to use Tolgee, I'd recommend Weblate over Crowdin. Weblate is more accessible for a translator, and their system is better made, as I noticed while translating some projects.

[prem-k-r]

Great!
No need to do research now

[itz-rj-here]

Bruuhhh Don’t worry we already did our research on this we will add the crowdin thingy. But we will have problem with the number translation. Maybe @prem-k-r can give us some ideas on this. Also i was thinking about adding a code scanning tool like the codeql. Whats your opinion @prem-k-r? By this the codeql will check all the js codes in the pr and if it has some kind of issue we can remove it.

[prem-k-r]

Not really sure bro. I haven't actually used them, just heard about them. Go with whatever you guys think works best.

[itz-rj-here]

Not really sure bro. I haven't actually used them, just heard about them. Go with whatever you guys think works best.

Uhhh fine i will do that.

[itz-rj-here]

We need the help of @MestreWalla. As he introduced the translation. Also there are too low information about setting up the crowdin too. In the other hand, the languages are in one js file. It needed to be in different files with the name of the language code (2 words). Also we need @XengShi's help too. For creating a project on crowdin.

I will see about it later. For now im going byeeeee.

[prem-k-r]

How about Tolgee as first preference as @ceskyDJ suggested.

[itz-rj-here]

How about Tolgee as first preference as @ceskyDJ suggested.

Let me check then. But nowadays people like to use the crowdin for the translation system that's way.

[itz-rj-here]

How about Tolgee as first preference as @ceskyDJ suggested.

Well you look good actually. 🙂
We have a cool looking person on the repo. 🫠

[itz-rj-here]

Does the tolgee.io even works?

[itz-rj-here]

Well the Weblate UI doesn't looks good for me. I couldn't even understand what was what.

[prem-k-r]

Does the tolgee.io even works?

[itz-rj-here]

I think we should go with the Crowdin.

[itz-rj-here]

Does the tolgee.io even works?

Well thats interesting. Let me use VPN.

[itz-rj-here]

Well. In my ISP the tolgee.io not working but the app.tolgee.io is working thats odd.

[itz-rj-here]

Well yeah we can use the Tolgee. It's great.
Let me deep dive into it.

[itz-rj-here]

@XengShi Needs to set this up by his own. We can only maybe setup the system files for the repo.