From: Michele Ballabio <barra_cuda@katamail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Paul Mackerras <paulus@samba.org>, git <git@vger.kernel.org>
Subject: Re: gitk translation updates needed?
Date: Wed, 3 Feb 2010 11:13:10 +0100 [thread overview]
Message-ID: <201002031113.11212.barra_cuda@katamail.com> (raw)
In-Reply-To: <7vd40nundv.fsf_-_@alter.siamese.dyndns.org>
On Wednesday 03 February 2010, Junio C Hamano wrote:
> Generating catalog po/it.msg
> msgfmt --statistics --tcl po/it.po -l it -d po/
> 282 translated messages, 1 fuzzy translation, 6 untranslated messages.
I don't get any fuzzy translation here, but I used to, so I guess it
regards the copyright message. If that's the case, maybe msgfmt
mishandles the (C)opyright sign (or maybe gitk uses a weird encoding,
I don't know).
The untranslated messages are either abbreviations (IgnCase) or
expressions I couldn't translate effectively (Cherry-picking);
they are quite understandable anyway.
next prev parent reply other threads:[~2010-02-03 10:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 15:16 git-gui translation updates needed Shawn O. Pearce
2010-02-02 10:20 ` [PATCH] git-gui: update Japanese translation Nanako Shiraishi
2010-02-02 12:18 ` [PATCH] git-gui: update french translation Emmanuel Trillaud
2010-02-03 1:09 ` git-gui translation updates needed Junio C Hamano
2010-02-03 1:19 ` gitk translation updates needed? Junio C Hamano
2010-02-03 10:13 ` Michele Ballabio [this message]
2010-02-03 19:46 ` Junio C Hamano
2010-02-03 20:56 ` Michele Ballabio
2010-02-03 21:46 ` Paul Mackerras
2010-02-03 22:21 ` Junio C Hamano
2010-02-03 22:20 ` Junio C Hamano
2010-02-03 22:24 ` Junio C Hamano
2010-02-03 10:11 ` git-gui translation updates needed Michele Ballabio
2010-02-03 19:42 ` Junio C Hamano
2010-02-03 19:52 ` git-gui clone WTFery Shawn O. Pearce
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=201002031113.11212.barra_cuda@katamail.com \
--to=barra_cuda@katamail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=paulus@samba.org \
/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).