Weblate as a translation platform #958
Comments
|
Benefits include:
|
|
Just a quick word to say that as a translator, Weblate is a lot more convenient. For instance, I made a stupid mistake and clicked on discard commits while updating my fork which trashed all the translations I had uploaded on #948 (of which I didn't have local copies anymore, so I had to do it all of it again). And see the commit log of #956 on which I spent quite some time hunting for forgotten escape sequences. So Weblate, please, yes! Additionally, other translators can see and review current translations more easily there than with git and pull requests which are, at the end of the day, developer tools. |
|
weblate is supercomplicated to set up. please contact us to help in setting it up. |
|
@m2049r It shouldn't be, I can help. You'd just have to first request libre hosting /create a project in hosted.weblate.org, and add me as an admin for that project. Then we can see how it goes! |
|
How would I go about contacting you...? |
|
On 9.10.2024 03:01, Lucas wrote:
How would I go about contacting you...?
@m2049r has an e-mail address on his GitHub profile page, and the
Monerujo website also has a contact address. Hope this is helpful in
some way.
|
Weblate makes things much easier; It is pretty easy to set up. It also lets you deal with a bunch of issues that can be caused by translators, and makes the process more accessible. Please look into this.
#521 was a previous attempt
The necessary steps:
Merge all translation related PRs (you can also try importing them into Weblate manually later)
Request to create a new project in https://hosted.weblate.org (you can use translate.codeberg.org as well, either as a replacement or as a testing ground! Note that it does not integrate with GitHub pull requests of course and you'd have to manually pull from the Weblate Git repo)
Configure the app component in it, you can make it go through a GitHub pull request which is probably the most ideal method (Weblate automatically detects Android app setups as a suggestion and so this should be somewhat easy)
Check out a few plugins, one relevant one is "Mark unchanged translations as need for editing". Don't add too much, they can cause issues.
Disable linting checks that don't make sense e.g. MissingTranslation since translations are crowd-sourced
The text was updated successfully, but these errors were encountered: