2. RoR Player

This is the translation platform for RoR Player, a browser-based player and composer for the drumming patterns played by Rhythms of Resistance. Everyone can contribute here and create a translation for a new language or work on an existing language. The original texts (in English) are managed in the source code of the RoR Player. Here on Weblate you can translate those texts into other languages. After you have made some translations, the RoR Internet Working Group will automatically be notified and needs to approve and apply the changes in order for them to appear in the RoR Player. As you might know, this can take time, but feel free to remind us.

To contribute, you first need to register and log in here on Weblate.

Have a look at the “Glossary” component first. Its translations are not directly used in the RoR Player, but they have the purpose to be a guideline for translators. They contain terms that appear throughout the app, and you should familiarize with them in order to translate them in a consistent way. If you are starting the work on a new language, translate the terms from the glossary first to define for yourself and for future translators how they should be translated. To create a new language, enter the Glossary component and then click on the + on the top left of the table of languages. It takes a few minutes until the language becomes available also in all the other components. If you are working on an existing language, click on the language and then on “All strings” to see the existing translations of the glossary.

When the language that you want to work on is created and you have made yourself familiar with the glossary, start in the Languages tab of the project itself and click on your language. Here you can see the progress of the translation of each component. To start translating, click on a component and then on the black “Translate” button on the right. It is best to start with the RoR Player component, as that is not so much work but is essential for using the app (it contains the labels of all buttons and other UI elements). The tune descriptions you can do later bit by bit, they are really a lot of work, and most people will probably only ever read the ones of the most popular tunes, if at all.

If a text contains an expression in double curly braces, such as {{value}}, this is a placeholder that will be replaced with an actual value in the UI. The placeholder must be the same in all languages, so leave the placeholder name inside the curly braces in English. For example, the text {{count}} days ago would be translated to German as Vor {{count}} Tagen, so the word count must not be translated.

When translating the tune descriptions, it is important to keep any Markdown formatting characters (such as ** for bold, * or _ for italic and things like [YouTube]{1} for links) in the translation.

Sometimes it can be difficult to understand the context where a specific text appears in the app. Looking at the ID of the text, which is written on the right above the English text, can sometimes help understanding the context. Feel free to send us a list of the texts where you need more context and we can add an explanation.