From: Dmitry Potapov <dpotapov@gmail.com>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] Add Russian translation to gitk
Date: Mon, 27 Apr 2009 12:39:53 +0400 [thread overview]
Message-ID: <20090427083953.GB15723@dpotapov.dyndns.org> (raw)
In-Reply-To: <20090426132452.GB30825@blimp.localdomain>
On Sun, Apr 26, 2009 at 03:24:52PM +0200, Alex Riesen wrote:
> Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
> ---
>
> As with the git-gui translation, if someone understanding russian sees
> this, could you please take a look and drop me a note if you find
> something "strange"?
The translation uses a single Russian verb "Перейти" in different
meanings (where the original English phrase had "check out", "move",
"go to", "focus) and that creates some ambiguity. For example:
> +#: gitk:2347
> +msgid "Check out this branch"
> +msgstr "Перейти на эту ветвь"
> +#: gitk:2644
> +msgid "<Home>\t\tMove to first commit"
> +msgstr "<Home>\t\tПерейти к первому состоянию"
How one is supposed to know that when we speak about branch, "Перейти"
means "check out" but when about some commit then it is "move"? Only
because gitk does not allow to check out arbitrary commit _yet_?
IMHO, it is very very confusing.
I think "Check out this branch" should be translated as "Переключить
рабочий каталог на эту ветвь" (which literally means: Switch worktree
to this branch).
Dmitry
next prev parent reply other threads:[~2009-04-27 8:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 13:24 [PATCH] Add Russian translation to gitk Alex Riesen
2009-04-27 7:51 ` Dmitry Potapov
2009-04-27 8:10 ` Alex Riesen
2009-04-27 18:04 ` Alex Riesen
2009-04-27 8:39 ` Dmitry Potapov [this message]
2009-04-27 9:20 ` Alex Riesen
2009-04-27 9:32 ` Dmitry Potapov
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=20090427083953.GB15723@dpotapov.dyndns.org \
--to=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=paulus@samba.org \
--cc=raa.lkml@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 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).