Plugin with 'translation stats not available'

Plugin with 'translation stats not available'

by German Valero -
Number of replies: 3
Picture of Language pack maintainers
Hi. I wanted to translate some new plugins, but I found one with 'translation stats not available'. https://moodle.org/plugins/mod_serlo/translations I could not see a string concatenation. So, I wonder what might be wrong with this plugin. I will greatley appreciatte if a programmer can teach me what is wrong with this plugin that prevents it from being available in AMOS. Thanks in advance.
In reply to German Valero

Re: Plugin with 'translation stats not available'

by German Valero -
Picture of Language pack maintainers
There WAS an issue described in https://github.com/serlo/moodle-mod_serlo/issues/9 :

the plugin uses hard-coded text without the ability to change/translate language strings.

All user-facing strings should be defined in the language file and displayed using the get_string() function.
https://moodledev.io/general/community/plugincontribution/checklist#strings

But the English language strings are in the GitHub code and inside the ZIP package for download.

And in line 35 think there is a string concatenation... which I think might be the problem...
 
$string['firefox_warning'] = 'There are some problems with Firefox at the moment. ' .
    'Please use a Chromium based browser like Chrome, Brave or Opera for a better experience.';

BUT the GitHub code does not have this concatenated string...
In reply to German Valero

Re: Plugin with 'translation stats not available'

by David Mudrák -
Picture of Language pack maintainers

Hi German.

You have debugged the issue here correctly. There is a problem with concatenated strings:

$string['firefox_warning'] = 'There are some problems with Firefox at the moment. ' .
    'Please use a Chromium based browser like Chrome, Brave or Opera for a better experience.';

This problem is not visible at Github as clearly the maintainers no longer publish their recent development there! Their repository was last updated 7 months ago. I am going to report this as an issue -- plugins are expected to have their Git repository updated even after they are approved.

For the record, the developers are informed about troubles with AMOS integration of their plugin. This is how their Dev zone page looks for them:

Screenshot