From: Johannes Sixt <j.sixt@viscovery.net>
To: "Mathieu Liénard--Mayor" <mathieu.lienard--mayor@ensimag.fr>
Cc: Peter Krefting <peter@softwolves.pp.se>,
git@vger.kernel.org, gitster@pobox.com,
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: Mon, 17 Jun 2013 17:10:49 +0200 [thread overview]
Message-ID: <51BF26F9.1080900@viscovery.net> (raw)
In-Reply-To: <0b88af05ea8d4723a870476036992abc@ensibm.imag.fr>
Am 6/17/2013 15:57, schrieb Mathieu Liénard--Mayor:
> Le 2013-06-17 15:54, Peter Krefting a écrit :
>> Mathieu Liénard--Mayor:
>>
>>> Actually, at first I dealt with it this way:
>>>
>>> status_printf_ln(s, color,
>>> _("Splitting %s while rebasing branch '%s' on '%s'."),
>>> stopped_sha ? stopped_sha : _("a commit"),
>>> ....);
>>>
>>> Would this be more suitable for translators ?
>>
>> Not really, the text surrounding "a commit" might need to be
>> inflected differently depending on whether it is a SHA-1 or the "a
>> commit" string. Word order might also be different.
> Okay, I'll use what you suggested then.
That's not a good idea. Do we already use "%1$" style formats elsewhere?
I'm afraid that they are not supported everywhere.
-- Hannes
next prev parent reply other threads:[~2013-06-17 15:11 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 [this message]
2013-06-17 16:33 ` Junio C Hamano
2013-06-20 7:56 ` Peter Krefting
2013-06-20 8:10 ` Johannes Sixt
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=51BF26F9.1080900@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).