From: Junio C Hamano <gitster@pobox.com>
To: Frederik Schwarzer <schwarzerf@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: i18n: Avoid sentence puzzles
Date: Mon, 30 Jan 2012 10:57:12 -0800 [thread overview]
Message-ID: <7vty3dauif.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <201201301231.21090.schwarzerf@gmail.com> (Frederik Schwarzer's message of "Mon, 30 Jan 2012 12:31:20 +0100")
Frederik Schwarzer <schwarzerf@gmail.com> writes:
> So my question would be: Is it considered worth it to extend the code
> for translators' and translations' sake? If so, I would be glad to
> help with that.
The sample you supplied for 'branch' vs 'remote branch' is a good change
in the logic to choose what translatable message to use, and I do suspect
that there are other instances of problems of this kind.
I am expecting that we may see some activity to the logic in that file
during this cycle, and we would need to be careful not make people step on
other people's toes, though.
next prev parent reply other threads:[~2012-01-30 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 11:31 i18n: Avoid sentence puzzles Frederik Schwarzer
2012-01-30 11:46 ` Nguyen Thai Ngoc Duy
2012-01-30 18:57 ` Junio C Hamano [this message]
2012-01-30 21:12 ` Ævar Arnfjörð Bjarmason
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=7vty3dauif.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=schwarzerf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.