Re: gitk : french translation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2009/11/7 Nicolas Sebrecht <nicolas.s.dev@xxxxxx>:
> [
>  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?
> ]
I am aware of this recommendation but this translation is almost 22kb and
I tought that put it inline wouldn't make the review easier. I will
submit a patch
gathering my workand those of the reviewers soon.

> 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.
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_
and _are_ appropriate (that's why I'm not sure about translate
"cherry-pick" by "ceullir").
I prefer to translate "Diff this -> selected" by "Différence entre ça
et selection"
because it is what the user do when he make a diff. I am also ok to
translate "merge" by "fusion"
because it's what "merge" is in french and I don't this we mislead the
user by using the term
"fusion".

>> > 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.
Have you read this document? I read it and it contains some
interesting _advices_ in it
(especially for an amateur translator like me) and some translations
ideas. That said, I agree with
your concerns to not make things harder for the user and to choose the
good translations
for the Git vocabulary. I will make a glossary of the Git words and
the proposed translations for them

Cordiallement

Emmanuel
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]