All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Emmanuel Trillaud <etrillaud@gmail.com>
Cc: Thomas Moulard <thomas.moulard@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Subject: Re: gitk : french translation
Date: Sat, 7 Nov 2009 03:54:39 +0100	[thread overview]
Message-ID: <20091107025439.GC13724@vidovic> (raw)
In-Reply-To: <9f50533b0911061259w54b57fcdo2c0b21e95dbbdc54@mail.gmail.com>

[
  Please, conform to Documentation/SubmittingPatches of the git.git
  project and send your patches inline to make the work for reviewers
  easier.

  Both of your patches lack the Signed-off-by but maybe you don't want
  them to be merged?
]

The 06/11/09, Emmanuel Trillaud wrote:

> > Here is an updated translation with the following changes:

<...>

> > - make some consistency changes
> >  * s/diff/différences/
> >  * s/patch/correctif/ everywhere

I disagree here. Words like "diff", "commit", "patch", etc should be
kept as is. Translation of those terms make things harder for the users.

> > IMHO the most important should be to decide how to translate the git vocabulary.
> > The Subversion project has guidelines concerning that issue:
> > http://svn.collab.net/viewvc/svn/trunk/subversion/po/fr.po?revision=39920&view=markup
> > It may be a good idea to stick with what they are doing if possible.

No, no. SVN and Git vocabulary/operations are not identical (not only
for 'commit' as you stated). Please, don't make things harder than it
already is.

-- 
Nicolas Sebrecht

  reply	other threads:[~2009-11-07  2:55 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 [this message]
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

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=20091107025439.GC13724@vidovic \
    --to=nicolas.s.dev@gmx.fr \
    --cc=etrillaud@gmail.com \
    --cc=git@vger.kernel.org \
    --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 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.