Re: [Libexif-devel] Time for a libexif release

[Marcus M. <ma...@je...>]

On Mon, Nov 03, 2008 at 07:20:57PM -0800, Dan Fandrich wrote:
> On Mon, Nov 03, 2008 at 09:52:16PM +0100, Marcus Meissner wrote:
> > Only if you changed an exported interface. I think there wasn't one.
> 
> That makes it much easier.  The "REVISION" field should be bumped, though.
> 
> > Sync from the translation project before releasing:
> > 
> > 	rsync -Lrtvz  translationproject.org::tp/latest/libexif/  po
> 
> I took a look at the translations and it looks like they're all up to date.
> However, a number of the translations are not in sync with 
> translationproject.org because they were edited in the libexif CVS!  This
> is a big no-no now (as described in the README file).  Any local changes
> will be overwritten the next time a Translation Project volunteer updates
> a libexif translation.  All changes must now be made through TP, except for
> the ru and en_CA domains, which are the only ones handled exclusively through
> libexif's CVS.
> 
> These PO files all have local changes:
> 
> cs.po
> de.po
> es.po
> fr.po
> ru.po
> sv.po

Ok, what I found out during libgphoto2 <-> translation project communication:

- NEVER EVER RUN "make update-po".
	(I think for local translations this can be done, but not for externals.)
- If you did "make dist", the POT file was regenerated and included into the
  tarball.
  You should commit the POT file at this time, but the update language.po files
  should probably be reverted.

- Once the translation project has synced the release:
	-> fetch the language.po files from the translation project
	-> commit them.

This way you will get only diffs from the translation project.

Local translated languages can of course run make update-po , but should just
commit their PO file, nothing else.

Ciao, Marcus