Closed qua-rus closed 3 weeks ago
Hello Alexander, Thanks for your great work and your translation into Russian. I commited the tutorial file in this commit https://github.com/aardappel/treesheets/commit/d6b97b9a32fb9739a81d335764c61772ca8ec21e and I am looking for a good place for the introduction file. Thanks again! :+1: Best regards, Tobias
1) I’ll check the translation again and maybe correct it... where should I send the result?
2) I would take the trouble to convert the program interface into Russian, but the instructions in the file https://github.com/aardappel/treesheets/blob/master/TS/translations/readme_translations.txt did not produce results...
But running merge.sh (contains the command: msgmerge --update --backup=numbered ts.po ../ts.pot) does not change the ts.po and ts.pot files... I considered further actions inappropriate, because . After reading man msgmerge I don’t quite understand what to do (I don’t do programming)...
What should I do?
The first steps were correct. You initialized a new translation and took the template (pot) to derive a translation file (po) for the language from it and then you added the translation by modifying the msgstr lines. Now you would need to "compile" that translation into the binary format (mo) with msgfmt. There should be a compile.sh script that generates the mo file. The msgmerge is to update the language translation file po when the template pot has changed. Then the translation has to be updated in the human-readible po file and afterwards be compiled again with msgfmt / compile.sh to the machine-readible / binary format. Did this help you?
1) I’ll check the translation again and maybe correct it... where should I send the result?
Please feel free to upload it here if you are not familiar with git and GitHub Pull Requests. Otherwise you will also find plenty of tutorials on the Internet on how to create Pull Requests on GitHub but if you are not familiar with Git, then better to put it here if you like. Thanks in advance and looking forward to your translation!
1... Thank you, I’ll definitely figure it out with git a little later.
2... The first steps were correct. ... Did this help you?
Thank you, I understand the purpose of the command in the merge.sh file, I will proceed further.
Brought the Introduction into a human-readable form. intro-ru.cts.zip
Brought the Interactive Guide into a human-readable form. tutorial-ru.cts.zip I placed the file tutorial-ru.cts in the directory: /var/lib/flatpak/app/com.strlen.TreeSheets/current/active/files/share/doc/treesheets/examples/ ...on F1 I opened an Interactive Guide in Russian.
I took up the translations in the ts.po file. Completed a partial translation and compiled it into a ts.mo file. Moved ru_RU/ts.mo to the directory
/var/lib/flatpak/app/com.strlen.TreeSheets/current/x86_64/stable/files/share/locale/ (active = x86_64/stable)
The translation works... but in the translation catalog there are broken links to other language translations... maybe. you might be interested in:
Thanks for the translation work!
I can only guess that the Flatpak locale package for TreeSheets is split into packages for each language. https://github.com/flatpak/flatpak/issues/5560
Thank you, another question... The "&" character appears frequently in the ts.po (and ts.pot) file:
What is the purpose of the "&" character and how important is its presence (and location) in translation strings?
Brought the Interactive Guide into a human-readable form.
I noticed a functional inaccuracy in paragraph 17. tutorial-ru.cts.zip
The & are so-called mnemonics / accelerators and of use in case of navigation through the menus with the keyboard, see e.g. https://www.wxwidgets.org/docs/tutorials/using-mnemonics/ for more details and https://docs.wxwidgets.org/latest/classwx_menu_item.html#a8b0517fb35e3eada66b51568aa87f261 for the use in menu items in menu bars. So & is in strings for labels of window control elements you like to navigate to by keyboard, e.g. menu bars, buttons etc. For messages etc. this is not necessary so this why some strings contain & and others do not. Is this ok for you as a short explanation? And you are free to place the & at others letters than in the English string as long it seems sensible and it is not already used with the same letter in the same menu etc..
Brought the Interactive Guide into a human-readable form.
I noticed a functional inaccuracy in paragraph 17. tutorial-ru.cts.zip
Pushed as commit. Thanks!
The & are so-called...
Thank you. Additionally... Brought the Introduction into a human-readable form. intro-ru.cts.zip
...including the Introduction. TreeSheets_Help.zip