Johannes Sixt <j.s...@viscovery.net> writes:
> 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).
Did any message we saw in the patch (and the discussion to possibly
improve it) need to have such a format string, or are you pointing
out a common gotcha we may want to warn translators about in
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html