From wk at gnupg.org Wed Dec 2 18:12:51 2015 From: wk at gnupg.org (Werner Koch) Date: Wed, 02 Dec 2015 18:12:51 +0100 Subject: [HEAD PATCH] Use ngettext where appropriate In-Reply-To: <20151020070834.GA10871@gnu.org> (ineiev@gnu.org's message of "Tue, 20 Oct 2015 03:08:34 -0400") References: <20151020070834.GA10871@gnu.org> Message-ID: <87mvtsn59o.fsf@vigenere.g10code.de> On Tue, 20 Oct 2015 09:08, ineiev at gnu.org said: > I attach a patch against current HEAD to make use > of ngettext in some places; it also marks two more messages > localizable. At the cost of translating a lot more and quite similar strings. This breaks too many other translations. Although not being correct, it is better to not apply your patch. Sorry. Where possible I try to use a table format to avoid plural issues. BTW, for that reason this hunk would be wrong: > - log_info (_("permanently loaded certificates: %u\n"), > + log_info (ngettext(" permanently loaded certificate: %u\n", > + "permanently loaded certificates: %u\n", > + total_loaded_certificates), Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. From ineiev at gnu.org Wed Dec 2 18:37:46 2015 From: ineiev at gnu.org (Ineiev) Date: Wed, 2 Dec 2015 12:37:46 -0500 Subject: [HEAD PATCH] Use ngettext where appropriate In-Reply-To: <87mvtsn59o.fsf@vigenere.g10code.de> References: <20151020070834.GA10871@gnu.org> <87mvtsn59o.fsf@vigenere.g10code.de> Message-ID: <20151202173746.GA9187@gnu.org> On Wed, Dec 02, 2015 at 06:12:51PM +0100, Werner Koch wrote: > On Tue, 20 Oct 2015 09:08, ineiev at gnu.org said: > > I attach a patch against current HEAD to make use > > of ngettext in some places; it also marks two more messages > > localizable. > > At the cost of translating a lot more and quite similar strings. The string is the same (it's single msgid); what would be needed is filling different forms of the words (when the number of plural forms is more then one, which is not the case for some languages). > This breaks too many other translations. To be precise, it makes them 'fuzzy'. > Although not being correct, it is > better to not apply your patch. Sorry. In cases like - if (n_uids == 1 ) - log_info( _("key %s: \"%s\" 1 new user ID\n"), - keystr(keyid),p); - else if (n_uids ) - log_info( _("key %s: \"%s\" %d new user IDs\n"), - keystr(keyid),p,n_uids); ... + if (n_uids) + log_info( ngettext ("key %s: \"%s\" %d new user ID\n", + "key %s: \"%s\" %d new user IDs\n", n_uids), + keystr(keyid),p, n_uids); the number of messages decreases. will you accept the patch if I pick such cases? > Where possible I try to use a table format to avoid plural issues. BTW, > for that reason this hunk would be wrong: > > > - log_info (_("permanently loaded certificates: %u\n"), > > + log_info (ngettext(" permanently loaded certificate: %u\n", > > + "permanently loaded certificates: %u\n", > > + total_loaded_certificates), I'm not sure this method always works very well. Thank you! From fios at foramnagaidhlig.net Thu Dec 3 11:03:48 2015 From: fios at foramnagaidhlig.net (=?UTF-8?Q?F=c3=b2ram_na_G=c3=a0idhlig?=) Date: Thu, 3 Dec 2015 10:03:48 +0000 Subject: [HEAD PATCH] Use ngettext where appropriate In-Reply-To: <87mvtsn59o.fsf@vigenere.g10code.de> References: <20151020070834.GA10871@gnu.org> <87mvtsn59o.fsf@vigenere.g10code.de> Message-ID: <56601384.9040603@foramnagaidhlig.net> Sgr?obh Werner Koch na leanas 02/12/2015 aig 17:12: > On Tue, 20 Oct 2015 09:08, ineiev at gnu.org said: >> I attach a patch against current HEAD to make use >> of ngettext in some places; it also marks two more messages >> localizable. > > At the cost of translating a lot more and quite similar strings. This > breaks too many other translations. Although not being correct, it is > better to not apply your patch. Sorry. > 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. I hope hat I am not sounding too grumpy here, but if you localize a lot for a language that doesn't follow the English plural pattern, you sometimes feel like Don Quixote tilting at windmills. The resulting grammar errors also reflect badly on the localized version of the software ;) From wk at gnupg.org Fri Dec 4 10:36:13 2015 From: wk at gnupg.org (Werner Koch) Date: Fri, 04 Dec 2015 10:36:13 +0100 Subject: [HEAD PATCH] Use ngettext where appropriate In-Reply-To: <56601384.9040603@foramnagaidhlig.net> (=?utf-8?Q?=22F=C3=B2r?= =?utf-8?Q?am?= na =?utf-8?Q?G=C3=A0idhlig=22's?= message of "Thu, 3 Dec 2015 10:03:48 +0000") References: <20151020070834.GA10871@gnu.org> <87mvtsn59o.fsf@vigenere.g10code.de> <56601384.9040603@foramnagaidhlig.net> Message-ID: <87k2oulfn6.fsf@vigenere.g10code.de> 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. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. From fios at foramnagaidhlig.net Fri Dec 4 11:06:55 2015 From: fios at foramnagaidhlig.net (=?UTF-8?Q?F=c3=b2ram_na_G=c3=a0idhlig?=) Date: Fri, 4 Dec 2015 10:06:55 +0000 Subject: [HEAD PATCH] Use ngettext where appropriate In-Reply-To: <87k2oulfn6.fsf@vigenere.g10code.de> References: <20151020070834.GA10871@gnu.org> <87mvtsn59o.fsf@vigenere.g10code.de> <56601384.9040603@foramnagaidhlig.net> <87k2oulfn6.fsf@vigenere.g10code.de> Message-ID: <566165BF.7090905@foramnagaidhlig.net> Sgr?obh Werner Koch na leanas 04/12/2015 aig 09:36: > 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. I agree that the frontends are more important. So yes, do make any change a as low a cost for everybody as possible :) From ineiev at gnu.org Fri Dec 4 12:44:10 2015 From: ineiev at gnu.org (Ineiev) Date: Fri, 4 Dec 2015 06:44:10 -0500 Subject: [HEAD PATCH] Use ngettext where appropriate In-Reply-To: <87k2oulfn6.fsf@vigenere.g10code.de> References: <20151020070834.GA10871@gnu.org> <87mvtsn59o.fsf@vigenere.g10code.de> <56601384.9040603@foramnagaidhlig.net> <87k2oulfn6.fsf@vigenere.g10code.de> Message-ID: <20151204114410.GA12395@gnu.org> Hello, 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! From ineiev at gnu.org Mon Dec 7 09:34:24 2015 From: ineiev at gnu.org (Ineiev) Date: Mon, 7 Dec 2015 03:34:24 -0500 Subject: [HEAD PATCH RU] GnuPG 2.1 Russian update Message-ID: <20151207083424.GA15351@gnu.org> Hello, Please find an update for the Russian translation attached. Thank you! -------------- next part -------------- A non-text attachment was scrubbed... Name: 2.1-RU.patch.gz Type: application/octet-stream Size: 4244 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: From ineiev at gnu.org Mon Dec 21 09:40:55 2015 From: ineiev at gnu.org (Ineiev) Date: Mon, 21 Dec 2015 03:40:55 -0500 Subject: [PATCH STABLE-BRANCH-1-4 RU] Russian translation update Message-ID: <20151221084055.GA16453@gnu.org> Hello, Please find an updated and reviewed Russian translation for the 1-4 branch attached. Thank you! -------------- next part -------------- A non-text attachment was scrubbed... Name: 1.4-RU.patch.gz Type: application/octet-stream Size: 7024 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: