All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Thielow <ralf.thielow@googlemail.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: "Jiang Xin" <worldhello.net@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Git List" <git@vger.kernel.org>, "Jan Krüger" <jk@jk.gs>
Subject: Re: Please pull git-po master branch
Date: Wed, 2 May 2012 11:13:04 +0200	[thread overview]
Message-ID: <CAN0XMOJ0PBA2qptw2Lm9HOq4SAkeZNAyOwPdvcb-uAcsxKnzwg@mail.gmail.com> (raw)
In-Reply-To: <87d36n2f2r.fsf@thomas.inf.ethz.ch>

Well, basically I've tried to unify the translation with the git-gui one.
So i took over some of the translations from them (e.g. "commit").

>  A related issue is when a single word splits into several in German.
>
>  Examples:
>
>  "commit" -> "Eintrag/Version/eintragen"

I think we have to make a difference between "commit" as a noun and
"commit" as a verb here.

>
>  "commit" -> usually translated simply as "Commit", e.g. in the SVN Red
>              Book
>

As I said I've tried to unify with the git-gui translation. Actually, I was
wondered why they translate terms like "Tag" or "Commit" because
I think they should be known by a Git user.
I know German books about Git using many other terms like
"Staging" or "Index" as it is.

> * Make a glossary of the relevant terminology first.  Sadly
>  gitglossary(7) has gotten somewhat stale, and perhaps can also benefit
>  from an overhaul.  Ævar Arnfjörð Bjarmason recently made a list[4] of
>  the most important terms, which is a good start.
>
> * If you are interested in collaboration, IRC may be a good choice for
>  the many little questions that probably arise?  We hang out in
>  #git-devel on Freenode[3].  Email is of course also an option, but
>  more time-consuming.

I would be happy to work together with you on these things.
Tiny changes in the translation of basic terms can make
a big difference.

> Note that in the context of Git, a major problem is that the
> documentation and books are only available in English.  There isn't even
> a glossary.  For example, you translated "detached" as "losgelöst".
> From our experience the detached HEAD is something that users stumble
> into, rather than learn about beforehand.  They usually come crying for
> help when they've already lost their work in the "void" of unreachable
> commits.  Now put yourself into the position of a user.  Where can he
> look up what the root of his problem is?  At least for "detached HEAD"
> there is a wealth of blog posts that rescue the poor user.

That's a basic problem when messages are translated.

> We think -- pardon the strong words -- that your current draft
> translation makes things harder, not easier, for German users.  The
> issues mentioned above, especially when it comes to ambiguities, splits
> into several terms and mistakes, add up to considerable bad weather, and
> the lack of reference material leaves the user out in the rain.
>
> Of course now that it has been released, we'll also have to file patches
> in the true open source spirit.  Sigh.

I don't think that it's sooo bad that it needs to get reverted.
In the end it's an initial version. I'll join the IRC channel to
work with you (and others) together to make the translation
better.

Thanks

  reply	other threads:[~2012-05-02  9:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  2:45 Please pull git-po master branch Jiang Xin
2012-05-02  5:17 ` Junio C Hamano
2012-05-02  7:54 ` Thomas Rast
2012-05-02  9:13   ` Ralf Thielow [this message]
2012-05-02 13:58     ` Thomas Rast
2012-05-02 19:14       ` Ralf Thielow
2012-05-02 19:44         ` Christian Stimming
2012-05-02 13:49   ` [PATCH 0/5] de.po suggested updates Thomas Rast
2012-05-02 13:49     ` [PATCH 1/5] stash: make "saved" message translatable Thomas Rast
2012-05-02 16:42       ` Junio C Hamano
2012-05-02 13:49     ` [PATCH de.po 2/5] de.po: translate "bare" as "bloß" Thomas Rast
2012-05-02 13:49     ` [PATCH de.po 3/5] de.po: hopefully uncontroversial fixes Thomas Rast
2012-05-02 13:49     ` [PATCH de.po 4/5] de.po: translate "bad" as "ungültig" ("invalid") Thomas Rast
2012-05-02 13:49     ` [PATCH de.po 5/5] de.po: collection of suggestions Thomas Rast
2012-05-02 18:36       ` Ralf Thielow
2012-05-02 19:43         ` Thomas Rast
2012-05-02 19:42       ` Christian Stimming
2012-05-03  7:42         ` Thomas Rast
2012-05-03 13:12           ` [PATCH on ab/i18n] branch: remove lego in i18n tracking info strings Nguyễn Thái Ngọc Duy
2012-05-04 16:10             ` Junio C Hamano
2012-05-06 13:06               ` Nguyen Thai Ngoc Duy
2012-05-02 17:52     ` [PATCH 0/5] de.po suggested updates Ralf Thielow
2012-05-02 19:13     ` Christian Stimming
2012-05-02 16:40   ` Please pull git-po master branch Junio C Hamano
2012-05-03  4:31     ` Jiang Xin
2012-05-03  6:47       ` Junio C Hamano
2012-05-03 10:19         ` Jiang Xin
2012-05-03  7:49       ` Thomas Rast

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=CAN0XMOJ0PBA2qptw2Lm9HOq4SAkeZNAyOwPdvcb-uAcsxKnzwg@mail.gmail.com \
    --to=ralf.thielow@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jk@jk.gs \
    --cc=trast@student.ethz.ch \
    --cc=worldhello.net@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.