From: Benno Schulenberg <coordinator@translationproject.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Benno Schulenberg <coordinator@translationproject.org>,
guix-devel@gnu.org, web-translators@gnu.org
Subject: Re: Coordinating package meta-data translation
Date: Sat, 14 Jun 2014 17:49:12 +0200 [thread overview]
Message-ID: <539C6EF8.5080500@translationproject.org> (raw)
In-Reply-To: <87fvj8kefg.fsf@gnu.org>
Hello Ludo,
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.)
> 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.
> 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
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.
Benno
next prev parent reply other threads:[~2014-06-14 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 21:00 Coordinating package meta-data translation Ludovic Courtès
2014-06-08 8:30 ` Benno Schulenberg
2014-06-08 22:07 ` Ludovic Courtès
2014-06-12 20:14 ` Benno Schulenberg
2014-06-12 21:49 ` Ludovic Courtès
2014-06-14 15:52 ` Benno Schulenberg
2014-06-13 15:38 ` Ludovic Courtès
2014-06-14 15:49 ` Benno Schulenberg [this message]
2014-06-14 20:57 ` Ludovic Courtès
2014-06-15 20:10 ` Benno Schulenberg
2014-06-16 22:35 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=539C6EF8.5080500@translationproject.org \
--to=coordinator@translationproject.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=web-translators@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).