Allow internationalization

[trebmuh]

I'd be really happy to provides the project with a French translation for the GUI if a translation mechanism was made available.

[gilgongo]

Same applies to the Wiki/docs ideally. I don't think it's really feasible with Github's wiki though. Perhaps if we moved to Github Pages, but that might cause other issues.

[trebmuh]

If the docs should be moved elsewhere for being translatable, then I'd encourage to make use of https://hosted.weblate.org/ (it's free software and free to use for free software). Note that, you can use the hosted.weblate to make the GUI component translation too.

[gilgongo]

Interesting. How would this work in Jamulus's case? For example I notice from Weblate's own docs that they appear to be hosted on Github (there's an "edit" button in the top right which takes you to what I assume is a docs repo with .rst files in it). What I don't understand is how to switch to another language (or is that being auto-detected?), or where the web app is being hosted (Is it Github pages, or perhaps some 3rd party that you can deploy to via Github? - looks rather similar to this site which I see has a language switch as well) Is this the default if you opt for weblate hosting?

[trebmuh]

I don't understand very well what you wrote @gilgongo . Not a native English speaker here.

Not being a coding person neither, I can tell you how I understand it since I'm using it as a translator for several projects.

• the jamulus dev(s) set up a translation mechanism (let's say the Qt translation system here)
• the jamulus dev(s) does ask to hosted.weblate if they're ok to host the project's translation for free (being a free software)
• weblate says OK (most likely and hopefully 🤞 )
• then the dev or/and weblate people (I don't know) make a kind of a "hook" thing which allow to copy the translation file from github to weblate, and back
• the translators translate online (on hosted.weblate) and the hook take care of integrating things back into the github repo

I hope this helps.

If you need more information, I can maybe ask someone from a project I'm translating on weblate to talk with you on what are the details of the installation of that.

[gilgongo]

@trebmuh My apologies - I was referring to how weblate might work with the localisation of our documentation, not the application itself. Does weblate help with localising a collaboratively-edited website?

[trebmuh]

@gilgongo as far as I know, you just feed Weblate with files (.pot/.po or .ts type file, maybe there are other translations mechanism accepted) and translators can start working. I'm not sure with what you call a collaboratively-edited website. As an example, zrythm GUI interface and website is translated using hosted.weblate .

[gilgongo]

By "collaboratively-edited" I mean content created and maintained by more than one person, so that implies things like user permissions and things.

I've got very little experience with internationalisation, but for example if you take something like the Github wiki, or Wordpress, or just flat HTML, I assume the .pot/.po or .ts etc. files have to be integrated into that in some way so that weblate can manage the content independently of the presentation? Apologies, but I'm finding it hard to understand how it would work if we were to decide to internationalise the docs as we have them right now (that is, Github wiki), as opposed to the Jamulus app, which seems less of an issue.

[trebmuh]

I don't really know how it works at such a low level (only a translator here). You might want to chat with weblate people about that, and/or with people using it as project manager (ie: zrythm as a close example to what you're talking about here - its main dev "alextee" is usually on the #lad IRC channel on freenode). I'm sorry that I can't help you further than that. I still hope this talk was helping in some ways !

[gilgongo]

OK thanks - that's very helpful. I'll see if I can contact the zrythm project about it!

[corrados]

I have already prepared Jamulus for internationalization from the beginning. In the code you will find a lot of tr() calls, e.g.: https://github.com/corrados/jamulus/blob/master/src/clientdlg.cpp#L51

Using the Qt lupdate tool, you can extract the english text. I did this as an example for the following file:
jamulus_en.zip
You can load this file in the Qt Linguist GUI and do the translations:

Before you spend too much time on it, we should try it out with some example texts, e.g. the ones on the main windows and see how it works. The modifications inside the Jamulus software should hopefully be small.

[trebmuh]

I have already prepared Jamulus for internationalization from the beginning. In the code you will find a lot of tr() calls, e.g.: https://github.com/corrados/jamulus/blob/master/src/clientdlg.cpp#L51

Yes, I saw that in the code. Good thinking 😉

Let me know if/when a .ts file is ready for translation and I'll start providing a French version of it.

[corrados]

Finally I have done a very first implementation of the translations. For a test I added some German texts:

The translation files are here: https://github.com/corrados/jamulus/tree/master/src/res/translation

If you want to start the French translations, then you should clone the Git repo, open the file https://github.com/corrados/jamulus/blob/master/src/res/translation/translation_fr_FR.ts in QLinguist and do the translations. When you are done then create a pull request.

Maybe it is a good idea that you start with just a few translated texts, make a pull request and I can then generate you a Jamulus versino with which you can do a test that everything works for you.