Translation of the accompanying text in audit tests into a language other than English

[MikeWinny]

Is it possible and how to translate the Explanatory Text in audit tests into a language other than English?
I only found files for translating hints and helps.

[koenderks]

Hi Mike,

Are you referring to the explanatory text in the jfa package (which I do not think we have?), or in the JASP implementation in the Audit module?

[MikeWinny]

I am working with the Audit module, which was installed during the standard JASP installation and which I enabled via the modules menu using the [+] button. I need to translate the explanatory text generated by the tests of this module. At the same time, I observe that individual (simple and short) words and phrases in the explanatory text are translated into the language I need (which I have enabled in the settings).

[koenderks]

You can translate all the text via https://hosted.weblate.org/projects/jasp/jaspaudit-r/ by making an account. Which language do you want to translate it in?

[MikeWinny]

Russian.
Thanks for the help. I will study and participate if possible.

[koenderks]

Thank you very much for the contribution!

[MikeWinny]

Hi, Koen!
I have almost finished translating the texts for the JASP Audit module in the weblate environment.
There are several questions.

1. What should I do if there are only "labels" of variables in the text that requires translation? Just copy it and not process it in any way?
2. Among the terms requiring translation, there were often "header" forms with capital letters at the beginning of each word, but since there are no such forms in the Russian language then they were "translated" with a lowercase letter beginning, the system had problems with "matching translations". How to handle such cases?
3. What actions should be taken in the weblate environment to notify about the completion of the translation?
4. I was not able to position all the terms in the JASP reports, and therefore I would like to receive a "test" version of the *.mo file for its substitution into a working program, for testing and correcting the translation if necessary.
   And the last question is how can I share the *.md files of the Russian translation for the Audit module, which I translated into Russian?

[koenderks]

Thanks for the effort.

What should I do if there are only "labels" of variables in the text that requires translation? Just copy it and not process it in any way?

I'm not sure what you mean by this? Can you provide an example?

Among the terms requiring translation, there were often "header" forms with capital letters at the beginning of each word, but since there are no such forms in the Russian language then they were "translated" with a lowercase letter beginning, the system had problems with "matching translations". How to handle such cases?

You can just ignore these warnings.

What actions should be taken in the weblate environment to notify about the completion of the translation?
I was not able to position all the terms in the JASP reports, and therefore I would like to receive a "test" version of the *.mo file for its substitution into a working program, for testing and correcting the translation if necessary.

This is done automatically. I do not think it is possible to get a test version, but maybe it is better to ask these kinds of things in the general JASP issue repository (https://github.com/jasp-stats/jasp-issues/issues) instead of in this repository. Let's move this discussion there because then you can also get the input of the JASP core team.

And the last question is how can I share the *.md files of the Russian translation for the Audit module, which I translated into Russian?

This will be done automatically I think.

[koenderks]

You can just copy these texts

[MikeWinny]

OK. That's what I did. In general, the translation is finished, except for the comments, the logic of which I cannot understand :)

[koenderks]

What kind of comments? Maybe I can help.

[MikeWinny]

I was referring to the "duplicate translations" mentioned earlier, which you suggested ignoring.

[koenderks]

Ah yes, well they are just strings that get replaced with other text that you have translated separately ;)

[MikeWinny]

Hi, Koen!
Tell me, at what point in the program's lifecycle is the translation file for a specific language (in my case, ru) converted to help files (these are files like *_ru.md in the /help/ folder of the corresponding module)?
I did the translation in both translation files, they ended up in git.
I downloaded the nightly build and installed it. Translations of the interface and the resulting report have appeared, but there are no help files for my language.