git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: English/German terminology, git.git's de.po, and pro-git

From
Thomas Rast <trast@inf.ethz.ch>
Date
May 16, 2013, 09:00 UTC
Message-ID
<87wqqze1ub.fsf@linux-k42r.v.cablecom.net>
In-Reply-To
<CAN0XMOJ7hRwTAR+i8_C2z2NmmcycLQkiya0ayfWS0vAw3-zqkg@mail.gmail.com>
Ralf Thielow <ralf.thielow@gmail.com> writes:
Show 7 quoted lines
> 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
Previous: Ralf ThielowNext: Ralf Thielow
Message 20 of 32 in “English/German terminology, git.git's de.po, and pro-git”
  1. Thomas RastMay 13, 2013
  2. Jan EngelhardtMay 13, 2013
  3. Jens LehmannMay 13, 2013
  4. AW: English/German terminology, git.git's de.po, and pro-gitRalph Haußmann, May 13, 2013
  5. Jan EngelhardtMay 13, 2013
  6. Ralf ThielowMay 14, 2013
  7. Holger Hellmuth (IKS)May 15, 2013
  8. Jens LehmannMay 15, 2013
  9. Jan EngelhardtMay 15, 2013
  10. Jens LehmannMay 15, 2013
  11. Jan EngelhardtMay 15, 2013
  12. Holger Hellmuth (IKS)May 15, 2013
  13. Jan EngelhardtMay 15, 2013
  14. Ralf ThielowMay 16, 2013
  15. Holger Hellmuth (IKS)May 16, 2013
  16. Ralf ThielowMay 19, 2013
  17. Ralf ThielowMay 19, 2013
  18. Holger HellmuthMay 20, 2013
  19. Ralf ThielowMay 22, 2013
  20. Thomas RastMay 16, 2013
  21. Ralf ThielowMay 19, 2013
  22. Ralf ThielowMay 19, 2013
  23. Christian StimmingMay 20, 2013
  24. Ralf ThielowMay 22, 2013
  25. Holger Hellmuth (IKS)May 22, 2013
  26. Jan EngelhardtMay 22, 2013
  27. Bernhard R. LinkMay 23, 2013
  28. Ralf ThielowMay 24, 2013
  29. Jan EngelhardtJun 16, 2013
  30. Ralf ThielowMay 24, 2013
  31. Ralf ThielowMay 13, 2013
  32. Christian StimmingMay 16, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.