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.

[Snayler]

Nice, I'll start the Portuguese translations.

EDIT:
Question: There's some dialogs I'm not sure I should be translating. For example, on CAboutDlgBase, there a TextLabelVersion which seems like a placeholder for the text defined on CAboutDlg. What should be done in these cases?

Also, can we add translator next to the author in the about dialog? Like so:
Autor: Volker Fischer; Tradução: Snayler

[corrados]

In the About dialog white text box we have this: "We would like to acknowledge the contributors listed in the Github Contributors list". Additionally I could add a text for listing the translators.

[Snayler]

Well, it would not make sense to have the direct mention of the translators on the About Window without directly mentioning all other contributors who, IMHO, have made more significant contributions. So I'm happy with the "Github Contributors List" link.

[trebmuh]

@corrados : nice.

I've done a few strings translation as requested. See #176 .

In the About dialog white text box we have this: "We would like to acknowledge the contributors listed in the Github Contributors list". Additionally I could add a text for listing the translators.

It'd be great.

...her contributors who, IMHO, have made more significant contributions.

Well, that's only a PoV. For someone not able to read/understand English, having a good translation in his/her mother tongue is much more important than pretty much any other feature.

[Snayler]

Well, that's only a PoV. For someone not able to read/understand English, having a good translation in his/her mother tongue is much more important than pretty much any other other feature.

Yes, it's only my opinion, hence the "IMHO" acronym. I do understand your PoV, it's just that I'm fluent in English and I actually prefer to have all my systems and programs in English than in my mother tongue, as I can better understand technical texts and instructions that way. That's why I value more contributors who actually program features into the software than translators.

On the other hand, I did spend most of today translating, checking and re-checking all the strings on the translation files, I can say it's no easy task. Also, what's not needed for me might be needed for someone who doesn't fully grasp the English language and wants to learn how the software works and what each setting does, so I see your point.

Maybe just have one field for the translator and each language would have it's translator(s) named.

On another note, I found that no strings for most of the dropdown menus were included in the translation files, and I would like to be able to translate some options as it would match the translated explanations better.

[corrados]

My plan is to re-design the About dialog. My plan is to list all the contributors (code development, documentation, translation).

[ignotus666]

I could do the Spanish translation. Does the 'translation_es_ES.ts' file need to be created or could I just work with the 'translation_de_DE.ts' file (later changing the extension) seeing as it's still empty?

[corrados]

Great, I will prepare a file for your spanish translation.

[corrados]

I could do the Spanish translation.

Please wait for some days before you start. I want to change something in the texts soon.

[ignotus666]

Ok!

[corrados]

Ok, I think I am done now with the modifications. If you like you can start now your translations using the latest Git master commit.

[corrados]

@Snayler, @trebmuh Here is a first proposal for the new About dialog:

In this tab I will list the supported languages and the peoples names who contributed to the translations. How do you like it?

[trebmuh]

👍

[Snayler]

I'm having trouble selecting the language on 3.5.3git. I'm using --translation, but I'm not sure what to input next to select the Portuguese language.

[corrados]

FYI: I plan to make the next release 3.6.1 on Sunday morning, 22th of November. It would be good to have updated translations the day before (Saturday) if possible.

[corrados]

@dyeopensource wants to add Hungarian translations, see #760.

[corrados]

FYI: I plan to make the next release 3.6.2 on Sunday morning, 13th of December. It would be good to have updated translations the day before (Saturday) if possible.

[trebmuh]

@corrados : thanks for the "nbsp" changes, forgot to commit these.

[dyeopensource]

Thx for the info. Unfortunately I could not make it by now. I am done only with about the half of the texts. Volker Fischer <notifications@github.com> ezt írta (időpont: 2020. dec. 7., H, 17:10):

…

FYI: I plan to make the *next release 3.6.2 on Sunday morning, 13th of December*. It would be good to have updated translations the day before (Saturday) if possible. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#77 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB6J6AYHI7EMX3KWKEZE4RDSTT5AVANCNFSM4MJYFW4Q> .

[corrados]

@ann0see Are you interested in taking over the German translation in the Jamulus software? If yes, please do not forget to add your name here: https://github.com/corrados/jamulus/blob/7a6955d094caa8eeb1f0b2500b42fda0752aa524/src/util.cpp#L499

[ann0see]

I'm sorry to say that I don't want to take over. I already have the Wiki and actually wanted to hand it to someone else @SmuSmu .

Unfortunately he didn't respond. Maybe someone else would be interested in this?

[jerogee]

@ann0see, unfortunally my German is not good enough. Perhaps you know a German Jamulus-enthousiast who like to take that on? Or perhaps there is a German forum to post a message on and ask?

Apart from that, I suggest to add this sentence in the "Contribute!" block on https://jamulus.io/:

Contribute!

Ideas? Found a bug? Want to contribute? Or help translating into your language? Since Jamulus is free and open source software licensed under the GPL you can help us!

[ann0see]

@ALL I hope all translators are now in the Jamulussoftware/Translators team. I think it would be great to move discussion about translation there since translation also applies to the website now.

[SmuSmu]

I'm sorry to say that I don't want to take over. I already have the Wiki and actually wanted to hand it to someone else @SmuSmu .

Unfortunately he didn't respond. Maybe someone else would be interested in this?

Shame on me. Sadly i will Not bei able to translate as fast as you will need it in your new process. My Goal was to contribute from time to time. I suggest to Open an issue regarding Help wanted. And ask for Help directly in the Website. So sadly i am Out Here.

[ann0see]

Sadly i will Not bei able to translate as fast as you will need it in your new process

No problem. The project is quite active at the moment and especially the documentation is a big task to translate ;-). Maybe you can share work with somebody?

[ann0see]

@Snayler @Martyna27 @SeeLook @genesisproject2020 @jose1711 I've now added you to the jamulussoftware organisation. Please accept this invitation which will allow to make announcements of new releases and communication much easier. If I forgot to add a translator, please ping me.

[ann0see]

Closed since the initial feature request has been fulfilled:

1. Jamulus can be translated now (just recently the upcoming installer has also added translation support)
2. The documentation can be translated too
3. We now have an organisation with a translator team where every translator can comment and new releases can be announced: https://github.com/orgs/jamulussoftware/teams/translators please "watch" this team as translator to get a notification once a new release is coming up (which will be the case soon, I assume).

[ann0see]

Sorry I accidentally removed all translators from the GitHub team. Please re-accept the invitation.

[ann0see]

@jose1711 @Martyna27 I've renewed the invitation to the organisation. To the other translators: Soon someone will ping you soon since a release will be made shortly.

[rolamos]

Hi , I would like to help with the translations into German :-)