git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Dmitry Potapov <dpotapov@gmail.com>
Cc: git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH] Update Russian translation of git gui
Date: Mon, 27 Apr 2009 11:25:18 +0200	[thread overview]
Message-ID: <81b0412b0904270225m1762dd1l2ef60253e556b8c9@mail.gmail.com> (raw)
In-Reply-To: <20090427091047.GC15723@dpotapov.dyndns.org>

2009/4/27 Dmitry Potapov <dpotapov@gmail.com>:
> On Sun, Apr 26, 2009 at 03:21:40PM +0200, Alex Riesen wrote:
>> I also changed translation of the word 'tag': the old term was just a
>> transliteration. There is a russian word with a fitting meaning and
>> it is even used.
>
> таг (which was used before) is certainly incorrect, but both "тег" and
> "метка" are widely used in Russian. Though "тег" may be considered as
> computer slang, so "метка" is better for formal documentation...

My thinking exactly.

>> -#: git-gui.sh:932
>> +#: git-gui.sh:1076
>>  msgid "Cannot use funny .git directory:"
>>  msgstr "Каталог.git испорчен: "
> ------------------^
>
> Missing space before dot.
>

Oops...

>> -#: git-gui.sh:1644
>> +#: git-gui.sh:1878
>>  msgid "Starting gitk... please wait..."
>>  msgstr "Запускается gitk... пожалуйста, ждите..."
>
> s/ждите/подождите/
>
> "ждите" sounds somewhat impolite here...
>

Well, it is impolite to make people wait.
You can as well stop pretending :)
I'll change that, too.

>> -#: git-gui.sh:1888
>> +#: git-gui.sh:2316
>>  msgid "Visualize Current Branch's History"
>>  msgstr "История текущей ветви наглядно"
>
> The Russian phrase lacks of the verb and the added adverb at the end
> does not make much sense to me, so I would re-write the sentence as:
>
> "Показать историю текущей ветви"
>

Much better. I'll change that and the others.

>> +msgstr "Звершено"
>
> spelling: "Завершено"
>

Oops.

>> -#: git-gui.sh:2064
>> +#: git-gui.sh:2518
>>  msgid "Local Merge..."
>>  msgstr "Локальное объединение..."
>
> "слияние" is a more common term for "merge" in Russian computer
> literature though "объединение" is probably okay...
>

Ah, that's how it's called. Frankly, I just didn't know.
Will change.

Thank you very much for proofreading!

  reply	other threads:[~2009-04-27  9:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-26 13:21 [PATCH] Update Russian translation of git gui Alex Riesen
2009-04-27  9:10 ` Dmitry Potapov
2009-04-27  9:25   ` Alex Riesen [this message]
2009-04-27 17:54     ` Alex Riesen
2009-04-27 17:58   ` Alex Riesen
2009-04-28  9:22     ` Alexander Gavrilov
2009-04-28 16:04       ` [PATCH] Another update of Russian translation Alex Riesen
2009-04-29  5:56         ` [PATCH] Update Russian translation of git gui Alex Riesen
2009-04-29  7:20         ` [PATCH] Another update of Russian translation Dmitry Potapov
2009-04-29  9:11           ` Alexander Gavrilov
2009-04-29 15:32             ` Alex Riesen
2009-04-29 15:38               ` Shawn O. Pearce
2009-04-29 19:05                 ` Junio C Hamano
2009-04-29 19:07                   ` Shawn O. Pearce
2009-04-29 20:12                     ` Junio C Hamano
2009-04-30 23:50                   ` Paul Mackerras
2009-05-01  4:12                     ` Junio C Hamano

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=81b0412b0904270225m1762dd1l2ef60253e556b8c9@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=dpotapov@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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).