All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Rast <trast@inf.ethz.ch>
To: Ralf Thielow <ralf.thielow@gmail.com>
Cc: "Jens Lehmann" <Jens.Lehmann@web.de>,
	"Holger Hellmuth (IKS)" <hellmuth@ira.uka.de>,
	"Jan Engelhardt" <jengelh@inai.de>,
	"Ralph Haußmann" <ralph@scanmyfood.de>,
	"Christian Stimming" <stimming@tuhh.de>,
	"Sven Fuchs" <svenfuchs@artweb-design.de>,
	git <git@vger.kernel.org>, "Jan Krüger" <jk@jk.gs>
Subject: Re: English/German terminology, git.git's de.po, and pro-git
Date: Thu, 16 May 2013 11:00:28 +0200	[thread overview]
Message-ID: <87wqqze1ub.fsf@linux-k42r.v.cablecom.net> (raw)
In-Reply-To: <CAN0XMOJ7hRwTAR+i8_C2z2NmmcycLQkiya0ayfWS0vAw3-zqkg@mail.gmail.com> (Ralf Thielow's message of "Thu, 16 May 2013 07:57:11 +0200")

Ralf Thielow <ralf.thielow@gmail.com> writes:

> Hi,
>
> I think the discussion might work better via ML than GitHub.
> This is the full glossary of git's de.po as it would look
> like with (hopefully) all the changes included that have been
> discussed here. Still without any reasoning for decisions
> (except HEAD).
[...]
> +    remote branch          = externer Zweig
> +    remote tracking branch = externer Übernahmezweig

Hrm, before we (erm, you) do any extensive work on redoing the glossary,
I think we should step back and agree on a direction.

Remember what this thread started with:

} However, an unfortunate and unsatisfactory situation has developed:
} Christian Stimming's git-gui de.po uses a Ger translation, and Ralf
} Thielow built core git's de.po on top of it, so it's also Ger.
} 
} Meanwhile, and independently, Sven Fuchs and Ralph Haussmann wrote a
} translation of pro-git (which is also quite mature at this point, having
} apparently begun in 2009), and as you probably guessed by now, it's G+E.
} 
} So that leaves us at a point where "the" libre Git book (and also the
} one that happens to be hosted on git-scm.com, the official site) does
} not match the terminology used by German git.
} 
} Like, at all.  They're not even remotely near each other.

My thinly veiled opinion in the thread starter was that we should redo
git's de.po from scratch using a translation similar to pro-git.

I can accept that discussion takes a different turn, and thus the
translation does something else.  But my impression in the thread so far
was that:

* Everyone voted for G+E.

* The thread went of on a tangent, bikeshedding on some Ger
  translations.

Please tell me I'm wrong...

Otherwise, assuming any agreement can be reached, IMHO the first step
must be to write/complete a glossary that matches *current usage* in
pro-git.  We can perhaps bikeshed about some glaring issues in the
result, but remember that -- again assuming G+E is the conclusion -- any
such change again either means a divergence between book and git (bad!)
or a lot of work for the book translators.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  parent reply	other threads:[~2013-05-16  9:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13 12:54 English/German terminology, git.git's de.po, and pro-git Thomas Rast
2013-05-13 13:57 ` Jan Engelhardt
2013-05-13 17:19   ` Jens Lehmann
2013-05-13 18:57   ` AW: " Ralph Haußmann
2013-05-13 19:25     ` Jan Engelhardt
2013-05-14 17:51       ` Ralf Thielow
2013-05-15 10:23         ` Holger Hellmuth (IKS)
2013-05-15 11:26           ` Jens Lehmann
2013-05-15 11:56             ` Jan Engelhardt
2013-05-15 12:27               ` Jens Lehmann
2013-05-15 13:14                 ` Jan Engelhardt
2013-05-15 15:31                   ` Holger Hellmuth (IKS)
2013-05-15 17:28                     ` Jan Engelhardt
2013-05-16  5:57             ` Ralf Thielow
2013-05-16  8:48               ` Holger Hellmuth (IKS)
2013-05-19 16:06                 ` Ralf Thielow
2013-05-19 16:56                 ` Ralf Thielow
2013-05-20  4:01                   ` Holger Hellmuth
2013-05-22 14:09                     ` Ralf Thielow
2013-05-16  9:00               ` Thomas Rast [this message]
2013-05-19 16:49                 ` Ralf Thielow
2013-05-19 16:53               ` Ralf Thielow
2013-05-20 19:41                 ` Christian Stimming
2013-05-22 15:16                   ` Ralf Thielow
2013-05-22 15:52                     ` Holger Hellmuth (IKS)
2013-05-22 16:43                       ` Jan Engelhardt
2013-05-23 18:16                     ` Bernhard R. Link
2013-05-24 16:41                       ` Ralf Thielow
2013-06-16 21:22                       ` Jan Engelhardt
2013-05-24 16:51                 ` Ralf Thielow
2013-05-13 16:30 ` Ralf Thielow
2013-05-16 10:49 ` Christian Stimming

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=87wqqze1ub.fsf@linux-k42r.v.cablecom.net \
    --to=trast@inf.ethz.ch \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=hellmuth@ira.uka.de \
    --cc=jengelh@inai.de \
    --cc=jk@jk.gs \
    --cc=ralf.thielow@gmail.com \
    --cc=ralph@scanmyfood.de \
    --cc=stimming@tuhh.de \
    --cc=svenfuchs@artweb-design.de \
    /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.