[Request] Can add it to the online translation platforms?（可以添加到线翻译平台吗？） about obtainium

[ngocanhtve]

@Daviteusz I localized using a pull request, I feel more comfortable using a web service like weblate or crowdin.

[ImranR98]

Would there need to be changes to Obtainium's code to integrate with these services? Or would the translations made on these platforms end up being submitted as PRs to the existing assets/translations/ folder?

[ImranR98]

I see someone is already using Weblate for PRs: #713
Not sure if that is what you had in mind. I'm not familiar with Weblate.

[ygxbnet]

Would there need to be changes to Obtainium's code to integrate with these services? Or would the translations made on these platforms end up being submitted as PRs to the existing assets/translations/ folder?

I'm at Crowdin. No need to change the code.

[ImranR98]

Great, any PRs to add or update translations are welcome. I guess it wouldn't matter from the point of view of this repo where the PR comes from or what tools were used to make it.

[ygxbnet]

But I hope we can have a unified platform so that all translations for other languages can be done on it, making collaboration easier.

[ygxbnet]

And it can also allow more people to participate in the translation work.

[ImranR98]

Makes sense. I'm guessing you'd run the Weblate or Crowdin page that others would then contribute to? Also, if any changes are made to the translations via other means (direct PRs) would those still be fine?

[ygxbnet]

Yes, submitting PRs directly is still possible.

But because I don't have direct commit and branch creation permissions for the repository, it's challenging to set up a service that everyone can use. That's also the reason I submitted this issue.

[ImranR98]

Okay, I might have to take a look at these tools to understand more about how they work.

[ygxbnet]

Thanks!

Here are some simple differences:

Weblate does seem relatively simple to use, but if you're using the official hosting, each user can only create one translation project. Additionally, since it's open source, you can also set up your own instance if needed.

Crowdin does indeed offer more comprehensive features and allows one user to add multiple projects, but it's closed source. It's essential to consider the trade-offs between open-source and closed-source solutions based on your specific needs and preferences.

The differences between Weblate and Crowdin are as follows:

1. Open Source vs. Commercial:

   • Weblate is open source, meaning you can host and customize it freely. This can be more attractive for those who require more control or are cost-conscious.
   • Crowdin is a commercial platform offering cloud hosting services. It is typically more suitable for businesses and teams, providing a range of advanced features and support.

2. Pricing:

   • The open-source version of Weblate is free, but you need to host and maintain it yourself. They also offer paid hosting plans.
   • Crowdin has paid plans with pricing that varies based on project needs and the number of users.

3. User Interface and Features:

   • Both Weblate and Crowdin provide user-friendly interfaces for translation teams to collaborate effectively.
   • Crowdin tends to be more powerful in certain advanced features, such as automated translation and integrations. However, Weblate's open-source nature allows for custom development as needed.

4. Integrations:

   • Crowdin offers a wide range of integration options, allowing seamless integration with various project management tools and version control systems to better fit into your development workflow.
   • Weblate also has integration options but may require more manual configuration.

Ultimately, the choice between these platforms depends on your project requirements, budget, and technical capabilities. If you need more control and don't mind self-hosting, Weblate might be a good choice. If you require more advanced features, professional support, and cloud hosting, Crowdin may better suit your needs.

[Daviteusz]

@ImranR98 @ygxbnet I use Weblate, but there is a problem with plurals, because easy_localization forces to use the other key.

• #810 (comment)

Weblate only uses one few many keys e.g for Polish and for some other languages.
I'm forced to use this script to add missing other key after every push:

• https://gist.github.com/Daviteusz/c52946094c9ef97641dcc7ff7dbad21a

So integrating Weblate currently is not a good idea. I don't know about Crowdin, if it also does not include the other key for Polish, then the situation will be similar.

Example after pushung out changes from Weblate and after using script:

• https://github.com/ImranR98/Obtainium/compare/29210fcbb2fe8084ce4bca0facebdacfdc07fb55..2f4e1761164edd6988b65ef344e2207a46852ff0?diff=unified

[ngocanhtve]

What is the current possible way to localize this app?

[Daviteusz]

@ngocanhtve You can do this manually. I use weblate, but every time I have to run script that adds the "other" plural.

[inson1]

Isnt this duplicate of #352? Or maybe close the older issue, becase this is about all platforms?

I think one should be closed

[CertainBot]

@ngocanhtve You can do this manually. I use weblate, but every time I have to run script that adds the "other" plural.

Probably Weblate should ammend this in the first place, if its not already been done?

[zen0bit]

I am just adding:
Weblate can host open source translation projects for free.
You have to apply for approval...
Or host yourself as was already said