H5P translations

H5P translations

by Germán Valero -
Number of replies: 1
Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers Picture of Translators

Being the most popular additional Moodle plugin, one would expect that the Moodle H5P plugin had full translations for the major languages, but many translations are currently incomplete sad

But the real problem for many users in languages other than English might be the translations of the H5P modules themselves, that need to be done in the H5P GitHub site.

And the fact that these GitHub translations seem not to be incorporated into the H5P released packages soon enough sad

As typically we won't release a content type just to update languages. We will typically release the content types when a significant feature or bug fix will go out because of the overhead associated with releasing a new version of a content type.

Could there be a reasonably policy for updating translation for the H5P modules suggested for them and supported by Moodle users of this plugin with languages other than  English?


According to fnoks' post on Fri, 09/26/2014 - 11:39 "When we get new translation-files from the community, we will create a new release of the H5P content type containing the new/updated translation, and publish it here on h5p.org.".  Which seems not to be the case nowadays, as "For the content types it will be in effect when the respective content types are released." sad

Average of ratings: -
In reply to Germán Valero

Re: H5P translations

by Randy Thornton -
Picture of Documentation writers
Germán,

I think the whole issue of how the modules (aka library files or content types) will be managed is a big question. If the new plugin in Moodle 3.8 replaces the H5P supplied plugin, but does not have any way to manage those library files, but each Moodle site must still pull them from the H5P hub (or hunt around to get them to update manually), that is not really an improvement. Version control now really doesn't even exist for those library files and those are the important part. Users actually use those, so how those language files get timely updates is vital.

What if those library files could be pulled from Github without having to wait for H5P to bundle them up their releases? What if those strings could be pulled / pushed into AMOS so language maintainers could provide the various Moodle languages back to H5P as well?

If the content type modules were treated as subplugins of the main H5P plugin (similar say to what Custom Certificate and others do now), that would solve the problem. But it then means HQ must manage those library files on their way into Moodle as proper plugins just as they will be managing the way the main H5P plugin gets into Moodle. Hopefully, this is the eventual plan, as I don't see any other reasonable way to do it, since the package formats of the content files (which are mostly json) are not like Moodle plugins, and the strings are not the same as AMOS based strings. Some sort of conversion tool would have to be built, I would think.


Randy