Re: (no subject)

[Christian Rose <menthos gnome org>]

ons 2003-05-21 klockan 21.54 skrev Havoc Pennington:
> > * 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?

Yes. When translators update po files[1], they always run
"intltool-update xy" first, where 'xy' is the language code, which
essentially does what make dist would do to the specific po file in
question: It updates the source references, makes the messages in the po
file match those that are used at that time in the source, and performs
fuzzy matching, etc.
So when po files are updated by translators, they are always regenerated
to match the latest state first.

Some translators pick the po files from the translation status pages [2]
but those are also regenerated and matched with cvs sources with
intltool several times a day when the status pages are updated.


> 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.

They can have it up-to-date anyway by just running "intltool-update xy"
first.


Christian



[1] http://developer.gnome.org/doc/tutorials/gnome-i18n/translator.html
[2] http://developer.gnome.org/projects/gtp/status/