To be able to actively help with translations, you must create your own account. Note that Weblate publicly displays your profile and contributions.
After you ‘ve registered, you can can start making suggestions:
Open the “H5P” project in Weblate by clicking on Projects –> Browse all projects. Then click on H5P in the list.
You can now see the current status of all strings (texts) in the library:
By default new users only have permission to make suggestions (to avoid abuse). For these suggestions to be accepted and submitted to the H5P repositories on GitHub, there needs to be an active editor for the respective language. Editors have further privileges:
Note: If you make suggestions to a language without an active editor, these suggestions will never find their way into H5P!
Becoming an editor is easy: Create your account and tell the site admins through the contact form that you want to become one. Please include:
As an editor you can directly change translations without having to make suggestions.
If the translation of a library is finished, you can push the changes to GitHub. They will then be reviewed by Joubel and (hopefully) accepted:
Open the Repository maintenance page for the library you’re working on. To do this, click on Manage in the library’s overview page and then on Repository maintenance:
Click on the “push” on the right:
This will upload all the changes onto GitHub and create a pull request (a request asking Joubel to accept the changes).
Important: Only push single components and not the whole H5P project, as some libraries might be work in progress and at this time only have very few changes not worth pushing yet.
Important: As Weblate always pushes all language files for a library (“component”) you should avoid having “unfinished” language strings in the components: Other editors might push the component to GitHub because they’ve finished their translation and your “unfinished” work would be submitted, too. Weblate offers comments & suggestions for doing preliminary translations.
If no-one has ever worked on translations of a specific library into your library, chances are high that there is no language file for the library yet. This means you’ll have to create one yourself:
At the bottom of the list of already existing language, click on the button Start new translation:
In Weblate every string can have three to keep track of which strings are already finished and which ones need work:
Editors can change the state of a single string in the regular editor:
You can also change the state of all strings in a library in a special page, which you can reach from the overview page of a library’s language:
To improve consistency, Weblate supports glossaries. These are list of translations that translation conventions that translators should follow. A glossary consists of an English source string and the recommended translation. Whenever a translator encounters a string that contains the source string of a glossary item (even if it’s just a short part of it), the recommended translations will be automatically shown on the right:
You can enter new glossary items in the same panel or by opening the whole glossary. To open the whole glossary, click on Glossary in a library’s overview page:
As Weblate internally keeps a copy of the Git repository of content types and has to merge changes in its repository with changes in the upstream repository, there can be merge conflicts if these repositories converge too much. A way of reducing these conflicts is to notify Weblate of changes in the upstream repository, so that it can immediately fetch these changes. GitHub allows repository owners to do this by setting up a webhook. If you are a content type developer, you are encouraged to add translate-h5p.tk as a webhook like you can see in the screenshot: