From: Jens Lehmann <Jens.Lehmann@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jiang Xin" <worldhello.net@gmail.com>,
"Git List" <git@vger.kernel.org>,
"Ævar Arnfjörð" <avarab@gmail.com>
Subject: Re: [PATCH] i18n: Not add stripped contents for translation
Date: Mon, 05 Mar 2012 20:34:50 +0100 [thread overview]
Message-ID: <4F55155A.3050309@web.de> (raw)
In-Reply-To: <7vobsb67dn.fsf@alter.siamese.dyndns.org>
Am 05.03.2012 04:42, schrieb Junio C Hamano:
> Jiang Xin <worldhello.net@gmail.com> writes:
>
>> Orignal source code:
>>
>> 244 case WT_STATUS_CHANGED:
>> 245 if (d->new_submodule_commits || d->dirty_submodule) {
>> 246 strbuf_addstr(&extra, " (");
>> 247 if (d->new_submodule_commits)
>> 248 strbuf_addf(&extra, _("new commits, "));
>> 249 if (d->dirty_submodule & DIRTY_SUBMODULE_MODIFIED)
>> 250 strbuf_addf(&extra, _("modified content, "));
>> 251 if (d->dirty_submodule & DIRTY_SUBMODULE_UNTRACKED)
>> 252 strbuf_addf(&extra, _("untracked content, "));
>> 253 strbuf_setlen(&extra, extra.len - 2);
>> 254 strbuf_addch(&extra, ')');
>> 255 }
>>
>> The bad thing is strbuf_setlen() at line 253. We can not asume the translation
>> of ", " must be 2 characters.
>
> It sounds like you are merely working around a poor style in the original,
> which should have been structured more like this in the first place, no?
>
> /* a helper function elsewhere, possibly inlined */
> static void add_iwsep_as_needed(struct strbuf *buf, int origlen)
> {
> if (buf->len != origlen)
> strbuf_addstr(buf, _(","));
> }
>
> ...
> int origlen;
>
> strbuf_addstr(&extra, " ("))
> origlen = extra.len;
> if (a)
> strbuf_addstr(&extra, _("msg a"));
> if (b) {
> add_iwsep_as_needed(&extra, origlen);
> strbuf_addstr(&extra, _("msg b"));
> }
> if (c) {
> add_iwsep_as_needed(&extra, origlen);
> strbuf_addstr(&extra, _("msg c"));
> }
> strbuf_addstr(&extra, ")");
>
> Cc'ing Jens whose 9297f77 (git status: Show detailed dirty status of
> submodules in long format, 2010-03-08) introduced the "two-byte backstep".
I have no objections at all against changing the code that way to make it
possible to translate it in a sane way. This code predates the i18n effort
by a few months, so it didn't take this kind of problem into account.
next prev parent reply other threads:[~2012-03-05 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 1:21 [PATCH] i18n: Not add stripped contents for translation Jiang Xin
2012-03-05 2:27 ` Junio C Hamano
2012-03-05 3:01 ` Jiang Xin
2012-03-05 3:42 ` Junio C Hamano
2012-03-05 19:34 ` Jens Lehmann [this message]
2012-03-05 20:08 ` Junio C Hamano
2012-03-06 4:16 ` Jiang Xin
2012-03-06 6:46 ` Junio C Hamano
2012-03-06 6:55 ` Jiang Xin
2012-03-06 6:47 ` Jiang Xin
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=4F55155A.3050309@web.de \
--to=jens.lehmann@web.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=worldhello.net@gmail.com \
/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).