From: Nicolas Pitre <nico@fluxnic.net>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>,
Emmanuel Trillaud <etrillaud@gmail.com>,
Thomas Moulard <thomas.moulard@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: gitk : french translation
Date: Sun, 08 Nov 2009 20:30:38 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911082010590.16711@xanadu.home> (raw)
In-Reply-To: <vpqtyx5nql0.fsf@bauges.imag.fr>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1744 bytes --]
On Sun, 8 Nov 2009, Matthieu Moy wrote:
> Nicolas Sebrecht <nicolas.s.dev@gmx.fr> writes:
>
> >> > - 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.
>
> Metoo.
>
> One day or another, the user will have to face the words "diff",
> "commit" and "patch" even in a 100% french-speaking context (for
> example when requesting help and someone answering "open a terminal
> and type 'git commit --whatever'" or so).
>
> Matching the command-line concepts and the GUI concepts is made really
> hard by over-translating.
Striking a good balance is the key. Not translating enough might simply
look "cheap" to a new user who was not exposed to the concepts in the
first place.
It is not like if we were facing issues like:
"Made in Turkey" -> "Fait en dinde"
"arm rest and pad assembly" -> "armer le repos et rembourer l'assemblée"
It's like those stu**d people who decided that "email" was too hard to
translate. So they declared that "email" was "imél" in French.
Fortunately some non European people came up with a refreshing idea and
translated "email" into "courriel" instead. And with a step back, you
must admit that "courriel" is so much clearer and more descriptive
semantically.
Therefore I think that it is a good thing to _try_ to translate stuff
appropriately. but this is often much harder than it may seem.
> (and BTW, "correctif" is not a very good translation of "patch", since
> a patch is not necessarilly a correction of something).
In this case I think "retouche" would be a better choice.
Nicolas
next prev parent reply other threads:[~2009-11-09 1:31 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 [this message]
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=alpine.LFD.2.00.0911082010590.16711@xanadu.home \
--to=nico@fluxnic.net \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=etrillaud@gmail.com \
--cc=git@vger.kernel.org \
--cc=nicolas.s.dev@gmx.fr \
--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.