Re: Coordinating package meta-data translation

[Ludovic Courtès]

Saluton Benno,

Benno Schulenberg <address@hidden> skribis:

> On 2014-06-13 17:38, Ludovic Courtès wrote:
>> I’ve just done that:
>> 
>>   
>> http://git.savannah.gnu.org/cgit/guix.git/commit/?id=ee76417972b3a749a28a627c2858c09311d9c0c5
>
> Okay.  The setup is a bit unusual, but... if it works.
> (What gettext probably expects is that po is a subdir of the guix
> subdir, and that packages is another subdir of that guix subdir,
> which (packages) then has its own po subdir.)

Yup it works, and I prefer it this way.

>> How should I proceed to:
>> 
>>   1. register the new text domain at the TP?
>
> Slowly!  :)  First let's see what the POT files look like now.
> Could you build a preprepre-release tarball and post a URL?
> After also having done point 2, of course.

Here it is:

  http://www.fdn.fr/~lcourtes/software/guix/guix-0.6.90.tar.gz
  SHA1: 0add82cffccde09aa0801e0974aaa61e29dc8bef
  http://www.fdn.fr/~lcourtes/software/guix/guix-0.6.90.tar.gz.sig

>>   2. extract already-translated synopses/descriptions and move them to
>>      po/packages/*.po?
>
> First build the POT files, and then change into the po/guix subdir
> and run:
>
> for file in *.po;
>   do  msgmerge $file ../packages/packages.pot  >../packages/$file;
> done

Done:

  
http://git.sv.gnu.org/cgit/guix.git/commit/?id=240a2775ded34730607b00eb1a77f2d1989f4011

> That's all.  You could filter out all the obsolete messages, to have
> nice clean files, but you can leave that to the translators too.

Let’s do that, then.  ;-)

Thanks for helping out!

Ludo’.