You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Potential translators and those interested to become a translator are often not very tech-savvy, development or coding savvy. I think the current manual editing of resx files adds a very high barrier to potential translation contributions. The length and complexity that the TRANSLATING.md documentation describes is indicative of that. Knowledge in multiple tools is necessary to contribute translations.
For other FOSS projects I have some experience with hosted web platforms that provide a webpage interface for translators as end users, without a need to work with dedicated desktop software, files, git and pull requests. I have experience with them both from a translators role as well as administrative role.
There are multiple popular and established platforms available that provide free hosting for FOSS projects.
Weblate is free and open source software and implements such a translation web platform. The project also has a Hosted instance where they host projects for a price, or FOSS projects for free with some limits (that should suffice for a long time; 60 langs, 10k source strings).
I want to suggest introducing Hosted Weblate as a platform for translations, integrated into GitHub. For the maintainers of this project, apart from initial setup, their process will remain similar, with some additional benefits. Weblate will create PRs, as desired/configured, and those PRs can be reviewed and merged much like before.
If you have any questions about the other platforms, or comparison/differences, or Weblate or Hosted Weblate in particular, do not hesitate to ask.
As I do already have experience setting up Weblate for a GitHub hosted project I hereby also offer support in setting it up, should you decide to evaluate or use it.
The setup process is pretty straight forward. 1. Create the hosted project, 2. Set up GitHub integration (integration app, user as contributor, webhook), 3. set up components (translation file configurations), 4. request libre hosting for the project (starts as a trial)
This discussion was converted from issue #1321 on February 09, 2021 21:04.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Potential translators and those interested to become a translator are often not very tech-savvy, development or coding savvy. I think the current manual editing of resx files adds a very high barrier to potential translation contributions. The length and complexity that the TRANSLATING.md documentation describes is indicative of that. Knowledge in multiple tools is necessary to contribute translations.
For other FOSS projects I have some experience with hosted web platforms that provide a webpage interface for translators as end users, without a need to work with dedicated desktop software, files, git and pull requests. I have experience with them both from a translators role as well as administrative role.
There are multiple popular and established platforms available that provide free hosting for FOSS projects.
Weblate is free and open source software and implements such a translation web platform. The project also has a Hosted instance where they host projects for a price, or FOSS projects for free with some limits (that should suffice for a long time; 60 langs, 10k source strings).
For looking at the translation interface, a lot of publicly listed projects can be found at hosted.weblate.org/projects/, for example RedReader or Tox.
I want to suggest introducing Hosted Weblate as a platform for translations, integrated into GitHub. For the maintainers of this project, apart from initial setup, their process will remain similar, with some additional benefits. Weblate will create PRs, as desired/configured, and those PRs can be reviewed and merged much like before.
I recently evaluated multiple platforms for the FOSS project Mumble where we used Transifex previously. More information can be found in the corresponding discussion, and additional Weblate comment. An example PR can be found at Kissaki/mumble#13.
If you have any questions about the other platforms, or comparison/differences, or Weblate or Hosted Weblate in particular, do not hesitate to ask.
As I do already have experience setting up Weblate for a GitHub hosted project I hereby also offer support in setting it up, should you decide to evaluate or use it.
The setup process is pretty straight forward. 1. Create the hosted project, 2. Set up GitHub integration (integration app, user as contributor, webhook), 3. set up components (translation file configurations), 4. request libre hosting for the project (starts as a trial)
Beta Was this translation helpful? Give feedback.
All reactions