Re: german translation bug

From: Thomas Rast <tr@thomasrast.ch>
Date: Dec 28, 2013, 13:08 UTC
Message-ID: <87txdtazsn.fsf@linux-1gf2.Speedport_W723_V_Typ_A_1_00_098>
In-Reply-To: <20131226165815.GR20443@google.com>

Jonathan Nieder <jrnieder@gmail.com> writes:

Show 19 quoted lines

> Hi,
>
> Wolfgang Rohdewald wrote:
>> Am Mittwoch, 25. Dezember 2013, 22:53:29 schrieb Wolfgang Rohdewald:
>
>>> I suppose I should open a KDE bug report?
>>
>> I meant a ubuntu bug report of course.
>
> Yes, please.  Feel free to cc me if doing so.
>
> In generally, I'm a bit uncomfortable lately at how Ubuntu's
> translation system works for Git.  They are trying to solve a real
> problem: old Ubuntu releases stick to old versions of git that do not
> have as complete translations as the latest version.  But their
> solution to this problem does not seem to work well and creates a lot
> of confusion.  Worse, it creates duplicated effort, as their custom
> translations don't seem to have been submitted upstream for review or
> inclusion.

Even worse, the German one under discussion uses an entirely different vocabulary to describe git concepts:

  ubuntu (from OP):
    wr@s5:~/src/linux$ git status
    # Auf Zweig drm-intel-testing
    Nichts zum Einreichen, Arbeitsverzeichnis leer

  de.po current:
    msgid "nothing to commit, working directory clean\n"
    msgstr "nichts zu committen, Arbeitsverzeichnis unverändert\n"

  de.po before the big vocabulary change:
     msgid "nothing to commit, working directory clean\n"
     msgstr "nichts einzutragen, Arbeitsverzeichnis sauber\n"

So their word for "commit (v.)" is "einreichen", whereas we had "committen" and before that "eintragen". As if there weren't enough confusion around German terminology yet.

(FWIW I also think it's a terrible choice because it suggests a transaction between multiple people, which to me sounds like it should mean "push".)

-- 
Thomas Rast
tr@thomasrast.ch