From: Marco Paolone <marcopaolone@gmail.com>
To: Stefano Lattarini <stefano.lattarini@gmail.com>
Cc: "Jiang Xin" <worldhello.net@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Git List" <git@vger.kernel.org>,
"Peter Krefting" <peter@softwolves.pp.se>,
"Trần Ngọc Quân" <vnwildman@gmail.com>
Subject: Re: Nits abut the italian translation (was: Re: Please pull git-l10n updates on master branch)
Date: Fri, 1 Jun 2012 14:36:42 +0200 [thread overview]
Message-ID: <20120601123642.GA11543@quizzlo.invalid> (raw)
In-Reply-To: <4FC8A88D.3080700@gmail.com>
On Fri, Jun 01, 2012 at 01:33:33PM +0200, Stefano Lattarini wrote:
> I see few minor issues with the new translations; I hope it's OK if I report
> them here. Do not consider the following as an exhaustive list, since I've
> just skimmed the it.po file. And sorry for the messy and out-of-order report,
> but I'm short of time in these days.
Thanks for your report, I'll fix them in next commit. We could even leave terms
like "branch" or "tree" untranslated, but translation wouldn't have much sense
at this point. Some guides, like [1] use "ramo" or "albero" to better explain
how Git works, especially for beginners. Obviously we should leave terms like
"cherry-pick" or "push" as is. What do you suggest?
[1] http://www.linux.it/~rubini/docs/git/git.html
--
Linux Registered User #401479
GPG: 0x897AF14E
next prev parent reply other threads:[~2012-06-01 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 10:20 Please pull git-l10n updates on master branch Jiang Xin
2012-06-01 11:33 ` Nits abut the italian translation (was: Re: Please pull git-l10n updates on master branch) Stefano Lattarini
2012-06-01 12:36 ` Marco Paolone [this message]
2012-06-01 13:31 ` Nits abut the italian translation Stefano Lattarini
2012-06-01 13:49 ` Nits abut the italian translation (was: Re: Please pull git-l10n updates on master branch) 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120601123642.GA11543@quizzlo.invalid \
--to=marcopaolone@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peter@softwolves.pp.se \
--cc=stefano.lattarini@gmail.com \
--cc=vnwildman@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).