Hi,
I'd like to start translating postorius in french, where should I start? I've cloned the repository and I'm ready to generate the catalogs. Can I just translate it and submit it somewhere?
Thanks,
Guillaume PS: Please cc, I'm not subscribed to the list
-- Fabrique collective de biens communs -- http://unisson.co Faire un don : https://www.gittip.com/UnissonCo/
Guillaume Libersat writes:
I'd like to start translating postorius in french, where should I start? I've cloned the repository and I'm ready to generate the catalogs. Can I just translate it and submit it somewhere?
Thank you!
The usual procedure is to set up an account on Launchpad, push your code to your account as a branch of the mainline, and make a merge request through Launchpad. You can also announce your branch and your progress here to get testing. Once you have a pretty significant fraction of the work done, you can announce on mailman-users, as that has many more subscribers and presumably a lot more French speakers, too.
Steve
Hi Steve,
Le 15/10/2014 19:49, Stephen J. Turnbull a écrit :
The usual procedure is to set up an account on Launchpad, push your code to your account as a branch of the mainline, and make a merge request through Launchpad. You can also announce your branch and your progress here to get testing. Once you have a pretty significant fraction of the work done, you can announce on mailman-users, as that has many more subscribers and presumably a lot more French speakers, too. Ok, thanks for your advice! I've done exactly what you said, here's the beginning of the work: https://code.launchpad.net/~glibersat/postorius/i18n-french
I hope to finish the translation in a few days. I've also added a few "trans" tags so more strings are now internationalized.
Thanks!
Guillaume PS: I'm now subscribed to this list.
Guillaume Libersat writes:
Ok, thanks for your advice! I've done exactly what you said, here's the beginning of the work: https://code.launchpad.net/~glibersat/postorius/i18n-french
Great!
I hope to finish the translation in a few days. I've also added a few "trans" tags so more strings are now internationalized.
AFAIK Mailman in the past has given free reign to the translators on existing translations, but adding new translations (if I understand what you mean by "adding 'trans' tags") is subject to review by other developers, and eventually Florian and Terri. I don't know if it applies to the Postorius code, but I know I've run into situations where it was undesirable to use the internationalization mechanism to translate certain strings.
It is very helpful to the maintainers when reviewing and integrating if you make separate commits for the translations themselves, and for changes to the originals. It's even better if you keep separate kinds of changes in separate branches. (This is very cheap for Launchpad; they use "stacked branches" to minimize the work done to create a new branch.)
It occurs to me that if you are adding new translations, it might be a good idea even to do a separate commit for each one, including both the markup at the original string and the French translation.
Note that I'm not a Postorius maintainer, nor the project lead, and I've also not done translation work myself. So I don't know how much burden these guidelines put on you. They aren't "rules" (at least not until Florian or Terri says so!), but it would be helpful to the project if you consider using them in your work to make the integration side go more smoothly.
Thank you for your consideration, and thanks again for the translations!
Hi,
Le 16/10/2014 02:49, Stephen J. Turnbull a écrit :
AFAIK Mailman in the past has given free reign to the translators on existing translations, but adding new translations (if I understand what you mean by "adding 'trans' tags") is subject to review by other developers, and eventually Florian and Terri. I don't know if it applies to the Postorius code, but I know I've run into situations where it was undesirable to use the internationalization mechanism to translate certain strings.
It is very helpful to the maintainers when reviewing and integrating if you make separate commits for the translations themselves, and for changes to the originals. It's even better if you keep separate kinds of changes in separate branches. (This is very cheap for Launchpad; they use "stacked branches" to minimize the work done to create a new branch.)
It occurs to me that if you are adding new translations, it might be a good idea even to do a separate commit for each one, including both the markup at the original string and the French translation.
Note that I'm not a Postorius maintainer, nor the project lead, and I've also not done translation work myself. So I don't know how much burden these guidelines put on you. They aren't "rules" (at least not until Florian or Terri says so!), but it would be helpful to the project if you consider using them in your work to make the integration side go more smoothly.
Thank you for your consideration, and thanks again for the translations!
I've done exactly what you said (splitting commits between effective translation work and code/template instrumentation) and submitted a Merge Request there ( https://code.launchpad.net/~glibersat/postorius/i18n-french/+merge/240066 ).
I hope it's gonna be merged soon :)
Cheers,
Guillaume
Guillaume Libersat writes:
I've done exactly what you said (splitting commits between effective translation work and code/template instrumentation) and submitted a Merge Request there ( https://code.launchpad.net/~glibersat/postorius/i18n-french/+merge/240066 ).
Thank you! My, that was fast!
I hope it's gonna be merged soon :)
Me too, but I don't "own" that repo.
Florian? Terri? Can you review soon?
Steve
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/30/2014 04:47 AM, Stephen J. Turnbull wrote:
Guillaume Libersat writes:
I've done exactly what you said (splitting commits between effective translation work and code/template instrumentation) and submitted a Merge Request there ( https://code.launchpad.net/~glibersat/postorius/i18n-french/+merge/240066 ).
Thank you! My, that was fast!
+1
Thank you very much!
I hope it's gonna be merged soon :)
Me too, but I don't "own" that repo.
Florian? Terri? Can you review soon?
Yes, I can do a review. I'll let you know once it's merged...
Florian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEcBAEBAgAGBQJUUpvNAAoJEEceGbPdavl7Qp0H/3+KUV0ebSg7H+UcJRuLac1J kOV1FeQrY4WwDevF4T21fKCGcCsrMpNIWqYIP457eovNkvmXIAJ6u0F7scmdQiNi 4WGmzFgdU+4g64lEzm9eJmzCg0t8GhdHUnPLWIFgh5k29ukrpU4UPZQvhFH7wBgl +7euN6BQUKYVIcfo8yKnU8OdVHg8BsOCuu0YuwZ7r1ckIK+rdaEtYktYnHkmc8Ek NM/s2AXiG4ppVAl0cgbG63ECpnYxy3ca0d9tAgYPWLm5db6lniOjLnOUEnW+hWeK DUf7xZRllu8yuapd86w2aXRNg1tfKQk0KldUKZWUK8pfUjVULvFcwjWSeFsDI7s= =PRo0 -----END PGP SIGNATURE-----
participants (4)
-
Florian Fuchs -
Guillaume Libersat -
Guillaume Libersat -
Stephen J. Turnbull