Re: (no subject)
- From: Havoc Pennington <hp redhat com>
- To: Christophe Fergeau <teuf users sourceforge net>
- Cc: gnome-i18n gnome org, desktop-devel list <desktop-devel-list gnome org>
- Subject: Re: (no subject)
- Date: Wed, 21 May 2003 15:54:39 -0400
On Wed, May 21, 2003 at 09:49:14PM +0200, Christophe Fergeau wrote:
> * translator point of view: when a maintainer updates all the po files
> in a module, it doesn't bring anything, and potentially ruins some
> translator work. The updated po files shouldn't be committed.
>
> * developer point of view: a tarball content must exactly match what is
> tagged in CVS. The updated po files must be committed, or the build
> tools must be fixed not to modify those po files (the build tools still
> need to check the validity of those files though).
There's another issue isn't there - if you never commit the modified
po files, when do the line numbers etc. in the po files ever get
updated? Do translators always do that themselves when they update a
translation?
The idea of having this in distcheck I think was so someone could take
the po files from the tarball and have up-to-date strings and line
numbers and do a translation.
Havoc
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]