Replies: 7 comments 37 replies
-
|
Just saw this and thank you for evaluating alternatives. One thought: Wouldn't it be possible to put the whole translation into files instead of such platforms? I have worked on translation for some other projects and always noticed the difficulty that comes with such plattforms:
Maybe there are also other alternatives that consider these points. |
Beta Was this translation helpful? Give feedback.
-
|
😮 I see now, I should have stated more clearly that I didn't know about the advanced features of the Tools. If (in addition to that) we could have a login as easy as possible (via github e.g. 😉 ) and an easy agreement (not "sell your soul to the devil"), then it could be perfect 😃. |
Beta Was this translation helpful? Give feedback.
-
|
GitHub login is possible, this is how I connect to hosted Weblate anyway :) Regarding sell your soul to the devil: Weblate is open source so if you don't like the hosting terms and condition you can host it your own but I assure you it's the best license you can find plus GDPR which protects user's personal details so although GDPR sounds intimidating following its guidelines in open source system is quite natural. Transifex has a more restricting license but that's pretty obvious when were talking about closed vs open source (IIRC there's a GitHub login support). |
Beta Was this translation helpful? Give feedback.
-
|
I’m saying the concept you lay out is, to my knowledge, not possible. And you do not provide information on how you plan to implement your wishes, or even mention if you have a plan and confirmed technical possibility or not. |
Beta Was this translation helpful? Give feedback.
-
|
@Kissaki please elaborate, I don't understand. |
Beta Was this translation helpful? Give feedback.
-
|
I was addressing toby. |
Beta Was this translation helpful? Give feedback.
-
|
Regarding Weblate: @toby63 Both Weblate and Crowdin support full context (msgctxt, comments, original location of string and screenshots) so translating using these systems is not out of context, furthermore, I can click the string origin and reach the exact line on GitHub if I configured everything correctly. Transifex are offering context for subscribed members only. Crowdin is indeed pretty limiting, Weblate is open source and they are following GDPR. @Krzmbrzl Yup, exactly. |
Beta Was this translation helpful? Give feedback.
-
|
Well theoretically we have two lanes: The Sync lane is the Weblate UI where each and every contribution is immediately submitted to the repository, and then we have the async lane which is downloading from git, working, commiting with a good possibility of having someone changing the translation in the meanwhile (even if these are not the same strings, which is easier to merge in case of conflict and yet a bit inconvenient). Theoretically if we want to have the same results you'll have to commit and push on each and every string manually (while working on the localization file). It's not completely plausible but it's… well… inconvenient I'd say :) |
Beta Was this translation helpful? Give feedback.
-
I was not talking about as a project but as a user. |
Beta Was this translation helpful? Give feedback.
-
|
I’m not sure this is what you are discussing, but what I stumbled over two days ago was how Weblate clones the repository, including the upstream reference branch, and makes the changes on that. The user API key can be used to access the git repository https://hosted.weblate.org/accounts/profile/#api (cloning seemed to work fine without one, but obviously not pushing) |
Beta Was this translation helpful? Give feedback.
-
That sounds good. |
Beta Was this translation helpful? Give feedback.
-
I'll see if there's anything I can do.
We've tried the same thing, if oy find any way to make it work I'd love to know.
I'm managing "Remmina" on hosted Weblate. |
Beta Was this translation helpful? Give feedback.
-
WeblateIn Weblate a project is created. The project contains Components. For us a component may be 'Mumble Client'. If we were to create more than one translation file, we could create separate components for separate Mumble Client components. The project has a Git repository configured for at least pulling. The component is configured with file paths for translation files in the repository. Weblate hosts a git repository for a project within Weblate. Changes are pulled from the remote, upstream repository from source branches, and if desired pushed to a target branch, and merge requests can be created. It seems quite flexible in how to integrate. It can use bare git, or further integrations of platforms, like GitHub merge requests. A GitHub user, GitHub app, and a hook target ( Automatic translation files and languages seems to work fine for our mixed files (two letter codes, and two+two letter codes), although zh_TW seems to be misinterpreted as either zh_Hans or zh_Hant. Addons can be used to further adjust the translation/CI process. For example, commits can be squashed into a per file, author, language basis, or into one commit. This can preserve authors into Git through Conflicts in the Weblate hosted Git repository can be resolved through clearing the repository, or manually. |
Beta Was this translation helpful? Give feedback.
-
|
Provides a shared training set between projects machine learning suggestions platform like the other candidates. |
Beta Was this translation helpful? Give feedback.
-
|
Creates a pretty nice pull request with translation status per language as an image, with preservation of authors, either on commits directly, or with squash addon with Co-Authored-By footers. |
Beta Was this translation helpful? Give feedback.
-
|
Weblate looks great. I will advocate moving to it. |
Beta Was this translation helpful? Give feedback.
-
Transifex |
Beta Was this translation helpful? Give feedback.
-
|
Always had a pretty bad administration interface/UX. |
Beta Was this translation helpful? Give feedback.
-
|
Is bad UX the only reason for moving from Transifex? If so, are there any other benefits from other platforms to do such a work? |
Beta Was this translation helpful? Give feedback.
-
|
@itsTurnip We have already moved to Weblate. See https://www.mumble.info/blog/switch-to-weblate-as-translation-platform/ EDIT: And in order to answer your question concretely: The most problematic issue were their terms of use |
Beta Was this translation helpful? Give feedback.
-
|
I don’t think their ToS was their most problematic issue. The ToS discussion was the trigger for looking for alternatives. But the conclusion from checking the ToS was that they are basically fine. And not necessarily worse than other services. Other platforms did have advantages over Transifex, which is why we ended up moving. |
Beta Was this translation helpful? Give feedback.
-
Crowdin |
Beta Was this translation helpful? Give feedback.
-
|
In our current file lang-code postfix mixture of two letters and two_two letters Crowdin has difficulties handling them. Would require harmonization, or requires manual language code mapping for languages. Provides a shared training set between projects machine learning suggestions platform like the other candidates. |
Beta Was this translation helpful? Give feedback.
-
|
Harmonizing the naming of our translation files might be a good thing to do anyways though. |
Beta Was this translation helpful? Give feedback.
-
ConclusionThere is nothing Hosted Weblate lacks compared to the other hosted products, except for the limits they set on the free-for-libre tier.
Currently our Mumble client has 2k source strings, and 44 languages (6 completely empty). The GitHub integration, technology and features behind Weblate seem very good. Seemingly better than the other platforms. For me this is enough insight and information between the platforms, and enough to personally advocate for moving to Hosted Weblate. Are there other opinions regarding this? Agreement or disagreement to Hosted Weblate? Request for further discussion or analysis? Different preference? Suggested Transition to WeblateI set the project up for a test to my repository fork, and it could be switched to the official repository easily, and libre hosting could be requested. No further configuration necessary. We should decide if we want to do another feedback round with translators, asking them to provide feedback and opinions. Given the low current / generally low activity of the translation process, I don’t think switching without another feedback round would be a problem. Registration on the new platform is not too bad, the translation interface is similar. Additional planning and preparation will be necessary to notifying translators, and announcing the switch. We will also have to synchronize activating Hosted Weblate and deactivating Transifex along with our bot and potentially open PR. |
Beta Was this translation helpful? Give feedback.
-
|
Given that Weblate is FOSS it was always my preferred choice and from what I have seen it definitely looked at least "good enough" for the job. If you (who has looked into the issue much more than me) even conclude that it is overall better, then that's great.
Do we have a possibility to contact them that I don't know of? If we do, then I think checking back with them would probably be a good thing to do.
Agreed And I also agree that the limitation hosted Weblate puts on libre projects are put so high that we probably never have to worry about them. And if we do there'd always be the possibility to switch to a self-hosted instance (or pay them - whatever would be better for us in that case) 🤷 |
Beta Was this translation helpful? Give feedback.
-
|
IMO If we want feedback from the translators we would probably have to have Weblate already set up, so they can try it out. Having additional hurdles like them only being able to read feature promotion or documentation, or having to check on other projects would make fewer people participate. Of course this may cause conflicts between the state of the two platforms depending on how eager translators are to translate on either platform, possibly ignoring instructions. |
Beta Was this translation helpful? Give feedback.
-
|
Agreed |
Beta Was this translation helpful? Give feedback.
-
|
I agree with switching to Weblate. |
Beta Was this translation helpful? Give feedback.
-
|
Migration ticket #4727 |
Beta Was this translation helpful? Give feedback.
-
|
Seemed to work just fine when it was up on Hosted Weblate. Edit: The other two alternatives not only don't have a graits-for-libre offerings, they also operate either limits or fly by night. Edit2: Freezing the project on Transifex and then https://docs.transifex.com/projects/archiving-a-project/ with a notice saying it has moved helps prevent trouble before opening it on Hosted Weblate. |
Beta Was this translation helpful? Give feedback.
-
This topic is now locked as we concluded on an alternative and completed the move. See the respective news post on our website and corresponding work tickets.
We have been using Transifex as a translation platform for a long time. It works.
However, we want to explore our alternatives that we have today.
We want to try these out and see how they compare, and then make a decision whether a switch is worth it and to which platform.
Transifex
Free for Open Source
Crowdin
Crowdin promises a modern, sleek UI/UX, and great machine translation aid.
Free for Open Source
Weblate
Weblate is an open source solution that provides both hosted and self-hosted solutions.
Hosted: Limited Free for Open Source
The alternative would be to self-host, which would incur additional hosting and administrative costs.
Additional Alternatives
Pontoon
Mozilla’s FOSS translation platform/software. Mozilla instance for their products.
LingoHub
Not much information on the website. Free libre hosting. Requires term for a presentation to try it out/discuss.
Beta Was this translation helpful? Give feedback.
All reactions