[HEAD PATCH] Use ngettext where appropriate

Ineiev ineiev at gnu.org
Fri Dec 4 12:44:10 CET 2015


On Fri, Dec 04, 2015 at 10:36:13AM +0100, Werner Koch wrote:
> 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.

I don't think this is correct. I've just run msgfmt --statistics for
gnupg2.pot regenerated before and after applying the submitted patch.
before the patch it shows 2111 strings, after patch the count is 2102.
the difference is less than 0.5% (and it's negative). it hardly can
add considerable complexity. (of course I can further rewrite
the patch to eliminate new messages in some cases.)

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

I'm afraid I don't see the point. it isn't either-or: frontends
can properly internationalize their GUIs, and GnuPG can properly
internationalize it's own messages, at the same time.

Thank you!

More information about the Gnupg-i18n mailing list