From: Thomas Moulard <thomas.moulard@gmail.com>
To: Emmanuel Trillaud <etrillaud@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: gitk : french translation
Date: Fri, 6 Nov 2009 19:16:20 +0100 [thread overview]
Message-ID: <b0c32d010911061016t2208af0er8d7fe88508c30f10@mail.gmail.com> (raw)
In-Reply-To: <9f50533b0911060605p6ad28ad9neac3620a1809c3db@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
On Fri, Nov 6, 2009 at 3:05 PM, Emmanuel Trillaud <etrillaud@gmail.com> wrote:
> Hello all,
> I made an attempt to translate gitk in french. The translation is
> _almost_ complete
> and I would really appreciate to have some comments by the french people here.
> I also need to improve some translations I am not happy with so it's
> really a work in progress.
Here is an updated translation with the following changes:
- translated strings which was still untranslated
- fixed some fuzzy translations
- make some consistency changes
* s/diff/différences/
* s/patch/correctif/ everywhere
- fixed some spelling problems.
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.
The only exception should their translation of ``commit'' by
``propagation'' which
I find awkward. Especially in a Git context , ``git commit'' really
does not propagate anything.
BTW any reason to translate the GUIs (gitk / git-gui) but not the
command line tools?
--
Thomas Moulard
[-- Attachment #2: fr.po.bz2 --]
[-- Type: application/x-bzip2, Size: 7116 bytes --]
next prev parent reply other threads:[~2009-11-06 18:16 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 [this message]
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
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=b0c32d010911061016t2208af0er8d7fe88508c30f10@mail.gmail.com \
--to=thomas.moulard@gmail.com \
--cc=etrillaud@gmail.com \
--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).