All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maximilien Noal <noal.maximilien@gmail.com>
To: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Cc: Emmanuel Trillaud <etrillaud@gmail.com>,
	Thomas Moulard <thomas.moulard@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: gitk : french translation
Date: Mon, 09 Nov 2009 00:11:38 +0100	[thread overview]
Message-ID: <4AF7502A.9020903@gmail.com> (raw)
In-Reply-To: <20091108214130.GA12931@vidovic>

Nicolas Sebrecht wrote :
>>> I disagree here. Words like "diff", "commit", "patch", etc should be
>>> kept as is. Translation of those terms make things harder for the users.
>> I agree with you when those terms refers to _commands_ names, but the
>> main goal of a
>> translation is to _translate_ and we have to make the best effort to
>> use french word if they _exist_
> 
> I don't think so. Here is _why_: the user-frienliness of a translated
> software comes from "how hard is it to connect a word with the
> underlying concept".
> 
> IOW, we want to have good words to refer to the _concepts_. In the
> computer science world (and more _specially_ for a SCM), those concepts
> are much more well-known with the english terms. Keeping english words
> help users to directly understand what it is about, without making the
> users have to search for "what the fucking translators are refering to
> here?".
Why not put the translation first, then the english word between () ?
At least for English words above that are not used by French devs "as 
is" (not like "diff") ?

That way, newbies to SCMs' concepts get the idea, and old SCM users 
don't have to translate back.

But if it isn't done _everywhere_ (and not used anywhere for words we 
don't want to translate because there's no need or no good translation, 
like "diff" for the first case, and "patch" for the second one), it will 
make the situation worse.

Just my two cents.

  reply	other threads:[~2009-11-08 23:11 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 [this message]
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=4AF7502A.9020903@gmail.com \
    --to=noal.maximilien@gmail.com \
    --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.