I understood a thing: the github po file (https://github.com/geany/geany/blob/master/po/pt_BR.po) seems outdated -> the line numbers for the string in the code don't correspond to the entries in the .po file (as in po/pt_BR.po). That seems is very strange to me, as the references to line numbers in the code from http://i18n.geany.org/pt_BR.po corresponds to the code in https://github.com/geany/geany (the po/ there is outdated, but there are recent commits involving the files...)
On Sun, 17 May 2015 14:18:19 -0300 Felipe Braga fbobraga@gmail.com wrote:
The http://i18n.geany.org/ have a pt_BR.po very different for github (at https://github.com/geany/geany/blob/master/po/pt_BR.po).
What is the "correct" way to update a translation: sending the updated .po file by mail, or fork/update/make pull request in github?
Thanks
Felipe Braga fbobraga@gmail.com
Hi,
Am 17.05.2015 um 20:59 schrieb Felipe Braga:
I understood a thing: the github po file (https://github.com/geany/geany/blob/master/po/pt_BR.po) seems outdated -> the line numbers for the string in the code don't correspond to the entries in the .po file (as in po/pt_BR.po). That seems is very strange to me, as the references to line numbers in the code from http://i18n.geany.org/pt_BR.po corresponds to the code in https://github.com/geany/geany (the po/ there is outdated, but there are recent commits involving the files...)
The po file inside git master is only updated right in front of an upcoming release aka "string freeze" or if there is an update done. Everything else would cause a to high noise as changing only few lines inside code will cause an patchset of maybe 500 lines per translation. A solution like transiflex is not yet in place.
The po file which can be downloaded from i18n.geany.org is generated on daily basis based on github's master branch and therefore is up to date. But: As you need to compile latest version of po file together with corresponding sources of Geany to test your translations I recommend to clone the master tree of Geany and build it from sources. Running ./waf updatepo or make update-po (inside po folder) will update the translations catalogue as well as all po files.
If you have updated the po-file please send either a PR via github or the complete po-file to either me directly or the i18n mailing list.
Also: There have been updates on pt translation. Maybe you can use it for updating pt_BR translation.
Cheers, Frank
Ok
On Sun, 17 May 2015 21:09:32 +0200 Frank Lanitz frank@frank.uvena.de wrote:
Hi,
Am 17.05.2015 um 20:59 schrieb Felipe Braga:
I understood a thing: the github po file (https://github.com/geany/geany/blob/master/po/pt_BR.po) seems outdated -> the line numbers for the string in the code don't correspond to the entries in the .po file (as in po/pt_BR.po). That seems is very strange to me, as the references to line numbers in the code from http://i18n.geany.org/pt_BR.po corresponds to the code in https://github.com/geany/geany (the po/ there is outdated, but there are recent commits involving the files...)
The po file inside git master is only updated right in front of an upcoming release aka "string freeze" or if there is an update done. Everything else would cause a to high noise as changing only few lines inside code will cause an patchset of maybe 500 lines per translation. A solution like transiflex is not yet in place.
The po file which can be downloaded from i18n.geany.org is generated on daily basis based on github's master branch and therefore is up to date. But: As you need to compile latest version of po file together with corresponding sources of Geany to test your translations I recommend to clone the master tree of Geany and build it from sources. Running ./waf updatepo or make update-po (inside po folder) will update the translations catalogue as well as all po files.
If you have updated the po-file please send either a PR via github or the complete po-file to either me directly or the i18n mailing list.
I will finish the translation, test it, and make the PR
Also: There have been updates on pt translation. Maybe you can use it for updating pt_BR translation.
Hm, it sounds helpful :-)
Cheers, Frank
Completed translation and corrections, and created https://github.com/geany/geany/pull/498
* I will also attach the resulting file, in expect to be helpful :-)
On Sun, 17 May 2015 17:35:57 -0300 Felipe Braga fbobraga@gmail.com wrote:
Ok
On Sun, 17 May 2015 21:09:32 +0200 Frank Lanitz frank@frank.uvena.de wrote:
Hi,
Am 17.05.2015 um 20:59 schrieb Felipe Braga:
I understood a thing: the github po file (https://github.com/geany/geany/blob/master/po/pt_BR.po) seems outdated -> the line numbers for the string in the code don't correspond to the entries in the .po file (as in po/pt_BR.po). That seems is very strange to me, as the references to line numbers in the code from http://i18n.geany.org/pt_BR.po corresponds to the code in https://github.com/geany/geany (the po/ there is outdated, but there are recent commits involving the files...)
The po file inside git master is only updated right in front of an upcoming release aka "string freeze" or if there is an update done. Everything else would cause a to high noise as changing only few lines inside code will cause an patchset of maybe 500 lines per translation. A solution like transiflex is not yet in place.
The po file which can be downloaded from i18n.geany.org is generated on daily basis based on github's master branch and therefore is up to date. But: As you need to compile latest version of po file together with corresponding sources of Geany to test your translations I recommend to clone the master tree of Geany and build it from sources. Running ./waf updatepo or make update-po (inside po folder) will update the translations catalogue as well as all po files.
If you have updated the po-file please send either a PR via github or the complete po-file to either me directly or the i18n mailing list.
I will finish the translation, test it, and make the PR
Also: There have been updates on pt translation. Maybe you can use it for updating pt_BR translation.
Hm, it sounds helpful :-)
Cheers, Frank
Am 17.05.2015 um 21:09 schrieb Frank Lanitz:
Hi,
Am 17.05.2015 um 20:59 schrieb Felipe Braga:
I understood a thing: the github po file (https://github.com/geany/geany/blob/master/po/pt_BR.po) seems outdated -> the line numbers for the string in the code don't correspond to the entries in the .po file (as in po/pt_BR.po). That seems is very strange to me, as the references to line numbers in the code from http://i18n.geany.org/pt_BR.po corresponds to the code in https://github.com/geany/geany (the po/ there is outdated, but there are recent commits involving the files...)
The po file inside git master is only updated right in front of an upcoming release aka "string freeze" or if there is an update done. Everything else would cause a to high noise as changing only few lines inside code will cause an patchset of maybe 500 lines per translation. A solution like transiflex is not yet in place.
Just an example: I've just update one string inside German translation and regenerated po-file for it: [master 7553815] Small Update of German translation 1 file changed, 199 insertions(+), 209 deletions(-)
Cheers, Frank
Am 17.05.2015 um 23:51 schrieb Felipe Braga:
Completed translation and corrections, and created https://github.com/geany/geany/pull/498
- I will also attach the resulting file, in expect to be helpful :-)
Looks good so far. (I cannot say anthing about translations it self, but file looks good ;) ). Going to merge it.
Next time maybe you could also update the copyright string and version string on header of file. But this is not this important.
Cheers, Frank
On Mon, 18 May 2015 08:24:58 +0200 Frank Lanitz frank@frank.uvena.de wrote:
Am 17.05.2015 um 23:51 schrieb Felipe Braga:
Completed translation and corrections, and created https://github.com/geany/geany/pull/498
- I will also attach the resulting file, in expect to be helpful :-)
Looks good so far. (I cannot say anthing about translations it self, but file looks good ;) ). Going to merge it.
Next time maybe you could also update the copyright string and version string on header of file. But this is not this important.
Cheers, Frank
Sorry about that: created another PR on https://github.com/geany/geany/pull/500 :-)