Re: Updating po files on make dist

["R.I.P. Deaddog" <deaddog deaddog org>]

On 2003-05-21(Wed) 22:09:38 +0200, Christian Rose wrote:
> In all other cases, committing po files that were touched by make dist
> is just a nuisance that most translators would want to go away as soon
> as possible (see below).

Not only that, sometimes translations can be ruined by committing
touched po files by make dist. This doesn't happen often, but it does
occur sometimes. Probably some maintainers were still using old version
of gettext/intltool. I have seen jrb reverting the broken po files for
several times.

Abel


> > On the other hand, if a translator has a modified po file on his
> > computer that he hasn't committed yet, the next time he cvs updates,
> > he'll get a conflict for most of the strings in this file, which makes
> > resolving the conflicts next to impossible.
> 
> This unfortunately happens quite often, and correctly resolving such
> conflicts is in many cases non-trivial. And the problem is even more
> worrying as most "make dist touched the po file" commits are totally
> unnecessary. They also make unnecessary garbage for someone trying to
> follow cvs history for a po file.
> 
> 
> Christian
> 
> 
> _______________________________________________
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> http://lists.gnome.org/mailman/listinfo/gnome-i18n

-- 
Abel Cheung
GPG Key: (0xC67186FF) http://deaddog.org/gpg.asc
Key fingerprint: 671C C7AE EFB5 110C D6D1  41EE 4152 E1F1 C671 86FF

PGP signature