[HEAD PATCH] Use ngettext where appropriate

Werner Koch wk at gnupg.org
Fri Dec 4 10:36:13 CET 2015

On Thu,  3 Dec 2015 11:03, fios at foramnagaidhlig.net said:

> Not applying an ngettext patch will be at the cost of all the Slavic
> languages and of Arabic, just to name a few examples. You should at the
> very least try to always use ngettext when marking up new strings for
> translation.

And for German as well.  We already have way too many translatable
strings (2111 as of today) and using ngettext all over the place would
add a lot more of these strings, code complexity and new bugs.

The majority of users are anyway using a frontend to gpg and thus I
believe it is better to properly translate those GUIs.



Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

More information about the Gnupg-i18n mailing list