Translation inclusion criteria
Hi, I've followed the instructions in git-gui/po/README in 2008 but
pt.po was never included in master. Now I've just updated it.
Is there anything else I should do for it being merged to master? What is the criteria for including new translations?
Thanks in advance,
Rodrigo.
Quoted 5 lines · Rodrigo Rosenfeld Rosas
Hi, I've followed the instructions in git-gui/po/README in 2008 but pt.po was never included in master. Now I've just updated it.
Is there anything else I should do for it being merged to master? What is the criteria for including new translations?
Rodrigo,
Internationalization of Git is very much an ongoing process. I suspect that has something to do with the uptake of your contribution. Ævar may have more information.
Signature · 4 lines
-Drew Northup ________________________________________________ "As opposed to vegetable or mineral error?" -John Pescatore, SANS NewsBites Vol. 12 Num. 59
Quoted 11 lines · Drew Northup
Quoted 5 lines · Rodrigo Rosenfeld Rosas
Hi, I've followed the instructions in git-gui/po/README in 2008 but pt.po was never included in master. Now I've just updated it.
Is there anything else I should do for it being merged to master? What is the criteria for including new translations?
...
Rodrigo,
Internationalization of Git is very much an ongoing process. I suspect that has something to do with the uptake of your contribution. Ævar may have more information.
All the git-gui changes come through Pat Thoyts these days; Ævar has nothing to with git-gui i18n/l10n (except perhaps as a translator to his own language, but I don't see his name in the shortlog).
Perhaps the submission was sent with wrong Cc:; I don't pay attention to git-gui and gitk l10n patches myself.
Em 29-03-2011 15:59, Junio C Hamano escreveu:
Quoted 13 lines
Quoted 11 lines · Drew Northup
Quoted 5 lines · Rodrigo Rosenfeld Rosas
Hi, I've followed the instructions in git-gui/po/README in 2008 but pt.po was never included in master. Now I've just updated it.
Is there anything else I should do for it being merged to master? What is the criteria for including new translations?
...
Rodrigo,
Internationalization of Git is very much an ongoing process. I suspect that has something to do with the uptake of your contribution. Ævar may have more information.
Quoted 6 lines
All the git-gui changes come through Pat Thoyts these days; Ævar has nothing to with git-gui i18n/l10n (except perhaps as a translator to his own language, but I don't see his name in the shortlog).
Perhaps the submission was sent with wrong Cc:; I don't pay attention to git-gui and gitk l10n patches myself.
Sorry, I think I'm missing something. From the mentioned README, it seems we're supposed to push our changes to the mob branch of [email protected]:/srv/git/git-gui/git-gui-i18n.git/, which has write access enabled for everyone.
That's what I've done. I couldn't find any mention in the README about having to send some mail after that.
I'll wait for instructions from Pat Thoyts to understand better what should be my next step...
Thanks,
Rodrigo.
Quoted 29 lines · Rodrigo Rosenfeld Rosas
Em 29-03-2011 15:59, Junio C Hamano escreveu:
Quoted 13 lines
Quoted 11 lines · Drew Northup
Quoted 5 lines · Rodrigo Rosenfeld Rosas
Hi, I've followed the instructions in git-gui/po/README in 2008 but pt.po was never included in master. Now I've just updated it.
Is there anything else I should do for it being merged to master? What is the criteria for including new translations?
...
Rodrigo,
Internationalization of Git is very much an ongoing process. I suspect that has something to do with the uptake of your contribution. Ævar may have more information.Quoted 6 lines
All the git-gui changes come through Pat Thoyts these days; Ævar has nothing to with git-gui i18n/l10n (except perhaps as a translator to his own language, but I don't see his name in the shortlog).
Perhaps the submission was sent with wrong Cc:; I don't pay attention to git-gui and gitk l10n patches myself.
Sorry, I think I'm missing something. From the mentioned README, it seems we're supposed to push our changes to the mob branch of [email protected]:/srv/git/git-gui/git-gui-i18n.git/, which has write access enabled for everyone.
That's what I've done. I couldn't find any mention in the README about having to send some mail after that.
Quoted 6 lines
I'll wait for instructions from Pat Thoyts to understand better what should be my next step...
Thanks,
Rodrigo.
It's best to just send a patch to me and this list based against one of the current branches (master/maint/pu). The i18n fork was done for the original work adding i18n to git-gui and hasn't been kept up to date since 2008.
Signature · 2 lines
Pat Thoyts http://www.patthoyts.tk/ PGP fingerprint 2C 6E 98 07 2C 59 C8 97 10 CE 11 E6 04 E0 B9 DD
Em 30-03-2011 10:08, Pat Thoyts escreveu:
Quoted 33 lines
Quoted 31 lines · Rodrigo Rosenfeld Rosas
Em 29-03-2011 15:59, Junio C Hamano escreveu:
Quoted 13 lines
Quoted 11 lines · Drew Northup
Quoted 5 lines · Rodrigo Rosenfeld Rosas
Hi, I've followed the instructions in git-gui/po/README in 2008 but pt.po was never included in master. Now I've just updated it.
Is there anything else I should do for it being merged to master? What is the criteria for including new translations?
...
Rodrigo,
Internationalization of Git is very much an ongoing process. I suspect that has something to do with the uptake of your contribution. Ævar may have more information.Quoted 6 lines
All the git-gui changes come through Pat Thoyts these days; Ævar has nothing to with git-gui i18n/l10n (except perhaps as a translator to his own language, but I don't see his name in the shortlog).
Perhaps the submission was sent with wrong Cc:; I don't pay attention to git-gui and gitk l10n patches myself.
Sorry, I think I'm missing something. From the mentioned README, it seems we're supposed to push our changes to the mob branch of [email protected]:/srv/git/git-gui/git-gui-i18n.git/, which has write access enabled for everyone.
That's what I've done. I couldn't find any mention in the README about having to send some mail after that.
I'll wait for instructions from Pat Thoyts to understand better what should be my next step...
Quoted 7 lines
Quoted 3 lines
Thanks,
Rodrigo.
It's best to just send a patch to me and this list based against one of the current branches (master/maint/pu). The i18n fork was done for the original work adding i18n to git-gui and hasn't been kept up to date since 2008.
Ok, thanks. I've just noticed pt_br.po was already included some days ago on March 26 by Junio Hamano and it is up-to-date in the master branch.
But it would be great to update the README to replace those instructions regarding [email protected] by the new instruction for sending the patches by e-mail.
Best regards,
Rodrigo.
Quoted 46 lines · Rodrigo Rosenfeld Rosas
Em 30-03-2011 10:08, Pat Thoyts escreveu:
Quoted 33 lines
Quoted 31 lines · Rodrigo Rosenfeld Rosas
Em 29-03-2011 15:59, Junio C Hamano escreveu:
Quoted 13 lines
Quoted 11 lines · Drew Northup
Quoted 5 lines · Rodrigo Rosenfeld Rosas
Hi, I've followed the instructions in git-gui/po/README in 2008 but pt.po was never included in master. Now I've just updated it.
Is there anything else I should do for it being merged to master? What is the criteria for including new translations?
...
Rodrigo,
Internationalization of Git is very much an ongoing process. I suspect that has something to do with the uptake of your contribution. Ævar may have more information.Quoted 6 lines
All the git-gui changes come through Pat Thoyts these days; Ævar has nothing to with git-gui i18n/l10n (except perhaps as a translator to his own language, but I don't see his name in the shortlog).
Perhaps the submission was sent with wrong Cc:; I don't pay attention to git-gui and gitk l10n patches myself.
Sorry, I think I'm missing something. From the mentioned README, it seems we're supposed to push our changes to the mob branch of [email protected]:/srv/git/git-gui/git-gui-i18n.git/, which has write access enabled for everyone.
That's what I've done. I couldn't find any mention in the README about having to send some mail after that.
I'll wait for instructions from Pat Thoyts to understand better what should be my next step...
Quoted 7 lines
Quoted 3 lines
Thanks,
Rodrigo.
It's best to just send a patch to me and this list based against one of the current branches (master/maint/pu). The i18n fork was done for the original work adding i18n to git-gui and hasn't been kept up to date since 2008.
Ok, thanks. I've just noticed pt_br.po was already included some days ago on March 26 by Junio Hamano and it is up-to-date in the master branch.
Quoted 7 lines
But it would be great to update the README to replace those instructions regarding [email protected] by the new instruction for sending the patches by e-mail.
Best regards,
Rodrigo.
Thank you - I had not noticed the directions in the po/README file. I've now committed an update that encourages translators to mail a patch series. Sorry for any confusion caused by this.
Signature · 2 lines
Pat Thoyts http://www.patthoyts.tk/ PGP fingerprint 2C 6E 98 07 2C 59 C8 97 10 CE 11 E6 04 E0 B9 DD