From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Raphael Hertzog" <hertzog@debian.org>,
git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: Re: git: problematic git status output with some translations (such as fr_FR)
Date: Thu, 19 Dec 2013 12:50:49 -0800 [thread overview]
Message-ID: <20131219205049.GE20443@google.com> (raw)
In-Reply-To: <xmqqk3f0efhe.fsf@gitster.dls.corp.google.com>
Junio C Hamano wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:
>> This includes the colon in the translated string, to make it easier to
>> remember to keep the non-breaking space before it.
>
> Hmph, recent 3651e45c (wt-status: take the alignment burden off
> translators, 2013-11-05) seems to have gone in the different
> direction when it updated similar code for the non-unmerged paths.
Yes, if this seems to go in the right direction, I'd add a follow-up
for that when rerolling.
Alternatively if there is some library function to append a colon to a
string in a locale-appropriate way, that could work, too. Pointers
welcome.
Thanks,
Jonathan
next prev parent reply other threads:[~2013-12-19 20:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131008085036.11434.25160.reportbug@x230-buxy.home.ouaza.com>
[not found] ` <20131219104613.GA18379@x230-buxy.home.ouaza.com>
2013-12-19 19:43 ` git: problematic git status output with some translations (such as fr_FR) Jonathan Nieder
2013-12-19 20:46 ` Junio C Hamano
2013-12-19 20:50 ` Jonathan Nieder [this message]
2013-12-19 23:59 ` Duy Nguyen
2014-01-16 22:00 ` Raphael Hertzog
2014-02-08 9:51 ` Duy Nguyen
2014-03-12 18:53 ` Junio C Hamano
2014-03-12 19:22 ` [PATCH] wt-status: i18n of section labels Junio C Hamano
2014-03-12 20:05 ` Sandy Carter
2014-03-12 20:12 ` Junio C Hamano
2014-03-12 20:17 ` Sandy Carter
2014-03-13 18:01 ` 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=20131219205049.GE20443@google.com \
--to=jrnieder@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hertzog@debian.org \
--cc=pclouds@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).