Translate into Russian
Make a translation into Russian
- 12 replies
Good idea :- ) I don't speak Russian, but if you know someone who does and wants to translate, then, the instructions:https://github.com/debiki/talkyard/blob/master/translations/i18n-README.md
(steps 1 and 2 only). There's a CLA: https://github.com/debiki/talkyard/blob/master/docs/CLA-v2.txt
I translated into Russian.
Translation file in folder ru_RU
I would be very happy if you add russian translation )
Ok :- ) I'll include in the next release, hopefully some time next week.
Can you please sign the CLA? By squashing the commits, and appending this to the Git commit message:
I, Your Full Name <email@example.com>, agree to the Contributor License Agreement, docs/CLA-v2.txt.
Or alternatively, just reply here to me that you agree to the CLA, i.e. this: https://github.com/debiki/talkyard/blob/master/docs/CLA-v2.txt.
(It's better if you squash the commits and edit the commit message — then i can include the translations in the main Git repository, which is slightly more convenient, when making updates, later.)
This looks fine & works fine, I've tested the translations on localhost now. (I noticed just a few tiny typos, e.g. an extra trailing
.somewhere — I'll fix that later.)
What if you squash the commits to just one commit, and keep the "I ... agree to the Contributor License Agreement ..." commit message, and then you submit a PR? Then I'll merge it.
I am not familiar with the work of GitHub. You want me to add a message "I ... agree to the Contributor License Agreement ..." in file https://github.com/Noobchenko/talkyard/blob/master/translations/ru_RU/i18n.ts ??
Summary: Now I've included the translation.
Thanks for asking — actually, no, you don't need (and shouldn't) do that. You already did the CLA related things in the right way :- ).
Namely by appending "I agree ..." to a commit message, not any text file.
This is just about sending a request from your GitHub repo fork, to my GitHub repo, so I can click a button and in that way include all your "code" / translations.
... Now ... It turns out I too can create a pull request (I just noticed). I just did, here: https://github.com/debiki/talkyard/pull/40.
And, GitHub has a Squash and merge button, which will squash all your commits into one — so GitHub can do that, and we won't need to.
(I prefer having all the commits squashed / "brought together" into just one commit, so the commit history looks prettier / cleaner.)
I've now merged the PR I created, and the translation will be included in the next release (hopefully some day next week).
- Progresswith doing this idea
I had to re-do the merge, because GitHub somehow deleted original author info.
Here's the PR, squashed and merged, with correct original-author info:
Ok so now the Russian translation has been merged, ... will be included in the next release.
- @KajMagnus marked this topic as Started 2019-11-17 05:28:52.151Z.
- @KajMagnus marked this topic as Done 2019-11-23 12:12:43.013Z.
Hi @Ecolog, I didn't bump the GitHub version number yet (because I wanted to give other self-hosted people some time to enable a certain Google People API, which is in the same new version).
Once I've bumped this version number, your server will auto upgrade to 0.6.51 which includes Russian.
Sorry I could probably have been more clear about this. I can bump the version number tomorrow Saturday I would think, maybe today.
Hi again @Ecolog now I bumped the version number for the self hosted Docker images. So this night your Talkyard installation should self-upgrade to v0.6.51, which includes Russian. — If you want to upgrade directly, you can:
sudo -i cd /opt/talkyard ./scripts/upgrade-if-needed.sh