From: Vincent van Ravesteijn <vfr@lyx.org>
To: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Collocate strings to simplify translation
Date: Thu, 24 May 2012 11:55:31 +0200 [thread overview]
Message-ID: <4FBE0593.7070205@lyx.org> (raw)
In-Reply-To: <4FBDF21F.1010807@in.waw.pl>
Op 24-5-2012 10:32, Zbigniew Jędrzejewski-Szmek schreef:
> On 05/24/2012 09:41 AM, Vincent van Ravesteijn wrote:
>> The translation of 'Untracked' and 'Ignored' might depend on the following
>> word. To help the translator, this patch collocates the term 'files'.
>>
>> Signed-off-by: Vincent van Ravesteijn<vfr@lyx.org>
>> ---
>> wt-status.c | 6 +++---
>> 1 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/wt-status.c b/wt-status.c
>> index dd6d8c4..9b65a8c 100644
>> --- a/wt-status.c
>> +++ b/wt-status.c
>> @@ -185,7 +185,7 @@ static void wt_status_print_other_header(struct wt_status *s,
>> const char *how)
>> {
>> const char *c = color(WT_STATUS_HEADER, s);
>> - status_printf_ln(s, c, _("%s files:"), what);
>> + status_printf_ln(s, c, _("%s:"), what);
> How can "%s:" be translated? _() should be removed here.
Some languages might use a character different from ':'. For example,
Chinese uses a full-width character ':' (unicode 0xFF1A) instead of a
half-width character. Maybe this is taken care of by the system/shell or
whatever, maybe not. Other examples are languages that read from right
to left. I guess it should then be translated by ":%s".
This will probably be a matter of convention.
Vincent
next prev parent reply other threads:[~2012-05-24 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 7:41 [PATCH] Collocate strings to simplify translation Vincent van Ravesteijn
2012-05-24 8:32 ` Zbigniew Jędrzejewski-Szmek
2012-05-24 9:55 ` Vincent van Ravesteijn [this message]
2012-05-24 12:20 ` Johannes Sixt
2012-05-24 12:34 ` Vincent van Ravesteijn
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=4FBE0593.7070205@lyx.org \
--to=vfr@lyx.org \
--cc=git@vger.kernel.org \
--cc=zbyszek@in.waw.pl \
/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).