From: Stefano Lattarini <stefano.lattarini@gmail.com>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Git List" <git@vger.kernel.org>,
"Marco Paolone" <marcopaolone@gmail.com>,
"Peter Krefting" <peter@softwolves.pp.se>,
"Trần Ngọc Quân" <vnwildman@gmail.com>
Subject: Nits abut the italian translation (was: Re: Please pull git-l10n updates on master branch)
Date: Fri, 01 Jun 2012 13:33:33 +0200 [thread overview]
Message-ID: <4FC8A88D.3080700@gmail.com> (raw)
In-Reply-To: <CANYiYbF3sbtKVTZJOTbQ-aOjBKGKFZfq-xQDwyOvR56C7akrLw@mail.gmail.com>
On 06/01/2012 12:20 PM, Jiang Xin wrote:
> Hi Junio,
>
> As usual, this pull is for master branch. In this pull, both 'it.po'
> and 'zh_CN.po'
> have fuzzy translations. One translation in 'zh_CN.po' intends to be fuzzy,
> because it is hard to translate right, and I sent a patch for this yesterday.
>
> Marco Paolone (1):
> l10n: New it.po file with 504 translations
>
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.
Regards,
Stefano
~~~
#: diff.c:1421
#, c-format
msgid ", %d insertion(+)"
msgid_plural ", %d insertions(+)"
msgstr[0] ", %d aggiunta(+)"
msgstr[1] ", %d aggiunte(+)<"
Spurious "<" here?
~~~
#: help.c:214
msgid "git commands available from elsewhere on your $PATH"
msgstr "i comandi git sono disponibili in un altro percorso nel tuo $PATH"
Given the context this message is use in (output of "git help -a"), I think a
more correct translation would be:
comandi git disponibili altrove nel tuo $PATH
~~~
#: sequencer.c:403
#, c-format, fuzzy
msgid "Cannot get commit message for %s"
msgstr "Non è possibile prelevare il messaggio di commit per %s"
What about "Impossibile ottenere il messaggio di commit per %s" instead?
"Prelevare" sounds weird in this context, at least to me ...
~~~
"branch" is sometimes translated, sometimes not:
#: wt-status.c:744
msgid "Not currently on any branch."
msgstr "Al momento non si è su alcun ramo."
#: sha1_name.c:869
#, c-format
msgid "No upstream configured for branch '%s'"
msgstr "Nessun upstream configurato per il branch '%s'"
BTW, are we sure it's a good idea to translate technical terms like
'branch'? And if yes, why translate some terms (branch -> albero),
but not others (tag -> etichetta)?
~~~
#. TRANSLATORS: Make sure to include [Y] and [n] in your
#. translation. The program will only accept English input
#. at this point.
#: git-bisect.sh:279
msgid "Are you sure [Y/n]? "
msgstr "Si è sicuri? [S/n] "
The translation "[S/n]" seems to contradict the comment above.
#. TRANSLATORS: Make sure to include [y], [n], [e], [v] and [a]
#. in your translation. The program will only accept English
#. input at this point.
#: git-am.sh:766
#, fuzzy
msgid "Apply? [y]es/[n]o/[e]dit/[v]iew patch/[a]ccept all "
msgstr "Applicare? [s]ì/[n]o/[m]odifica/[v]isualizza/mostra [p]atch/[a]ccetta tutto "
Likewise, but worse.
~~~
#: common-cmds.h:28
#, fuzzy
msgid "Create, list, delete or verify a tag object signed with GPG"
msgstr "Crea, elenca. elimina o verifica un oggetto tag firmato con GPG"
Minor typo: should be "elenca," not "elenca.".
~~~
#: builtin/tag.c:376
#, c-format, fuzzy
msgid "The tag message has been left in %s\n"
msgstr "Il messaggio tag è stato lasciato in %s\n"
"Il messaggio del tag" or "Il messaggio associato al tag" seems clearer and more
correct.
~~~
#: builtin/reset.c:325
#, c-format, fuzzy
msgid "%s reset is not allowed in a bare repository"
msgstr "%s reset non è consentito in un archivio scoperto #FIXME: bare"
What about translating "bare" with "spoglio"?
~~~
#: builtin/mv.c:171
msgid "not under version control"
msgstr "non si trova nel sistema di controllo versione"
What about "non e' sotto controllo di versione"? It seems a slightly more
faithful translation to me.
~~~
#: builtin/merge.c:1146 builtin/merge.c:1303
#, c-format, fuzzy
msgid "%s - not something we can merge"
msgstr "%s - non è qualcosa per cui effettuare il merge"
I'd say: "non è qualcosa per cui possiamo effettuare il merge"
~~~
#: builtin/help.c:108
#, c-format
msgid "emacsclient version '%d' too old (< 22)."
msgstr "la versione '%d' di emacsclient è vecchia (<22)."
s/vecchia/troppo vecchia/?
~~~
#: builtin/commit.c:1588
msgid ""
"Repository has been updated, but unable to write\n"
"new_index file. Check that disk is not full or quota is\n"
"not exceeded, and then \"git reset HEAD\" to recover."
msgstr ""
"L'archivio è stato aggiornato, ma non è stato possibile scrivere il file\n"
"new_index. Verificare che l'unità disco non sia piena o che la quota non sia\n"
"stata superata, ed eseguire \"git reset HEAD\"ccc per il ripristino."
What is that "ccc" after "HEAD" for?
~~~
#: builtin/add.c:297
msgid "Empty patch. Aborted."
msgstr "Patch vuota. Operazione terminata."
I beliave "bloccata" (or even "abortita") would be clearer than "terminata" in
this context?
next prev parent reply other threads:[~2012-06-01 11:33 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 ` Stefano Lattarini [this message]
2012-06-01 12:36 ` Nits abut the italian translation (was: Re: Please pull git-l10n updates on master branch) Marco Paolone
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=4FC8A88D.3080700@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.
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).