From: Dmitry Potapov <dpotapov@gmail.com>
To: Alex Riesen <raa.lkml@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 13:10:47 +0400 [thread overview]
Message-ID: <20090427091047.GC15723@dpotapov.dyndns.org> (raw)
In-Reply-To: <20090426132139.GA30825@blimp.localdomain>
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...
> -#: git-gui.sh:932
> +#: git-gui.sh:1076
> msgid "Cannot use funny .git directory:"
> msgstr "Каталог.git испорчен: "
------------------^
Missing space before dot.
> -#: git-gui.sh:1606 git-gui.sh:1607 git-gui.sh:1608 git-gui.sh:1609
> +#: git-gui.sh:1838 git-gui.sh:1839 git-gui.sh:1840 git-gui.sh:1841
> +#: git-gui.sh:1842 git-gui.sh:1843
> msgid "Requires merge resolution"
> msgstr "Требуется разрешение конфликта при объединении"
>
> -#: git-gui.sh:1644
> +#: git-gui.sh:1878
> msgid "Starting gitk... please wait..."
> msgstr "Запускается gitk... пожалуйста, ждите..."
s/ждите/подождите/
"ждите" sounds somewhat impolite here...
> -#: 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:
"Показать историю текущей ветви"
>
> -#: git-gui.sh:1892
> +#: git-gui.sh:2320
> msgid "Visualize All Branch History"
> msgstr "История всех ветвей наглядно"
"Показать историю всех ветвей"
> -#: git-gui.sh:1901
> +#: git-gui.sh:2329
> #, tcl-format
> msgid "Visualize %s's History"
> msgstr "История ветви %s наглядно"
"Показать историю ветви %s"
> -#: git-gui.sh:2002 git-gui.sh:2389
> +#: git-gui.sh:2432
> +msgid "Done"
> +msgstr "Звершено"
spelling: "Завершено"
> -#: 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...
Dmitry
next prev parent reply other threads:[~2009-04-27 9:11 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 [this message]
2009-04-27 9:25 ` Alex Riesen
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=20090427091047.GC15723@dpotapov.dyndns.org \
--to=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--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).