All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Lattarini <stefano.lattarini@gmail.com>
To: Marco Paolone <marcopaolone@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
Date: Fri, 01 Jun 2012 15:31:32 +0200	[thread overview]
Message-ID: <4FC8C434.1050902@gmail.com> (raw)
In-Reply-To: <20120601123642.GA11543@quizzlo.invalid>

On 06/01/2012 02:36 PM, Marco Paolone wrote:
> 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.
>
Thanks.

> 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?
>
I have no strong feeling honestly (as I'm no user of localized messages myself);
what I suggest is that you should decide to either translate all the "translatable"
technical terms (e.g., if you go for "branch -> ramo" and "tree -> albero", you
must also go for "tag -> etichetta"), or none of them (that is my personal opinion
though, and other people might legitimately disagree).  In the former case, adding
a new help category (say "translation") that explains how the terms and concepts
are mapped from the original english to the current language might be a good idea:

  $ git help translation
  Git parla italiano ora!
  [ ... blah blah ... piu' dettagli qui ...]
  branch -> ramo
  tag -> etichetta
  directory -> cartella
  ...

Regards,
  Stefano

  reply	other threads:[~2012-06-01 13:31 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
2012-06-01 13:31     ` Stefano Lattarini [this message]
2012-06-01 13:49     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FC8C434.1050902@gmail.com \
    --to=stefano.lattarini@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=marcopaolone@gmail.com \
    --cc=peter@softwolves.pp.se \
    --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.
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.