From: Jakub Narebski <jnareb@gmail•com>
To: Piotr Krukowiecki <piotr.krukowiecki@gmail•com>
Cc: "Junio C Hamano" <gitster@pobox•com>, "Jeff King" <peff@peff•net>,
"Sverre Rabbelier" <srabbelier@gmail•com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail•com>,
git@vger•kernel.org
Subject: Re: What's cooking in git.git (Feb 2011, #06; Sun, 27)
Date: Wed, 02 Mar 2011 02:32:23 -0800 (PST) [thread overview]
Message-ID: <m3k4gh7r0m.fsf@localhost.localdomain> (raw)
In-Reply-To: <AANLkTi=+iBR3OBZ=4fi_g=JMQKi=47F47hRsWxK=RbMv@mail.gmail.com>
Piotr Krukowiecki <piotr.krukowiecki@gmail•com> writes:
> On Wed, Mar 2, 2011 at 6:24 AM, Junio C Hamano <gitster@pobox•com> wrote:
>> Jeff King <peff@peff•net> writes:
>>> - Nit: you nicely use "%d commit%s" to handle the single/plural case
>>> in the warning message, but then you "them" later on. It needs
>>> (1 < lost) ? "them" : "it".
>>
>> I actually don't like playing games like that, especially when i18n topic
>> is in flight. Among the languages I know rules reasonably well, two has
>> the rule that a countable noun is spelled differently depending on the
>> number of that thing is one or more, and one spells the noun the same way
>> regardless of the number. Who knows if git needs to be translated into a
>> language whose noun changes its shape three-way, depending on the number
>> being one, two, or more?
Well, one of such languages with spelling depending in number of
things is Russian, for which we have translation for git-gui, so
I guess somebody would add one for git itself.
> For gettex this is described at
> http://www.gnu.org/software/gettext/manual/gettext.html#Plural-forms
Which includes example for Polish language:
1 file = 1 plik
2,3,4 files = 2,3,4 pliki
5-21 files = 5-21 plików
22-24 files = 22-24 pliki
25-31 files = 25-31 plików
and so on
[...]
Three forms, special case for one and some numbers ending in 2, 3, or 4
The header entry would look like this:
Plural-Forms: nplurals=3; \
plural=n==1 ? 0 : \
n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;
Languages with this property include:
Slavic family
Polish
> Don't know how it's handled in shell scripts or perl or whatever other
> language (which does not use gettext?)
Both shell scripts and Perl scripts would use gettext: gettext.sh for
shell, Locale::Messages for Perl (we need lower level than Text::Domain,
and Locale::Maketext is first no longer recommended, and second does
not use gettext at least by default).
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2011-03-02 10:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 6:48 What's cooking in git.git (Feb 2011, #06; Sun, 27) Junio C Hamano
2011-02-28 13:22 ` Sverre Rabbelier
2011-02-28 16:52 ` Junio C Hamano
2011-03-01 20:54 ` Jeff King
2011-03-02 2:07 ` Junio C Hamano
2011-03-02 21:27 ` Jeff King
2011-03-02 5:24 ` Junio C Hamano
2011-03-02 7:17 ` Piotr Krukowiecki
2011-03-02 10:32 ` Jakub Narebski [this message]
2011-03-10 9:44 ` Ævar Arnfjörð Bjarmason
2011-03-10 16:37 ` Jakub Narebski
2011-03-02 21:28 ` Jeff King
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=m3k4gh7r0m.fsf@localhost.localdomain \
--to=jnareb@gmail$(echo .)com \
--cc=avarab@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=peff@peff$(echo .)net \
--cc=piotr.krukowiecki@gmail$(echo .)com \
--cc=srabbelier@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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