From: Johannes Sixt <j.sixt@viscovery.net>
To: Peter Krefting <peter@softwolves.pp.se>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Mathieu Liénard--Mayor" <mathieu.lienard--mayor@ensimag.fr>,
git@vger.kernel.org,
"Jorge Juan Garcia Garcia"
<Jorge-Juan.Garcia-Garcia@ensimag.imag.fr>,
"Matthieu Moy" <Matthieu.Moy@grenoble-inp.fr>
Subject: Re: [PATCH] status: display the SHA1 of the commit being currently processed
Date: Thu, 20 Jun 2013 10:10:02 +0200 [thread overview]
Message-ID: <51C2B8DA.6040400@viscovery.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1306200853250.7267@ds9.cixit.se>
Am 6/20/2013 9:56, schrieb Peter Krefting:
> Junio C Hamano:
>
>> But my understanding is that the reordering using printf() is the
>> mechanism we suggest l10n folks to use when the order of parameters
>> given to printf does not match the preferred word order in the message
>> in their language.
>
> It's documented in the gettext manual, and seems to be used in the
> zh_CN.po to change the word order in quite a few places.
It is fine to use %n$ in translated strings as long as gettext is enabled
only on systems that have a sufficiently capable printf and these formats
are not used in the source code.
But you can't have this string:
"Splitting a commit while rebasing branch '%2$s' on '%3$s'."
neither in the template nor in the translation, because the numbers must
begin at 1 (and must be used without gaps).
-- Hannes
next prev parent reply other threads:[~2013-06-20 8:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 12:10 [PATCH] status: display the SHA1 of the commit being currently processed Mathieu Lienard--Mayor
2013-06-17 12:44 ` Thomas Adam
2013-06-17 13:10 ` Peter Krefting
2013-06-17 13:33 ` Mathieu Liénard--Mayor
2013-06-17 13:54 ` Peter Krefting
2013-06-17 13:57 ` Mathieu Liénard--Mayor
2013-06-17 15:10 ` Johannes Sixt
2013-06-17 16:33 ` Junio C Hamano
2013-06-20 7:56 ` Peter Krefting
2013-06-20 8:10 ` Johannes Sixt [this message]
2013-06-20 18:11 ` Junio C Hamano
2013-06-21 5:34 ` Johannes Sixt
2013-06-21 14:23 ` Junio C Hamano
2013-06-17 18:37 ` Junio C Hamano
2013-06-18 10:12 ` Mathieu Liénard--Mayor
2013-06-18 16:32 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51C2B8DA.6040400@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=Jorge-Juan.Garcia-Garcia@ensimag.imag.fr \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mathieu.lienard--mayor@ensimag.fr \
--cc=peter@softwolves.pp.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).