mirror of
git://git.gnupg.org/gnupg.git
synced 2025-07-02 22:46:30 +02:00
Preparing a release
This commit is contained in:
parent
99c80f8c39
commit
862652ebe1
5 changed files with 12 additions and 17 deletions
|
@ -35,25 +35,17 @@ Content-Type: multipart/mixed; boundary="=-=-="
|
|||
|
||||
Hi!
|
||||
|
||||
We are preparing for the 1.4 release of GnuPG and like you to ask to
|
||||
start with the translation. The recent release 1.3.91
|
||||
(ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.3.91.tar.bz2) won't be
|
||||
the last one before 1.4 and experience has shown that we will still
|
||||
need to change some strings on the way to 1.4. However due to a lot
|
||||
of fuzzy entries and about 110 new strings it would be good to start
|
||||
translating right now but wait with sending the translation back. We
|
||||
will tell when we think that we are ready and provide a new POT file
|
||||
for merging with your current translation.
|
||||
We are preparing for a new 1.4 release of GnuPG and like you to ask to
|
||||
update your translation.
|
||||
|
||||
Please find attached the very latest version of the PO file for your
|
||||
GnuPG translation ($file) from 1.3.91.
|
||||
GnuPG translation ($file).
|
||||
|
||||
IMHO it is important to have a basic understanding of GnuPG's
|
||||
functionality to do a correct translation. A false translation might
|
||||
lead to security problems. Furthermore the TP Robot is not able to
|
||||
handle more than one version of a project (we have 1.2, 1.3 and also
|
||||
1.9) and thus I'd ask you *not to use the TP Robot* for 1.3.x or
|
||||
1.4.x.
|
||||
handle more than one version of a project (we have 1.2, 1.4 and also
|
||||
1.9) and thus I'd ask you *not to use the TP Robot* for GnuPG.
|
||||
|
||||
Output of msgfmt is:
|
||||
$(msgfmt --check --statistics $file 2>&1 | head)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue