On Thu, 2005-02-17 at 13:42, Jeremy Katz wrote:
On Thu, 2005-02-17 at 13:12 +1000, Sarah Wang wrote:
>a. Let each package maintainer perform "msgmerge" whenever pot file is
This is doable, I just think it causes pain for translators due to CVS
If this is doable and all pkg maintainers are disciplined enough, I
certainly think it's the best solution.
>b. I set up a cron job to "msgmerge" all locales and all packages
>(nightly or weekly)
This causes lots of noise for developers trying to actually watch CVS
commits. And in cases where things haven't changed, it's kind of
counter-productive because gettext isn't all that smart about noticing
that things haven't really changed.
>c. Each locale coordinator to ensure all packages in that locale is
>consistent and up to date
>d. Each translator to perform "msgmerge" prior translation
c/d seem like the best from a perspective of minimizing changes and
It won't work for those locales don't have a
in case the translators are not very Technical but have good languages
skills. We still want people to join the project and work on the latest
>Personally I prefer option b, because I can ensure all updates will be
>performed. The downside of it is the possible file conflicts. However,
>if we agree upon a specific time to perform this update, and we all try
>to avoid this time to commit works, most conflicts can be avoided.
It's not a matter of avoiding the time to commit works, you have to
avoid _working_ on things then. And if you have something underway
that's not committed, you have to do silly tricks with copying your
work, cvs updating and then re-msgmerge'ing.
Sure, dealing with conflicts are always quite painful ;) I don't enjoy
it either. I'm happy to adopt the option that is most effective and