From: Emmanuel Trillaud <etrillaud@gmail.com>
To: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Cc: Maximilien Noal <noal.maximilien@gmail.com>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Nicolas Pitre <nico@fluxnic.net>,
Thomas Moulard <thomas.moulard@gmail.com>,
Guy Brand <gb@unistra.fr>, Git Mailing List <git@vger.kernel.org>
Subject: Re: gitk : french translation
Date: Wed, 11 Nov 2009 02:10:15 +0100 [thread overview]
Message-ID: <9f50533b0911101710q2f1ed9a4i7b682988a0983ef8@mail.gmail.com> (raw)
In-Reply-To: <20091110204742.GA27518@vidovic>
2009/11/10 Nicolas Sebrecht <nicolas.s.dev@gmx.fr>:
>> commiter : auteur du commit : commiteur
>
> Why not "commiteur" for gitk too?
It's ok for me.
>> Check out : Récupérer : charger
>> to cherry-pick : Ceuillir
>> Diff : Différence : Diff
>
> See comment at the end.
>
>> Soft (Reset) : Douce :
>
> Léger ?
Souds better. I will make the change, except if someone has a better
proposal.
>> I prefer to translate "Diff" by "Différences" _especially_ when we are
>> talking about the action of making a "diff"
>
> You don't explain _why_. We had 3 points in favour of the "diff" term in
> french in this thread (keep Git's commands consistency, rough
> translation and english word more used even by french people as for
> "patch"). I have another argument to use "diff" now: keep consistency
> with 'git gui'.
I see now that I have no good reasons to prefer "Différences".
>> translation of "cherry-pick". For this one we could use "<translation>
>> (<english-word>) ..." as suggest previously.
>
> I'm fine here.
Thanks for your comments.
Emmanuel Trillaud
prev parent reply other threads:[~2009-11-11 1:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 14:05 gitk : french translation Emmanuel Trillaud
2009-11-06 18:16 ` Thomas Moulard
2009-11-06 20:59 ` Emmanuel Trillaud
2009-11-07 2:54 ` Nicolas Sebrecht
2009-11-08 12:33 ` Matthieu Moy
2009-11-09 1:30 ` Nicolas Pitre
2009-11-09 8:39 ` [OT] " Matthieu Moy
2009-11-09 9:24 ` Maximilien Noal
2009-11-08 17:55 ` Emmanuel Trillaud
2009-11-08 21:41 ` Nicolas Sebrecht
2009-11-08 23:11 ` Maximilien Noal
2009-11-08 23:15 ` Maximilien Noal
2009-11-09 1:24 ` Nicolas Sebrecht
2009-11-10 17:45 ` Emmanuel Trillaud
2009-11-10 21:02 ` Nicolas Sebrecht
2009-11-11 0:10 ` Nicolas Sebrecht
2009-11-11 14:15 ` Thomas Moulard
2009-11-11 16:59 ` Nicolas Sebrecht
2009-11-11 17:10 ` Emmanuel Trillaud
2009-11-19 19:47 ` Emmanuel Trillaud
2009-11-19 20:01 ` Emmanuel Trillaud
2009-11-19 21:23 ` [PATCHv4] gitk " Emmanuel Trillaud
2009-11-19 23:57 ` [PATCHv4] " Nicolas Sebrecht
2009-11-20 0:28 ` Emmanuel Trillaud
2009-12-02 10:24 ` gitk : " Emmanuel Trillaud
[not found] ` <c558c59b3fe779e8577fe06233d3da5d2711127f.1259795550.git.ni.s@laposte.net>
2009-12-29 22:39 ` [RESEND PATCH] french translation of gitk Nicolas Sebrecht
2010-01-08 13:22 ` Emmanuel Trillaud
2010-01-12 11:21 ` Paul Mackerras
2010-01-12 13:02 ` Emmanuel Trillaud
2010-01-28 13:23 ` Emmanuel Trillaud
2009-11-10 18:05 ` gitk : french translation Emmanuel Trillaud
2009-11-10 20:47 ` Nicolas Sebrecht
2009-11-11 1:10 ` Emmanuel Trillaud [this message]
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=9f50533b0911101710q2f1ed9a4i7b682988a0983ef8@mail.gmail.com \
--to=etrillaud@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=gb@unistra.fr \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=nicolas.s.dev@gmx.fr \
--cc=noal.maximilien@gmail.com \
--cc=thomas.moulard@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 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).