2138 replies to this topic

[Pr2]

I also was under the impression that all translations based on the POT from PR2 were supposed to be meant for the RC. But, as I am defenitely no specialist, my knowledgelevel is far to low, I could be wrong.

 

I am mentioning for which branch the pot file is, you just have to read the text I wrote.  So I provide pot for both branch, it is up to you to know then for which branch you want to work with the pot file I propose.

 

I even generate again all the .po files for both develop and rc and then propose 2 distinct pull request, but they are not committed and in between you publish your nl.po file which gives conflicts so I close on of the PR.

[Pr2]

The submitted translations will not appear on RC 6.2 until it's synced with the develop branch again. This happened last a few days ago so any translation submitted after that will not be updated immediately.

 

Yes but it is crazy to see in translation that they are new strings to translate in the RC branch that are not in the Develop branch, for po files generated nearly at the same time.

So I really wonder where new stuff are added... sounds like it depends on the developer some are adding new stuff directly in the RC branch other first in the develop one.

 

So if I generate a pot file for the develop we will still have untranslated strings in the RC after a merge due to this.

 

If I generate pot files both for develop and rc this seems to confuse translators too. :-)

 

So I come back to my suggestion to include in the build process the creation of the enigma2.pot (this should only be done once since it is common to all platform) and publish it to the github. So translators, just pickup the po file and the very latest enigma2.pot file from the github branch that they want and start working on it and then create a PR to send back the file to github.

 

When working on two branches this become a nightmare.

[Gringosat]

I think best online tool is https://weblate.org/en/ (opensource) with good integration with Github repository.

 

1) Using an online tool give you the opportunity to everyone to partecipe, maybe creating a team of translators for each language being coordinated by someone inside the team.

2) I think translators should do what they better know, translate (and not understand how to use github to commit they job)

3) What to translate should be offer to translators without post here the .po files or guess which branch use in the sources

 

I know that it's a big effort to have such a tool and developers are concentrated on fixing issues and developing new features for OpenPLi but having near 30 languages to translate should be a "plus" that increase the community of not speaking english users.

For what I know most of OpenPLi users are not native english and have menus in their local language is a good help and is really appreciated (this is the reason by I decided to support OpenPLi with translations, return back to the community a part of what i received from it).

[WanWizard]

There are a lot of things that all have to link together to make things happen properly.

 

We need to get our shit together when it comes to development, and do not use "develop" as a dumping ground, but use feature branches, develop there, and only merge with develop when the feature is finished. I don't have a problem reviewing a new feature when it comes to proper English, before it is merged. That would mean you only need to translate once, and it also means there is no need for "hot-fix" translations in rc, because there are no code changes needed in rc (apart from the occasional hotfix).

 

But is very difficult, in this open source project as much as any other open source project, to adapt and adhere to professional development methods, and get rid of the "hobby" mentality.

[Gringosat]

Completely agree with you!!!

Since OpnePLi is a big project things become complex and a more "professional method" is required to help every single component of the puzzle with benefits for all.

[Pr2]

Hi,

 

I have just generated both develop and rc branch whole po files here:

 

https://github.com/pr2git/enigma2

 

In it you will also find the latest:  enigma2.pot file.

 

@Dev,

 

I hope that you can pick-up the latest and up-to-date french translation from there and push then into your repo.

 

Pr2

[WanWizard]

@Dev,

 

I hope that you can pick-up the latest and up-to-date french translation from there and push then into your repo.

 

Meaning? Isn't creating a PR easier? Is that different from https://github.com/O...igma2/pull/1502 (just merged)?

[Pr2]

Hi,

 

I will continue to propose PR, forget about the idea to come an pick-up the update.

 

I have setup a script that create a branch, etc... automatically so I can always propose a clean PR with the translation.

Moreover I have also created another branch (ALL-po-update) where I publish all the po files updates and also the very latest enigma2.pot everything is based on OpenPLi develop branch. So translator can come and pick up the latest files from my github.

 

I am waiting for update in OpenPLi github to test if my script it is working fine.

 

Pr2

[Pr2]

Hi,

 

My script seems to do the job.

 

So from now it will be possible for translators to come an download the latest enigma2.pot file that I generate based on the develop branch of OpenPLi.

 

https://raw.githubus.../po/enigma2.pot

 

Or download the latest po files that they want to work on.

 

https://github.com/p...LL-po-update/po

 

Pr2

[Gringosat]

Hi,

 

My script seems to do the job.

 

So from now it will be possible for translators to come an download the latest enigma2.pot file that I generate based on the develop branch of OpenPLi.

 

https://raw.githubus.../po/enigma2.pot

 

Or download the latest po files that they want to work on.

 

https://github.com/p...LL-po-update/po

 

Pr2

 

Good job!!!

 

When the translation is completed I need to create a PR in your repo or do it as always again OpenPLi repos?

[Pr2]

No please create the PR towards OpenPLi github,  I just provide my repo to pick up the files instead of zipping them and publishing them on the forum.

[angelodos]

hello friends I leave you the es.po translated spanish when they can upload it to the git hub thanks

Attached Files

•  es.po.zip   77.88KB   2 downloads

[zeros]

https://github.com/O...igma2/pull/1521

 

[angelodos]

thanks friends

[Pr2]

Hi,

 

Based on your latest es.po I have put it into the RC branch and re-generate the file, can you please update it and submit this version to the RC branch so it will be included into OpenPLi 6.2 release-candidate.

 

 es.po-for-RC-branch.zip   78.5KB   3 downloads

 

Thanks,

 

Pr2

[MCelliotG]

So, to summarize we now have two different .pot files, one for develop and one for RC!

 

And in order to have OpenPLI update pass you need to upload two files to two different branches in github, am I correct?

[Pr2]

Yes you are correct, you can find both from my own repo:

 

For the develop branch:   https://raw.githubus.../po/enigma2.pot

 

For the rc branch:    https://raw.githubus.../po/enigma2.pot

 

If you want your translation in the OpenPli 6.2 you need to provide also update for the rc branch.

 

You can also find the updated po files from it.

 

Pr2

Edited by Pr2, 2 May 2018 - 19:54.

[angelodos]

Hi,

 

Based on your latest es.po I have put it into the RC branch and re-generate the file, can you please update it and submit this version to the RC branch so it will be included into OpenPLi 6.2 release-candidate.

 

es.po-for-RC-branch.zip

 

Thanks,

 

Pr2

ok no problem here you have it done

Attached Files

•  es.po.zip   78.83KB   1 downloads

[Pr2]

Thanks pull request created:

 

https://github.com/O...igma2/pull/1524

 

Pr2

[Pr2]

Hi,

 

You can find the po files updated from new OpenPLi branch "release-6.2" here:

 

https://github.com/p...2-po-updated/po

 

enigma2.pot file also proposed and updated.

 

Pr2

Edited by Pr2, 7 May 2018 - 21:22.