Mailing List Archive: GnuPG: devel

[STABLE-BRANCH-1-4 PATCHES] translation related helper, and a few typos

Index | Next | Previous | View Threaded

taffit at debian

Aug 6, 2012, 10:55 AM

Post #1 of 6 (144 views)
Permalink

[STABLE-BRANCH-1-4 PATCHES] translation related helper, and a few typos

Hi,

As agreed with Gaël Quéri, the former translator, I'm updating the
French translation of gnupg. I began to review and update the 1.4
branch, and have a few remarks and questions:

[PATCH 1/3] In order to help translators to update their files, using
the --previous option of msgmerge would be highly welcome.

[PATCH 2/3] A few translators notes didn't show up in the PO files.

[PATCH 3/3] Three minor typos spotted during the translation update and
review.

It would be nice to take care of the trivial unfuzzy when updating the
PO files after the typo fix (even if the first patch will minimize the
headache to translators), I can provide you a patch for that too if you
wish.

The first patch applies cleanly in the STABLE-BRANCH-2-0, the second one
needs some tweaks in scd/app-openpgp.c (I can send you the commit too),
and the third one is not needed (strings have disappeared).

Is it OK to send you patches attached to this list like I did, or do you
prefer a real “git send-email” stuff, maybe elsewhere?
Where should I send the updated PO files (<gnupg-i18n [at] gnupg> looks
inactive), and what is the preferred form (compressed PO file or git
commit)?

Gaël also asked me to make sure that messages can be displayed in an 80
colons terminal, but some have variable length (due to %s that can be as
long as user ID), and some strings are displayed after “gpg:” (by the
way, would it be possible to change this string, depending on the
localization?), so do you have a test suite or some advice to make sure
I didn't go off limits?

Regards

David

Attachments:

0001-Keep-previous-msgids-of-translated-messages.patch (0.78 KB)

0002-Actually-show-translators-comments-in-PO-files.patch (3.11 KB)

0003-Fix-typos-spotted-during-translations.patch (1.42 KB)

signature.asc (0.82 KB)

taffit at debian

Aug 22, 2012, 9:43 AM

Post #2 of 6 (120 views)
Permalink

Re: [STABLE-BRANCH-1-4 PATCHES] translation related helper, and a few typos [In reply to]

Hi,

Le 06/08/2012 13:55, David Prévot a écrit :

> As agreed with Gaël Quéri, the former translator, I'm updating the
> French translation of gnupg.

French translation now up to date for STABLE-BRANCH-1-4,
STABLE-BRANCH-2-0, and master branches. I'll send the updated PO files
to <gnupg-i18n [at] gnupg> after this ones and the similar ones I'm about
to post to -devel.

> [PATCH 3/3] Three minor typos spotted during the translation update and
> review.

Adding a 4th patch of the same kind, attached, fixing Syntax consistency.

> Is it OK to send you patches attached to this list like I did, or do you
> prefer a real “git send-email” stuff, maybe elsewhere?

I'll “git send-email” the similar patches against STABLE-BRANCH-2-0 and
master after that message.

Regards

David

Attachments:

0001-Fix-typos-spotted-during-translations.patch (0.81 KB)

signature.asc (0.82 KB)

wk at gnupg

Aug 24, 2012, 7:46 AM

Post #3 of 6 (121 views)
Permalink

Re: [STABLE-BRANCH-1-4 PATCHES] translation related helper, and a few typos [In reply to]

On Mon, 6 Aug 2012 19:55, taffit [at] debian said:

> [PATCH 1/3] In order to help translators to update their files, using
> the --previous option of msgmerge would be highly welcome.
>
> [PATCH 2/3] A few translators notes didn't show up in the PO files.
>
> [PATCH 3/3] Three minor typos spotted during the translation update and
> review.

All applied.

> It would be nice to take care of the trivial unfuzzy when updating the
> PO files after the typo fix (even if the first patch will minimize the

Does anyone know a tool for it? I sometimes don't fix types so not to
break translations.

> Is it OK to send you patches attached to this list like I did, or do you

THis is low traffic, thus I think it is okay.

> Where should I send the updated PO files (<gnupg-i18n [at] gnupg> looks
> inactive), and what is the preferred form (compressed PO file or git

I think a git commit is easier if there is already a commit messages.

> Gaël also asked me to make sure that messages can be displayed in an 80
> colons terminal, but some have variable length (due to %s that can be as

Well, sometimes it is not possible and thus messages will wrap. A logn
filename will trigger wrapping in most cases and you can't do anything
about it.

> long as user ID), and some strings are displayed after “gpg:” (by the
> way, would it be possible to change this string, depending on the

I don't think that this is a good idea. "foo:" shall be the name of the
program which is running - this name is not subject to translation. GUI
frontends may easily strip that prefix.

Salam-Shalom,

Werner

--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

taffit at debian

Aug 24, 2012, 8:04 AM

Post #4 of 6 (117 views)
Permalink

Re: [STABLE-BRANCH-1-4 PATCHES] translation related helper, and a few typos [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Werner,

Thanks for your answers,

Le 24/08/2012 10:46, Werner Koch a écrit :

>> It would be nice to take care of the trivial unfuzzy when updating the
>> PO files after the typo fix (even if the first patch will minimize the
>
> Does anyone know a tool for it? I sometimes don't fix types so not to
> break translations.

I now use msguntypot from po4a, but I used to do that with sed… I can
take of it if you wish.

>> what is the preferred form (compressed PO file or git
>
> I think a git commit is easier if there is already a commit messages.

Snap, i went the other way around, will send you a commit message ASAP.

>> long as user ID), and some strings are displayed after “gpg:” (by the
>> way, would it be possible to change this string, depending on the
>
> I don't think that this is a good idea. "foo:" shall be the name of the
> program which is running - this name is not subject to translation.

In French we should use “gpg :” (with a non-breaking space before the
colon), so it would be nice to make the colon translatable.

Regards

David

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQN5ftAAoJELgqIXr9/gny6q8P/0AdI6P/z8YTWJw/jNYhFFFk
nIYCEbKP6NAbVeWNuw/KG0TMOIBV1gyx2qfSijvLxF+jRLmK7gnIAf1d8gpVbMcs
wtzO78oTq4/5r1mCxBqZFXBhU5ksOVRhQ9a1db4HjoVjzTdPX+Ct06oKhFs8N45J
w5Ywk7pqThkFx4cR6aCxbQKhO6LtTAuxGe/eVbRhjo+xjZoD1zP1sTrbCoGBNzSu
RPp8pYxDETKKX/H2fIb8wXdRirGhs0QiEQLVHv3ay0w0CWX3CVfkFOODzBrPWQeX
+oclNhzNlUhzI7nW7KviSlvYA2GzsSS8DGicu/PU6v7lPnH1QftA2W/pf27U+uSn
sVSILYUb9KxOCHL84BHIGGs8fkTY3F8KOMZV8lWO+U/dnxSP7HEsbtqqURvbNAXG
oiRXzTzzTTKNnkaGlr7nyKWLQ7c6jRRzXEkzdWDAMSzjck6VCiJBdMKZ3Nqxmhv/
mAesId6gwpalaQCj3jEsDocKeUH/wARjQYd5wtH0ODQUE3DivwO28+y0BsE7aFPl
bBuD4pTZ3+yDnMZ8dfWzPybdWq/Z5eohy5UYR/wSQaFct8kAxClq+U+xJ59DaGRK
fQDFp/ftUWOfNHKhMk6tRb55lXwDY+6IrXJJGFn/nIHSZLBjx4EPcEbn4R10b8gP
2PKkwCHCYhaQ7Rij616Z
=D+8r
-----END PGP SIGNATURE-----

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

wk at gnupg

Aug 24, 2012, 8:56 AM

Post #5 of 6 (118 views)
Permalink

Re: [STABLE-BRANCH-1-4 PATCHES] translation related helper, and a few typos [In reply to]

On Fri, 24 Aug 2012 17:04, taffit [at] debian said:

> Snap, i went the other way around, will send you a commit message ASAP.

I already pushed them. Thanks for the offer.

> In French we should use “gpg :” (with a non-breaking space before the
> colon), so it would be nice to make the colon translatable.

Ah, that is the reason for underscores I noticed. How do other tools
handle it? IIRC, the GNU coding standards are quiet on that.

Shalom-Salam,

Werner

--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

nicholas.cole at gmail

Aug 24, 2012, 1:26 PM

Post #6 of 6 (118 views)
Permalink

Re: [STABLE-BRANCH-1-4 PATCHES] translation related helper, and a few typos [In reply to]

On Fri, Aug 24, 2012 at 4:56 PM, Werner Koch <wk [at] gnupg> wrote:
> On Fri, 24 Aug 2012 17:04, taffit [at] debian said:
>
>> Snap, i went the other way around, will send you a commit message ASAP.
>
> I already pushed them. Thanks for the offer.
>
>> In French we should use �gpg :� (with a non-breaking space before the
>> colon), so it would be nice to make the colon translatable.
>
> Ah, that is the reason for underscores I noticed. How do other tools
> handle it? IIRC, the GNU coding standards are quiet on that.
>
>
> Shalom-Salam,
>
> Werner

Careful about changing that string - scripts may look for "gpg:" as a
marker of particular messages. (eg. for messages that might need to be
relayed to users)

Within error messages themselves, of course it is reasonable to use
French conventions about spacing, but I don't think it is a good idea
to change the marker at the start of the string.

Best wishes,

Nicholas

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads