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

[Werner Koch]

On Mon,  6 Aug 2012 19:55, taffit at debian.org 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.org> 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.