Re: [Gramps-devel] gramps.pot - how to get it?

[Kees B. <kee...@xs...>]

Op vrijdag 18 augustus 2006 22:14, schreef Alex Roitman:
> Kees,
> 
> On Fri, 2006-08-18 at 21:55 +0200, Kees Bakker wrote:
> > On the wiki, in the TipsForTranslators, there is a note about gramps.pot
> > However I'm a bit confused as to what the procedure these days is. Also
> > in the section "Updating your translation" it talks about template.po.
> 
> The wiki is describing the stable series. We've changed to intltool
> in the 2.1/2.2 so things are slightly different. The gramps.pot file
> is not under svn now. To generate it, do 'make gramps.pot' in the
> po directory.

AFAIK the stable series needed a template.op, not gramps.pot. At the top of that
page it says:
  "Tips for translators of 2.1/2.2 branch"
That's not the stable branch is it?

> 
> > Here is what I did. Maybe someone can comment on it whether this is the
> > Right Thing to do.
> > 
> > 1) Start with a fresh copy from SVN:
> >     svn co https://svn.sourceforge.net/svnroot/gramps/trunk/gramps2
> >     cd gramps2
> > 2) Run autogen
> >     ./autogen.sh
> 
> So far so good.
> 
> > 3) Create gramps.pot:
> >     (cd po;
> >      INTLTOOL_EXTRACT=../intltool-extract srcdir=. ../intltool-update --gettext-package gramps --pot
> >     )
> 
> Sure. Or just: cd po; make gramps.pot

Ah, you're right. I tried it before doing autogen.sh. Now it works.

> 
> > 4) Update the po file using the old one:
> >     (cd po;
> >      msgmerge --no-wrap XX.po gramps.pot  -o newXX.po
> >     )
> 
> Sounds good. You can also do 'make update-po' but this will
> generate gramps.pot and then update *every* po file, which
> is a lot of CPU load.
> 
> > Now I'm ready to edit the newXX.po contents.
> 
> Yep.
> 
> If this is any help, the released tarballs for 2.1.90 and 2.1.91
> have already up-to-date po files (with respect to the code
> released in those same tarballs).  So unless you're really on
> the cutting edge and want to have the latest SVN translated,
> you may just use those po files without any hassle. Whatever
> works for you :-)

I'm not sure what you mean with "already up-to-date po files".
Right now I'm looking at the nl.po and it needs a bit of work.

Oh, I also want to mention check_po. So after editing I do:
  (cd po;./check_po newXX.po)
and it should report 0 errors, right?

I now have:
kees@spirit:/loc/kees/packages-gramps/gramps2.work> (cd po;./check_po newnl.po)
File:            newnl.po
Template total:  2808
PO total:        2808
Fuzzy:           590
Untranslated:    384
%s mismatches:   0
%()s mismatches: 0
%() missing s/d: 0
Runaway context: 0
PO Coverage:     86.32%
Template Coverage:  86.32%

That is a big improvement from the nl.po which is in SVN.

- Kees