git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Hocevar <sam@zoy.org>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Git List <git@vger.kernel.org>,
	Alexandre Bourget <alexandre.bourget@savoirfairelinux.com>
Subject: Re: [PATCH] git-gui: various French translation fixes
Date: Thu, 19 Mar 2009 13:49:02 +0100	[thread overview]
Message-ID: <20090319124901.GM27280@zoy.org> (raw)
In-Reply-To: <20090319075855.GJ27280@zoy.org>

On Thu, Mar 19, 2009, Sam Hocevar wrote:
> On Thu, Mar 19, 2009, Christian Couder wrote:
> > > >  #: git-gui.sh:2484 lib/index.tcl:410
> > > >  msgid "Revert Changes"
> > > > -msgstr "Annuler les modifications (revert)"
> > > > +msgstr "Révoquer les modifications"
> > >
> > > I am not sure that "Révoquer" is better than "Annuler".
> > 
> > Perhaps "Inverser"?
> 
>    I suggested "révoquer" because it was close enough to "revert" that
> there was no need to specify "(revert)" in the translation itself.
> It's what the French Wikipedia interface used to say to revert edits.
> But I see they now use "défaire" (undo), so apparently they deemed
> it inappropriate for some reason. I have no strong preference for
> "Inverser" or even "Annuler", I just want it to be consistent and to get
> rid of the "(revert)" at the end of this message.

   Sorry, I misread the Wikipedia interface because I wasn't logged in
and only admins can truly revert edits. So it does have "revert" (to
cancel an edit) and "undo" (to perform the opposite edit of a given
edit), which get translated to "révoquer" and "défaire". I therefore
think "révoquer" is just as good as the others.

-- 
Sam.

  reply	other threads:[~2009-03-19 12:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 20:54 [PATCH] git-gui: various French translation fixes Sam Hocevar
2009-03-19  5:09 ` Christian Couder
2009-03-19  6:14   ` Christian Couder
2009-03-19  7:58     ` Sam Hocevar
2009-03-19 12:49       ` Sam Hocevar [this message]
2009-03-19 18:38         ` [PATCH] " Nicolas Sebrecht
2009-03-20  6:45           ` Christian Couder
2009-03-19  7:02   ` [PATCH] " Mike Hommey
2009-03-19  7:11     ` Christian Couder
2009-03-20  0:54 ` git-gui: some French translation enhancements Nicolas Sebrecht
     [not found] ` <cd2d922d5257aac105de08fd90e6dbd389f0b6f0.1237506346.git.nicolas.s-dev@laposte.net>
2009-03-20  0:54   ` [PATCH 2/2] " Nicolas Sebrecht
2009-03-20  7:13     ` Mike Hommey
2009-03-20 14:34       ` Alexandre Bourget
2009-03-20 18:42         ` Nicolas Pitre
2009-03-20 19:43           ` Mike Hommey
2009-03-21  3:54           ` Christian Couder
2009-03-21  3:48         ` Christian Couder
2009-03-21 10:14         ` [PATCH 2/2] " Nicolas Sebrecht
2009-03-21 17:26           ` Mike Hommey
2009-03-21 10:27         ` Nicolas Sebrecht
2009-03-21 14:47           ` [PATCH v2 1/2] git-gui: various French translation fixes Nicolas Sebrecht
2009-03-21 18:57             ` Christian Couder
2009-03-21 14:47           ` [PATCH v2 2/2] git-gui: impove some French translations Nicolas Sebrecht
2009-03-20  7:37     ` [PATCH 2/2] git-gui: some French translation enhancements Sam Hocevar
2009-03-20  7:41     ` Christian Couder
2009-03-20 15:03       ` Shawn O. Pearce
2009-03-21  9:33         ` [PATCH 2/2] " Nicolas Sebrecht

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=20090319124901.GM27280@zoy.org \
    --to=sam@zoy.org \
    --cc=alexandre.bourget@savoirfairelinux.com \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    /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).